Unable To Obtain Connection To Hyperion Essbase

Unable To Obtain Connection To Hyperion Essbase

This issue come from the Planning Webform and Smart View as shown below.

1. When accessing a Planning Web Form, the following error appears:  "The data form 'data form name' is invalid, Unable to obtain a connection to Hyperion Essbase."
2. When using Smart View and connecting to Planning, the following error appears: "Cannot open cube view. Essbase Error (1019038): DB file is missing."

Possible Causes for this issue are

1. Deletion of the dbname.db from the application's three databases.
2. Extra Essbase server processes that are still running and should be stopped.
3. An unresponsive application that needs a restart.
4. An unresponsive Essbase server.
5. Essbase network configuration is not set correctly for your environment.

Solution #1
This solution is based upon the additional error message "Cannot open cube view. Essbase Error (1019038): DB file is missing."  Please check for the application file, dbname.db, and make sure it exists under the application directory.  To check, do the following:

1. Go to the server where the Essbase server is installed. Locate the dbname.db in the ARBORPATH/app/appname/dbname/ directory.
2. Once you are at the dbname folder, if the dbname.db is missing, restore a copy of dbname.db from backup or rename your dbname.dbb to dbname.db.  The dbname.dbb is located in the same directory, ARBORPATH/app/appname/dbname/.  Do this for the rest of the databases under your appname folder if they are missing the dbname.db.
3. Restart all services.
4. Refresh Planning to Essbase.

Solution #2
Sometimes there are Essbase server processes that are running that should not be.  Confirm this by stopping all Essbase related activities.  If you still see an Essbase process running in Task Manager, follow these steps:

1. From Task Manager, select End Task on the Essbase process, ESSSVR.exe.  
2. When there are multiple Essbase processes in Task Manager and you don't know which one to End Task,  end all Essbase processes.  If you know that no one is running any Essbase related processes, then you are safe to end the processes.

Note:  Once the Essbase process has ended, you do not have to restart services.

Solution #3
In the case of an unresponsive application, you simply stop and start your Planning application from the Essbase Administration Services console.

1. From the EAS console, go to the application.
2. Right-click on the application and select Stop.
3. Right-click on the application again, and select Start.
4. If login still fails with the same error then:

Solution #4
An unresponsive Essbase server can cause this problem.  This communication problem with Planning and Essbase can be resolved by simply restarting the Essbase and Planning servers.

Solution #5
You can set your network settings for Essbase in the Essbase.cfg file to resolve your Essbase connection problem. . 
To set NETDELAY and NETRETRYCOUNT:
If you do not have an $ARBORPATH/bin/essbase.cfg file on your server computer and client computer in the $ARBORPATH\bin directory, create one using a text editor.

1. In the $ARBORPATH/bin/essbase.cfg file on both the server and client computer, set NETDELAY to a default value of 200.
2. In the $ARBORPATH/bin/essbase.cfg file on both the server and client computer, set NETRETRYCOUNT to a default value of 300.
3. Stop and restart Essbase Server.

Note:  You want to increase it until your issue is resolved, or until you have reached a maximum combined total of around 10 minutes for both values

Thanks.