We have an Exchange 2013 organization with two Mailbox servers running on Windows Server 2012 Datacenter in Hyper-V virtual machines. Every so often the following error appears in the Application log on those servers (not simultaneously):
Source: Application error
Event ID: 1000
Message:
Faulting application name: w3wp.exe, version: 8.0.9200.16384, time stamp: 0x50108835
Faulting module name: wsmsvc.dll, version: 6.2.9200.16384, time stamp: 0x50108617
Exception code: 0xc0000005
Fault offset: 0x000000000009859a
Faulting process id: 0x4818
Faulting application start time: 0x01cf499932647338
Faulting application path: c:\windows\system32\inetsrv\w3wp.exe
Faulting module path: C:\Windows\system32\wsmsvc.dll
Report Id: 4bbb281d-b8c2-11e3-9425-00155d854004
Faulting package full name:
Faulting package-relative application ID:
In turn, it triggers an alert in the Operation Manager console similar to the following one:
A process serving application pool 'MSExchangePowerShellAppPool' suffered a
fatal communication error with the Windows Process Activation Service. The
process id was '18456'. The data field contains the error number.
The pool mentioned in the message can be any backend Exchange pool.
In fact, we have these errors since the servers were first deployed about an year ago. They appeared on, consequently, Exchange 2013 RTM, CU1, CU2, SP1. They temporarely disappeared after installing CU2, however, they appeared again in a couple of months.
It seems that these IIS aplication pool faults don't affect anything. At least, I can't see that something goes wrong due to them. Therefore, these error messages are just annoying.
Is it possible to prevent the IIS pools from crashing? Or should I just disable the SCOM monitor and forget about it?
