Many error messages (MainType 'xxx' is invalid) in log when installing BOND-package on an older BOND-version

Article Id: 141098

Status: Published

Updated On: 03-12-2019 10:59

Products:

CA Continuous Delivery Automation - Automation Engine

Issue/Introduction:

After installing the BOND-Action Pack version 1.2 on an older BOND-version (e.g. 7.0.x) the log is floated with error message about custom types.

Error is logged for BOND 7.0.6 and 8.0.4.

For example:

2019-02-21 15:02:33,784 [34(AUTOMIC/100/SERVICE_USER/SERVICE)] ERROR RM.CustomTypeRegistryLoader - Could not read custom type info from registry row. MainType 'ARTIFACTSOURCE' is invalid.
Ventum.Bond2.Exceptions.RmBridgeException: MainType 'ARTIFACTSOURCE' is invalid.
   at Ventum.Bond2.AeBridge.CustomTypeRegistryEntry.ParseMainType(String mainTypeString) in E:\BuildAgent\work\bondrelease\7.0.6\Projects\Ventum.Bond2.DomainModels\AeBridge\CustomTypeRegistryEntry.cs:line 114
   at Ventum.Bond2.AeBridge.CustomTypeRegistryEntry.FromVaraRow(String key, String[] rows) in E:\BuildAgent\work\bondrelease\7.0.6\Projects\Ventum.Bond2.DomainModels\AeBridge\CustomTypeRegistryEntry.cs:line 54
   at Ventum.Bond2.Services.CustomTypeRegistryLoader.LoadRegistryTable() in E:\BuildAgent\work\bondrelease\7.0.6\Projects\Ventum.Bond2.AEBridge\Services\CustomTypeRegistryLoader.cs:line 79

Cause:

Error message about not supported types is showing only once on application start up (as handled exception, no stack trace)

Environment:

Error is found on BOND 7.0.6 and 8.0.4.

Resolution:

The issue has been fixed from Release Manager v9.0.3