I am running Loggernet as a service which calls a number of monitoring sites every day. I then have a batch file run in Task Master that splits off the data by site from the master file. This worked for several days in a row, and then it just stops splitting off the data. When I look in Task Master it says the batch file ran. And if I click on the batch file to run it directly it will open up Split and run just fine.
From looking at the Split logs, I can see that the computer thinks a version of Split is already open, because it keeps adding extra lines to the splitrunning log whenever Task Master runs. However I can not see the instance of Split that is running in Windows Task Manager because it is running on the LoggerNet account.
How can I kill that instance of Split? Do I have to login to the computer as LoggerNet? Turn off the computer? (this is made more complicated by the fact that I am remoting into this computer from another physical location). Is there a way to avoid Split hanging up like this in the future?
Look in the Split help file index, under Command Line Parameters.
Split has a /R option that will close the executable after it *successfully* runs.
Dana W.
Thanks, I already had the /R in my program, so it must have not "successfully" run at some point, and then got hung up. I've since changed my program to /Q which I think closes the program even if it fails. That seems to be doing the trick.
Hello emress, Would you be willing to share that batch file?