Microsoft KB Archive/889524

= FIX: You receive an &quot;Unexpected error encountered while updating repository Overflow&quot; error message when you try to restore an OLAP database in SQL Server 2000 Analysis Services =

Article ID: 889524

Article Last Modified on 11/21/2006

-

APPLIES TO


 * Microsoft SQL Server 2000 Analysis Services
 * Microsoft SQL Server 2000 Analysis Services

-



Bug #: 14488 (Plato 7x)



''Microsoft distributes SQL Server 2000 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2000 fix release.''



Article Contents

 * Summary
 * Introduction
 * Issues that are fixed by this hotfix package
 * More Information
 * Service pack information
 * Hotfix information
 * Prerequisites
 * Restart information
 * Registry information
 * Hotfix file information
 * Status
 * References



SUMMARY
This article describes the following about this hotfix release:


 * The issues that are fixed by this hotfix package.
 * The prerequisites for installing the hotfix package.
 * Whether you must restart your computer after you install the hotfix package.
 * Whether the hotfix package is replaced by any other hotfix package.
 * Whether you must make any registry changes.
 * The files that are contained in the hotfix package.

back to the top



Issues that are fixed by this hotfix package
The following issue is fixed in this Microsoft SQL Server 2000 hotfix package:  When you try to restore a Microsoft SQL Server Analysis Server 2000 database, the restore operation fails, and you receive the following error message:

&quot;Unexpected error encountered while updating repository Overflow&quot;



For a list of previous hotfixes, see the &quot;Microsoft SQL Server 2000 Post-Service Pack 3 or Microsoft SQL Server 2000 Post-Service Pack 3a hotfixes&quot; section in the following Microsoft Knowledge Base article:

290211 How to obtain the latest SQL Server 2000 service pack

back to the top



CAUSE
This problem may occur when you use the pipe character (&quot;|&quot;) in the OLAP database object definition.

back to the top



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

290211 How to obtain the latest SQL Server 2000 service pack

Prerequisites

 * Microsoft SQL Server 2000 Service Pack 3 (SP3)

You must have SQL Server 2000 SP3 installed. For information about how to obtain SQL Server 2000 SP3, see the following article in the Microsoft Knowledge Base:

290211 How to obtain the latest SQL Server 2000 service pack

back to the top

Restart information
You do not have to restart your computer after you apply this hotfix.

back to the top

Registry information
You do not have to make any changes to the registry.

back to the top

Hotfix file information
This hotfix contains only those files that are required to correct the issues that this article lists. This hotfix may not contain of all the files that you must have to fully update a product to the latest build.

The English version of this hotfix 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.

SQL Server 2000, 32-bit versions

Date        Time   Version            Size    File name -- 16-Nov-2004 20:15  8.0.989.0       1,380,944  Msdmine.dll 06-Apr-2004 20:25                     18,800  Msmd.h 16-Nov-2004  20:15  8.0.989.0         221,760  Msmdcb80.dll 16-Nov-2004 20:15  8.0.0.989       4,076,096  Msmddo80.dll 16-Nov-2004 20:15  8.0.989.0       1,036,864  Msmdgd80.dll 16-Nov-2004 20:15  8.0.989.0         172,608  Msmdpump.dll 16-Nov-2004 20:15  8.0.0.989       9,642,564  Msmdsgn80.dll 16-Nov-2004 20:15  8.0.989.0       1,847,876  Msmdsrv.exe 16-Nov-2004 20:15  8.0.989.0       1,397,312  Msmdvldm.exe 16-Nov-2004 20:15  8.0.989.0       2,085,456  Msolap80.dll 06-Apr-2004 20:19  8.0.21213.0       352,256  Msvcr71.dll 06-Apr-2004 20:19  2000.80.796.0      57,904  Osql.exe 06-Apr-2004 20:19  2000.80.534.0     127,548  Sqdedev.dll 06-Apr-2004 20:19  2000.80.194.0     180,290  Sqlunirl.dll 16-Nov-2004 19:49  8.0.989.0         446,524  Msmdsgn.rll 16-Nov-2004 18:51  8.0.989.0         213,068  Msolap80.rll

SQL Server 2000, 64-bit version

Date        Time   Version            Size    File name         Platform

16-Nov-2004 22:50  8.0.989.0       5,150,720  Msdmine.dll 06-Apr-2004 20:25                     18,800  Msmd.h 16-Nov-2004  22:50  8.0.989.0       5,533,184  Msmdcb80.dll 16-Nov-2004 22:50  8.0.989.0       5,842,432  Msmdgd80.dll     IA-64 16-Nov-2004 22:50  8.0.989.0       5,171,712  Msmdpump.dll     IA-64 16-Nov-2004 22:50  8.0.989.0       6,048,256  Msmdsrv.exe      IA-64 16-Nov-2004 22:50  8.0.989.0       6,711,808  Msolap80.dll     IA-64 06-Apr-2004 20:05  2000.90.631.0      88,064  Osql.exe 06-Apr-2004 20:05  2000.80.760.0     269,824  Sqdedev.dll 16-Nov-2004 20:30  8.0.989.0         201,728  Msolap80.rll Note Because of file dependencies, the most recent hotfix or feature that contains these files may also contain additional files.back to the top



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section.

This problem was first corrected in Microsoft SQL Server 2000 Service Pack 4.

