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.
|Source: MSExchange Availability|
Process 6052[w3wp.exe:/LM/W3SVC/1/ROOT/EWS-1-128999185984805259]: Microsoft.Exchange.InfoWorker.Common.Availability.PublicFolderRequest failed. The exception returned is Microsoft.Exchange.InfoWorker.Common.Availability.PublicFolderRequestProcessingException: The remote name could not be resolved: ''remoteserverdqdn''. The request information is http://remoteserverfqdn/public/Cmd=freebusy&start=2009-10-13T23:00:00Z&end=2009-11-11T00:00:00Zemail@example.com.. The Availability service could not successfully retrieve Schedule+ free/busy data for one or more legacy Exchange mailboxes. To find the root cause of this error increase the diagnostic logging level of the MSExchange Availability service.
|English: Request a translation of the event description in plain English.|
We've got this event migrating from Exchange 2003 to Exchange 2010 (on the Exchange 2010 server). Update Pack 4 for Exchange 2010 didn't fixed the problem. Users on 2010 couldn't see free & busy from users on 2003. I found the solution at EV100311 (Free/Busy Not Working Exchange 2007).
If you migrated users from an Exchange 2003 server, chances might be good that you did not migrate over the Free/Busy public folder information correctly. To check open the Exchange Management Shell (EMS) as administrator and run the following command:
Get-PublicFolder -server CASSERVER "\non_ipm_subtree\SCHEDULE+ FREE BUSY" -recurse | Format-List
You will see a bunch of information, but what you are looking for is two Public folder groups:
\NON_IPM_SUBTREE\SCHEDULE+ FREE BUSY\EX:/o=Company/ou=First Administrative Group - AND
\NON_IPM_SUBTREE\SCHEDULE+ FREE BUSY\EX:/o=Company/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)
In my case, we were missing the First Administrative Group. To add it I ran the following from EMS:
Set-PublicFolder –Identity "\NON_IPM_SUBTREE\SCHEDULE+ FREE BUSY\EX:/o=Company/ou=First Administrative Group" –Replicas "CASSERVER\Public Folder Database"
This error is typical if there are network connection issues between the Availability Service and the remote 2003 server that hosts the public folder based free/busy folder that the firstname.lastname@example.org is hosted on.
The content should look like this:
- <a:response xmlns:a="WM">
Check the firewalls and the network connectivity to that server.
|Private comment: Subscribers only. See example of private comment|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
|Custom search for *****: Google - Bing - Microsoft - Yahoo|
Send comments or solutions
- Notify me when updated