Link to home
Start Free TrialLog in
Avatar of powerbiz
powerbizFlag for Australia

asked on

OMA Event ID 1503 problem

I am running SBS2003 standard and have OWA running well. However, when I try to access http://server/oma, I get the error message "A System error has occurred while processing your request. Please try again. If the problem persists, contact your administrator." The error logged in the Event logs is Event ID 1503. I have read up on most of the other 1503, but have not come across one with the following text:

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)
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

So far, I have tried the following:
1. Followed settings for http://support.microsoft.com/?id=898131
2. Had a look at http://support.microsoft.com/default.aspx?scid=kb;en-us;817379
3. Looked at http://support.microsoft.com/default.aspx?scid=kb;en-us;842119

Thw wierd thing is that I have set up several other servers, and oma is working fine on the other servers. However, this one hosts a few websites.

Any help would be greatly appreciated. Full points will be awarded. I've been messing around with this for over 2 months off and on.
Avatar of Jeffrey Kane - TechSoEasy
Jeffrey Kane - TechSoEasy
Flag of United States of America image

Hi powerbiz,

Check out the VERY BOTTOM of this page:  http://www.sbsusers.net/techinfo/SBS_RelNotes.htm

Which shows why users are unable to log into OMA.

Good Luck!

Jeff
TechSoEasy
Avatar of powerbiz

ASKER

I've already read that one. Tried it, no luck. Just rechecked it again. Still no luck.
Thanks.
Boon, Powerbiz
Well, the "guy who knows everything about SBS and Windows Mobile"  is Sean Daniels... (Don't tell him I said that... he'll blush).

He's a member of the SBS team at Microsoft and has a blog here:  http://seanda.blogspot.com/

There are a number of articles on configuration and troubleshooting on his site... it may help to just read them over and see what's up.

Jeff
TechSoEasy
Sorry, I've tried all the various ideas there to no avail. It is quite weird, as I manage a few SBS 2003 sites, but I can't get this one going, while all the others are working happily away. I'll leave this for a while longer, and maybe I'll call MS if I don't get any more leads.

Boon, Powerbiz
Boon,

The EXACT wording of your error is quoted in this public newsgroup thread:  http://snipurl.com/jfv0

It seems that it's something of a bug... if you uncheck and recheck the SSL box of the Exchange IIS folder, the problem seems to go away.

Jeff
TechSoEasy
It was the most promising lead yet ... but alas, it didn't work. I also tried setting SSL on the exchange-oma folder and removing it, and several other variations. I even tried logging in with a different user, just in case there was a problem with the user I was trying to connect with.

Boon, Powerbiz
Each time you are doing these "changes" are you rerunning the CEICW?  You should be.

You might also try REMOVING ALL stored certificates from your server and then running the CEICW to reestablish them.

I've found that an errantly named certificate can stick around for a long time... there are some good overviews in this tutorial which will lead you to where the certificates are:  http://www.msexchange.org/tutorials/pubowa2003part1.html

Jeff
TechSoEasy
I restarted IIS using IISRESET. Now that you have mentioned it, I have also rerun CEICW. Didn't work.
Not game to remove the certificates yet. I'll try that later.
Thanks,
Boon, Powerbiz
I'm fairly sure it's a certificate issue... SBS creates them automatically and sometimes making changes creates a new one without replacing it everywhere needed.

Jeff
TechSoEasy
OK. I'll try it over the weekend.
Thanks,
Boon
I ran CEICW again and recreated a new certificate. I then tried all the various fixes above again to no avail. I think it is a job for MS.
Boon
ASKER CERTIFIED SOLUTION
Avatar of modulo
modulo

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial