powerbiz
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.Compa reInfo.Ind exOfString (Void* pSortingTable, Int32 win32LCID, String source, String value, Int32 startIndex, Int32 count, Int32 options)
at System.Globalization.Compa reInfo.Ind exOf(Strin g source, String value, Int32 startIndex)
at Microsoft.Exchange.OMA.Pre ferencing. AdUserObje ct.get_glo balWireles sEnable()
at Microsoft.Exchange.OMA.Pre ferencing. AdUserObje ct.get_Use rIsWireles slyEnabled ()
at Microsoft.Exchange.OMA.Pre ferencing. OmaUserInf o.get_User IsWireless lyEnabled( )
at Microsoft.Exchange.OMA.Use rInterface .Global.Se ssion_Star t(Object sender, EventArgs e)
Message: Exception of type Microsoft.Exchange.OMA.Dat aProviderI nterface.P roviderExc eption 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.Use rInterface
Stack trace:
at Microsoft.Exchange.OMA.Use rInterface .Global.Se ssion_Star t(Object sender, EventArgs e)
at System.Web.SessionState.Se ssionState Module.Rai seOnStart( EventArgs e)
at System.Web.SessionState.Se ssionState Module.Com pleteAcqui reState()
at System.Web.SessionState.Se ssionState Module.Beg inAcquireS tate(Objec t source, EventArgs e, AsyncCallback cb, Object extraData)
at System.Web.AsyncEventExecu tionStep.S ystem.Web. HttpApplic ation+IExe cutionStep .Execute()
at System.Web.HttpApplication .ExecuteSt ep(IExecut ionStep 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.
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.Compa
at System.Globalization.Compa
at Microsoft.Exchange.OMA.Pre
at Microsoft.Exchange.OMA.Pre
at Microsoft.Exchange.OMA.Pre
at Microsoft.Exchange.OMA.Use
Message: Exception of type Microsoft.Exchange.OMA.Dat
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.Use
Stack trace:
at Microsoft.Exchange.OMA.Use
at System.Web.SessionState.Se
at System.Web.SessionState.Se
at System.Web.SessionState.Se
at System.Web.AsyncEventExecu
at System.Web.HttpApplication
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.
ASKER
I've already read that one. Tried it, no luck. Just rechecked it again. Still no luck.
Thanks.
Boon, Powerbiz
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
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
ASKER
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, 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
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
ASKER
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
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
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
ASKER
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
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
Jeff
TechSoEasy
ASKER
OK. I'll try it over the weekend.
Thanks,
Boon
Thanks,
Boon
ASKER
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
Boon
ASKER
I have resolved the question myself by applying the following fixes:
http://randomelements.me.uk/blog/Lists/Blog/DispForm.aspx?ID=980
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q319886
http://randomelements.me.uk/blog/Lists/Blog/DispForm.aspx?ID=980
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q319886
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
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