ITsVISTA
Information that makes life easier when it comes to installing, managing, and using Windows Vista.
Start About FAQ Blogroll Shop

ITsVISTA KB-Link: KB954920

When an application requests a result set from new SQL Server 2008 collations, you may receive an “MSG 40242″ or “MSG 40205″ error when the ODBC driver for SQL Server is used or an “MSG 40234″ error when the SQL OLE DB provider is used

Consider the following scenario:

  • You have data that is stored in one of the new Microsoft SQL Server 2008 collations.
  • You have an application on a computer that is running one of the following operating systems:
    • Windows XP
    • Windows Server 2003
    • Windows Vista
    • Windows Server 2008

In this scenario, you may experience one of the following symptoms:

Symptom 1

You receive an error message when the following conditions are true:

  • The application uses the Open Database Connectivity (ODBC) driver or the SQL OLE DB provider to request a result set.
  • The result set contains a column that uses one of the new collations.
  • The column is defined as the SQLTEXT type, the SQLBIGCHAR type, or the SQLBIGVARCHAR type.

If the application uses the ODBC driver, you receive the following error message:

Msg 40242

Unable to resolve column level collations system

If the application uses the SQL OLE DB provider, you receive the following error message:

Msg 40234

Unicode conversion failed. Code page of server not on client

Symptom 2

The connection to the new SQL Server 2008 collations is closed, and an error message is logged in the SQL Server Error log file when the following conditions are true:

  • The application uses the Open Database Connectivity (ODBC) driver or the SQL OLE DB provider to request a result set.
  • The result set contains data of the SQL_VARIANT data type.
  • The data is stored in one of the new collations, and the SQL_VARIANT data contains the SQLTEXT type, the SQLBIGCHAR type, or the SQLBIGVARCHAR type.

If the application uses the ODBC driver, you receive the following error message:

Msg 40242

Unable to resolve column level collations system

If the application uses the SQL OLE DB provider, you receive the following error message:

Msg 40234

Unicode conversion failed. Code page of server not on client

Symptom 3

The client application requests an output parameter. If the output parameter uses one of the new collations, the parameter is defined as the SQLBIGCHAR type, the SQLBIGVARCHAR type, or the SQLTEXT type, and an error is returned to the client application.

If the application uses the ODBC driver, you receive the following error message:

Msg 40242

Unable to resolve column level collations system

If the application uses the SQL OLE DB provider, you receive the following error message:

Msg 40234

Unicode conversion failed. Code page of server not on client

Symptom 4

The connection to the new SQL Server 2008 collations is closed, and an error message is logged in the SQL Server Error log file when the following conditions are true:

  • The application requests an output parameter.
  • The data type of the output parameter is SQL_VARIANT.
  • The output parameter uses one of the new collations, and the SQL_VARIANT data contains the SQLCHAR type or the SQLVARCHAR type.

If the application uses the ODBC driver, you receive the following error message:

Msg 40242

Unable to resolve column level collations system

If the application uses the SQL OLE DB provider, you receive the following error message:

Msg 40234

Unicode conversion failed. Code page of server not on client

Symptom 5

The client application connects to a database, and the default collation that the database uses is one of the new collations. In this case, an error is returned to the client application.

If the application uses the ODBC driver, you receive the following error message:

Msg 40205

Unicode conversion failed

If the application uses the SQL OLE DB provider, you receive the following error message:

Msg 40234

Unicode conversion failed. Code page of server not on client

Symptom 6

When you run the USE statement to switch to a database that uses one of the new collations, you receive the error messages that are listed for “Symptom 5.”

There is a download that resolves this issue. See Hotfixes for details.

For more information on this issue, including potential causes, workarounds, and resolutions, see: Microsoft KB Article KB954920.

Get notified of new posts for FREE via RSS or E-mail

Subscribe to ITsVISTA!

Related Posts