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 revision | ||
wiki:server_error_in_oma_application [2017/11/06 03:19] – wikiadmin | wiki: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/ | + | When you try to access Outlook Mobile Access on the Exchange 2003 Server at < |
- | < | + | |
- | ~~# | + | |
+ | | ||
- | __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 | + | **Exception |
- | 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 < |
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 | + | **Source |
- | ^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 | + | **Stack |
- | ^{UnauthorizedAccessException: | + | |
- | | + | |
- | | + | System.IO.__Error.WinIOError(Int32 errorCode, String str) +393 |
- | | + | System.IO.Directory.InternalCreateDirectory(String fullPath, String path) +632 |
- | | + | System.IO.Directory.CreateDirectory(String path) +195 |
- | | + | System.Web.Compilation.PreservedAssemblyEntry.DoFirstTimeInit(HttpContext context) +85 |
- | | + | System.Web.Compilation.PreservedAssemblyEntry.EnsureFirstTimeInit(HttpContext context) +97 |
- | | + | System.Web.Compilation.PreservedAssemblyEntry.GetPreservedAssemblyEntry(HttpContext context, String |
- | | + | |
- | | + | System.Web.UI.TemplateParser.GetParserCacheItemFromPreservedCompilation() +91 |
- | | + | System.Web.UI.TemplateParser.GetParserCacheItemInternal(Boolean fCreateIfNotFound) +178 |
- | | + | System.Web.UI.TemplateParser.GetParserCacheItemWithNewConfigPath() +125 |
- | | + | System.Web.UI.TemplateParser.GetParserCacheItem() +99 |
- | | + | System.Web.UI.ApplicationFileParser.GetCompiledApplicationType(String inputFile, HttpContext context, |
- | | + | |
- | | + | 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.__ | + | ------------------------- |
- | See: [http:// | + | **To Resolve the problem so that this error message will not appear and OMA displays correctly.** |
+ | |||
+ | 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 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, | + | **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. | ||
- | 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: | + | 3. Type cd drive: |
- | ^CORRECTION to Support Article: | + | |
- | 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, | + | 5. Note the folder |
- | ^CORRECTION to Support Article: | + | 6. Type cd VersionFolderName, |
- | (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. | ||
+ | |||
+ | | ||
- | 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.~~^ | + | |
+ | | ||
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; | + | User Agent: Mozilla/4.0 (compatible; |
- | + | | |
- | __You may not want to fix this.__ | + | |
- | Go test it now from IE. Then come back and disable | + | **You may not want to fix this.** Your mobile device may have the ability to access |
+ | Go test it now from IE. Then come back and disable the access from Unsupported Devices like IE. |
wiki/server_error_in_oma_application.1509938341.txt.gz · Last modified: 2017/11/06 03:19 (external edit)