FIX: You may receive an "Error Connecting OLAP Catalog: Database '<databaseName>' does not exist." error message when you try to connect to a cube by using a role that was created with DSO through an ASP page in SQL Server 2000 Analysis Services (320730)

The information in this article applies to:

Microsoft SQL Server 2000 Analysis Services

This article was previously published under Q320730

BUG #: 12828 (plato7x)

SYMPTOMS

When you try to connect to a cube by using a database role that was created with Microsoft Decision Support Objects (DSO) through an ASP page on Microsoft Internet Information Services (IIS), you may receive an error message that is similar to the following:

Error Connecting OLAP Catalog: Database '<databaseName>' does not exist.

CAUSE

This problem occurs because the component that is running on Internet Information Services (IIS) cannot correctly validate the Security Identifier (SID) for the user accounts in the cube role.

RESOLUTION

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

290211 INF: How to obtain the latest SQL Server 2000 service pack

The English version of this fix should have the following file attributes or later:

   Date         Time   Version            Size    File name
   --------------------------------------------------------------
   19-Mar-2002  19:57  8.0.0.601       4,043,328  Msmddo80.dll     
   19-Mar-2002  19:56  8.0.601.0       1,008,192  Msmdgd80.dll     
   19-Mar-2002  18:53  8.0.601.0       1,774,148  Msmdsrv.exe      
   19-Mar-2002  19:57  8.0.601.0       2,024,016  Msolap80.dll     
   18-Apr-2001  06:23  2000.80.382.0     815,676  Sqldata.dll      
   19-Mar-2002  19:56  2000.80.534.0     590,396  Sqlsort.dll

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

WORKAROUND

To work around the problem, you must re-validate the database role. For example, to re-validate the database role you can use the "Database Role Manager" to edit and to save the Membership option.

For more information about the Database Role Manager, visit the following Microsoft Web site:

http://msdn.microsoft.com/library/en-us/olapdmad/dboxdbroleman_64du.asp

STATUS

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

MORE INFORMATION

The fix that is mentioned in this article resolves the problem by forcing all Security Identifiers (SID) to be validated in the Analysis Services server process.

Modification Type:	Major	Last Reviewed:	3/19/2004
Keywords:	kbASPObj kberrmsg kbbug kbfix kbSQLServ2000preSP3fix KB320730 kbAudDeveloper