DCA Fails When OEMCP Is Set to a Value Other Than 437 (United States) (314010)

SYMPTOMS

When Content Management Server (CMS) 2001 is installed on localized versions of Windows 2000 other than English and you run the CMS Database Configuration Application (DCA), you may receive the following error message:

"Database Creation Failed [Microsoft][ODBC SQL Server Driver][SQL Server]CodePage 866 is not supported by SQL Server [Microsoft][ODBC SQL Server Driver]Unable to resolve column level collations -2147221504 Microsoft SQL-DMO (ODBC SQLState: S1000)"

CAUSE

When you run the DCA for the first time after you install CMS, the DCA does not set the code page before it performs the BCP. The BCP uses the default OEM page that is set by the user locale (in the example in this article, the OEMCP is set to 866, or Russian). You should modify the function that creates and populates a database to set the OEMCP to 437 (the ANSI English US code page) before you copy the data schema to a database. OEMCPs other than 437 are not supported.

RESOLUTION

To resolve this problem, obtain the latest service pack for Microsoft Content Management Server 2001. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

313957 How to Obtain the Latest Content Management Server 2001 Service Pack

WORKAROUND

To work around this problem, change the MS-DOS code page (OEMCP) value in the registry to 437 (United States) while you install CMS, and then change the OEMCP value back to the original value. To do this, follow these steps:

Modify the following registry key and set the OEMCP value to 437:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Nls\CodePage
Restart the computer.
Create a new database in Microsoft SQL Server. Make sure that you start with a blank database that does not contain CMS tables.
Run DCA to populate the database and set the CMS system account.
Change the OEMCP registry value back to the original value (in this example, 866).
Restart the computer.
Proceed with the installation and configuration.

STATUS

Microsoft has confirmed that this is a problem in Microsoft Content Management Server 2001. This problem was first corrected in Microsoft Content Management Server 2001 Service Pack 1.