Issues table

Fixed in 

25.3.01

When you create a federated class in the CMDB in CORE Deployment mode, the system logs the following error message: 

ERROR (120011) : Class already exists. BMC.FED

 When you create an attribute for a custom class in the CMDB in CORE Deployment mode, an error starting with the following message is logged:

ERROR (317) : Duplicate form name BMC.CORE 

atcom.bmc.arsys.server.domain.validation.FormValidatorImpl.validateCreateForm(FormValidatorImpl.java:1910)

When you create a transformation using the step Load file content in memory, add a file in the content tab, and leave Encoding blank, an error starting with the following message is logged:

​org.pentaho.di.core.exception.KettleException:
Error during processing a row

at org.pentaho.di.trans.steps.loadfileinput.LoadFileInput.getOneRow(LoadFileInput.java:459)

23.3.04,
25.2.00,
25.1.02,
25.1.01,
25.1.00

After upgrading Atrium Integrator Spoon, jobs with steps having JavaScript modifications by using strings such as startsWith generate the following error in the logs:
 

TypeError: Cannot find function startsWith in object.

23.3.04,
25.2.00,
25.1.02,
25.1.01,
25.1.00

25.1,
23.3.04

Reconciliation

When you run a reconciliation job, you might get the following error:

com.bmc.arsys.api.ARException: ERROR (92): Timeout during database update

Workaround: Perform the following steps to resolve this error and improve the performance of the reconciliation job:

1. Log in to Mid Tier
2. Select Applications > AR System Administration > AR System Administration Console > System > General > Centralized Configuration.
3. From the Component Type list, select com.bmc.cmdb.recon.idservice > *
4. In the Setting Name column, if the Identify-Source-Duplicates parameter is absent, click Add to add the setting.
   This parameter is enabled by default and is not displayed in the Setting Name list. 
5. Disable the RE ID Service feature by changing the Setting Value to F (False).

Fixed in 25.2

25.1,
23.3.04

CMDB-1835

Atrium Integrator

Some Atrium Integrator jobs fail to run according to the schedule because the primary server is unavailable, and the Atrium Integrator server does not switch to the secondary server. 

Open

25.1

CMDB-333

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,
23.3.04

CMDB-90

Atrium Integrator Spoon

You get the following error when you run the transformation in Atrium Integrator Spoon when you rename a folder in the Repository explorer that is used in the transformation.:

Open

25.1,
23.3.04

CMDB-981

Atrium Integrator Spoon

In Atrium Integrator Spoon, when you delete a folder from Repository explorer, the other folders in the repository are not displayed.

Workaround: Close and reopen the Repository explorer window to view the folders.

Open

25.1,
23.3.04

CMDB-938

Dashboard utility 

In Configurations > Schedule, when you schedule a Dashboard or the Datasources utility job according to the server's time, the Dashboard utility does not run the scheduled jobs at the specified time.

Workaround: Perform the following steps to resolve the issue:

1. Log in to Mid Tier.
2. Open the AR System Configuration Component Setting form.
   Use the URL format https://<MidTierServer>/arsys/forms/<arserver>/AR System
   Configuration Component Setting.
3. In the Setting Name, search for the Run-Process-Command-WhiteList parameter. 
4. In the Setting Value field, add the value within double quotes "<parameter value>". For example, “/opt/bmc/AtriumCore/cmdb/utils/DashboardDataGenerator/rundashboardutil.cmd”|”
   /opt/bmc/AtriumCore/cmdb/utils/DashboardDataGenerator/rundashboardutil.sh”
5. In the CMDB Portal, schedule the Dashboard utility to run at a specified time.

Open

25.1,
23.3.xx

CMDB-797

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

25.1,
23.3.xx

CMDB-720

CMDB

While creating a CI in the CMDB Portal or creating a class-configuration you encounter the following error:

Something Went Wrong

Workaround: 

Verify the ingress definition for ingress platform-int pod and update path definitions as follows:

Change the /api/cmdb/v1.0/classes/ path to /api/cmdb/v1.0/classes

and

/api/cmdb/v1.0/attributes/ to /api/cmdb/v1.0/attribute

Open

25.1,
23.3.03

CMDB-717

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