Class form generation issues

This section provides information about troubleshooting the Sync-UI utility that enables you to synchronize forms in BMC Helix CMDB with other BMC applications. For more information about generating forms, see Generating-forms-for-other-applications.

You might encounter errors when you synchronize the BMC Helix CMDB class forms with the forms in other applications by using the Sync-UI command. For example, you might have a missing entry in the Application Pending form, or corresponding BMC Helix CMDB forms that are not created in the other application. Use the following procedure to troubleshoot these issues. 

To troubleshoot CMDB Sync-UI issues

1. When you create a class in BMC Helix CMDB, verify that a record is created in the SHR:SchemaNames form.
2. After you click the Update Asset UI button, verify that a record is created in the Application Pending form.

3. Verify that the arcmdbd server process is running.

   Success

   Tip

   To view the processes that are running on a Windows computer, open the Task Manager and click Processes. On UNIX, type the ps -ef command at the prompt.

4. Examine the arerror.log file for any errors logged for the arcmdbd server process.
   For more information about arerror.log, see AR System server logging.
5. Verify that the record in the Application Pending form is deleted.
   After the arcmdbd server process starts, the record is deleted.

6. Examine the output in the CMDBSynchronizeUI_<integer>.log file.
   A log file using this naming convention is created when the user interface in the BMC Helix ITSM: Asset Management application is updated. This log file is saved in the the following location:
   (Windows) <installationdirectory\ARSystem\Arserver\db 
   (UNIX) <serverInstallationDirectory>/db
   
   

   Success

   Tip

   If you do not see an Application UI synchronization completed entry in the log file, the operation is still in progress.

7. Verify that the CMDB shared library file is in the same directory as the arcmdbd server process. The CMDB shared library file name is one of the following, depending on your environment:
   (Unix ) libcmdb2asset.sl (also, possibly with .so or .dll extensions)
   (Windows ) cmdb2asset_win64.dll
8. If the synchronization process was not successful, view the arapi.log or arsql.log file for detailed information about any errors that might have occurred.
   Enable API and SQL logging. Log files are created in the location:
   (Windows) <installationdirectory\ARSystem\Arserver\db 
   (UNIX) <serverInstallationDirectory>/db

Warning messages when synchronizing BMC Helix CMDB forms with other applications

When you synchronize forms in BMC Helix CMDB with other BMC applications, such as BMC Helix ITSM: Asset Management, you might receive warnings as listed below:

These warnings, which are recorded in the CMDBSynchronizedUI.log, indicate that the resulting UI form has a missing field. However, you can safely ignore these warnings if the field meets the following conditions:

• The field does not correspond to an attribute defined by the superclass.
• The field corresponds to an attribute defined by a categorization class.

In such cases, the SyncUI process finds the fields defined by a categorization class on the parent form. You should not create these fields on the UI form because they are not defined by the super class.