MSExchange Web Services Errors
I've been receiving errors - event ID's 5,6,7 from MSExchange Web Services Core on one of my CAS-HT servers that is load balanced using WNLB. I've set diagnostic logging to expert, but don't receive any further information in the event log. I found the information below but it hasn't helped me find what is causing the problem. I've also viewed IIS logs and found nothing that points to the cause of the problem. The events move to my other CAS-HT server if i reboot the server currently receiving the errors and vice versa. Can someone help me? See this post on th Exchange technet forum: http://social.technet.microsoft.com/Forums/en-US/exchangesvrgeneral/thread/ec50b24c-0073-4dee-b698-764bff0841e7 The event 5, 6, and 7 are basically event that telling us that a device/client is subscribing a server event, but when the server when to notify the client/device, the client is not there to respond to it, so the server threw and error and close the subscription.
March 10th, 2010 8:32pm

Hi,As you have gone thru above said URL you can see event id 5,6,7 is not a bif error and can be ignored. Do you have a custom or third-party application using SOAP to access your Exchange server? It looks like someone is trying to attach a rogue mobile device to your Exchange server using Jakarta protocol.You can enable diagnostic logging on EAS in exchange (If enable active synch) to fix this issue.Anil
Free Windows Admin Tool Kit Click here and download it now
March 10th, 2010 8:50pm

Diagnostic logging won't get you anything here - you'd need to get PSS to look at tracing data.That said, you likely can ignore this unless you've got a tangible problem to investigate.Active Directory, 4th Edition - www.briandesmond.com/ad4/
March 11th, 2010 6:01am

I was hoping to avoid calling PSS. It doesn't seem to be causing a problem, i just have a thing about the event logs being clean. Any help on tracing the data would be greatly appreciated.
Free Windows Admin Tool Kit Click here and download it now
March 11th, 2010 7:59pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics