| Modified 01-OCT-2010 | |||||
Applies to:
Hyperion Financial Management - Version: 3.0.4.0.00 to 11.1.1.2.00 - Release: 3.0 to 11.1Hyperion BI+ - Version: 9.0.0.0.00 to 11.1.1.2.00 [Release: 9.0 to 11.1]
Hyperion Reports - Version: 7.0.0.0.00 and later [Release: 7.0 and later]
Information in this document applies to any platform.
Symptoms
'Access Denied' DCOM error messages when connecting with Financial Reporting reports
Error
DCOM got error 'General access denied error'
Other symptoms relating to the same fix when running HFM tasks causing:
Error: "Could not connect to the server"
Or
Error: "Could not connect to any server in the specified cluster"
Cause
In some Windows 2003 SP1/SP2 installations, clients may experience Access Denied issue while connecting from Hyperion Reports, HFM Win32 or HFM Web. The client machine event log will have the followingGeneral access denied error entry:
Microsoft has provided the following workaround to resolve a code issue with their RPC layer by disabling bind time negotiation for security context multiplexing.
To disable bind time negotiation for security context multiplexing, you need to install hotfix Q899148 (http://support.microsoft.com/kb/899148 ).
Solution
To disable bind time negotiation for security context multiplexing, you need to install hotfix Q899148 (http://support.microsoft.com/kb/899148 ).
Contact Microsoft Support directly for the Hot Fix. Will need to be provided an id and password to download and follow steps below:
If running Windows 2003 SP2 you ONLY need apply the below registry steps to ALL HFM and Hyperion Reports/BI+ servers
1. Click "Start", click "Run", type "regedit" (without the quotation marks), and then click "OK"
2. Locate and then click the following registry subkey:
HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\Rpc
3. Click the "Edit" menu, point to "New", and then click "DWORD Value".
4. Type "Server2003NegotiateDisable" (without the quotation marks) as the name of the new DWORD Value
5. Right-click "Server2003NegotiateDisable", and then click "Modify".
6. In the "Value Data" box, type "1", and then click "OK". Note This setting disables the bind time negotiation and multiple transfer syntax negotiation.
7. Quit Registry Editor. Restart the Windows Server 2003-based computer.
NB If Win32 client is not being used, applying Hot Fix to the client machine is not necessary.
Click Start, click Run, type regedit, and then click OK.
Locate the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Ole registry subkey.
Right-click the Ole value, point to New, and then click DWORD Value.
Type ActivationFailureLoggingLevel, and then press ENTER. Double-click ActivationFailureLoggingLevel, type 1 in the Value data box, and then click OK.
Right-click the Ole value, point to New, and then click DWORD Value.
Type CallFailureLoggingLevel, and then press ENTER. Double-click CallFailureLoggingLevel, type 1 in the Value data box, and then click OK.
Restart the DCOM program, and then examine the System log and the Application log for DCOM errors.
Further details can be found at http://support.microsoft.com/kb/892500
GKontos
Comments