This article has been archived. It is offered "as is" and will no longer be updated.
BUG #: 13928 (Plato7x)
When you define a dimension as a time dimension by using the TYPE TIME keyword in a CREATE CUBE command when you are creating a local cube, you may receive the following error message:
Run-time error '-2147217900 (80040e14):
Syntax error, unrecognized data type, near:
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
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 bytes Msmdcb80.dll 12-Feb-2003 02:49 8.0.767.0 1,024,576 bytes Msmdgd80.dll 27-Jan-2003 07:47 126.96.36.1991 9,638,464 bytes Msmdsgn80.dll 17-Feb-2003 20:09 8.0.770.0 1,827,396 bytes Msmdsrv.exe 17-Feb-2003 21:35 8.0.770.0 2,069,072 bytes 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 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:
822017 FIX: Hotfix Information for Build 8.0.810.0 of SQL Server 2000 Analysis Services 64-bit
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.