Art of BI: Hyperion 11.1.2 Namespace Communication Error

By | In Art of BI, Big Data, Business Intelligence | December 04th, 2010

I’ve been working a bit with the new Hyperion Disclosure Management tools due to some requirements for efficient electronic filing. In doing so several additional components must be installed on top of the Foundations suite. Several new services are created on the environment and they are mainly self-explanatory. However, the other day I was getting performance issues and wasn’t using Disclosure Management so I decided to just drop a few services from which I recalled installed with Hyperion Disclosure Management. I then attempted to sign into Hyperion Workspace and I got a Namespace Communication Error.

[sourcecode language=’xml’] URI: http://demoepm1112:19000/raframework/browse/dyn

XML Returned:


Art of BI: Weblogic Bridge Message<br />

Failure of server APACHE bridge:


No backend server available for connection: timed out after 10 seconds or idempotent set to OFF.


Build date/time: Oct 27 2009 13:34:24


Change Number: 1013



[/sourcecode]

What’s even stranger is that once I saw the error, clicked the OK button to close the error and began some troubleshooting, when I returned to my Workspace login page (5 or so minutes later) I was logged in but several menu features, etc. in Workspace didn’t work properly. I continued to troubleshoot and ultimately after reading the detail error message underneath the original Namespace Communication Error prompt, I see the URI is referencing the raframework (http://:19000/raframework/browse/dyn). This happened to be one of the services I had shutdown trying to increase performance of my server.

Solution

Ultimately I started thetwo RA Frameworkd Services. Then I did a quick restart on the Oracle Process Manager and Weblogic Managed Server. This seemed to fix the issue and upon refresh of the Workspace login page, I no longer saw the error message.

Cause

Many people believe 11.1.2 is a GA Beta Release and sure it has its bugs but the only conclusion I can draw here is that because I added a new application and a new set of services, Workspace now sees them as dependencies and attempts to load those new services (i.e.: Disclosure Management) for some level of reference into Workspace when logging in. Once it can’t find it via the OPMN it throws an error but the error isn’t critical and that maybe why Workspace continued to log me in after a few minutes even though the error showed up.  I’ll keep investigating this but for now just starting all configured services in the EPM environment that you have configured, etc. should prevent this issue.

Contact Us
Christian Screen
Christian is an innovator in analytics and data warehousing design, best practices, and delivery. With more than fifteenyears of decision support and data warehousing with key experiences at Office Depot HQ, Sierra-Cedar, and Capgemini, he oversees the Oracle Analytics Practice which includes the technical development and delivery of Oracle BI collaboration software, data warehouse solutions, Oracle BI/EPM projects, and packaged analytics solutions at Datavail.

Leave a Reply

Your email address will not be published.
Required fields are marked (*).

1 thought on “Art of BI: Hyperion 11.1.2 Namespace Communication Error”
  1. I have seen this error pop up when there is no proper temporary folder allocated or no proper access to the temporary folder on the machine the services are installed. By changing the temp folder in the registry settings to a folder where everyone has full access seemed to resolve this issue.nJas. Y.