Calc Manager Connection refused: connect

We had a up and running environment, it was compact deployment running on 9000 port, later we redeployed all the components to individual ports. Everything was working fine, we were able to access all the components however when were are trying to access planning applications from Calc Manager were are getting following error:
http://<Server>:9000/HyperionPlanning/servlet/HspAppManagerServlet:
Connection refused: connect

Though we can access calc manager from workspace on 19000 port, we can see all three nodes under Calc Manager, but when we are expanding Planning node in calc manager we were getting above error in the Msg Box (as information), but after clicking ok, we can access all the rules listed under the planning applications.

Error was obvious its still trying to connect to planning at 9000 but planning can be accessed at 19000 or 8300 port! How can we make calc manager to check planning at 8300/19000 port not 9000.

Here are the parts of Calc Manager logs:

<oracle.EPMAWT.DATASOURCE.com.hyperion.awb.web.datasource.Service> <BEA-000000> <Connection refused: connect  java.net.ConnectException: Connection refused: connect

<oracle.EPMAWT.UTIL.com.hyperion.awb.web.util.RegistryUtil> <BEA-000000> <java.net.ConnectException: Connection refused: connect
com.hyperion.awb.web.common.BaseServiceException: java.net.ConnectException: Connection refused: connect

Now the solution part, what can cause this issue, from where its picking 9000 port of planning not 8300, I guess most of you know the answer its EPM Registry. So the first step will be to exporting registry and checking planning entry. To export registry we have a simple command that we need to run on the foundation server, its epmsys_registry.bat, can be found at below location:
<MIDDLEWARE_HOME>\user_projects\epmsystem1\bin


PLANNING_LWA (LOGICAL_WEB_APP): Object ID:   bee6d6feba94f924497fb41413d5e36a41dS7789
It was showing two childeren:
1. PLANNING_WEBAPP (PLANNING_WEBAPP): Object ID:   bee6d6feba94f924497fb41413d5e36a41S7782
2. PLANNING_WEBAPP (PLANNING_WEBAPP): Object ID:   bee6d6feba94f924Sf302b97140875f1ed3S6b01

Ofcourse one of them was pointing to 9000 and other one to 8300, all we need to do was to delete 9000 entry and run the registry clean up (about registry clean up) restart services and you are done.

So,
1. Port Issues -> Check EPM Registry!.
2. There is no harm in cleaning up the registry once in a while!

Cheers..!!
Rahul S.

Comments

Popular posts from this blog

Multiple Navigation Flows are Active

The Member Does Not Exists For The Specified Cube

"Smart View handled an unknown exception thrown by Microsoft Office" Error on Vista, Windows 7, Windows 2008