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

Both sides previous revisionPrevious revision
Next revision		Previous revision
wiki:server_error_in_oma_application [2017/11/06 03:33] – wikiadminwiki:server_error_in_oma_application [2017/11/06 03:44] (current) – external edit 127.0.0.1
Line 5: Line 5:
   Server Error in '/OMA' Application.   Server Error in '/OMA' Application.
  
-  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.
Line 15: Line 16:
 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.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+  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.+**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. +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 55: 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.
Line 63: Line 68:
 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,  
 +  and then press enter. 
 4. Type dir, and then press ENTER. 4. Type dir, and then press ENTER.
  
Line 70: Line 77:
 6. Type cd VersionFolderName, where VersionFolderName is the folder that you noted in step 5, and then press ENTER. 6. Type cd VersionFolderName, where VersionFolderName is the folder that you noted in step 5, and then press ENTER.
  
-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. +  CORRECTION to Support Article: Instead Type 
-(Familiarity with MS DOS command line directory navigation is a plus.)+  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.
Line 94: Line 104:
 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.
  
-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. User Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322)+  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)
  
-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.+**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. Go test it now from IE. Then come back and disable the access from Unsupported Devices like IE.
wiki/server_error_in_oma_application.1509939180.txt.gz · Last modified: 2017/11/06 03:33 by wikiadmin