The sort order/collation setting for the SQL Server installation must be case insensitive; case-sensitive installations are not supported. In addition, the collation must match for all databases and tables. Run Deployment Scanner to check for collation issues prior to an upgrade. If the above error is received, use the steps below to resolve the issue.
1. Stop the EV Services.
2. Start either 'Enterprise Manager' (2000) or 'SQL Management Studio'(2005) and (2008)
3. Expand the 'EnterpriseVaultDirectory' Database, select 'Tables' (2000) or expand 'Tables' (2005) and (2008)
a. For SQL Server 2000, right-click the MQUpgrade table and select "Design"
b. For SQL Server 2005, right-click the MQUpgrade table and select "Design"
c. For SQL Server 2008, right-click the MQUpgrade table and select "Modify"
5. In the Column Name, select the AgentType field
6. In the Column Properties section, select, "Collation"
7. Use the Ellipsis (...) button to get the properties of this field
8. Select the "Restore Default" button
9. Select "OK"
10. Close the table
11. Select "Yes" at the "Save changes to the following items" dialog box
1. Run the following query against the EnterpriseVaultDirectory database, in SQL management studio or Query Analyzer to verify the collation of the MQUpgrade table and its columns:
select collation, sysobjects.name tablename, syscolumns.name as columnname, syscolumns.xtype
from sysobjects inner join syscolumns on sysobjects.id = syscolumns.id and sysobjects.xtype = 'U'
where collation != convert(sysname,DATABASEPROPERTYEX(DB_NAME(), 'Collation'))
2. If there are no collation issues, the query from step 1 will return no results and the deployment scanner should not show any collation issues with the MQUpgrade table. If the query does show issues with the MQUpgrade table and the AgentType column, the following query can be used to correct the issue:
ALTER TABLE MQUpgrade ALTER COLUMN AgentType
varchar(50) COLLATE SQL_Latin1_General_CP1_CI_AS NOT NULL
After running the query from step 2, run the query from step 1 again to confirm the issue is no longer reported in the query output. If the query returns no rows, run the deployment scanner again.