How to resolve an common error while installing ITCM's MDB against a previously installed SDM's MDB

book

Article ID: 101607

calendar_today

Updated On:

Products

CA Automation Suite for Data Centers - Configuration Automation CA Client Automation - Asset Management CA Client Automation - IT Client Manager CA Client Automation CA Client Automation - Remote Control CA Client Automation - Asset Intelligence CA Client Automation - Desktop Migration Manager CA Client Automation - Patch Manager

Issue/Introduction



I'm installing Client Automation's MDB against a previously installed Service Desk's MDB and it results in failure, how to resolve it?
 

Environment

Release: UASMGT60000-1402-Asset Management
Component:

Resolution

One of the steps to integrate Client Automation and Service Desk is install both MDBs together, but an error may popup on ITCM's installer, similar to:

Error Code: 3

MDBTools install error: setup MDB failed, please see install_<dbname>.log file for details


Reviewing "install_mdb.log" the following error can be found:

06-13,18:51:23 INFO - MDBTools_0305E - Error processing foreign key '$usm_t_r00002c7f00000000.xml'; details follow:
06-13,18:51:23 ERROR - com.microsoft.sqlserver.jdbc.SQLServerException: The ALTER TABLE statement conflicted with the FOREIGN KEY constraint "$usm_t_r00002c7f00000000". The conflict occurred in database "mdb", table "dbo.usm_runtime_component", column 'runtime_component_id'.
com.microsoft.sqlserver.jdbc.SQLServerException: The ALTER TABLE statement conflicted with the FOREIGN KEY constraint "$usm_t_r00002c7f00000000". The conflict occurred in database "mdb", table "dbo.usm_runtime_component", column 'runtime_component_id'.


This error means that the target table "usm_runtime_component" is empty, this can be verified running the following query:

SELECT * FROM usm_runtime_component

If the table is empty, the constraint can't be completed by Client Automation's installer and will throw the above error. In order to resolve this problem, the following query can be executed against SDM's MDB:

INSERT INTO usm_runtime_component
VALUES ('Scheduler',NULL,NULL,NULL,NULL,NULL)


NOTE: Take a full backup of the MDB before running any update/insert

After this, Client Automation's installer can be executed again.