Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

The Edgetransport.exe process crashes when it processes meeting requests in Exchange Server 2007


View products that this article applies to.

Symptoms

On a Microsoft Exchange Server 2007 server, the Edgetransport.exe process may crash when it processes a meeting request. This problem occurs when the following conditions are true:
  • The regional setting of the local computer is set to Arabic.
  • The Calendar type of the local computer is set to the UmAlquraCalendar class.
    Note Generally, the default Calendar type is set to the UmAlquraCalendar class.
Additionally, the following event is logged in the Application event log:


Log Name: Application
Source: MSExchangeTransport
Event ID: 10003
Task Category: PoisonMessage
Level: Error
Keywords: Classic
Description:
The transport process failed during message processing with the following call stack: System.ArgumentOutOfRangeException: Specified time is not supported in this calendar. It should be between 04/30/1900 00:00:00 (Gregorian date) and 05/13/2029 23:59:59 (Gregorian date), inclusive. Parameter name: time at System.Globalization.UmAlQuraCalendar.CheckTicksRange(Int64 ticks) at System.Globalization.UmAlQuraCalendar.GetDatePart(DateTime time, Int32 part) at System.DateTimeFormat.FormatCustomized(DateTime dateTime, String format, DateTimeFormatInfo dtfi, TimeSpan offset) at System.DateTimeFormat.Format(DateTime dateTime, String format, DateTimeFormatInfo dtfi, TimeSpan offset) at Microsoft.Exchange.Data.ContentTypes.iCalendar.CalendarCommon.FormatDateTime(DateTime s) at Microsoft.Exchange.Data.ContentTypes.iCalendar.CalendarWriter.WritePropertyValue(DateTime value, CalendarValueType valueType) at Microsoft.Exchange.Data.Storage.VCalendar.DemoteTimeZone() at Microsoft.Exchange.Data.Storage.VCalendar.Demote(CalendarWriter calendarWriter) at Microsoft.Exchange.Data.Storage.CalendarDocument.ItemToICal(Item item, OutboundAddressCache addressCache, Stream stream, String charsetName, OutboundConversionOptions outboundConversionOptions) at Microsoft.Exchange.Data.Storage.ItemToMimeConverter.WriteMimeBody(MimePartContentType contentType, MimeFlags flags) at Microsoft.Exchange.Data.Storage.ItemToMimeConverter.StaticWriteMimeBody(ItemToMimeConverter converter, MimePartInfo part, MimeFlags flags) at Microsoft.Exchange.Data.Storage.ItemToMimeConverter.WriteMimePart(MimePartInfo part, MimeFlags mimeFlags) at Microsoft.Exchange.Data.Storage.ItemToMimeConverter.WriteMimeParts(List`1 parts, MimeFlags mimeFlags) at Microsoft.Exchange.Data.Storage.ItemToMimeConverter.WriteMimePart(MimePartInfo part, MimeFlags mimeFlags) at Microsoft.Exchange.Data.Storage.ItemToMimeConverter.ConvertItemToMimeInternal(MimeStreamWriter writer, ConversionLimitsTracker limits, MimeFlags flags) at Microsoft.Exchange.Data.Storage.ItemConversion.<>c__DisplayClassf.<InternalConvertItemToMime>b__e() at Microsoft.Exchange.Data.Storage.ConvertUtils.CallCts(Trace tracer, String methodName, String exceptionString, CtsCall ctsCall) at Microsoft.Exchange.Data.Storage.ItemConversion.InternalConvertAnyMimeToMime(EmailMessage messageIn, Stream mimeOut, OutboundConversionOptions outboundOptions) at Microsoft.Exchange.Data.Storage.ItemConversion.ConvertAnyMimeToMime(EmailMessage messageIn, Stream mimeOut, OutboundConversionOptions outboundOptions) at Microsoft.Exchange.Data.Storage.ConvertUtils.CallCts(Trace tracer, String methodName, String exceptionString, CtsCall ctsCall) at Microsoft.Exchange.Data.Storage.ItemConversion.ConvertAnyMimeToMime(MimeDocument documentIn, Stream mimeOut, OutboundConversionOptions outboundOptions) at Microsoft.Exchange.Transport.Categorizer.ContentConverter.GenerateContentForNewMailItem(TransportMailItem originalMailItem, TransportMailItem newMailItem, RecipientEncoding encoding) at Microsoft.Exchange.Transport.Categorizer.ContentConverter.GenerateNewMailItem(IList`1 newMailItemRecipients, RecipientEncoding encoding) at Microsoft.Exchange.Transport.Categorizer.MailItemBifurcator`1.CreateItemForRecipients(Int32 startRecipientIndex, Int32 endRecipientIndex) at Microsoft.Exchange.Transport.Categorizer.MailItemBifurcator`1.CreateMailItems() at Microsoft.Exchange.Transport.Categorizer.MailItemBifurcator`1.GetBifurcatedMailItems() at Microsoft.Exchange.Transport.Categorizer.CategorizerComponent.ConvertMailItemContent(TransportMailItem transportMailItem, TaskContext taskContext) at Microsoft.Exchange.Transport.Categorizer.TaskContext.Invoke() at Microsoft.Exchange.Transport.Categorizer.CatScheduler.JobThreadEntry(Object ignored) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state) at System.Threading._ThreadPoolWaitCallback.PerformWaitCallbackInternal(_ThreadPoolWaitCallback tpWaitCallBack) at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback(Object state)

↑ Back to the top


Cause

This problem occurs if the DateTime property of the meeting request has no year data. In this case, when Exchange Server 2007 processes the meeting request, it sets the DateTime property of the meeting request to "1/1/1600". However, the Arabic regional setting only supports aDateTime range between 04/30/1900 and 05/13/2029. Therefore, the ArgumentOutOfRangeException exception occurs, causing the Microsoft Exchange Transport Service process crash.

↑ Back to the top


Resolution

To resolve this problem, install the following update rollup:
979784 Description of Update Rollup 3 for Exchange Server 2007 Service Pack 2

↑ Back to the top


Status

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

↑ Back to the top


More information

For more information about the UmAlquraCalendar class, visit the following Microsoft Web site:

↑ Back to the top


Keywords: KB977923, kbqfe, kbsurveynew, kbexpertiseinter, kbhotfixrollup, kbfix

↑ Back to the top

Article Info
Article ID : 977923
Revision : 2
Created on : 10/10/2011
Published on : 10/10/2011
Exists online : False
Views : 318