Essbase Error (1053025)

Failed to deploy Essbase cube.
Caused by: Failed to build Essbase cube dimension: (CostCenters) .
Caused by: Cannot put olap file object. Essbase Error(1053025): Object [CostCent] already exists and is not locked by user [Sarah@Domain]
Failed to deploy Essbase cube.
Caused by: Failed to build Essbase cube dimension: (CostCenters) .

Caused by: Cannot put olap file object. Essbase Error(1053025): Object [CostCent] already exists and is not locked by user [Sarah@Domain]

This is the error I got on a cube deploy about a month ago.  As non-descript as this error is, it seems EPMA is trying to tell me that the cube is corrupt.

We tried restarting the services.

We tried restarting the servers.

No luck.

I was able to copy the application as a new application and was able to deploy that application with no problem.  I was also able to export all the data in EAS to load into the newly created application.

If anyone has any more info to add on this error, please post your findings.  All I could find online was chirping crickets…

2 comments

  1. Hi, I am receiving the same error tonight and don't know how to resolve it.
    If our consultant replies to my email tonight and his solution works, I will let you know.

    Good luck!

  2. @Mark – This was fixed by going into EAS and unlocking the Rules file mentioned in the error. Essbase Studio didn't remove the lock from the last deploy, so it hung. Finally figured it out yesterday.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s