Error: "HTTP 404 Errors Received from ASMX Pages after Successful Installation and Configuration
(Doc ID 738756.1)
Last updated on FEBRUARY 21, 2019
Applies to:Hyperion Data Relationship Management - Version 184.108.40.206.00 to 220.127.116.11.101 [Release 9.3 to 11.1]
Microsoft Windows (32-bit)
Microsoft Windows Server 2003
Unable to connect to the server via the DRM client after installation. When trying to access through the VersionMgr.asmx page (which is used to test connectivity from the console) you get an HTTP 404 error (page cannot be displayed).
The IIS logs also show HTTP 401.1 errors (access denied) when a request is made for any of the DRM asmx pages.
Alternatively, you may receive an ASP server error. In order to see what the exact error is, turn off friendly errors in ASP by changing the custom errors mode line in the web.config file for the mdm_ntier folder to <customErrors mode="off"/>. Test again. The following error is then received:
Server Error in '/mdm_ntier' Application.
Description: An error occurred during the compilation of a resource required to service this request. Please review the following specific error details and modify your source code appropriately.
Compiler Error Message: CS0016: Could not write to output file 'c:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files\mdm_ntier\52d3e637\9ccc9081\App_global.asax.8xp3yddc.dll' -- 'Access is denied.'
IIS had been customized in the Windows Server 2003 build used for DRM to use a local admin account rather than Network Service or Local System.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document