3.6.0 Matrix Server Upgrade Guide (5697-7085, February 2008)

Chapter 2: Overview 12

Possible causes of the error are:

• The Virtual SQL Server is not active on the primary node.

• A DNS entry including an A record and a [PTR] record for forward

and reverse lookup does not exist.

• No SQL instances are associated with the Virtual SQL Server.

• The upgrade tool is not installed on all nodes in the cluster.

• The cluster nodes are configured to use a proxy server. For the

upgrade to succeed, add each node, or the subnet in which the node is

configured, to the proxy exclusion list on each node. This

configuration ensures proper communication among all nodes via

http while using the upgrade tool and can be backed out after the

upgrade is successfully completed.

3. Uninstall the Upgrade Tool

After the last Virtual SQL Server has been upgraded successfully, the

upgrade tool must be uninstalled on each node. This step is necessary

because the upgrade tool conflicts with the user authorization

mechanisms used by Matrix Server 3.6.0. To uninstall the tool, use the

Add/Remove Programs interface on the Control Panel.

Complete Syntax and Options for mssql_upgrade.js

The mssql_upgrade.js script includes options that perform the following:

• Create a new local profile (the N profile) for the primary node for a

Virtual SQL Server and its associated Virtual SQL instances.

• Fix duplicate registry entries if possible.

• Dump the current configuration of all Virtual SQL Servers and Virtual

SQL instances in the matrix.

The command has the following syntax:

cscript /nologo mssql_upgrade.js (/upgrade|/fix|/dump) /vsql

<vsql_name> /path <path_target> /backup <backup_IP> /matrix

<hostname> [/user <username> /password <password>|/noauth]