gatorIT
asked on
OMA a system error has occurred
Issue with Outlook Mobile Access...(OWA works fine)
https://sub.domain.com/oma
prompted for username and password, then get:
A System error has occurred while processing your request. Please try again. If the problem persists, contact your administrator.
[EVENT VIEWER LOG ENTRY]
Event Viewer log entry:
An unknown error occurred while processing the current request:
Message: The remote server returned an error: (400) Bad Request.
Source: Microsoft.Exchange.OMA.Exc hangeDataP rovider
Stack trace:
at Microsoft.Exchange.OMA.Exc hangeDataP rovider.Om aWebReques t.GetReque stStream()
at Microsoft.Exchange.OMA.Exc hangeDataP rovider.Ex changeServ ices.GetSp ecialFolde rs()
at Microsoft.Exchange.OMA.Exc hangeDataP rovider.Ex changeServ ices..ctor (UserInfo user)
Message: Exception has been thrown by the target of an invocation.
Source: mscorlib
Stack trace:
at System.Reflection.RuntimeC onstructor Info.Inter nalInvoke( BindingFla gs invokeAttr, Binder binder, Object[] parameters, CultureInfo culture, Boolean isBinderDefault)
at System.Reflection.RuntimeC onstructor Info.Invok e(BindingF lags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
at System.RuntimeType.CreateI nstanceImp l(BindingF lags bindingAttr, Binder binder, Object[] args, CultureInfo culture, Object[] activationAttributes)
at System.Activator.CreateIns tance(Type type, BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture, Object[] activationAttributes)
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.
[/EVENT VIEWER LOG ENTRY]
System configuration is:
SBS 2003 Premium SP1
Exchange 2003 SP2
ISA 2004 SP3
I have tried several MS KB's to no avail:
http://support.microsoft.com/default.aspx?kbid=817379
http://support.microsoft.com/default.aspx?kbid=883380
For brevity, those KBs refer to running CEICW which should create/fix ExchangeVDir registry entries and recreating the default Exchange/OWA/OMA virtual directories.
Nothing is getting blocked in ISA.
https://sub.domain.com/oma
prompted for username and password, then get:
A System error has occurred while processing your request. Please try again. If the problem persists, contact your administrator.
[EVENT VIEWER LOG ENTRY]
Event Viewer log entry:
An unknown error occurred while processing the current request:
Message: The remote server returned an error: (400) Bad Request.
Source: Microsoft.Exchange.OMA.Exc
Stack trace:
at Microsoft.Exchange.OMA.Exc
at Microsoft.Exchange.OMA.Exc
at Microsoft.Exchange.OMA.Exc
Message: Exception has been thrown by the target of an invocation.
Source: mscorlib
Stack trace:
at System.Reflection.RuntimeC
at System.Reflection.RuntimeC
at System.RuntimeType.CreateI
at System.Activator.CreateIns
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.
[/EVENT VIEWER LOG ENTRY]
System configuration is:
SBS 2003 Premium SP1
Exchange 2003 SP2
ISA 2004 SP3
I have tried several MS KB's to no avail:
http://support.microsoft.com/default.aspx?kbid=817379
http://support.microsoft.com/default.aspx?kbid=883380
For brevity, those KBs refer to running CEICW which should create/fix ExchangeVDir registry entries and recreating the default Exchange/OWA/OMA virtual directories.
Nothing is getting blocked in ISA.
That's an ASP .NET error.
What version of ASP .NET do you have installed on your sever? All of SBS's default sites must be running under .NET 1.1 with SP1. If you have .NET 2.0 installed, you need to make sure that the install didn't automatically modify all of the default web sites to use 2.0 by looking on their properties > ASP .NET tab.
Jeff
TechSoEasy
What version of ASP .NET do you have installed on your sever? All of SBS's default sites must be running under .NET 1.1 with SP1. If you have .NET 2.0 installed, you need to make sure that the install didn't automatically modify all of the default web sites to use 2.0 by looking on their properties > ASP .NET tab.
Jeff
TechSoEasy
ASKER
Yes, the site is running ASP.NET 1.1.
At this point I'm leaning towards an uninstall/reinstall of Exchange, IIS and ISA.
I've rebuilt just about all of the components involved including virtual directories in ESM and IIS and registry settings.
At this point I'm leaning towards an uninstall/reinstall of Exchange, IIS and ISA.
I've rebuilt just about all of the components involved including virtual directories in ESM and IIS and registry settings.
ASKER CERTIFIED SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
ASKER
On the problem server, http does not resolve. However ISA is allowing the traffic to pass, so I'm thinking we're looking at an IIS issue.