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:
  SqlServerError:
  Source: .Net SqlClient Data Provider
  Number: 446
  State: 9
  Class: 16
  Server: ServerName
  Message: Cannot resolve collation conflict for like operation.
  Procedure: NSFire2
  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.

The NotificationWorkflowNotificationWorkflowApp database and the NotificationWorkflowNSMain database use a collation designation. This problem occurs if the collation designation that these databases 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
• Case-insensitive
• 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.

To resolve this problem, follow these steps:

1. Remove the three COLLATE statements from the CGTruncationBugFix.sql script that is included with the Notification_Workflow_Hotfix.zip file. To do this, follow these steps:
   1. Create a backup copy of the CGTruncationBugFix.sql script that you updated with the correct sender name and polling interval. By default, this file is located in the following folder:
      %ProgramFiles%\Microsoft\Notification Workflow\Notification Workflow\SQL\Scripts
   2. Use a text editor, such as Notepad, to open the CGTruncationBugFix.sql script.
   3. On the Edit menu, click Find, type collate in the Find what box, and then click Find Next. The following section of the script appears.

      CREATE TABLE [dbo].[AlertComputerGroups] (
      	[Guid] [uniqueidentifier] NOT NULL ,
      	[ComputerGroupName] [nvarchar] (4000) COLLATE SQL_Latin1_General_CP1_CI_AS NULL 
      ) ON [PRIMARY]
      GO
      
      CREATE TABLE [dbo].[AlertProperties] (
      	[Guid] [uniqueidentifier] NOT NULL ,
      	[Name] [nvarchar] (510) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
      	[Owner] [nvarchar] (510) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
      	[RepeatCount] [int] NULL ,
      	[TimeAdded] [datetime] NULL ,
      	[TimeofFirstEvent] [datetime] NULL ,
      	[TimeofLastEvent] [datetime] NULL ,
      	[TimeRaised] [datetime] NULL ,
      	[ServerLocalTime] [datetime] NULL 
      ) ON [PRIMARY]
      GO

   4. Remove the three COLLATE statements together with their parameters from this section of the script. This section of the script now appears as follows.

      CREATE TABLE [dbo].[AlertComputerGroups] (
      	[Guid] [uniqueidentifier] NOT NULL ,
      	[ComputerGroupName] [nvarchar] (4000) NULL 
      ) ON [PRIMARY]
      GO
      
      CREATE TABLE [dbo].[AlertProperties] (
      	[Guid] [uniqueidentifier] NOT NULL ,
      	[Name] [nvarchar] (510) NULL ,
      	[Owner] [nvarchar] (510) NULL ,
      	[RepeatCount] [int] NULL ,
      	[TimeAdded] [datetime] NULL ,
      	[TimeofFirstEvent] [datetime] NULL ,
      	[TimeofLastEvent] [datetime] NULL ,
      	[TimeRaised] [datetime] NULL ,
      	[ServerLocalTime] [datetime] NULL 
      ) ON [PRIMARY]
      GO

   5. Save the changes to the script, and then exit the text editor.
2. Follow the instructions in the Using the Notification Workflow Hotfix document to install the hotfix package. In steps 4 through 7 in the "Applying the Hotfix" section of these instructions, use the CGTruncationBugFix.sql script that no longer contains the three COLLATE statements.

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

For more information, click the following article number to view the article in the Microsoft Knowledge Base: