Because the process can be seen in the task list the job started successfully and the process was also started successfully using another user credentials. However, you might be still out of luck if your process attempts to access certain network resources that cannot be accessed from a service the same way they are accessed from a regular application. Check you process uses only UNC file names ( like "\\server\share\dir\file")for network files and doesn't refer to network files using drive mapping. If you process writes to log files search in those logs for error messages. If you start a graphical program make sure it doesn't display any message boxes or dialogs. Do not attempt to send keystrokes when starting it from a service. : I have a job set up to run an executable as the current user and it works
: fine. The problem with this is that if someone accidentally closes the
: 24x7 program from the systray, the job stops running. So, I set it up to
: run as a particular user and then set 24x7 to run as a service. This way,
: there doesn't even have to be a user logged on to the server. However,
: when the job runs like this, it doesn't work the way it is supposed to. I
: checked the process table and I see the program running, but nothing is
: happening. : The documentation says the user specified to run the program as must have
: "Log on as Batch User" rights and I checked this and found this
: to be true of my user. Now I am stumped. : Any suggestions?
|
