We have a program that launches a lot of small processes (50-100 at a time). These processes make WMI calls (lots of them), to systems across multiple forests. The service logs in as a privileged user, so access is not a problem. When we run the program from a cmd prompt, it operates as expected. When we run it as a service, it fails. The individual spawned processes almost (but not quite) all fail with error code 128. If we reboot the machine, the service runs properly for 16-30 hours, and then starts failing in exactly the same way. Restarting just the service does not help, to correct this, the entire machine must be restarted to recover. If we crank the scale of the program back so that it only launches 3-4 processes, it runs as expected. There is nothing untoward in the event logs on failure. We see this error on a Windows 2003 R2 64-bit system with 16 cores, 32 GB ram. Anyone have advice as to where to look?

Hi, According to the description, it seems that you have a own developed application. If so, the issue seems to be related to coding development. As we mainly focus on the General question about Windows Server system and here is not the best support resource for coding development, it is recommend you to get further support in the corresponding community so that you can get the most qualified pool of respondents. Thanks for your understanding. For your convenience, I have list the related link as followed. MSDN Forums http://social.msdn.microsoft.com/Forums/en/categories Best Regards, Vincent Hu