Troubleshooting object definition corruption issues
When using Developer Studio, you might encounter certain issues such as you cannot view objects while you access them from Developer Studio or you get the "Unknown system error" message while opening or modifying objects. See the guidelines described here to resolve the issues about AR System metadata corruption. Alternatively, you can create a BMC Support case.
- You get the "Unknown system error" message while opening or modifying objects.
- You get the "Workflow does not exist" error message while accessing workflow reporting.
- You get an error message while importing or exporting workflow definitions.
- You cannot view objects while you access them from Developer Studio.
One or more users might experience the symptoms.
Perform the following steps to troubleshoot the issues with object definition corruption:
|1.||Clear the Developer Studio cache.|
|Change the Developer Studio workspace.|
|3.||Identify error messages in logs.|
Identify and record any related error messages in the following log files in the
|Enable AR Server logs.|
Perform the following steps to enable the AR Server-side API logs and SQL logs:
|5.||Reproduce the behavior and review logs.|
|6.||Try to import the affected workflow from the working environment of a similar version.|
|Run the Database Consistency Checker utility to identify the corrupted workflow objects.|
The Database Consistency Checker is a separate process that runs in the background during the server startup and terminates when the server startup is completed. This utility logs the results of the consistency check to the log file that you specify.
The utility checks the following database information:
For more information, see Running the Database Consistency Checker utility.
The Database Consistency Checker utility report might identify other problems that are not related to the affected objects. Focus your attention only on the workflow objects being affected.
|8.||Collect the logs.|
Copy the following log files to another location and then review them so that they do not get overwritten. A few log files might be huge in size depending upon the use case that was run.
See the table to troubleshoot issues based on the symptoms and error messages.
|9.||Create a BMC Support case.|
Collect and send logs and detailed information when creating a case with BMC Support:
After you determine a specific symptom or error message, use the following table to identify the solution:
|When you open or modify an object, you get ||On screen||KA000120931|
When you try to save a form in Developer Studio, you get
Locate the affected field on the form and then remove it and try to reimport the definition file.
For example, you might get an error message
This error message indicates that the records based on the "ARADMIN.SYS_C0010370" column contain a duplicate value that conflicts with the unique constraint of this column. The name=Date/Time Field__c field is involved in this scenario.
You must remove the name=Date/Time Field__c from the form and then save the form so that the form is saved without any error.