Backup on an empty SSAS database hangs I created an SSIS package to iterate through all databases on an SSAS instance. It grabs the DatabaseId using AMO in a vbscript, then generates the XMLA to backup each database. 

Most databases backup with no problems, but when the ForEach gets to one particular database, the Execute Analysis Services DDL Task seems to hang. The .abf file is created, but the SSIS package doesn't seem to get the response that the command is completed. It's like the backup process is stuck on the file.

When I backup the database using SSMS dialogs, the same problem occurs. I verified that other databases backup successfully using this method.

I should note that the database in question is 0.0MB in "estimated" size according to the db properties in SSMS. Is the database truly empty, or could this be a sign of corruption?

Why doesn't the backup process complete? I get no error messages, just a long-running process that does not end. Is there anything I can do to find the root cause?
The backup hangs because the SSAS database is corrupt, which was the result of a forced reboot of the server.

Some questions this raises:

If an SSAS database has an estimated size of 0, does that always indicate a corrupted database?
Are there any other ways to detect SSAS db corruption by using SSMS dialogs or AMO?