[英]A process serving application pool 'xxx' suffered a fatal communication error with the Windows Process Activation Service
After a software update the application pool was stopped two times after receiving several errors of this type: A process serving application pool 'xxx' suffered a fatal communication error with the Windows Process Activation Service. 软件更新后,应用程序池在收到此类错误后停止了两次:为应用程序池“xxx”提供服务的进程与Windows进程激活服务发生致命的通信错误。 The process id was 'yyy'.
进程ID是'yyy'。 The data field contains the error number.
数据字段包含错误编号。
Event ID: 5011 Error code: 0x6D000780 事件ID:5011错误代码:0x6D000780
Software changes respect to last version was small and can't explain this problem (just a new field in a stored procedure) but I can't restore the old version to check if this have the problem. 关于最新版本的软件更改很小,无法解释此问题(只是存储过程中的新字段)但我无法恢复旧版本以检查是否存在问题。
I have the same software (the same version) con three servers, one have this issue, the other two no. 我有相同的软件(相同的版本)con三个服务器,一个有这个问题,另外两个没有。
After receiving this error several times in each hour this night I tried to restart completely IIS and I didn't receive any error for 5 hours (the application was working also if night time) 在今晚每小时多次收到此错误后,我尝试完全重启IIS并且我没有收到任何错误5小时(如果夜间应用程序也正常工作)
The problem appeared again 1 hour after the scheduled recycle time and didn't happen again in the last 4 hours (but I can't consider this problem solved). 问题在预定的回收时间后1小时再次出现,并且在最近4小时内没有再次发生(但我不能认为这个问题已经解决了)。
What I can do to find the real problem? 我能做些什么才能找到真正的问题? It's a 100% software problems also if the two nodes are working?
如果这两个节点正在工作,那么这也是100%的软件问题?
I can increase the "failure interval (minutes)" but this doesn't solve my problem: the software has data in memory and if crash without writing it is a disaster. 我可以增加“故障间隔(分钟)”,但这并不能解决我的问题:软件在内存中有数据,如果崩溃而不写它就是一场灾难。
I'm using Windows Server 2012 R2 and IIS 8. 我正在使用Windows Server 2012 R2和IIS 8。
I answer to myself, maybe this could be useful for others in the future. 我回答自己,也许这对将来的其他人有用。
I believe that in this cause the problem is always a software issue and that the answer can almost always be found in Windows Logs / Application. 我相信在这个原因中,问题始终是一个软件问题,并且几乎总能在Windows日志/应用程序中找到答案。
声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.