[Last Call] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 220
  • Last Modified:

Have problem with Exchange 2003 OMA

Hi i ahve a problem with oma, when i try connect from the outside i get this in the event viewer, owa works fine and so does exchange? any one any ideas.

An unknown error occurred while processing the current request:
Message: The remote server returned an error: (400) Bad Request.
Source: Microsoft.Exchange.OMA.ExchangeDataProvider
Stack trace:
   at Microsoft.Exchange.OMA.ExchangeDataProvider.OmaWebRequest.GetRequestStream()
   at Microsoft.Exchange.OMA.ExchangeDataProvider.ExchangeServices.GetSpecialFolders()
   at Microsoft.Exchange.OMA.ExchangeDataProvider.ExchangeServices..ctor(UserInfo user)

Message: Exception has been thrown by the target of an invocation.
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: 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)
0
nostrasystems
Asked:
nostrasystems
  • 17
  • 12
1 Solution
 
LeeDerbyshireCommented:
The 400 - Bad Request error in OMA is sometimes caused by having a Host Header configured for the Default Web Site.  OMA doesn't like it.
0
 
nostrasystemsAuthor Commented:
could u explain a bit?

i tried http://support.microsoft.com/kb/898131
0
 
LeeDerbyshireCommented:
Were you able to find out if a Host Header is configured for the Default Web Site?  It's usually best to leave this blank, but obviously there may have been a good reason to put one in there on your server.
0
Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

 
nostrasystemsAuthor Commented:
here is a screen shot of my host header
iss.jpg
0
 
LeeDerbyshireCommented:
Yes, that might cause the problem.  Are you sure it needs to be there?  If there is only one single Web site shown in IIS Manager inside the Web Sites container, then you definitely will not need it.  If there are several Web sites, then things get slightly more complicated.
0
 
nostrasystemsAuthor Commented:
only one the default website

so do i remove the 80 header and 443 header?
0
 
nostrasystemsAuthor Commented:
the ok button is greyed out if i remove the top info i cant click on ok?
0
 
LeeDerbyshireCommented:
Host Headers don't work with SSL, so you don't need to do anything with the SSL identities.  For the port 80 identity, just double-click the entry to edit it, and remove the Host Header name.

Or are you saying that when the Host Header field is empty, the OK button becomes inactive?
0
 
nostrasystemsAuthor Commented:
i did that and removed the header value and i could click on ok so applied the settings and restarted the iss admin service but still the same error

  A System error has occurred while processing your request. Please try again. If the problem persists, contact your administrator.
0
 
LeeDerbyshireCommented:
Does the error display still mention the 400 - Bad Request message, or is it now slightly different?
0
 
nostrasystemsAuthor Commented:
no error is still the same
0
 
LeeDerbyshireCommented:
Can you post the IIS log file entries generated when you try to use OMA?  You should see the initial request to GET /OMA , followed by several other kinds of request to /Exchange .
0
 
nostrasystemsAuthor Commented:
where is the log file and i will send it asap
0
 
LeeDerbyshireCommented:
Latest file in C:\Windows\System32\LogFiles\W3SVC1 .
0
 
nostrasystemsAuthor Commented:
here is the log file
ex080611.log
0
 
LeeDerbyshireCommented:
Okay, thanks.  I can see the initial client requests for /oma , but there are no OMA-related WebDAV requests following it.  There are some Entourage ones which give some idea of what they should have looked like, but clearly Entourage is not related to OMA.

I notice in the screen shot you posted earlier, that the Default Web Site appears to be configured to listen on a specific IP address, and not the more usual 'All unassigned' value from the drop-down list.  Since the server only hosts one web site, there is no good reason I can think of for not setting it to 'All unassigned'.  Is that something you can try?
0
 
nostrasystemsAuthor Commented:
i have two nics in the server, one is a backup nic, will i still setit to all unassigned?
0
 
LeeDerbyshireCommented:
Yes, it should still work.  If IIS appears to stop responding to all requests, then change it back, but if the situation is no worse (i.e. you still get the OMA error), then leave it All Unassigned.  This is the default setting, and I think it will help further trouobleshooting of the situation if your settings are as standard as possible.
0
 
nostrasystemsAuthor Commented:
Hi

It seems to be the same after i set it to all unassigned? any ideas?
0
 
LeeDerbyshireCommented:
Is there any change at all in the error output.  They tend to be long and all look the same, but there may be some small change in detail.  Also, if you require SSL on your OWA directory, you will need to make some small changes to IIS and the registry.  Look for MS KB817379 .
0
 
nostrasystemsAuthor Commented:
the problem is that this was all working up until about 4 days ago?
0
 
nostrasystemsAuthor Commented:
this is the error in the event viewer i get now

An unknown error occurred while processing the current request:
Message: The remote server returned an error: (403) Forbidden.
Source: Microsoft.Exchange.OMA.ExchangeDataProvider
Stack trace:
   at Microsoft.Exchange.OMA.ExchangeDataProvider.OmaWebRequest.GetRequestStream()
   at Microsoft.Exchange.OMA.ExchangeDataProvider.ExchangeServices.GetSpecialFolders()
   at Microsoft.Exchange.OMA.ExchangeDataProvider.ExchangeServices..ctor(UserInfo user)

Message: Exception has been thrown by the target of an invocation.
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: 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)
0
 
nostrasystemsAuthor Commented:
I have checked all the security settings against a known good and followed the ms kb's but to no avail any suggestions people?
0
 
LeeDerbyshireCommented:
The error is now quite different.  Note that it now says '403 - Forbidden'.  There are 20 different types of 403 error in IIS - you will need to look at your latest IIS log file to find the request for Exchange that results in the 403 status.  When you find the relevant line, the number after the 403 will indicate the subcode, which will tell us where to look next.
0
 
nostrasystemsAuthor Commented:
Hi Lee

Here is my latest iis logfile attached, can you help?
New-Text-Document.txt
0
 
nostrasystemsAuthor Commented:
here it is

2008-06-20 13:01:36 W3SVC1 172.132.4.1 PROPFIND /exchange-oma/Administrator/ - 80 - 172.132.4.1 - 403 6 0
0
 
LeeDerbyshireCommented:
Okay, I can see that when you go to use oma, the server makes an internal call to the exchange-oma virtual directory (which means you've done KB817379).  The log file reveals the the server responds with a 403;6 status, which means 'IP Address rejected'.  Have a look at the exchange-oma VDir in IIS Manager, and check the IP Address restrictions table.  Something there is blocking the server's access.
0
 
nostrasystemsAuthor Commented:
Here is a screen shot ip is the one of the exchange server
screen.jpg
0
 
nostrasystemsAuthor Commented:
Hi Lee

You pointed me in the correct direction I now have it fixed, the server has two nic's so I added the ip of the second nic and all working now. the second nic links two servers for replication.

Thank Lee

Points to you
0

Featured Post

Free recovery tool for Microsoft Active Directory

Veeam Explorer for Microsoft Active Directory provides fast and reliable object-level recovery for Active Directory from a single-pass, agentless backup or storage snapshot — without the need to restore an entire virtual machine or use third-party tools.

  • 17
  • 12
Tackle projects and never again get stuck behind a technical roadblock.
Join Now