Guest

Cisco Unified Web Interaction Manager

Cisco Interaction Manager 4.2(5) upgrade fails due to SQL Collation incompatibility

Document ID: 109603

Updated: Feb 12, 2009

   Print

Introduction

The Cisco Interaction Manager 4.2(5) upgrade fails due to a SQL Collation incompatibility. This document discusses how to troubleshoot this issue.

Prerequisites

Requirements

Cisco recommends that you have knowledge of these topics:

Installing Cisco Unified Web and E-Mail Interaction Manager

Components Used

The information in this document is based on the Cisco Unified Web and E-Mail Interaction Manager version 4.2(5).

The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command.

Conventions

Refer to Cisco Technical Tips Conventions for more information on document conventions.

Background Information

warning Warning: Only configurations that meet certain criteria can be upgraded to Cisco Interaction Manager 4.2(5).

Before you proceed with the upgrade, you must verify that your current system has these settings:

  • On the master, active, and archive databases, collation settings must be set to SQL_Latin1_General_CP1_CI_AS.

  • On configurations that are already on SQL Server 2005, the SQL Server collation setting must be set to SQL_Latin1_General_CP1_CI_AS.

  • Complex password settings must not be enforced on SQL Server 2005.

  • On all servers in the Cisco Interaction Manager configuration, the regional option must be set to English.

warning Warning:  If any of these conditions are not met, do not proceed with the upgrade to Cisco Interaction Manager 4.2(5). You must download 4.2(5a) from Software Downloads (registered customers only) .

Problem

The Cisco Unified E-Mail Interaction Manager/Web Interaction Manager (EIM/WIM) 4.2(5) upgrade fails due to a SQL Collation incompatibility. When the SQL server collation order is not SQL_Latin1_General_CP1_CI_AS, the upgrade fails.

This issue is documented by Cisco Bug ID CSCsx24230 (registered customers only) and is fixed in Cisco Unified EIM/WIM version 4.2(5a).

Solution

On All Servers

Complete these steps in order to verify the Regional Options setting on the file, services, database, and all application and web servers:

  1. Choose Start > Settings > Control Panel.

  2. Double-click Regional and Language Options.

  3. In the Regional and Language Options window, on the Regional Options tab, in the Standards and formats section, verify that English (United States) is selected.

On the Database Server

Complete these steps in order to verify the Regional Options settings on the database server:

  1. Verify that the collation setting for the master, active, and archive databases is set to SQL_Latin1_General_CP1_CI_AS. In order to verify the database collation, run this query on the active, master, and archive databases:

    Note: If you have already upgraded to Microsoft SQL server 2005, run the query on the databases on SQL Server 2005. If the databases are still on SQL Server 2000, run the query on SQL Server 2000.

    SELECT convert(sysname,DatabasePropertyEx('Database_Name','Collation'))
  2. On the SQL Server 2005 database server, verify that the collation setting is set to SQL_Latin1_General_CP1_CI_AS. Run this query:

    SELECT convert(sysname,ServerProperty(‘Collation’))
  3. On SQL Server 2005, verify that complex password policies are not enforced by the SQL Server 2005 instance. In order to verify this, run this query:

    IF (SELECT distinct 1 FROM sys.sql_logins
    WHERE is_policy_checked = 1) = 1
    PRINT ‘Complex password policy is enforced’
    ELSE
    PRINT ‘Complex password policy is not enforced’

Related Information

Updated: Feb 12, 2009
Document ID: 109603