Question : MsexchangeOma event id 1801

Hello,

We have used oma succesfully for 1,5 years on a sbs server 2003 sbs, but suddenly after a server reboot it stopped working.

After the server reboot i got a event id 1503 message:

An unknown error occurred while processing the current request:
Message: Er is een time-out voor de bewerking opgetreden.
Source: Microsoft.Exchange.OMA.ExchangeDataProvider
Stack trace:
   at Microsoft.Exchange.OMA.ExchangeDataProvider.OmaWebRequest.GetResponse()
   at Microsoft.Exchange.OMA.ExchangeDataProvider.ExchangeServices.GetSpecialFolders()
   at Microsoft.Exchange.OMA.ExchangeDataProvider.ExchangeServices..ctor(UserInfo user)

Message: Het doel van een aanroep heeft een uitzondering veroorzaakt.
Source: mscorlib
Stack trace:
   at System.Reflection.RuntimeConstructorInfo.InternalInvoke(BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture, Boolean isBinderDefault)
   at System.Reflection.RuntimeConstructorInfo.Invoke(BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
   at System.RuntimeType.CreateInstanceImpl(BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture, Object[] activationAttributes)
   at System.Activator.CreateInstance(Type type, BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture, Object[] activationAttributes)
   at Microsoft.Exchange.OMA.UserInterface.Global.Session_Start(Object sender, EventArgs e)

Message: Er is een uitzondering van het type Microsoft.Exchange.OMA.DataProviderInterface.ProviderException veroorzaakt.
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[/quote

 i trouble shooted this to that for some reason the asp.net service was not started. After i started it the event id 1503 dissapeared but got replaced by a system event id 1801 message:

Unable to connect to the Microsoft(R) Exchange server FILE-SERVER. To fix this problem, verify that there is network connectivity between this server and the Exchange server.
Also, verify that the Exchange server that this server is attempting to connect to is functioning properly.

Everything else seems to be working fine: i restarted the IIS web server but no avail.

Any idea's ?

Answer : MsexchangeOma event id 1801

I finally managed to troubleshoot this to our anti virus solution on the server, the tmproxy service from trend micro wfbs was the problem.

When i restarted the service oma was working again.