Upgrade of MDB for CA Client Automation fails with Appcrash with dsminfoa.dll error

book

Article ID: 39877

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

Introduction:                                        

When doing an upgrade you first need to Upgrade them MDB, especially if your MDB is on a remote machine.

<Please see attached file for image>

3-21-2016 4-40-33 PM.jpg

 

When you get to the following Screen you select OK:

<Please see attached file for image>

Config.jpg

You will see the following Error Screen popup with the following Appcrash in dsminfoa.dll  
and in the Application Event viewer you will see the following Errors (Error 1638).

<Please see attached file for image>

AppCrash.jpg    

<Please see attached file for image>

1638.jpg

 

Question:

Why am I getting an Appcrash with dsminfoa.dll when upgrading my MDB ?

 

Environment:                                          

 

CA Client Automation - All Versions 

 

Answer:

This problem is caused by a missing entry in the ca_settings table.

The version of the mdb is listed in the ca_settings table in the set_id column under the 903 record (which is missing from this table).

<Please see attached file for image>

NoVal.jpg

 

To resolve the issue do a DSMver to find out what version of DSM you are at now:

<Please see attached file for image>

dsmver.jpg

Then use that version to create the ca_settings record :

use mdb
  insert into ca_settings(set_id,set_val_text)
  values (903,'12.9.0.338')
 

Now if you look at the ca_settings table, it will list the ca_settings 903 record:

<Please see attached file for image>

CorrectVal.jpg

 

A similar issue, is when doing an upgrade you get Appcrash msvcr100.dll:

<Please see attached file for image>

msvcr100.jpg

 

This is caused by the ca_settings,  record 903 has a value that is not a correct version

<Please see attached file for image>

wrongVal.jpg 

 

To resolve this change the incorrect version to a "real version" (again, check DSMVER)

 
  update ca_settings
  set set_val_text= '12.9.0.338'
  where set_id = 903
 
This will change the ca_settings table to the correct version and this will allow the upgrade to progress.
 

Environment

Release: UASIT.99000-12.8-Asset Intelligence
Component:

Attachments

1558715134464000039877_sktwi1f5rjvs16tou.jpeg get_app
1558715132552000039877_sktwi1f5rjvs16tot.jpeg get_app
1558715130701000039877_sktwi1f5rjvs16tos.jpeg get_app
1558715128694000039877_sktwi1f5rjvs16tor.jpeg get_app
1558715126831000039877_sktwi1f5rjvs16toq.jpeg get_app
1558715124853000039877_sktwi1f5rjvs16top.jpeg get_app
1558715120384000039877_sktwi1f5rjvs16too.jpeg get_app
1558715117834000039877_sktwi1f5rjvs16ton.jpeg get_app
1558715115974000039877_sktwi1f5rjvs16tom.jpeg get_app