This KB article will be released shortly – http://support.microsoft.com/kb/928643
For more Resolution and More information please see the KB article itself. Here is some detail from the article
After you install and configure the Notification Workflow Solution Accelerator for Microsoft Operations Manager (MOM) 2005, notifications are generated as expected. However, when you install the Notification_Workflow_Hotfix.zip file, you experience the following symptoms:
- When you run the MSMNWBuFixUpdate.cmd file the second time, as instructed in step 10 of the Using the Notification Workflow Hotfix document, you receive the following error message:
Source: .Net SqlClient Data Provider
Message: Cannot resolve collation conflict for like operation.
Line Number: 35
Cannot resolve collation conflict for like operation.
- After the hotfix installation is complete, notifications that you have configured in the Notification Workflow Solution Accelerator are no longer sent.
This problem occurs if the collation designation that the NotificationWorkflowNotificationWorkflowApp database and the NotificationWorkflowNSMain database use differs from the default SQL_Latin1_general_CP1_CI_AS collation. If a collation other than the default SQL_Latin1_general_CP1_CI_AS collation is set, the installation of the Notification_Workflow_Hotfix.zip file is not completed successfully.
When you perform a custom installation of Microsoft SQL Server 2000, you can select the collation type in the Collation Settings dialog box of the installation program. By default, the SQL Server 2000 installation program uses the following SQL Server collation options for the installation of SQL Server 2000:
- Dictionary order
- 1252 Character Set
After SQL Server 2000 is installed, these settings appear as SQL_Latin1_general_CP1_CI_AS in the SQL Server Enterprise Manager tool.
If you click Collation designator in the Collation Settings dialog box when you install SQL Server 2000, the Latin1_General option appears in the Collation designator list. This is by default. After SQL Server 2000 is installed, this setting appears as Latin1_General in the SQL Server Enterprise Manager tool.
Note The Latin1_General option may be followed by symbols such as CI or AS. These symbols indicate whether extended options such as case-insensitivity (CI) or accent-sensitivity (AS) have been set.