Hyperion 11.1.2 Namespace Communication Error

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.

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 framework (http://:19000/raframework/browse/dyn). This happened to be one of the services I had shutdown trying to increase the performance of my server.

Solution

Ultimately I started the two RA Framework 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.