Issues table


Review the following table for issues that were corrected in BMC Helix CMDB 25.4 and for known issues that remain open.

Corrected issues

View the issues in the following tables by the default sort order, Corrected in, which shows the corrected issues first. 

The version number represents the update ( Year.Month.Release ) or release number (MajorRelease.MinorRelease.ServicePack.Patch) in which the issue is fixed.

Known (open) issues

To view only the open issues, click the Corrected in filter, and select empty. An issue without a value for Corrected in remains open.

Warning

Important

The following table lists all the known issues and only the critical customer and partner reported issues corrected in BMC Helix CMDB 25.3. For information about any particular issue that is not listed in this table, contact BMC Customer Support. 

 

 

Component

Description

Status

Found in

Defect ID

CMDB

When the Reconciliation Engine pod launches, it fails to start and displays the error:

Failed to encrypt Remedy Application Service password and add it to ar.conf.

This issue occurs because in the plugin server base image, some components are identified as vulnerable and are no longer required. These components are removed from the base image and moved to a Reconciliation Engine utility tool for limited internal use to prevent security risks.

Fixed 

in 26.1.00

25.1.00CMDB-8322
Reconciliation

The Delete and Purge activities delete all endpoint CIs and relationships when a reconciliation job uses a qualification rule defined only for relationship classes.​​​

Fixed 

in 26.1.00

25.4.00CMDB-8327
Atrium IntegratorThe Atrium Integrator Client 25.4.00 installer splash screen incorrectly displays the version as 25.3.00 instead of 25.4.00.Fixed 

in 26.1.00

25.4.00CMDB-7497
Reconciliation

The list of failed Configuration Items (CIs) displayed under the “CIs” column shows either the CI Name or the Instance ID, depending on the attributes defined in the identification rule during reconciliation processing.

If the CI Name is not available, the Instance ID is shown.

Open 

 

26.1.00,
25.4.00,
25.3.00,
25.2.00,
25.1.00,
23.3.04

CMDB-1241

CMDB

AR Server

When you set the locale to Arabic, the following messages, data, or text are not supported for Arabic translation:

  • AR form messages.
  • Messages originating from bmc:core forms.
  • Data from CMDB on SYS:Message Box and PCT:MenuItems.
  • Labels in CI Explorer and Topology View.
Open

 

26.1.00,
25.4.00

CMDB-7245 

CMDB-6565 

CMDB-7398

Reconciliation

When a large volume of instances is created with MarkAsDeleted=Yes, RE Id Service SQL queries take a long time to execute.

Workaround:

Create the following index having column RelLeadClassId, ClassId, and DatasetId on the BMC.CORE:BMC_BaseElement table:

CREATE INDEX i775_reidmadinstances_t775_psr ON public.t775 USING btree (c400131300, C400079600, C400127400)

Open 

25.4.00CMDB-7116
NormalizationIn a normalization job, when you select the Allow Updates to a Product Catalog Entry option, newly created CIs with null CTI values are not normalized.
Workaround: Run the normalization job twice. In the first run, only the CTI values are normalized. In the second job run, the end-of-life dates are also normalized.
Open26.1.00,
25.4.00,
25.3.00,
25.2.0
CMDB-2627

Atrium Integrator Spoon

When you click the Help button in a step in a job or a transformation, a webpage is displayed with an error.

Open

25.1.00,
23.3.04

CMDB-90

Service context

When you open a CI in CMDB Explorer to view the Service Context information, the BMC Service Context dialog box does not open. 

Workaround:

  1. Log in to Mid Tier. 
  2. From Applications, select Atrium Core > Service Context administration
  3. Click the Test Connections tab.
    In the test results, see the applications that show the following error:
    Result: Fail
    Provider Error Code=0, Error Message=ARERR[623] Authentication failed : C2CDemo:
    Please Configure the SRM provider in the BMC Atrium Service Context Administration Console. 
  4. Click the Advance Settings tab.
  5. In Configure Authentication Information, click Configure.
  6. For each application with this error, replace the C2CDemo username with an existing username and re-enter the password.
  7. Save your changes.
  8. Click the Test Connections tab to confirm there are no errors for any applications.

Open

26.1.00,
25.4.00,
25.3.00,
25.2.00,
25.1.00,
23.3.00,

CMDB-158

CMDB Explorer

Same icon is displayed for different types of relationships in CMDB Explorer when you open a CI in CMDB Explorer, and click Simulate Impact

Open

25.1,
23.3.xx

DRD21-80625

 

 

 

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

BMC Helix CMDB 26.1