G
google.100.frause
Previously I had the same Problem discussed and solved here:
http://clariusconsulting.net/blogs/hdl/archive/2005/12/02/410.aspx?CommentPosted=true#commentmessage
but now I've got the next problem. "application failed to initialize
properly (0xc0000142). Click OK to terminate the application.".
I'm running a service, trying to create a process, redirecting the
output and I enabled the Event Raising.
The Process already exists in correct security context - visible in the
Task Manager at the time the MessageBox appears. This is not an
exception in my code. the called application raises this box even when
I call it without user interaction. It does not matter what Applicaiton
I call. I tested "cscript.exe" "wscript.exe" "cmd.exe" "calc.exe" etc.
And yes everybody is fully equiped with all rights in file system and
with all local policies, additionally everybody is local administrator.
The really weird thing is when I specify the "sub" process to start in
the same account as the creator. It works fine the first time but never
again. When the accounts differ even the first try will fail.
When I make the same call to run in the same account as the creator -
"username" and "password" not specified - all works fine. Everything
works fine when it runs as normal process it will only fail when I run
the Process creator as service.
Any suggestions??
http://clariusconsulting.net/blogs/hdl/archive/2005/12/02/410.aspx?CommentPosted=true#commentmessage
but now I've got the next problem. "application failed to initialize
properly (0xc0000142). Click OK to terminate the application.".
I'm running a service, trying to create a process, redirecting the
output and I enabled the Event Raising.
The Process already exists in correct security context - visible in the
Task Manager at the time the MessageBox appears. This is not an
exception in my code. the called application raises this box even when
I call it without user interaction. It does not matter what Applicaiton
I call. I tested "cscript.exe" "wscript.exe" "cmd.exe" "calc.exe" etc.
And yes everybody is fully equiped with all rights in file system and
with all local policies, additionally everybody is local administrator.
The really weird thing is when I specify the "sub" process to start in
the same account as the creator. It works fine the first time but never
again. When the accounts differ even the first try will fail.
When I make the same call to run in the same account as the creator -
"username" and "password" not specified - all works fine. Everything
works fine when it runs as normal process it will only fail when I run
the Process creator as service.
Any suggestions??