FIX: Archive of Analysis Services Database Fails with Overflow and CabArc.exe Failed Errors (327170)



The information in this article applies to:

  • Microsoft SQL Server 2000 Analysis Services

This article was previously published under Q327170
BUG #: 13628 (Plato7x)

SYMPTOMS

When you try to archive an Analysis Services database that contains a large number of data files (greater than 32 KB), the archive fails. The archive log will have the following messages:

Archiving database <database name> from server <Server Name>.
Saving repository.
Creating .cab File: <FileName>
Overflow
Cabarc.exe failed.
					

CAUSE

The Analysis Services archive utility stores the file count in a signed integer value that results in a maximum file count of 32,767. In heavily partitioned implementations of Analysis Services, it is possible for the number of files to be greater than the 32 KB limitation.

RESOLUTION

To resolve this problem, obtain the latest service pack for Microsoft SQL Server 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

290211 INF: How To Obtain the Latest SQL Server 2000 Service Pack

NOTE: The following hotfix was created before the release of Microsoft SQL Server 2000 Service Pack 3.

The English version of this fix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
   Date         Time    Version     Size              File name
   -------------------------------------------------------------------

   07/31/2002   14:28   8.0.0.668   9,613,888 bytes   Msmdsgn80.dll 
				
NOTE: Because of file dependencies, the most recent hotfix or feature that contains the files may also contain additional files.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
This problem was first corrected in Microsoft SQL Server 2000 Service Pack 3.

Modification Type:MajorLast Reviewed:6/30/2004
Keywords:kbbug kbfix kbSQLServ2000preSP3fix kbSQLServ2000sp3fix KB327170