Previous Topic: CCS ConsiderationsNext Topic: Preconditions of the DSM Manager Installation

Installation of Client Automation › Management Database (MDB) › CCS Installation Error Messages

CCS Installation Error Messages

Note that installation of CCS calendars only with a scalability server is reliable. The following messages can occur when a full CCS installation is performed with a DSM manager. All the failures here relate to interaction between CCS and a SQL Server-based MDB.

Error Text
(in %TEMP%\
TRC_Inst2_ITRM.log)

Conditions

Diagnoses and Solutions

The MSSQLServer service is not running on \\local_host.

The MDB is remote; local and remote hosts are not in the same domain.

This message is misleading because contact is not being established with the remote MDB host.

Add the local host to the same domain as the remote host.

Specified password for user nsmadmin is invalid.

 
  • The nsmadmin account already existed in SQL Server and the password specified during the DSM install was different. Either (a) delete all DSM/CCS logins and DB users from SQL Server before starting the install, (b) specify a matching password during the DSM install, or (c) change the nsmadmin password in SQL Server to match what will be specified during the DSM install.
  • The nsmadmin password does not satisfy the system password strength criteria. Make the password stronger.

The supplied MDB credentials are not valid

 

The nsmadmin account was already defined to SQL Server; the MDB itself may or may not exist. We get this even if the nsmadmin password matches what is already in SQL Server.

Delete the DSM/CCS login(s) and DB user(s) from SQL Server so that it is clean.

There are active processes connected to one or more databases that will be used by this product. Gracefully shut down those processes to close database connections before initiating the installation so as to maintain data integrity and system stability.

[In %TEMP%\ITRM.CCS\wizint.log or %TEMP%\DSM_CCS_wizint.log.]

 

Other remote Client Automation managers are sharing the MDB, for example:

11:36:50 ** Active DB Processes **
11:36:50 DB Processes for 
11:36:50 DB Name = mdb, Node = UNI6505L3-065, Process = CA IT Client Manager r12
11:36:50 DB Name = mdb, Node = CMQA158, Process = CA IT Client Manager r12
11:36:50 DB Processes for 
11:36:50 ** End DB Processes **
11:36:50 There are active processes connected …

This is unlikely to happen in practice unless the whole Client Automation system is misconfigured or is being configured in the wrong sequence.

Temporarily shut down the remote processes. The log file shows which remote hosts are involved.

A Dependency checker test has failed.

Terminal Services is enabled on the host.

Temporarily disable terminal services while installing CCS. Installing on the console may work, also.

Or, as the CCS/NSM Implementation Guide states: "…this release supports installations through Windows Terminal Services even when configured in Application Server Mode." However, the following settings are required:

  • CONSOLE mode must be used when performing installation from remote access.

    Example:

    mstsc /v:HostName /console
  • Terminal server USER settings should be changed to INSTALL prior to the installation.

    Example:

    change user /install

To verify the user settings, execute the following command: 

change user /query

For more information about the Windows Terminal Server CHANGE USER utility, see http://support.microsoft.com/kb/186504.