Windows 10: Fatal communication error with the Windows Process Activation Service in Windows 2016

Hello Team,


We have hosted our websites in the Windows server 2016 and we faced an issue with an application where the application is stopped to respond with the following message.

Event Error log:"A process serving application pool 'PROD-Site' suffered a fatal communication error with the Windows Process Activation Service. The process id was '6408'. The data field contains the error number.“


In the below article, it was mentioned that it may occur due to any of the following reasons.
Ping failure.

Communication failure with WAS.

Worker process startup time-out.

Worker process shutdown time-out.

Worker process orphan action failure.

Ref: https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc735271v=ws.10?redirectedfrom=MSDN


But the article was applied to Windows Server 2008. We are having Windows Server 2016. Could you kindly help us to understand why are we getting the error?

Thanks,

Sathya M.

:)

 

Fatal Error

I've been trying to format my system but right after it finishes formatting I get a Fatal Error during the Windows installation process. That Fatal Error is a Data Error (cyclic redundancy check). I know that it's because of my hard drives, but how do I fix this issue? I have 2 Seagate Barracuda 7200.10 250GB SATA II Hard Drives in RAID 0. Any help and suggestions would be greatly appreciated. *Smile

 

Fatal Error

Well, I just got a Fatal Error during the Windows installation process with the first hard drive. So I removed it and now formatting the second hard drive. I will post up the results when it's done.

 

[SOLVED] Error 193: 0xc1 .NET Windows Service

Symptom:
When you install a .NET Windows Service, it says there was no error. Yet, when you go to start the service, you get an "Error 193: 0xc1" message and subsequently, the process refuses to start.

Cause:
The binary you installed as a service is not a "Windows Application."

Solution:
Uninstall the old service, change the project output type to "Windows Application" and build it, install the new binary (should be *.exe), and start the service again.


This is just one example of what can cause the error message.