The alarm scripts associated with the SLA alerts do not trigger.

Document ID : KB000007618
Last Modified Date : 14/02/2018
Show Technical Document Details
Issue:

The alarm scripts associated with the SLA alerts are no longer effective. The below error  message has been captured in the info.log for the Informatica_loader Job: 

17-07-24 15.55.31 [ INFO] idash-SLA-processing: processAlarm():       sla=Informatica_loader^ACE

17-07-24 15.55.31 [ INFO] idash-SLA-processing: processAlarm():       job=Informatica_loader

17-07-24 15.55.31 [ INFO] idash-SLA-processing: processAlarm():  deadline=20170724-1755

17-07-24 15.55.31 [ INFO] idash-SLA-processing: processAlarm():alarm type=SLA_PREDICTED_MISSED_END

17-07-24 15.55.31 [ INFO] idash-SLA-processing: processAlarm():alarm name=SLA_PREDICTED_MISSED_END

17-07-24 15.55.31 [ INFO] idash-SLA-processing: empty configuration:type=alarm.policy:id=

17-07-24 15.55.31 [ INFO] idash-SLA-processing: Alarm Notification Policy:notify.always

17-07-24 15.55.31 [ INFO] store-jfm-msg-thread-1: storeJfmConsoleMessage(): using primary db connection

17-07-24 15.55.31 [ INFO] idash-SLA-processing: doCommand:D:\SLA\alert.bat

17-07-24 15.55.31 [ INFO] idash-SLA-processing: Append:D:\Program Files\CA\idash\dat\audit\idash-server_audit_20170724.idaa

17-07-24 15.55.31 [ INFO] store-jfm-msg-thread-1: storeJfmConsoleMessage(): unable to connect to secondary db connection

17-07-24 15.55.32 [ INFO] idash-SLA-processing: shell command=:cmd

17-07-24 15.55.32 [ INFO] idash-SLA-processing: shell command argument=:/c

17-07-24 15.55.32 [ INFO] idash-SLA-processing: command=:D:\SLA\alert.bat > D:\Program Files\CA\idash\dat\tmp\comm.out0.8563400289127369 2>&1 

17-07-24 15.55.32 [ERROR] idash-SLA-processing: Error in iDash command

com.ca.idash.core.exception.IdashException: java.io.FileNotFoundException:D:\Program Files\CA\idash\dat\tmp\comm.out0.8563400289127369 (The system cannot find the file specified)

at com.ca.idash.core.instance.ae.UserCommand.doCommand(UserCommand.java:363)

at com.ca.idash.core.instance.ae.UserCommand.doCommand(UserCommand.java:226)

at com.ca.idash.core.sla.SLAAlarmProcessorUtils.issueAlarmCommand(SLAAlarmProcessorUtils.java:156)

at com.ca.idash.core.sla.SESLA.processAlertX(SESLA.java:1550)

at com.ca.idash.core.sla.SESLA.processAlert(SESLA.java:1364)

Environment:
All CA WA iDash supported Windows Operating systems
Cause:

The problem happens if the CA WA iDash is installed on Windows server while the volume shortname (8dot3name) is enabled on the drive and later the shortname is disabled.

Resolution:

1. Stop the CA WA iDash service from the Service Control Manager (services.msc).

2. Check the Windows directory shortname status.

D:\>dir /x

 Volume in drive D is loddisk2
 Volume Serial Number is B2EB-5DDC
 Directory of D:\

07/25/2017  09:46 AM    <DIR>                       .
07/25/2017  09:46 AM    <DIR>                       ..
07/25/2017  09:46 AM    <DIR>                       Program Files
               0 File(s)              0 bytes
               4 Dir(s)   8,873,586,688 bytes free

Notice in the above result that the shortname for the directory "Program Files" is blank.

D:\>fsutil file setshortname "Program Files" PROGRA~1
Error:  Short names are not enabled on this volume

The error confirms that the 8dot3name is disabled.

3. Enable the shortname and set the shortname for "Program Files" directory.

D:\>fsutil.exe 8dot3name set 0
The registry state is now: 0 (Enable 8dot3 name creation on all volumes).
D:\>
D:\>fsutil file setshortname "Program Files" PROGRA~1
The Shortname for the Directory "Program Files" has been successfully created
D:\>dir /x

07/25/2017  09:46 AM    <DIR>                       .
07/25/2017  09:46 AM    <DIR>                       ..
07/25/2017  09:41 AM    <DIR>          PROGRA~1     Program Files

4. Start the CA WA iDash Service from the services manager.

Additional Information:

Fsutil 8dot3name