Rick,

We have a new situation happening that is causing trouble. When we update our WWWC app we do an iisreset /stop, delete the wwwc exe , rename a new.exe to live.exe then iisreset /start. It has worked just fine for a long time. Recently, we need to reboot to get IIS to start.

In the event viewer we have this "The server {63F92764-4890-4846-A7AB-4C005375B6AE} did not register with DCOM within the required timeout." along with "A process serving application pool 'apppoolname' terminated unexpectedly. The process id was '856'. The process exit code was '0xc0000409'." -

These errors are happening when the iisreset /start runs.

Any thoughts?

Sounds like your COM server is crashing or hanging during startup perhaps due to permissions or other related settings.

Recent blog post covered a lot of what you can do to track down startup errors:

• Startup Error Tracing in Web Connection

Common cause during server startup (ie. after a reboot) is that Windows has not fully loaded all the COM subsystem components required to run DCOM services. So when servers are requested they can't load. This used to be a problem I saw, but it seems to have been fixed since my recent move to Server 2016. This should only be a problem during startup - that doesn't account for application pool or Web site restarts.

+++ Rick ---

Do you think that this may be as a result of some recent Windows OS updates? Pretty weird that it would just start happening for no good reason.

I'll review your blog post and see if I can figure something out.

Thanks!