Cannot Import International Character Strings to the Data Warehouse

This article was previously published under Q323770
This article has been archived. It is offered "as is" and will no longer be updated.
The Report Preparation Data Transformation Services (DTS) Task fails and the following error message appears in the Application Event log:
Event Type: Error
Event Source: CSDataWareHouse
Event Category: None
Event ID: 45057
Date: 5/30/2002
Time: 15:22:55 PM
User: N/A
Prepare Reports DTS task : Error Processing error [The dimension member key is not unique] '/deu/catalog/cat_results.asp?txtsearch=aufmass (Uri)'
The Uniform Resource Identifier (URI) table uses varchar and the RequestsByURI table uses nvarchar, which is Unicode. When the varchar URI values are promoted to nvarchar, when the RequestsByURI table is populated, a single URIID can map to multiple URIs.

For dimension processing to work properly in online analytical processing (OLAP), there must be a 1:1 correspondence between the URIID and URI. If the URIID is not unique in the RequestsByURI table, you receive the dimension member key error message when you run the Report Preparation DTS task.
To resolve this problem, obtain the latest service pack for Commerce Server 2000. For additional information, click the following article number to view the article in theMicrosoft Knowledge Base:
297216 INFO: How to Obtain the Latest Commerce Server 2000 Service Pack
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    Size    File name   -----------------------------------------   11-Jun-2002   19:50   3,776   Q323770.sql				

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 Commerce Server 2000 Service Pack 3 (SP3).

Article ID: 323770 - Last Review: 10/26/2013 17:13:32 - Revision: 1.1

Microsoft Commerce Server 2000 Standard Edition

  • kbnosurvey kbarchive kbbug kbfix kbcommserv2000sp3fix kbqfe kbcommserv2000presp3fix kbhotfixserver KB323770