A "System.ArgumentOutOfRangeException" exception occurs when you click the "Scheduling Assistant" tab in Exchange Server 2007 OWA


Consider the following scenario:
  • You access a Microsoft Exchange Server 2007 mailbox by using Outlook Web Access (OWA).
  • You set the time zone to (GMT-04:00) Santiago.
  • You create a meeting request or an appointment that occurs in February, and then you click the Scheduling Assistant tab.
In this scenario, you receive the following error message:

Outlook Web Access encountered an unexpected error and was unable to handle your request.

Additionally, if you click the Copy error details to clipboard option, the following error details are copied:

Url: https://<owa url> /owa/ev.owa?oeh=1&ns=EditCalendarItem&ev=UpdateScheduling
User host address: <IP address>
User: <user name>
EX Address: /o=<domain>/ou=Exchange Administrative Group (<xxxxxx>)/cn=Recipients/cn=<user name>
SMTP Address: <user email address>
OWA version: <xxxx>
Mailbox server: <Exchange Server 2007  Mailbox server name>

Exception type: System.ArgumentOutOfRangeException
Exception message: startIndex cannot be larger than length of string. Parameter name: startIndex.

Call stack
System.String.InternalSubStringWithChecks(Int32 startIndex, Int32 length, Boolean fAlwaysCopy) Microsoft.Exchange.Clients.Owa.Premium.SchedulingTabRenderingUtilities.SetFreeBusyDayLightBasedValue(DateTime startDate, DateTime endDate, ExchangeTimeZone timeZone, String& freeBusyData) Microsoft.Exchange.Clients.Owa.Premium.SchedulingTabRenderingUtilities.RenderRecipientFreeBusyData(TextWriter output, SchedulingRecipientInfo[] schedulingRecipientInfos, FreeBusyQueryResult[] freeBusyQueryResults, DateTime startDateFreeBusyWindow, DateTime endDateFreeBusyWindow, Boolean show24Hours, Boolean renderDataForAllRecipients, ExchangeTimeZone timeZone) Microsoft.Exchange.Clients.Owa.Premium.EditCalendarItemEventHandler.UpdateScheduling()


To resolve this issue, install the following update rollup:
2608656 Description of Update Rollup 6 for Exchange Server 2007 Service Pack 3


Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.