Build a great reporting interface using Splunk, one of the leaders in the Security Information and Event Management (SIEM) field, linking the collected Windows events to www.eventid.net. The EventId.Net for Splunk Add-on assumes that Splunk is collecting information from Windows servers and workstation via the Splunk Universal Forwarder.
Request from user UserA@domain.com resulted in the Microsoft(R) Exchange back-end server <ServerName> returning an HTTP error with status code 403:Forbidden.
|English: Request a translation of the event description in plain English.|
In our case, we were getting EventID 1776 from source Davex and EventID 1805 from source MSExchangeOMA. We were unable to activesync and browse OMA directory. We successfully ran the command “regsvr32 msxml3.dll”, and we were able to activesync.
I had this issue and I needed to recreate the virtual directories. See ME883380 for details.
As per Microsoft: "This event indicates that the request made by the Outlook Mobile Access browse user was not successful because the back-end Exchange server returned an HTTP error code". See MSEX2KDB for additional information about this event.
This problem can occur if you have reached the storage limit for your mailbox. See ME842023 for details.
See ME817379 and ME822177 to see why this occurs and how to fix it.
|Private comment: Subscribers only. See example of private comment|
|Links: ME817379, ME822177, ME842023, ME883380, EventID 1776 from source DAVEX, MSEX2KDB|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
Send comments or solutions
- Notify me when updated