I’ve recently been installing Oracle Essbase on my laptop in order to do some local development activities with Essbase Studio and – due to certain problems on my machine – I needed to perform this installation a couple of times (the database that I’m using as a repository is SQL Server 2008 which, so far, has not caused any problems being used with EPM).
Once I had eventually installed the software and configured the Shared Services and Essbase components, I went to start-up the Essbase Studio Server service and it kept bombing out.
So, I thought I would stick a pause statement into startServer.bat file located in the D:\Hyperion\products\Essbase\EssbaseStudio\Server folder (replace D:\Hyperion with your own local installation folder) to see what was going on.
“Pause” duly inserted, I re-ran startServer.bat and discovered the “SEVERE Cannot initialize catalog storage” error:

Incidentally, the error can also be found in the server.log file which can be found at D:\Hyperion\logs\esbstudio
So, consider me confused – the configuration process completed OK when it was performing the database configuration tasks but Essbase Studio Server cannot connect to the SQL Server repository.
First place I had a look was in the server.properties file (D:\Hyperion\products\Essbase\EssbaseStudio\Server) which looks like:
catalog.autoinit=true
catalog.username=oraepmsys
catalog.url=sqlserver\://SERVERNAME\:1433
catalog.password=ihhjCZwhjdcjY37d1efg62A\=\=
catalog.db=OracleEPM.dbo
server.hss.bpmApplication=BPM\:79100
In this I checked:
catalog.username - Fine.
catalog.db - OK (I have had problems with that in the initial release of Essbase Studio where the dbo was placed before the server name)
catalog.url - Was the server name and I tried switching it to localhost or the IP address and re-running startServer.bat; still no luck.
With these options exhausted, I thought I should check whether the user being used to connect to the database had the default dbo schema.
Turns out it did but while I was checking this I spotted something, the user had no “Default database” value defined.
This was because I had:
- Created a database (oraepm) and user (oraepmsys)
- Assigned the oraepmsys user to the oraepm database and set the users “Default database” to be oraepm
- Installed and configured Essbase
- Uninstalled Essbase
- Deleted the original repository database
- Created a new database (oracleepm) and mapped the oraepmsys user to the new database
- Re-installed Essbase
When I deleted the oraepm database, the oraepmsys users default database value was also removed.
I then set the oraepmsys user to have a default database and then tried again to start the Essbase Studio Server which subsequently started successfully.

Obviously, this gives rise to a question as to how the Essbase Studio server handles connections given that Shared Services had no qualms in obtaining a connection to the database.