ddllc
asked on
Exchange 2007 - Free/busy issue
I'm having issues with free/busy information not displaying for a particular user. We're running Exchange 2007 SP1 (8.1.240.6) in a 2008 R2 domain. We have two Exchange servers and we're seeing the error in the event log on one server. Both servers have Mailbox, CAS, and Hub Transport roles installed.
Here's the event log from the requesting server:
Process 7820[w3wp.exe:/LM/W3SVC/1/ ROOT/EWS-1 -129895137 820575880] : Proxy request CrossSite from Requester:S-1-5-21-3771264 439-232845 084-685686 092-6251 to https://<servername>/EWS/Exchange. asmx failed. Caller SIDs: S-1-5-21-3771264439-232845 084-685686 092-6251. The exception returned is Microsoft.Exchange.InfoWor ker.Common .Availabil ity.ProxyW ebRequestP rocessingE xception: System.InvalidOperationExc eption: There is an error in XML document (1, 3445). ---> System.ArgumentOutOfRangeE xception: Value specified for a parameter of type Microsoft.Exchange.Data.St orage.Days OfWeek is invalid.
Parameter name: daysOfWeek
at Microsoft.Exchange.Data.En umValidato r.ThrowIfI nvalid[ENU M_TYPE](EN UM_TYPE valueToCheck, String paramName)
at Microsoft.Exchange.Data.St orage.Stor ageWorking Hours.Upda teWorkingP eriod(Days OfWeek daysOfWeek, Int32 startTimeInMinutes, Int32 endTimeInMinutes)
at Microsoft.Exchange.InfoWor ker.Common .Availabil ity.Workin gHours.set _WorkingPe riodArray( WorkingPer iod[] value)
at Microsoft.Xml.Serializatio n.Generate dAssembly. XmlSeriali zationRead erService. Read23_Wor kingHours( Boolean isNullable, Boolean checkType)
at Microsoft.Xml.Serializatio n.Generate dAssembly. XmlSeriali zationRead erService. Read24_Fre eBusyView( Boolean isNullable, Boolean checkType)
at Microsoft.Xml.Serializatio n.Generate dAssembly. XmlSeriali zationRead erService. Read25_Fre eBusyRespo nse(Boolea n isNullable, Boolean checkType)
at Microsoft.Xml.Serializatio n.Generate dAssembly. XmlSeriali zationRead erService. Read34_Get UserAvaila bilityResp onse(Boole an isNullable, Boolean checkType)
at Microsoft.Xml.Serializatio n.Generate dAssembly. XmlSeriali zationRead erService. Read42_Get UserAvaila bilityResp onse()
at Microsoft.Xml.Serializatio n.Generate dAssembly. ArrayOfObj ectSeriali zer3.Deser ialize(Xml Serializat ionReader reader)
at System.Xml.Serialization.X mlSerializ er.Deseria lize(XmlRe ader xmlReader, String encodingStyle, XmlDeserializationEvents events)
--- End of inner exception stack trace ---
at System.Xml.Serialization.X mlSerializ er.Deseria lize(XmlRe ader xmlReader, String encodingStyle, XmlDeserializationEvents events)
at System.Xml.Serialization.X mlSerializ er.Deseria lize(XmlRe ader xmlReader, String encodingStyle)
at System.Web.Services.Protoc ols.SoapHt tpClientPr otocol.Rea dResponse( SoapClient Message message, WebResponse response, Stream responseStream, Boolean asyncCall)
at System.Web.Services.Protoc ols.SoapHt tpClientPr otocol.End Invoke(IAs yncResult asyncResult)
at Microsoft.Exchange.InfoWor ker.Common .Availabil ity.Proxy. Service.En dGetUserAv ailability (IAsyncRes ult asyncResult)
at Microsoft.Exchange.InfoWor ker.Common .Availabil ity.ProxyW ebRequest. CompleteRe quest(). The request information is ProxyWebRequest type = CrossSite, url = https://<servername>/EWS/Exchange. asmx
Mailbox list = <username>SMTP:<email>, Parameters: windowStart = 8/26/2012 12:00:00 AM, windowEnd = 10/7/2012 12:00:00 AM, MergedFBInterval = 30, RequestedView = MergedOnly
.. Make sure that Active Directory site/forest containing the user mailbox has at least one local Exchange 2007 server running Exchange Availability service. Turn up logging for MSExchange Availability service and test basic network connectivity.
The odd thing about this error is both servers are in the same domain and no other users have any issues with free/busy information. If anyone has any idea how to resolve this I'd really appreciate it.
Thanks in advance!
Here's the event log from the requesting server:
Process 7820[w3wp.exe:/LM/W3SVC/1/
Parameter name: daysOfWeek
at Microsoft.Exchange.Data.En
at Microsoft.Exchange.Data.St
at Microsoft.Exchange.InfoWor
at Microsoft.Xml.Serializatio
at Microsoft.Xml.Serializatio
at Microsoft.Xml.Serializatio
at Microsoft.Xml.Serializatio
at Microsoft.Xml.Serializatio
at Microsoft.Xml.Serializatio
at System.Xml.Serialization.X
--- End of inner exception stack trace ---
at System.Xml.Serialization.X
at System.Xml.Serialization.X
at System.Web.Services.Protoc
at System.Web.Services.Protoc
at Microsoft.Exchange.InfoWor
at Microsoft.Exchange.InfoWor
Mailbox list = <username>SMTP:<email>, Parameters: windowStart = 8/26/2012 12:00:00 AM, windowEnd = 10/7/2012 12:00:00 AM, MergedFBInterval = 30, RequestedView = MergedOnly
.. Make sure that Active Directory site/forest containing the user mailbox has at least one local Exchange 2007 server running Exchange Availability service. Turn up logging for MSExchange Availability service and test basic network connectivity.
The odd thing about this error is both servers are in the same domain and no other users have any issues with free/busy information. If anyone has any idea how to resolve this I'd really appreciate it.
Thanks in advance!
Do you have more than one database? Can you try moving the user to one of the other databases to see if that clears up any settings issues?
I know this is going to sound silly since this isn't likely a client issue, but have you tried to have the user, who's freebusy is not showing, open outlook with the following arguments?
outlook.exe /cleanfreebusy
outlook.exe /cleanfreebusy
ASKER
I'll try both of these and get back to you. Thanks for the quick response.
ASKER
Tried both but we're still seeing the same issue.
What version of Outlook are you using? One thing you can check is to make sure they are allowing Free/busy. In Outlook 2010, you would go to the options (under file tab), click on Calendar, and it would be under the Calendar Options. Look for the Free/Busy Options button. Make sure Default has the permission level of Free/Busy time.
If it's Outlook 2007, check out the following article:
Technet Article "Troubleshooting Free/Busy"
Technet Article "Troubleshooting Free/Busy"
ASKER
We're using Outlook 2003 (ugh) - checked the Calendar options and it's configured correctly.
Have you tried restarting the Exchange services?
ASKER
Yes, we rebooted both Exchange servers.
Any reason you are still on Exchange 2007 SP1? That is very old and no longer supported. I would suggest moving to Exchange 2007 SP3 plus the latest rollup before you try anything else. The service pack installation will resolve many things.
Simon.
Simon.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Ooo, good one. Make sure you mark this as resolved and select your own solution as the answer.
ASKER
I was able to resolve the issue myself.