Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>The LocalSystem account should have sufficient rights to read and execute any program on the local system (unless you have gone to specific trouble to deny it access to something). Given that, I'm guessing that maybe the program you're executing resides on some other computer. The reason this would cause a failure is because LocalSystem has no network identity and in general can't access remote shares. Can you check that the program definitely resides on a local drive, versus a network share (which could be masked by a mapped drive)?</p> <p>If that isn't the problem, I would try using <a href="http://technet.microsoft.com/en-us/sysinternals/bb896645.aspx" rel="nofollow">ProcMon</a> to debug the problem. This will display all file and registry activity on your system, including successful accesses and failures. If you run this and then reproduce the problem, I expect you will see an entry with a result of ACCESS DENIED, and that should point you toward the cause. You can use the filtering function to restrict the output to your service process and the process you are spawning. If you're running on Vista/2008 or later, you will need to run ProcMon with elevated rights.</p> <p>You could also check the Windows event log, particularly the Security log. You may need to <a href="http://support.microsoft.com/kb/310399" rel="nofollow">enable audit logging</a> if it's not already enabled; I would enable "Audit object access", "Audit logon events", "Audit account logon events", and "Audit privilege use", including successes and failures. In my experience these changes can take a little while to become effective, so if you don't start seeing logs, you might reboot the test system. Once the logging is working, retry the CreateProcessWithLogon and see what events appear. You could also compare the series of events generated when things work with the series of events when things don't work, and that might help show what's wrong.</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload