OMA fails with Event ID: 1503

[Ian Wilson]

Just couple of hours ago I migrated my my SBS 2003 implementation to new hardware with SBS 2003 with SP1. Procedure went fine without any problem, even Web sites, OWA, etc works fine. But as the title says, my OMA fails with the event id error saying “A System error has occurred while processing your request. Please try again. If the problem persists, contact your administrator.“

This is what I got in the Event Viewer Log:

Event Type: Error
Event Source: MSExchangeOMA
Event Category: (1000)
Event ID: 1503
Date: 16/08/2006
Time: 22:52:54
User: N/A
Computer: <DELETED>

Description:
An unknown error occurred while processing the current request:
Message: Index was out of range. Must be non-negative and less than the size of the collection.
Parameter name: startIndex
Source: mscorlib
Stack trace:
at System.Globalization.CompareInfo.IndexOfString(Void* pSortingTable, Int32 win32LCID, String source, String value, Int32 startIndex, Int32 count, Int32 options)
at System.Globalization.CompareInfo.IndexOf(String source, String value,Int32 startIndex)
at
Microsoft.Exchange.OMA.Preferencing.AdUserObject.get_globalWirelessEnable()
at
Microsoft.Exchange.OMA.Preferencing.AdUserObject.get_UserIsWirelesslyEnabled()
at
Microsoft.Exchange.OMA.Preferencing.OmaUserInfo.get_UserIsWirelesslyEnabled()
at Microsoft.Exchange.OMA.UserInterface.Global.Session_Start(Object sender, EventArgs e)

Message: Exception of type
Microsoft.Exchange.OMA.DataProviderInterface.ProviderException was thrown.
EventMessage:
UserMessage: A System error has occurred while processing your request. Please try again. If the problem persists, contact your administrator.
Source: Microsoft.Exchange.OMA.UserInterface
Stack trace:
at Microsoft.Exchange.OMA.UserInterface.Global.Session_Start(Object
sender, EventArgs e)
at System.Web.SessionState.SessionStateModule.RaiseOnStart(EventArgs e)
at System.Web.SessionState.SessionStateModule.CompleteAcquireState()
at System.Web.SessionState.SessionStateModule.BeginAcquireState(Object source, EventArgs e, AsyncCallback cb, Object extraData)
at
System.Web.AsyncEventExecutionStep.System.Web.HttpApplication+IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)

All helps will be appreciated.

[Eduards$]

I think you need to re-configure the OMA to get rid of this error. Just follow the steps provided below:

1. Have the user reset the mobile device.
2. Edit the web.config File in the “\Program Files\Exchsrvr\OMA\Browse” directory and search for a line: <sessionState mode="InProc"/>
3. Then add the following line in a new line above this line: <pages enableSessionState="true"/>.

For more help, check this article: http://www.chicagotech.net/exchange/event1503.htm

[jdc]

Thanks for your solution posting! I had the exact same situation...used the the Swing migration method last year, and could not get OMA working using my own account. accounts created after the migration were working, but mine created before was not.

Your post saved me a lot of time!

Thanks,
JDC

[TheElderOne]

I've spent the last 3 weeks trying to resolve this issue and came upon this post today. Nice One - I now have my remotes back on to OMA and Active Sync.

Just hope it gets global recognisation.

TEO

[LMHansen]

Al,

You're a genius!

[Hammer_PDX]

I also did the Swing Migration from SBS 2003 to SBS 2003. This fixed the OMA problem for me! Thanks. Huge!