Issues table

When you create or search for a multilevel CI in CMDB Explorer, group nodes or CI nodes might shrink and not be displayed correctly. 

Workaround:

Use the following steps to display the CI nodes correctly:

• Refresh the browser, and then click the + icon on the left side of the affected CI nodes to expand them.
• Adjust the browser zoom level (zoom in or out) to stabilize the view.

When you define concatenation incorrectly in a reconciliation identification rule, the system does not match CI records and may assign different reconciliation IDs to the same CI.

This issue occurs because the rule must match a value in one column that is created by combining values from two columns. If the concatenation is not defined correctly, the system cannot match the CI records.

Workaround:

Define the identification rule using the correct concatenation format. 

For example, to match a value like laptop@bmc.com, where the result is derived from the Name and Domain attributes, define the rule as:
'Name' = $Name$ + "@" + $Domain$

This ensures the rule correctly constructs the combined value and matches the target CI records as intended.

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

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

Open 

CMDB-1241

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.

CMDB-7245 

CMDB-6565 

CMDB-7398

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.2.00,
26.1.00,
25.4.00,
25.3.00,
25.2.00,
25.1.00,
23.3.00,

CMDB-158