Solved

Have problem with Exchange 2003 OMA

Posted on 2008-06-11
29
212 Views
Last Modified: 2011-10-19
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
Comment
Question by:nostrasystems
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 17
  • 12
29 Comments
 
LVL 31

Expert Comment

by:LeeDerbyshire
ID: 21760270
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
 

Author Comment

by:nostrasystems
ID: 21760595
could u explain a bit?

i tried http://support.microsoft.com/kb/898131
0
 
LVL 31

Expert Comment

by:LeeDerbyshire
ID: 21760630
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
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

 

Author Comment

by:nostrasystems
ID: 21760766
here is a screen shot of my host header
iss.jpg
0
 
LVL 31

Expert Comment

by:LeeDerbyshire
ID: 21760796
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
 

Author Comment

by:nostrasystems
ID: 21760819
only one the default website

so do i remove the 80 header and 443 header?
0
 

Author Comment

by:nostrasystems
ID: 21760862
the ok button is greyed out if i remove the top info i cant click on ok?
0
 
LVL 31

Expert Comment

by:LeeDerbyshire
ID: 21760882
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
 

Author Comment

by:nostrasystems
ID: 21760952
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
 
LVL 31

Expert Comment

by:LeeDerbyshire
ID: 21761104
Does the error display still mention the 400 - Bad Request message, or is it now slightly different?
0
 

Author Comment

by:nostrasystems
ID: 21761403
no error is still the same
0
 
LVL 31

Expert Comment

by:LeeDerbyshire
ID: 21761440
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
 

Author Comment

by:nostrasystems
ID: 21761452
where is the log file and i will send it asap
0
 
LVL 31

Expert Comment

by:LeeDerbyshire
ID: 21761477
Latest file in C:\Windows\System32\LogFiles\W3SVC1 .
0
 

Author Comment

by:nostrasystems
ID: 21761516
here is the log file
ex080611.log
0
 
LVL 31

Expert Comment

by:LeeDerbyshire
ID: 21763009
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
 

Author Comment

by:nostrasystems
ID: 21766997
i have two nics in the server, one is a backup nic, will i still setit to all unassigned?
0
 
LVL 31

Expert Comment

by:LeeDerbyshire
ID: 21767798
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
 

Author Comment

by:nostrasystems
ID: 21768033
Hi

It seems to be the same after i set it to all unassigned? any ideas?
0
 
LVL 31

Expert Comment

by:LeeDerbyshire
ID: 21768401
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
 

Author Comment

by:nostrasystems
ID: 21768847
the problem is that this was all working up until about 4 days ago?
0
 

Author Comment

by:nostrasystems
ID: 21768956
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
 

Author Comment

by:nostrasystems
ID: 21770246
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
 
LVL 31

Expert Comment

by:LeeDerbyshire
ID: 21777292
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
 

Author Comment

by:nostrasystems
ID: 21830792
Hi Lee

Here is my latest iis logfile attached, can you help?
New-Text-Document.txt
0
 

Author Comment

by:nostrasystems
ID: 21830937
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
 
LVL 31

Accepted Solution

by:
LeeDerbyshire earned 500 total points
ID: 21830949
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
 

Author Comment

by:nostrasystems
ID: 21831014
Here is a screen shot ip is the one of the exchange server
screen.jpg
0
 

Author Comment

by:nostrasystems
ID: 21831053
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

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This process describes the steps required to Import and Export data from and to .pst files using Exchange 2010. We can use these steps to export data from a user to a .pst file, import data back to the same or a different user, or even import data t…
This article explains how to install and use the NTBackup utility that comes with Windows Server.
The video tutorial explains the basics of the Exchange server Database Availability groups. The components of this video include: 1. Automatic Failover 2. Failover Clustering 3. Active Manager
The basic steps you have just learned will be implemented in this video. The basic steps are shown to configure an Exchange DAG in a live working Exchange Server Environment and manage the same (Exchange Server 2010 Software is used in a Windows Ser…

735 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question