"Index and length must refer to a location within the string" exception when you try to create a new meeting request or appointment in Exchange Server 2010

Consider the following scenario:

• You install Microsoft Exchange Server 2010.
• You create a new meeting request or a new appointment in Outlook Web App (OWA).
• You click Scheduling Assistant.

In this scenario, the time suggestions may not be displayed as expected. When this issue occurs, you may receive the following error message:
Additionally, error details that resemble the following are logged:

Request

Url: https://owa.contoso.com:443/owa/ev.owa?oeh=1&ns=EditCalendarItem&ev=UpdateScheduling
User host address: ip_address
User: user
EX Address: /o=organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=User1
SMTP Address: user@contoso.com
OWA version: 14.2.247.5
Mailbox server: server.contoso.com

Exception

Exception type: System.ArgumentOutOfRangeException
Exception message: Index and length must refer to a location within the string. Parameter name: length

Call stack

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

This issue occurs because, under certain conditions, Exchange Server 2010 incorrectly calculates current daylight saving time (DST) start dates and end dates.

To resolve this issue, install the following update rollup:

This issue is date dependent. Therefore, it is most likely to occur for mailboxes that use dynamic DST, where the DST start dates and DST end dates change each year.