Solution to Errno:7 in MaxL for Essbase Studio redeployment scripts

Question

This is an answer to an archived forum post that I found via a Google search.  The forum post no longer accepts replies.  The forum post contained an unanswered question about how to resolve "Errno:7" in MaxL in release 11.1.2.3 when trying to redeploy an outline through Essbase Studio.
I encountered the same error in a client environment and could not find any resolution or references to this in the Knowledge Base, patches, release notes, etc.
I wanted to post the resolution that worked for me, in case someone else encounters Errno:7 in MaxL.
In this particular instance, the MaxL "deploy outline" script worked fine until we upgraded 11.1.2.1 to 11.1.2.3.  After upgrading, we could still connect to the Essbase Agent via MaxL, but the "deploy outline" script fails with "Not able to connect to BPM Server. Errno:7" and "BPM Connect Status: Error".  No evidence of the error could be found in the logs for the Essbase Agent, the Essbase application in question, and Essbase Studio.  Using the Essbase Studio Console to redeploy the outline worked fine.
The root cause was learned when we ran the EPM Registry Editor to view a registry report.  The report showed that while Essbase Studio was correctly listening on port 5300, the web port was still on the old 11.1.2.1 port (9080) instead of the port 11.1.2.3 was expecting (12080).  This port number is not exposed to us if we go back into the EPM Configuration tool and drill down to Essbase Studio.  The config tool only allows us to change the relational database connection and the "datafiles" folder location.  Running "netstat -na" from the command prompt confirmed that the server was listening to 9080 instead of 12080.
Using the EPM Registry Editor command-line tool to update the port's property value and then restarting the Essbase Studio service fixed the issue for us.  If you read the Essbase Studio documentation as I did, you may have had the impression that editing a file on the server would do the trick.  But the Readme for Essbase Studio 11.1.2.3 provides the real answer:
"Starting in Release 11.1.2.3, the following Essbase Studio server properties are stored in the
Oracle Hyperion Shared Services Registry database.
The 11.1.2.3 Oracle Essbase Studio User's Guide describes all server properties as being in the
server.properties file. To view or modify the settings in Shared Services Registry, use the
epmsys_registry utility, described in the Oracle Enterprise Performance Management System
Deployment Options Guide."
I hope this helps and good luck!

Answer 1

Hi Santy,
Here's the original forum post: Essbase Studio Cube deployment via MaxL error
In that thread, someone had questioned if an 11.1.2.2 MaxL client could still connect and bypass the error.  I happened to have a laptop handy with the 11.1.2.2 MaxL client installed on it and was able to test that.  The 11.1.2.2 MaxL client got the error as well.
In my 11.1.2.3 environment I tried both the 32-bit and 64-bit MaxL runtimes and verified both were on the latest available Essbase patch set for 11.1.2.3.  Again, they still got the Errorno:7 message.  The problem was only fixed after updating the "server.httpPort" property value via the epmsys_registry tool.
Regards,
- Dave