We just migrated the last of our mailboxes from our exchange 2007 server to our exchange 2010 server, the exchange 2007 server is now completely decommissioned and offline.
We are running server 2008 and exchange 2010 sp1.
Multiple times every week we receive the following error on our exchange 2010 server.
Watson report about to be sent to dw20.exe
TIME OF EVENT: 2/17/2012 6:08:42 PM
EVENT LOG: Application
EVENT SOURCE: MSExchange Common
EVENT ID: 4999
DESCRIPTION: Watson report about to be sent for process id: 3012, with parameters: E12, c-RTL-AMD64, 14.01.0218.015, M.E.RpcClientAccess.Service, M.E.RpcClientAccess.Handler, M.E.R.H.RopHandler.Logon, System.InvalidOperationException, 41bd, 14.01.0218.012.
I have been researching this, but haven't found much in the way of a clear explanation as to what it is.
Bar the error in the event log, I don't see it actually having a negative effect.
Any help or advice is welcome!
Thank you in advance.
Some of these were resolved in the RU up to SP2. I'd put on SP2 RU2. Also, these events from what I have seen dont have any user impact.
just to keep this alive for anyone having the same issue.
I logged a support call with microsoft about a month ago for this, they have yet to resolve the error.
I can tell you it is the process w3wp.exe (MSExchangeECPAppPool) crashing intermittently that is causing the error, but no reason as to why yet.
Will keep updating as Microsoft continue to work on the problem.
On a side note, this doesn't seem to be actually having any kind of impact that we are aware of.
ok so the latest is, it looks as if SCOM was causing the error.
We put SCOM monitoring for the exchange server into maintenance mode and we didnt get the error for a week (it ususally come sin once or twice a day). Reenabled the monitoring and the error came in again.
Looking deeper it seems to be the ECP monitoring in particular causing the problem.
The exchange guys in microsoft want to increase the interval of scanning, but the SCOM guys say this is not possible, so we have disabled the ECP monitoring for the moment to see if the error comes in again.
Hopefully this helps somebody out.
I'll update again next week when I have monitored the server.
- Edited by OwenJKirwan Wednesday, August 01, 2012 8:35 AM