SQL Server Collation Must Match Metastorm Database Collation

Metastorm · May 16, 2005

The information in this article applies to:

Product: Metastorm BPM (e-Work)
Version: 5.x 6.x 7.x

Issue

Client message Failed to obtain list is displayed when trying to retrieve To Do or Watch list.

In addition, the following error message may be written to the Windows application event log:

Application event log: ErrorCode: '-2147217900' Description: 'Cannot resolve collation conflict for equal to operation.'
Source: 'Microsoft OLE DB Provider for SQL Server' SQL State: '42000' NativeErrorCode: '446'
When running a stored procedure script against a version 7.0 database, the following error message may be written to the Windows application event log:

Server: Msg 446, Level 16, State 9, Procedure psp\_join\_key\_columns, Line 39 Cannot resolve collation conflict for equal to operation. Cannot add rows to sysdepends for the current stored procedure because it depends on the missing object 'psp\_join\_key\_columns'. The stored procedure will still be created.

As stated in the Installation Guide, when running against SQL Server, the collation of the Metastorm database must be the same as the SQL Server collation.
The collation can be verified as follows:

SQL Server 2000
Open Enterprise Manager --> Right-click on the SQL Server instance --> select Properties --> General --> Server collation
Open Enterprise Manager --> Databases --> Right-click on the Metastorm database --> select Properties --> General --> Maintenance --> Collation name

SQL Server 2005
Open SQL Server Management Studio --> Right-click on the SQL Server instance --> select Properties --> General --> Server Collation
Open SQL Server Management Studio --> Databases --> Right-click on the Metastorm database --> select Properties --> General --> Maintenance --> Collation
For more information, see the Microsoft article How to transfer a database from one collation to another collation in SQL Server.