Microsoft KB Archive/873386

= FIX: The Analysis Services service may restart unexpectedly when you try to process a cube partition that has one or more virtual dimensions =

Article ID: 873386

Article Last Modified on 11/21/2006

-

APPLIES TO


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

-



Bug #: 20000001 (Plato7x)

Bug #: 24772 (Content Maintenance)



SYMPTOMS
When you try to process a partition in your Microsoft SQL Server 2000 Analysis Services cube and the cube partition contains one or more virtual dimensions, the SQL Server 2000 Analysis Services service may restart unexpectedly.

One or more mini dump files (.mdmp) may be generated in the Analysis Services data folder. If you open the mini dump file in WinDbg.exe or in a similar debugging tool and you set the last stack to the error context (.ecxr), the call stack includes the following call details:

msmdsrv!PNNTab::GetMasterSource+0x31

msmdsrv!PNModel::ExtendDataSetSliceByVDim+0x22f

msmdsrv!PNAggregate::Init+0x20e

msmdsrv!PNPartition::Init+0x70

msmdsrv!PNMapDataSet2::InitIndexForWrite+0x35

msmdsrv!PNAggregate::BuildAggregationsAndIndexies+0x1fd

msmdsrv!PNPartition::BuildAggregationsAndIndexies+0x9e8

msmdsrv!PNServer::LazyBuilderThread+0x4c4

msmdsrv!PNServer_LazyBuilderThread+0x15

msvcrt!_threadstartex+0x8f

KERNEL32!BaseThreadStart+0x52

Note After the SQL Server 2000 Analysis Services service restarts, the processing operation finishes successfully if you reprocess the cube partition that caused the problem.



CAUSE
This problem occurs because of an invalid link between the virtual dimension and the dimension member property that serves as the source of the virtual dimension data. This invalid link may be a pointer to a deleted level in the dimension member property for a virtual dimension level.



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

Hotfix information
The English version of this hotfix has the file attributes (or later file attributes) 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 Analysis Services 32-bit
This hotfix build is designed to be applied on a server that is running SQL Server 2000 Analysis Services 32-bit.   Date         Time   Version            Size    File name --  06-Apr-2004  07:56                     18,800  Msmd.h   15-Jul-2004  13:22  8.0.960.0         221,760  Msmdcb80.dll 15-Jul-2004 13:48  8.0.0.960       4,063,808  Msmddo80.dll 15-Jul-2004 13:15  8.0.960.0       1,036,864  Msmdgd80.dll 15-Jul-2004 13:09  8.0.960.0         172,608  Msmdpump.dll 15-Jul-2004 12:47  8.0.960.0         446,524  Msmdsgn.rll 15-Jul-2004 13:57  8.0.0.960       9,642,564  Msmdsgn80.dll 15-Jul-2004 13:10  8.0.960.0       1,839,684  Msmdsrv.exe 15-Jul-2004 13:33  8.0.960.0       2,085,456  Msolap80.dll 15-Jul-2004 12:28  8.0.960.0         213,068  Msolap80.rll

SQL Server 2000 Analysis Services 64-bit
This hotfix build is designed to be applied on a server that is running SQL Server 2000 Analysis Services 64-bit.   Date         Time   Version            Size    File name --  06-Apr-2004  07:56                     18,800  Msmd.h   15-Jul-2004  15:24  8.0.960.0       5,507,584  Msmdcb80.dll 15-Jul-2004 15:24  8.0.960.0       5,816,320  Msmdgd80.dll 15-Jul-2004 15:24  8.0.960.0       5,146,624  Msmdpump.dll 15-Jul-2004 15:24  8.0.960.0       6,010,368  Msmdsrv.exe 15-Jul-2004 15:24  8.0.960.0       6,686,208  Msolap80.dll 15-Jul-2004 14:11  8.0.960.0         201,216  Msolap80.rll

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 in the &quot;Applies to&quot; section.

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

