• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 3745
  • Last Modified:

Exchange 2013 - Event ID 4999 MS Exchange Common - Watson report about to be sent for process id

Hi,

We have a single Exchange 2013 server and are getting this error many times in a day.  I haven't been able to find a solution and was wondering if anyone came across this error or have any suggestions.

Edition             : Standard
AdminDisplayVersion : Version 15.0 (Build 913.22)

Log Name:      Application
Source:        MSExchange Common
Date:          10/16/2014 9:15:46 AM
Event ID:      4999
Task Category: General
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      exchangeserver.name
Description:
Watson report about to be sent for process id: 3952, with parameters: E12IIS, c-RTL-AMD64, 15.00.0913.022, M.Exchange.Imap4, M.Exchange.Net, M.E.N.NetworkConnection.BeginNegotiateTlsAsClient, System.InvalidOperationException, 99a4, 15.00.0913.007.
ErrorReportingEnabled: True
0
wepz
Asked:
wepz
  • 3
  • 2
1 Solution
 
Simon Butler (Sembee)ConsultantCommented:
Have you got IMAP4 enabled?

Simon.
0
 
wepzAuthor Commented:
Yes the client uses IMAP4
0
 
Simon Butler (Sembee)ConsultantCommented:
IMAP4 is where the error is coming from.
Could be a corrupt message in a mailbox, I have seen similar before. You would need to see whether an IMAP user is having problems getting their email.

Simon.
0
 
wepzAuthor Commented:
Thanks Simon,

Is there a way to isolate this?
0
 
Simon Butler (Sembee)ConsultantCommented:
Not easily.
There might be something in the IMAP logs, if you have that enabled.
Could be something in the Application logs.

I don't do much with IMAP myself.

Ensure that any AV on the server has the correct exclusions set as well.

Simon.
0

Featured Post

Get your Disaster Recovery as a Service basics

Disaster Recovery as a Service is one go-to solution that revolutionizes DR planning. Implementing DRaaS could be an efficient process, easily accessible to non-DR experts. Learn about monitoring, testing, executing failovers and failbacks to ensure a "healthy" DR environment.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now