Extending CMDB may report failures when extending/synching classes if “Max Entries Returned By Getlist” has been set to a limit and other errors.

Problem

 

When the CMDB is extended or synchronized with Asset (cmdb2asset synch), then the extensions may include cmdbdriver scripts, AR scripts, and/or data import operations. These operations may encounter AR Errors which mean that the operation failed, or AR WARN messages which mean the operation succeeded but with exceptions to the requested operation.  These warnings can be due to configuration problems or defects, but more importantly they will not be visible in the UI because they are captured in logs. One of those logs is CMDBSynchronizeUI.log. Each time a synchronization (Update UI) is triggered, the progress can be observed in this log and its completion is tracked by this last line of the log:

 

“Application UI synchronization completed”

If all of the operations were completed successfully. If not than errors might be seen in the log. Although some errors or warnings can be ignore.

 

These errors would say:

 

“Message:  The query matched more than the maximum number of entries specified for retrieval”  < This is a problem. This message typically means the “Max Entries Returned by GetList” setting for the server is not set to zero.

 

“Failed to create reserved system field: DSOUniqueId on Form” < This can be ignored.

 

“Admin operations are disabled on this server” < This is a problem. Uncheck the “Disable Admin Operations.

 

 

Solution

 

To check the value for  “Max Entries Returned by GetList” setting, access the AR System Administration Console from BMC Remedy User (or Mid-Tier) and select the following from the Vertical Navigation Bar:

AR System Administration Console –> General –> Server Information -> Select the Configuration Page

 

Check the value of  “Max Entries Returned By Getlist”

 

It is possible that this setting even if set to zero and the above warning may still be encountered.  It may be related to installation on a server that is slow low on resources, either due to insufficient memory or for other reasons.

Other reasons maybe users on the system are performing resource consuming tasks or data processing tasks such as Reconciliation or AIE Data Exchanges may have been triggered at the same time.

 

NOTE: The system should be returned to its previous state by restoring the limit as it was before.

 

On this same page you will also find the “Disable Admin Operations”. If it is checked, then please uncheck it.

Making changes in this panel will prompt for ARS restart. Please do so once you’ve completed the changes in this panel.