Hi John,

What is the version of SQL Server (Service Pack)? Such issues tend to be
complex and take up extensive research time. I'd like to set your
expectations that it may take a while for us to help you narrow down the
problem.

I would like you to provide more information so that we can perform further
research.
1. I would like to know if you are archiving a database on a remote server.
If so, please describe it in detail.

2. Please make sure that the System logon account is in the local
Administrators group and OLAP Administrators group.

3. Please check the permissions of the folder where the database stored.
Make sure it can be access by your logon account freely. These folders
usually are:
C:\Program Files\Microsoft Analysis Services\Data and C:\Program
Files\Microsoft Analysis Services\Data\<Database Name>

4. Please perform the following steps to try to copy and paste this
problematic database to create a new database.
Right-click the problematic database--> Select the Copy
command-->Right-click the SQL Server instance-->Select the Paste
command-->Type the name of the new database in the Duplicate name
dialog-->Press OK.

Can you create a new database by performing the above steps? If so, please
try to archive this new database again. If not, did any error occur? Please
provide the detail error message.

I am standing by for your response.

Regards,

Michael Shao
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.

Hi John,

Thanks for your feedback. It is normal that the .CAB file is smaller the
original one, because the copied database does not include the data in the
original database. I suspect that there is something wrong in the folder
where the problematic database stored. I would like you to provide more
following information so that I can perform further research.

1. Please perform these steps below:
a. Make sure stop the MSSQLServerOLAPService Service.
b. Rename this folder C:\Program Files\Microsoft Analysis
Services\Data\<DatabaseName> (The DatabaseName here is the name of the
problematic database)
c. Start the MSSQLServicerOLAPService Service.
d. In the Analysis Servers, try to archive the problematic database.

Can you archive the database?

Note: After finishing the above test, please stop the
MSSQLServicerOLAPService Service-->delete the new folder with the same name
of problematic database-->Change the original folder name back-->Restart
the Service. In other words, please let everything be involuted.

2. The information provided by you from Archive Log is insufficient. Please
provide the complete Archive Log. You can send it to me at
v-yshao (AT) microsoft (DOT) com.

3. How is the volume of processing the problematic database? How long will
it take? We may eventually recommend you to process the problematic
database again. If the volume of the processing is very large, we need to
find on which file this error occurred and process this portion of the
problematic database.

I am standing by for your response.

Regards,

Michael Shao
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.

Hi Michael,

Sorry for the delayed response...I was out of the office
yesterday.

It takes around 15 hours to run a full process on the
database.

We have been running a full process once a week for this
database. A co-worker of mine executed the full process
last night and it finished earlier today.

When the full process finished I was able to succesfully
archive the database with no errors!

It looks like the problem just disapeared after the full
process. Do you have any idea why this could be?

I would appreciate any feedback you may have.

Thanks again,

John

Hi John,

Thanks for your response. I am glad that the error disappeared. According
to my experience, this error regarding archiving database is seldom to
occur. It is hard to find out the exact reason inducing this error.
However, according to the error message, I am sure that there is something
wrong with the data of the database. Processing the problematic database
always can correct these kinds of problems.

Also, I worried about the volume of processing the problematic database. If
the volume is very large, we will have to find the problematic file and
process the portion of the problematic database. This method is complex.
Fortunately, the volume is not very large and we correct the problem via
processing the full database.

I hope this explanation is clear. Please let us know if you need further
assistance on this issue.

Regards,

Michael Shao
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.

Hi Michael,

So that means our data was bad before the full process? If
I notice this behavior in the future, do you recommend
doing a full process to fix the bad data immediately?

Thanks,

John

Hi John,

Thanks for your response. According to the error message, there is most
likely something wrong with the data file. Generally, processing can
resolve this kind of issue. Whether or not we can process the full database
depends on the volume of processing. If the processing time is very
important, we need to find the problematic data file and process the
portion of the problematic database to reduce the processing time.
Otherwise, processing the full database is a good alternative.

Please let me know if this solves your problem or if you would like further
assistance.
Regards,

Michael Shao
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights

OK. If I happen to come accross this error in the future I
will run a full process on the database.

Thank you for all of your help with this Michael!

John