During Service Catalog installation, the error "Configuring mdb failed." is received.

Products

• CA Service Catalog
• CA Service Management - Asset Portfolio Management
• CA Service Management - Service Desk Manager

Issue/Introduction

During installation of Service Catalog 14.1 - 17.1, the procedure fails with error:
“Configuring mdb failed.”

Looking at “install.log” file, the following can be seen:
 

INFO [DeployThread: Configuración de CA Service Catalog: CA MDB] [ConfigureSLCMMDB] SLCM MDB Configuration Command: "F:\Program Files\CA\Service Catalog\scripts\configurator.bat" -c mdb -p "C:\Users\bc215401\AppData\Local\Temp\\slcm_config.properties"
DEBUG [DeployThread: Configuración de CA Service Catalog: CA MDB] [CommonProcessUtilities] Deploy module 'mdb' failed with return code - -3
DEBUG [DeployThread: Configuración de CA Service Catalog: CA MDB] [CommonProcessUtilities] Command terminated with exit code: -3
DEBUG [DeployThread: Configuración de CA Service Catalog: CA MDB] [ConfigureSLCMMDB] SLCM MDB Configuration Exit Code: -3
DEBUG [DeployThread: Configuración de CA Service Catalog: CA MDB] [ConfigureSLCMMDB] Configuring mdb failed. Firing Task Error.
DEBUG [DeployThread: Configuración de CA Service Catalog: CA MDB] [ProgressPage] Task State Changed. TaskID: task.configuring_mdb,Configuración de CA Service Catalog: CA MDB, Old State: running, New State:failed
 

In “view.log” file, the following error is visible:

ERROR [main] [ConfigureSQLServer] Could not connect to the database.
com.microsoft.sqlserver.jdbc.SQLServerException: Login failed for user 'sa'. ClientConnectionId:d54a566c-62b6-41e8-84ac-41ba83e542a4
ERROR [main] [ConfigureSQLServer] Unknown exception.
com.ca.catalog.deploy.exceptions.OperationFailedException

ERROR [main] [CmdDeploymentManager] Deployment of the module 'mdb' failed 

Environment

CA Service Catalog and CA Service Management 14.1 to 17.1.
SQL Server – all supported versions

Resolution

The ‘sa’ user of the Database server contains a special character like ‘&’. Being this sign a command separator, during password encryption the letters until ‘&’ are being treated as the password, and post that as another command, leading to the ‘sa’ login failure, which actually is the cause behind the failure of MDB configuration.

Verify the password of ‘sa’ user, if it contains any special character, it needs to be removed.

Additional Information

If this doesn’t help to advance in Service Catalog installation, a Support case should be created.