Occasionally, I see a friendly error when attempting to refresh or deploy a Planning application that indicates there are active users on the Essbase application.
This error is often adjacent to the error, “Date &Time]Starting Cube Create/Refresh…[Date &time]: Cannot restructure.
There are other active users on database [%s]
[Date&tim]: An Exception occurred during Application deployment.:
The Hyperion Essbase operation failed with an error code: 1013101.”
The obvious cause is someone has an exclusive lock on the BSO database that is preventing Essbase from processing Planning’s request. The typical remedy is to wait it out. Once the existing lock is released, we can attempt to refresh again.
Rarely, I still see this error in Planning when I attempt to refresh even after confirming there are no active sessions. As much as I hate to admit it, the path of least resistance to fix this is to stop the EPM services then completely restart the Essbase server.
I have found another method to overcome this without having to restart. Using TCPVIEW (available from Microsoft at https://technet.microsoft.com/en-us/library/bb897437.aspx), I am able to see all inbound TCP connections to the Essbase server. Once I confirm users are inactive or logged out completely, I sort the connections shown in TCPVIEW by the remote address and disconnect all of the ones inbound from the Planning server. The disconnect is much faster than a system restart. The impact to the user community is the requirement to close and relaunch the Planning application from Workspace.
1) when i add a member and refreshing the database, its throwing me this error”check your network connection”. without adding members in the cube the database refresh is happing.
please help me out on this .