Article ID: 817285
Article Last Modified on 11/21/2006
APPLIES TO
- Microsoft SQL Server 2000 Analysis Services
- Microsoft SQL Server 2000 Analysis Services
BUG #: 13939 (Plato7x)
SYMPTOMS
You have an MDX query that has a user-defined function that returns a string result. If you run this query in Analysis Services 64-bit or after you install Analysis Services Service Pack 3 (SP3) on a 32-bit system, you may occasionally receive one or more of the following error messages:
Note The "referenced memory address" in the error message may vary.
RESOLUTION
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
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.
Date Time Version Size File name -------------------------------------------------------------- 20-Feb-2003 00:08 8.0.772.0 217,668 Msmdcb80.dll 12-Feb-2003 02:49 8.0.767.0 1,024,576 Msmdgd80.dll 27-Jan-2003 07:47 8.0.0.761 9,638,464 Msmdsgn80.dll 07-Mar-2003 21:09 8.0.783.0 1,831,492 Msmdsrv.exe 20-Mar-2003 18:46 8.0.792.0 2,073,168 Msolap80.dll
Note Because of file dependencies, the most recent hotfix or feature that contains these files may also contain additional files.
SQL Server 2000 Analysis Services 64-bit
For a hotfix that is designed to be applied on a server that is running SQL Server 2000 Analysis Services 64-bit, see the following article in the Microsoft Knowledge Base:
822017 FIX: Hotfix Information for Build 8.0.810.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 in the "Applies to" section.This problem was first corrected in Microsoft SQL Server 2000 Service Pack 4.
Keywords: kbbug kbfix kbqfe kbsqlserv2000presp4fix kbhotfixserver KB817285