Hi.
Facts:* This is a new install.
* Windows 2008 R2 SP1.
* Security policies (specifically user rights) have been restricted as part of security posture
* Using a domain user account for credentials to launch the process.
Situation:I have a batch file that does nothing but echo some text to stdout. When I execute it as a background process it fails. Job log shows:
exit code of 77777
Output = No output
Output (stderr) = Exception in Task: Non zero exit code
When I execute the job in the foreground it seems to work just fine.
exit code = 0
Output = Completed successfully
Output (stderr) = No Output
Could this be a product of the User Rights changes? (things like Act as part of the operating system, logon as batch job, etc..) If so, do you have documentation that describes what rights should be granted?
In background mode when the job seems to fail, I can see in the Security event log that the process performs a Logon, a Special Logon, several processes are created (including the cmd.exe that should process my batch file) and the logoff occurrs- all without errors.
I also note that if I change the batch file to execute something else, like notepad.exe, that the process does not seem to get started or appear as a running task.
Any suggestions would be helpful. I am demoing the product and would love to license it but need to get it working first.
Thanks