XCCC: "Server Error in '/OMA' Application" Error Message When You View the Outlook Mobile Access Web Site

Article translations Article translations
Article ID: 818486 - View products that this article applies to.
Expand all | Collapse all

Symptoms

When you try to view the Microsoft Outlook Mobile Access Web site on a server after you install Exchange Server 2003 on that server, you receive an error message that is similar to the following:
Server Error in '/OMA' Application.
Access to the path "Drive:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\Temporary ASP.NET Files\oma\4707b1f2\a6dd9810" is denied.

Description: An unhandled exception occurred during the execution of the current Web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.UnauthorizedAccessException: Access to the path "Drive:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\Temporary ASP.NET Files\oma\4707b1f2\a6dd9810" is denied. ASP.NET is not authorized to access the requested resource. Consider granting access rights to the resource to the ASP.NET request identity. ASP.NET has a base process identity (typically {MACHINE}\ASPNET on IIS 5 or Network Service on IIS 6) that is used if the application is not impersonating. If the application is impersonating via <identity impersonate="true"/>, the identity will be the anonymous user (typically IUSR_MACHINENAME) or the authenticated request user.

Cause

This problem occurs when you install the Microsoft .NET Framework on a server that is running Microsoft Windows 2000 or when you install Microsoft ASP.NET on a server that is running Microsoft Windows Server 2003 before you promote the server to the role of domain controller. When you promote the server, the access control list (ACL) permissions that you configured during the .NET Framework or during the ASP.NET installation are modified, and all ASP.NET applications are affected by this change. You must install ASP.NET after you promote the computer to a domain controller for applications that require ASP.NET. This problem may also occur if you upgrade a Windows 2000 domain controller to a Windows Server 2003 domain controller.

Note A configuration where Exchange Server 2003 is installed on a domain controller is sometimes referred to as a onebox configuration.

Resolution

To resolve this problem, reset the ASP.NET ACLs.

To have us fix this problem for you, go to the "Fix it for me" section. To fix this problem yourself, go to the "Let me fix it myself" section.

Fix it for me

To fix this problem automatically, click the Fix itbutton or link. Click Run in the File Downloaddialog box, and then follow the steps in the Fix it wizard.
Collapse this imageExpand this image
assets fixit1
Fix this problem
Microsoft Fix it 50343
Collapse this imageExpand this image
assets fixit2

Note this wizard may be in English only; however, the automatic fix also works for other language versions of Windows.

Note if you are not on the computer that has the problem, save the Fix it solution to a flash drive or a CD and then run it on the computer that has the problem.

Let me fix it myself

To resolve this problem yourself, use the ASP.NET IIS Registration Tool (Aspnet_regiis.exe) to reset the ASP.NET ACLs.

To run Aspnet_regiis.exe, follow these steps:
  1. On the domain controller, click Start, and then click Run.
  2. In the Open box, type cmd, and then click OK.
  3. Type cd drive:\Windows\Microsoft.NET\Framework, where drive is the drive that Windows is installed on, and then press ENTER.
  4. Type dir, and then press ENTER.
  5. Note the folder names that are listed, and then locate the folder name that begins with the letter v.

    This folder indicates the version of .NET Framework that is installed on your computer.
  6. Type cd VersionFolderName, where VersionFolderName is the folder that you noted in step 5, and then press ENTER.
  7. Type aspnet_regiis.exe -i, and then press ENTER.
.

Workaround

To work around this problem, install Exchange Server 2003 on a server that is running Windows 2000 in the following sequence:
  1. Install Windows 2000.
  2. Promote the server to the role of domain controller.
  3. Install the .NET Framework.
  4. Install Exchange Server 2003.
To work around this problem, install Exchange Server 2003 on Windows Server 2003 in the following sequence:
  1. Install Windows Server 2003.
  2. Promote the server to the role of domain controller.
  3. Install ASP.NET.
  4. Install Exchange Server 2003.

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

More information

Promoting a domain controller after you install the .NET Framework or ASP.NET breaks the Exchange Server 2003 features that depend on ASP.NET. ASP.NET is required for certain Exchange Server 2003 features such as Outlook Mobile Access.

For more information about the ASP.NET IIS Registration Tool, visit the following Microsoft Web site: http://msdn2.microsoft.com/en-us/library/k6h9cz8h(VS.80).aspx

Properties

Article ID: 818486 - Last Review: September 18, 2013 - Revision: 5.0
Applies to
  • Microsoft Exchange Server 2003 Enterprise Edition
  • Microsoft Exchange Server 2003 Standard Edition
Keywords: 
kbmsifixme kbfixme kberrmsg kbprb KB818486

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com