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

Document ID : KB000039877
Last Modified Date : 14/02/2018
Show Technical Document Details

Introduction:                                        

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

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

 

When you get to the following Screen you select OK:

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).

AppCrash.jpg    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).

NoVal.jpg

 

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

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:

CorrectVal.jpg

 

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

msvcr100.jpg

 

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

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.