In Mid Tier, the calendar does not load.
- In a server group environment, the calendar does not open in one or more servers.
- More than one change requests that have the same scheduled dates are associated to the same CI.
Diagnosing and reporting an issue
| | |
---|
| Enabling the network logs | |
| | |
| Enabling the server-side AR system logs | |
| Validating the calendar configuration | |
If you upgrade BMC Helix ITSM, you can access the logs by performing the following steps:
- In Internet Explorer 11:
- From the Tools menu, select F12 Developer Tools .
- Click the Console tab.
- In Google Chrome:
- Go to Customize and control Google Chrome > More tools > Developer tools.
- Click the Console tab.
In the logs, look for the following error that might occur after after you upgrade BMC Helix ITSM. To resolve this issue, see Resolution for HTTP Error 500.
"mimeType": "application/json",
"text": "{\"error\":\"ServiceException: java.lang.AbstractMethodError\"}"
| | |
---|
The calendar does not load and keeps spinning. | - From Applications > AR System Administration > AR System Administration Console , select General > Centralized Configuration.
- From Component Name, select om.bmc.arsys.smartit > *
- Make sure that ar.date.format meets the following conditions:
- ar.date.format matches the time format of the BMC Helix ITSM server.
For example: ar.date.format=dd/MM/yyyy HH:mm:ss (24-hour format) ar.date.format=MM/dd/yyyy hh:mm:ss a (12-hour format)
| |
The calendar does not load and displays the following error: | This error occurs because the .jar file from the earlier release exists in the Smart IT directory location. Perform the following steps to resolve the issue: - Take a backup of the .jar file for the earlier release and delete the .jar file from the following folder location.
<Install Directory>\Smart_IT\Smart_IT\smartit\WEB-INF\classes\provider\change - Restart the Smart IT services.
| |
When you try to open the calendar, you experience performance issues. | This issue occurs because two or more change requests are associated to the same CI and have the same scheduled dates. To resolve the issue, add new indexes in the following forms: - Make the following changes on the BMC.CORE:BMC_BaseElement form:
Create new indexes on the BMC.CORE:BMC_BaseElement form with the primary key field and add INCLUDE for C179 and C200000020.
For example, to primary key pk_T549, add INCLUDE for C179 and C200000020 - Make the following changes on the CHG:Associations form:
- Create new indexes with the primary key field and INCLUDE for C1000000204 and C303633900 .
- Create second index I2270_0_1000000205 and INCLUDE for C1.
- (Optional) After adding the above indexes, refresh Stats for the two tables in database.
| |