Install Config Wiki

All about installing, configuring and troubleshooting

User Tools

Site Tools

Trace:
wiki:server_error_in_oma_application

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision		Previous revision
wiki:server_error_in_oma_application [2017/11/06 03:16] – created wikiadminwiki:server_error_in_oma_application [2017/11/06 03:44] (current) – external edit 127.0.0.1
Line 1: Line 1:
 ======Server Error in OMA Application====== ======Server Error in OMA Application======
  
-When you try to access Outlook Mobile Access on the Exchange 2003 Server at http:// serverIP/oma/, you may receive the following error message:+When you try to access Outlook Mobile Access on the Exchange 2003 Server at <nowiki>http:// serverIP/oma/,</nowiki> you may receive the following error message:
  
-!~~#FF0000:Server Error in '/OMA' Application.~~+  Server Error in '/OMA' Application.
  
-~~#FF0000:''Access to the path "C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\Temporary ASP.NET Files\oma\55aaeb43\5ef66257" is denied.'' ~~+  Access to the path "C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\Temporary ASP.NET  
 +  Files\oma\55aaeb43\5ef66257" 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. +**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 "C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\Temporary ASP.NET Files\oma\55aaeb43\5ef66257" is denied. +**Exception Details:** System.UnauthorizedAccessException: Access to the path "C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\Temporary ASP.NET Files\oma\55aaeb43\5ef66257" 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. +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.
  
 To grant ASP.NET write access to a file, right-click the file in Explorer, choose "Properties" and select the Security tab. Click "Add" to add the appropriate user or group. Highlight the ASP.NET account, and check the boxes for the desired access. To grant ASP.NET write access to a file, right-click the file in Explorer, choose "Properties" and select the Security tab. Click "Add" to add the appropriate user or group. Highlight the ASP.NET account, and check the boxes for the desired access.
  
-__Source Error: __+**Source Error:**
  
-^An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.^  +  An unhandled exception was generated during the execution of the current web request. Information regarding  
 +  the origin and location of the exception can be identified using the exception stack trace below.
  
-__Stack Trace:__ +**Stack Trace:**
  
