By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
459,212 Members | 1,314 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 459,212 IT Pros & Developers. It's quick & easy.

System.Diagnostics.Process - "Applicaton failed to initialize properly (0xc0000142)."

P: n/a
Previously I had the same Problem discussed and solved here:
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??

Mar 14 '06 #1
Share this Question
Share on Google+
3 Replies

P: n/a
Ohh by the way, this is in .Net 2.0 running on WinXP SP2 and the same
on W2K3 SP1

Mar 14 '06 #2

P: n/a
Ohh and Output redirecting and event raising doesn't matter.
It works fine when the server runs as executable. It fails when it's
running as service equal what account is used.

Mar 15 '06 #3

P: n/a
Posted via
Sep 18 '06 #4

This discussion thread is closed

Replies have been disabled for this discussion.