wiki:server_error_in_oma_application
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
wiki:server_error_in_oma_application [2017/11/06 03:29] – wikiadmin | wiki:server_error_in_oma_application [2017/11/06 03:44] – wikiadmin | ||
---|---|---|---|
Line 3: | Line 3: | ||
When you try to access Outlook Mobile Access on the Exchange 2003 Server at < | When you try to access Outlook Mobile Access on the Exchange 2003 Server at < | ||
- | Edit Section | ||
Server Error in '/ | Server Error in '/ | ||
+ | Access to the path " | ||
+ | Files\oma\55aaeb43\5ef66257" | ||
- | Access to the path "C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\Temporary ASP.NET Files\oma\55aaeb43\5ef66257" | + | **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: | + | **Exception Details:** System.UnauthorizedAccessException: |
- | + | ||
- | Exception Details: System.UnauthorizedAccessException: | + | |
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 < | 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 < | ||
Line 17: | Line 16: | ||
To grant ASP.NET write access to a file, right-click the file in Explorer, choose " | To grant ASP.NET write access to a file, right-click the file in Explorer, choose " | ||
- | 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 |
+ | | ||
- | Stack Trace: | + | **Stack Trace:** |
- | {UnauthorizedAccessException: | + | |
- | System.IO.__Error.WinIOError(Int32 errorCode, String str) +393 | + | |
- | 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, | + | 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 | + | |
- | 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& | + | 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 | + | |
+ | 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: | + | **Version Information: |
------------------------- | ------------------------- | ||
- | 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:// | + | See: [[http:// |
Article ID: 818486 - Last Review: October 25, 2007 - Revision: 2.4 | Article ID: 818486 - Last Review: October 25, 2007 - Revision: 2.4 | ||
Line 57: | 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, | + | **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, |
1. On the domain controller, click Start, and then click Run. | 1. On the domain controller, click Start, and then click Run. | ||
Line 65: | Line 68: | ||
3. Type cd drive: | 3. Type cd drive: | ||
- | CORRECTION to Support Article: Instead Type cd\Windows\Microsoft.NET\Framework, | + | |
+ | | ||
4. Type dir, and then press ENTER. | 4. Type dir, and then press ENTER. | ||
Line 72: | Line 77: | ||
6. Type cd VersionFolderName, | 6. Type cd VersionFolderName, | ||
- | 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. | ||
Line 96: | 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. | + | |
+ | | ||
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', | + | **To fix 'Your user account has not been enabled for wireless access' |
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; | + | |
+ | | ||
+ | | ||
- | 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 " | + | **You may not want to fix this.** Your mobile device may have the ability to access OMA without making any additional changes. However, |
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.txt · Last modified: 2017/11/06 03:44 by 127.0.0.1