800xA scheduled report not run
Dear Geof,
I have some scheduled report which were configured and run well. But from 2 days ago, 2 of them did not run (1 is daily as schedule and 1 is demand run).
I have checked job log and just saw that "Report Action not run".
Please see attached file as my screenshots.
Please give me some advice to check. Parallel, I also submitted support request to ABB Singapore but not receive answer yet.
Thanks in advance.
I have some scheduled report which were configured and run well. But from 2 days ago, 2 of them did not run (1 is daily as schedule and 1 is demand run).
I have checked job log and just saw that "Report Action not run".
Please see attached file as my screenshots.
Please give me some advice to check. Parallel, I also submitted support request to ABB Singapore but not receive answer yet.
Thanks in advance.
Asked 10 days ago
Answers
1
Vutq,
There are a number of items that you can check that may provide some insight to what the problem could be. First, in the directory, "C:\ProgramData\ABB\IM\Scheduler", there should be two files, ABBAction.log and ABBScheduler.log. These can be examined to see if there is any issues shown. The next thing to check is to see if you can run the report from the "Test Action" in the Action Aspect. You need to right-click on the Action Aspect and select the "Test Action" option.
This will eliminate the actual Scheduling software and just check the entries in the Action Aspect. After this is done, you can check again the ABBAction.log file for any information. Depending on the success or failure of these steps, it may be necessary to open a Support Case with your local Support Group, and if necessary, they can forward the case to the US-L3 Support Group, where I work.
One other item to check is the status of the Output File location where you are storing the Results. When initially configured, this directory is configured with the maximum number of Reports to hold. Make sure that this directory is not full.
Regards,
Geof
There are a number of items that you can check that may provide some insight to what the problem could be. First, in the directory, "C:\ProgramData\ABB\IM\Scheduler", there should be two files, ABBAction.log and ABBScheduler.log. These can be examined to see if there is any issues shown. The next thing to check is to see if you can run the report from the "Test Action" in the Action Aspect. You need to right-click on the Action Aspect and select the "Test Action" option.
This will eliminate the actual Scheduling software and just check the entries in the Action Aspect. After this is done, you can check again the ABBAction.log file for any information. Depending on the success or failure of these steps, it may be necessary to open a Support Case with your local Support Group, and if necessary, they can forward the case to the US-L3 Support Group, where I work.
One other item to check is the status of the Output File location where you are storing the Results. When initially configured, this directory is configured with the maximum number of Reports to hold. Make sure that this directory is not full.
Regards,
Geof
0
1) Always try to provide enough time gap between Scheduled time of Reports.
2) If Operators are adopting habit to Close all other Excel Files before the time of Auto-generation of reports, that is going to be another Help for your issue.
3) Check the "TimeOut" parameter in your Scheduling Definition/Action Aspect.
2) If Operators are adopting habit to Close all other Excel Files before the time of Auto-generation of reports, that is going to be another Help for your issue.
3) Check the "TimeOut" parameter in your Scheduling Definition/Action Aspect.
Answered 9 days ago
Source: PRACTISE
Add new comment