Essbase/MaxL error: Error (1013204) Client Commands are currently not being accepted.

We were trying to execute a shell script which in turn runs a MaxL script to load data to our ASO cube.
As soon as we run the script, we face an error:

Error: 1013204 Client commands are currently not being accepted.

The clear script which was run before executing this Maxl script was at the end of completion/the session was still in process.
Restarting the application and then executing the script cleared the error.

Waiting for the other process to complete, and then going ahead with the next script should be helping in avoiding such error. Sometimes there is some erroneous lock on the application.
So restarting the application should sort this one out.

Database clear unsuccessful error in EAS

When trying to clear the data (mostly as a part of Defragmentation), we encounter an error prompting that the database clear was unsuccessful.

The clearing of data from the EAS sometimes throws an error as above.
Sometimes, we are also not able to see the Runtime parameters in the statistics tab for the cube.

Check if any changes are being made at that time by any other person.
Need to be aware in case any cache parameters settings are being changed.

A simple restart of the application and then trying to clear the data would be successful in this case.

Unable to validate Partition in EAS

Sometimes when trying to validate the Partition, it errors out saying:  Partition definition is not valid: []

And the typical error message can be:

Typically this happens when there any data movements scripts running in the background or their sessions are still in progress.
Verify that no Data movement scripts are being executed and then try to validate the partition.

We have encountered this mostly for Replicated Partitions and the solution helped every time.