FIX: Local Cube Creation Fails If Dimension Member Key and Member Names Are from Different Tables (325199)



The information in this article applies to:

  • Microsoft SQL Server 2000 Analysis Services

This article was previously published under Q325199
BUG #: 12821 (Plato7x)

SYMPTOMS

When you try to create a local cube, you may receive one of the following error messages:
Unable to open connection
Error processing the dimension '[Microsoft][ODBC SQL Server Driver][SQL Server]The column prefix '<tablename>' does not match with a table name or alias name used in the query.;37000'

Unable to open connection.
Error processing the dimension 'The column prefix '<tablename>' does not match with a table name or alias name used in the query.;42000

This error message occurs if a level in one of the local cube's dimensions uses a different table for the member key and the member name.

RESOLUTION

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 INF: How To Obtain the Latest SQL Server 2000 Service Pack

NOTE: The following hotfix was created before the release of Microsoft SQL Server 2000 Service Pack 3.

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
   -----------------------------------------------------------------

   04/15/2002   05:59 PM   8.0.609.0   213,572 bytes   Msmdcb80.dll

				
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 at the beginning of this article.
This problem was first corrected in Microsoft SQL Server 2000 Service Pack 3.

Modification Type:MinorLast Reviewed:7/16/2004
Keywords:kbSQLServ2000sp3fix kbbug kbfix kbSQLServ2000preSP3fix KB325199