-^{UnauthorizedAccessException: Access to the path "C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\Temporary ASP.NET Files\oma\55aaeb43\5ef66257" is denied.} +  {UnauthorizedAccessException: Access to the path "C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\Temporary  
-   System.IO.__Error.WinIOError(Int32 errorCode, String str) +393 +  ASP.NET Files\oma\55aaeb43\5ef66257" is denied.} 
-   System.IO.Directory.InternalCreateDirectory(String fullPath, String path) +632 +  System.IO.__Error.WinIOError(Int32 errorCode, String str) +393  
-   System.IO.Directory.CreateDirectory(String path) +195 +  System.IO.Directory.InternalCreateDirectory(String fullPath, String path) +632  
-   System.Web.Compilation.PreservedAssemblyEntry.DoFirstTimeInit(HttpContext context) +85 +  System.IO.Directory.CreateDirectory(String path) +195  
-   System.Web.Compilation.PreservedAssemblyEntry.EnsureFirstTimeInit(HttpContext context) +97 +  System.Web.Compilation.PreservedAssemblyEntry.DoFirstTimeInit(HttpContext context) +85  
-   System.Web.Compilation.PreservedAssemblyEntry.GetPreservedAssemblyEntry(HttpContext context, String virtualPath, Boolean fApplicationFile) +29 +  System.Web.Compilation.PreservedAssemblyEntry.EnsureFirstTimeInit(HttpContext context) +97  
-   System.Web.UI.TemplateParser.GetParserCacheItemFromPreservedCompilation() +91 +  System.Web.Compilation.PreservedAssemblyEntry.GetPreservedAssemblyEntry(HttpContext context, String  
-   System.Web.UI.TemplateParser.GetParserCacheItemInternal(Boolean fCreateIfNotFound) +178 +  virtualPath, Boolean fApplicationFile) +29  
-   System.Web.UI.TemplateParser.GetParserCacheItemWithNewConfigPath() +125 +  System.Web.UI.TemplateParser.GetParserCacheItemFromPreservedCompilation() +91  
-   System.Web.UI.TemplateParser.GetParserCacheItem() +99 +  System.Web.UI.TemplateParser.GetParserCacheItemInternal(Boolean fCreateIfNotFound) +178  
-   System.Web.UI.ApplicationFileParser.GetCompiledApplicationType(String inputFile, HttpContext context, ApplicationFileParser& parser) +171 +  System.Web.UI.TemplateParser.GetParserCacheItemWithNewConfigPath() +125  
-   System.Web.HttpApplicationFactory.CompileApplication(HttpContext context) +43 +  System.Web.UI.TemplateParser.GetParserCacheItem() +99  
-   System.Web.HttpApplicationFactory.Init(HttpContext context) +485 +  System.Web.UI.ApplicationFileParser.GetCompiledApplicationType(String inputFile, HttpContext context,  
-   System.Web.HttpApplicationFactory.GetApplicationInstance(HttpContext context) +170 +  ApplicationFileParser& parser) +171  
-   System.Web.HttpRuntime.ProcessRequestInternal(HttpWorkerRequest wr) +414^+  System.Web.HttpApplicationFactory.CompileApplication(HttpContext context) +43  
 +  System.Web.HttpApplicationFactory.Init(HttpContext context) +485  
 +  System.Web.HttpApplicationFactory.GetApplicationInstance(HttpContext context) +170
  
--------------------------------------------------------------------------------- +  System.Web.HttpRuntime.ProcessRequestInternal(HttpWorkerRequest wr) +414
-__Version Information:__ Microsoft .NET Framework Version:1.1.4322.2300; ASP.NET Version:1.1.4322.2300 +
  
------------------------------------------------------------------+----------------------------  
 +**Version Information:** Microsoft .NET Framework Version:1.1.4322.2300; ASP.NET Version:1.1.4322.2300
  
-__To Resolve the problem so that this error message will not appear and OMA displays correctly.__+-------------------------
  
-See: [http://support.microsoft.com/kb/818486|http://support.microsoft.com/kb/818486] and reprinted in part below.+**To Resolve the problem so that this error message will not appear and OMA displays correctly.** 
 + 
 +See: [[http://support.microsoft.com/kb/818486]] and reprinted in part below. 
 Article ID: 818486 - Last Review: October 25, 2007 - Revision: 2.4 Article ID: 818486 - Last Review: October 25, 2007 - Revision: 2.4
  
Line 54: Line 60:
 Note: A configuration where Exchange Server 2003 is installed on a domain controller is sometimes referred to as a onebox configuration. Note: A configuration where Exchange Server 2003 is installed on a domain controller is sometimes referred to as a onebox configuration.
  
-__To resolve this problem, use the ASP.NET IIS Registration Tool (Aspnet_regiis.exe) to reset the ASP.NET ACLs. To run Aspnet_regiis.exe, follow these steps:__+**To resolve this problem, 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. 1. On the domain controller, click Start, and then click Run.
  
-2.  In the Open box, type cmd, and then click OK.+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.+3. Type cd drive:\Windows\Microsoft.NET\Framework, where drive is the drive that Windows is installed on, and then press ENTER.
  
-^CORRECTION to Support Article:  Instead Type __cd\Windows\Microsoft.NET\Framework__, and then press enter.^ +  CORRECTION to Support Article: Instead Type cd\Windows\Microsoft.NET\Framework,  
-4.  Type dir, and then press ENTER.+  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.+4. Type dir, and then press ENTER.
  
-6.  Type cd VersionFolderName, where VersionFolderName is the folder that you noted in step 5, 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.
  
-^CORRECTION to Support Article:  Instead Type __cd\Windows\Microsoft.NET\Framework\v1.1.4322__ (if that is your .NET version number) and then press ENTER.+6. Type cd VersionFolderName, where VersionFolderName is the folder that you noted in step 5, and then press ENTER.
  
-(Familiarity with MS DOS command line directory navigation is a plus.)^+  CORRECTION to Support Article: Instead Type 
 +  cd\Windows\Microsoft.NET\Framework\v1.1.4322 (if that is your .NET version number) 
 +  and then press ENTER. 
 +   
 +  (Familiarity with MS DOS command line directory navigation is a plus.)
  
-7.  Type aspnet_regiis.exe -i, and then press ENTER.+7. Type aspnet_regiis.exe -i, and then press ENTER.
  
---------------------------+----------
  
 To work around this problem, install Exchange Server 2003 on a server that is running Windows 2000 in the following sequence: 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. +1. Install Windows 2000.  
-2.  Promote the server to the role of domain controller. +2. Promote the server to the role of domain controller.  
-3.  Install the .NET Framework. +3. Install the .NET Framework.  
-4.  Install Exchange Server 2003.+4. Install Exchange Server 2003.
  
 To work around this problem, install Exchange Server 2003 on Windows Server 2003 in the following sequence: To work around this problem, install Exchange Server 2003 on Windows Server 2003 in the following sequence:
  
-1.  Install Windows Server 2003. +1. Install Windows Server 2003.  
-2.  Promote the server to the role of domain controller. +2. Promote the server to the role of domain controller.  
-3.  Install ASP.NET. +3. Install ASP.NET.  
-4.  Install Exchange Server 2003.+4. Install Exchange Server 2003.
  
-------------------------+-------- 
 After you re-apply ASP.NET to IIS, you will likely receive the following message when you attempt to access and logon to OMA from a web browser. After you re-apply ASP.NET to IIS, you will likely receive the following message when you attempt to access and logon to OMA from a web browser.
  
-^~~#FF0000:Your user account has not been enabled for wireless access. Please contact your system administrator for additional assistance.~~^+  Your user account has not been enabled for wireless access.  
 +  Please contact your system administrator for additional assistance.
  
 We will look at handling this while configuring exchange. We will look at handling this while configuring exchange.
  
-__To fix 'Your user account has not been enabled for wireless access'__, Open Exchange System Manager, expand Global Settings, right-click Mobile Services and select Properties.  On the General Tab, under Outlook Mobile Access, Check the box that states "Enable Outlook Mobile Access, and click the Apply button, and click OK button.+**To fix 'Your user account has not been enabled for wireless access'**, Open Exchange System Manager, expand Global Settings, right-click Mobile Services and select Properties. On the General Tab, under Outlook Mobile Access, Check the box that states "Enable Outlook Mobile Access, and click the Apply button, and click OK button.
  
 Now, when you try to reach OMA from Internet Explorer, you receive the following message: Now, when you try to reach OMA from Internet Explorer, you receive the following message:
  
-^The device type you are using is not supported. +  The device type you are using is not supported.  
-User Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322)^ +  User Agent: Mozilla/4.0 (compatible; MSIE 6.0;  
- +  Windows NT 5.1; SV1; .NET CLR 1.1.4322)
-__You may not want to fix this.__  Your mobile device may have the ability to access OMA without making any additional changes.  However, __to fix this to view the OMA in Internet Explorer (and from certain unsupported devices)__, you merely return to the same Mobile Service Properties, and on the General Tab click the checkbox that states "Enable Unsupported Devices" and click Apply and click OK.+
  
-Go test it now from IE.  Then come back and disable the access from Unsupported Devices like IE.+**You may not want to fix this.** Your mobile device may have the ability to access OMA without making any additional changes. However, **to fix this to view the OMA in Internet Explorer (and from certain unsupported devices)**, you merely return to the same Mobile Service Properties, and on the General Tab click the checkbox that states "//Enable Unsupported Devices//" and click Apply and click OK.
  
 +Go test it now from IE. Then come back and disable the access from Unsupported Devices like IE.
wiki/server_error_in_oma_application.1509938192.txt.gz · Last modified: 2017/11/06 03:16 by wikiadmin