FIX: You receive an "Analysis Server Error: Connection to the server is lost" error message when you suspend and then resume operations on a cube in SQL Server 2000 Analysis Services

View products that this article applies to.

Article contents

Summary
Symptoms
Cause
Resolution
Service pack information
Hotfix information
Prerequisites
Restart information
Hotfix file information
Status
References

Back to the top

SUMMARY

This article describes the following information 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.
The files that are contained in the hotfix package.

Back to the top

In Microsoft SQL Server 2000 Analysis Services, you suspend operations on a cube by using a custom Decision Support Object (DSO) application. When you resume operations on the cube, the processing of the cube may fail and you may receive the following error messages in the DSO processing log:

Initiating transaction in Database 'Database Name'
Processing Dimension 'Dimension Name'
Initializing Dimension 'Dimension Name'
Analysis Server Error: Connection to the server is lost;
Error(-2147221421): Internal error (Server initializing Dimension 'Dimension Name' (final));
Error(-2147221421): Internal error (Unexpected internal error (Dimension 'Dimension Name'));
Processing Dimension 'Dimension Name' failed. No changes have been made to the database.
Rolling back transaction in Database 'Database Name'
Analysis Server Error: Connection to the server is lost;

Back to the top

CAUSE

This problem may occur if the following conditions are true:

You use a custom DSO application to suspend operations, and then you resume operations on the cube.
A locking conflict occurs during processing of the cube. This problem may occur if processing starts before locks are acquired on objects.

Back to the top

RESOLUTION

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 (http://support.microsoft.com/kb/290211/ ) How to obtain the latest SQL Server 2000 service pack

Back to the top

Hotfix information

Prerequisites

This hotfix requires Microsoft SQL Server 2000 Analysis Services Service Pack 3 (SP3) or a later version. For additional information about how to obtain SQL Server 2000 Analysis Services Service Pack 3 or a later version, click the following article number to view the article in the Microsoft Knowledge Base:

290211 (http://support.microsoft.com/kb/290211/ ) How to obtain the most recent SQL Server 2000 Service Pack

Restart information

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

Hotfix file information

This hotfix only contains those files that are required to correct the issues that this article lists. This hotfix may not contain 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 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, 32 bit editions

  Date         Time   Version    Size       File name
  -------------------------------------------------------
  06-Apr-2004  20:25                18,800  Msmd.h
  05-Nov-2004  17:09  8.0.986.0    221,760  Msmdcb80.dll     
  05-Nov-2004  17:09  8.0.0.986  4,063,808  Msmddo80.dll     
  05-Nov-2004  17:09  8.0.986.0  1,036,864  Msmdgd80.dll     
  05-Nov-2004  17:09  8.0.986.0    172,608  Msmdpump.dll     
  05-Nov-2004  17:09  8.0.0.986  9,642,564  Msmdsgn80.dll    
  05-Nov-2004  17:08  8.0.986.0  1,847,876  Msmdsrv.exe      
  05-Nov-2004  17:09  8.0.986.0  1,397,312  Msmdvldm.exe     
  05-Nov-2004  17:09  8.0.986.0  2,085,456  Msolap80.dll     
  05-Nov-2004  03:24  8.0.986.0    446,524  Msmdsgn.rll
  05-Nov-2004  03:05  8.0.986.0    213,068  Msolap80.rll

SQL Server 2000, 64 bit editions

  Date         Time   Version    Size       File name
  ------------------------------------------------------
  06-Apr-2004  20:25                18,800  Msmd.h
  05-Nov-2004  18:50  8.0.986.0	 5,533,184  Msmdcb80.dll     
  05-Nov-2004  18:50  8.0.986.0	 5,842,432  Msmdgd80.dll     
  05-Nov-2004  18:50  8.0.986.0	 5,171,712  Msmdpump.dll     
  05-Nov-2004  18:50  8.0.986.0	 6,048,256  Msmdsrv.exe      
  05-Nov-2004  18:50  8.0.986.0	 6,711,808  Msolap80.dll     
  05-Nov-2004  17:38  8.0.986.0	   201,728  Msolap80.rll

Note Because of file dependencies, the most recent hotfix that contains these files may also contain additional files.

Back to the top

STATUS

Microsoft has confirmed that this is a bug in the Microsoft products that are listed in the "Applies to" section.

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

Back to the top

REFERENCES

For additional information about the naming schema for Microsoft SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base:

822499 (http://support.microsoft.com/kb/822499/ ) New naming schema for Microsoft SQL Server software update packages

For additional information about the terminology that Microsoft uses when correcting software after it is released, click the following article number to view the article in the Microsoft Knowledge Base:

824684 (http://support.microsoft.com/kb/824684/ ) Description of the standard terminology that is used to describe Microsoft software updates

Back to the top