Microsoft KB Archive/821103

= FIX: The Processing of a Cube That Contains a Virtual Dimension Fails with Error Message: &quot;Object does not exist&quot; =

Article ID: 821103

Article Last Modified on 2/21/2007

-

APPLIES TO


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

-



BUG #: 14037 (PLATO7x)



SYMPTOMS
The processing of a cube that contains a virtual dimension might fail, and you receive the following error message:

Analysis Server Error: Internal Error [Object Does Not Exist ]

The problem can occur if all the following conditions are true:
 * The cube contains a virtual dimension.
 * One of the levels in the virtual dimension is not based on a member property.
 * The Very Large Dimension Manager (VLDM) manages the regular dimension the virtual dimension depends on.

Analysis Services uses the VLDM to load very large dimensions in a separate process. By default, the threshold for a VLDM is 64 megabytes. You can configure the VLDM threshold value in the VLDMThreshold registry key, under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\OLAP Server\CurrentVersion. The value of the VLDMThreshold entry is in bytes. Any dimension that exceeds the threshold setting is automatically loaded to the VLDM process.



WORKAROUND
To work around this problem, you can either:
 * Use a regular dimension instead of a virtual dimension.

-or-
 * Increase the value of VLDMThreshold to a value sufficient to prevent the dimension that the virtual dimension depends on from being offloaded to the VLDM.



Service pack information
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 How to obtain the latest SQL Server 2000 service pack

Microsoft SQL Server 2000 Analysis Services
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 --  13-May-2003  06:14  8.0.806.0         217,668  Msmdcb80.dll 23-Jul-2003 04:23  8.0.0.843       4,055,616  Msmddo80.dll 13-May-2003 06:14  8.0.767.0       1,024,576  Msmdgd80.dll 16-May-2003 08:26  8.0.823.0         172,608  Msmdpump.dll 13-May-2003 06:14  8.0.0.761       9,638,464  Msmdsgn80.dll 22-Jul-2003 23:03  8.0.843.0       1,831,492  Msmdsrv.exe 27-Jun-2003 19:06  8.0.838.0       2,077,264  Msolap80.dll 10-May-2003 08:05  8.0.820.0         213,069  Msolap80.rll Note Because of file dependencies, the most recent hotfix or feature that contains these files may also contain additional files.

Microsoft SQL Server 2000 Analysis Services 64-bit
For additional information about a hotfix build designed to be applied on a server that is running SQL Server 2000 Analysis Services 64-bit, or to find out if a fix is scheduled to be included in SQL Server 2000 Analysis Services 64-bit Service Pack 4, click the following article number to view the article in the Microsoft Knowledge Base:

822672 FIX: Hotfix Information for Build 8.0.843.0 of SQL Server 2000 Analysis Services 64-bit



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

Keywords: kbbug kbfix kbqfe kbhotfixserver KB821103

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.