You receive an error message when you try to create an e-mail message, try to add a new contact, try to add a new task, try to create a new appointment in Outlook Mobile Access with Exchange Server 2003 (842023)
The information in this article applies to:
- Microsoft Exchange Server 2003 Standard Edition
- Microsoft Exchange Server 2003 Enterprise Edition
SYMPTOMSWhen you use Microsoft Outlook Mobile Access (OMA), you may experience the following symptoms: - When you try to create an e-mail message, try to add a new contact, try to add a new task, try to create a new appointment with other attendees, or try to perform any other function that requires the resolution of recipient names, you receive one of the following error messages:
A System error has occurred while processing your request. Please try again. If the problem persists, contact your administrator.
Unable to connect to your mailbox on server Server_Name. Please try again later. If the problem persists contact your administrator.
- If you try to create a new appointment with yourself as the only attendee, you do not receive an error message, but the appointment is not saved.
- On the Microsoft Exchange Server 2003 front-end server, events that are similar to the following may be logged in the application event log:Event Type: Error
Event Source: MSExchangeOMA
Event Category: (1000)
Event ID: 1506
Description:
An unknown error occurred while processing the current request: Exception of type System.Web.HttpUnhandledException was thrown.
Stack trace:
at System.Web.UI.Page.HandleError(Exception e)
at System.Web.UI.Page.ProcessRequestMain()
at System.Web.UI.Page.ProcessRequest()
at System.Web.UI.Page.ProcessRequest(HttpContext context)
at System.Web.CallHandlerExecutionStep.System.Web.HttpApplication+IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)
Inner Error: The root element is missing.
Stack trace:
at System.Xml.XmlTextReader.Read()
at Microsoft.Exchange.OMA.ExchangeDataProvider.StaticStuff.ParseDavResponse(Stream response, NewItemDelegate newItem, AddItemDelegate addItem, StatusDelegate handleStatus)
at Microsoft.Exchange.OMA.ExchangeDataProvider.ExchangeMessage.GetRecipients()
at Microsoft.Exchange.OMA.ExchangeDataProvider.ExchangeMessage.ResolveRecipients()
at Microsoft.Exchange.OMA.UserInterface.MessageEditor.SaveClick(Object sender, EventArgs e)
at System.Web.UI.MobileControls.Command.OnClick(EventArgs e)
at System.Web.UI.MobileControls.Command.System.Web.UI.IPostBackEventHandler.RaisePostBackEvent(String argument)
at System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl, String eventArgument)
at System.Web.UI.MobileControls.MobilePage.RaisePostBackEvent(IPostBackEventHandler sourceControl, String eventArgument)
at System.Web.UI.Page.RaisePostBackEvent(NameValueCollection postData)
at System.Web.UI.Page.ProcessRequestMain()
Note Event ID 1506 may be logged when the OMA client tries to resolve a recipient name.Event Type: Error Event Source: MSExchangeOMA Event Category: (1000) Event ID: 1805 Description:
Request from user Username@Domain_Name resulted in the Microsoft(R) Exchange back-end server Exchange_Server_Name returning an HTTP error with status code 507.Note If the OMA client tries to create a new appointment with the person who creates the appointment as the only attendee, Event ID 1805 may be logged in the application event log.
The error messages that you receive, and the events that are logged, do not clearly indicate the source of the problem. CAUSEThis problem occurs if you have reached the storage limit for your mailbox.
RESOLUTIONService pack information
To resolve this problem, obtain the latest service pack for Microsoft Exchange Server 2003. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
836993 How to obtain the latest updates and service packs for Exchange Server 2003
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
This problem was corrected in Exchange Server 2003 Service Pack 1 (SP1).
Modification Type: | Minor | Last Reviewed: | 11/8/2005 |
---|
Keywords: | kbExchange2003sp1fix kbfix kbBug KB842023 kbAudITPRO |
---|
|