WCC Forecast giving errors
search cancel

WCC Forecast giving errors

book

Article ID: 205996

calendar_today

Updated On:

Products

CA Workload Automation AE - Business Agents (AutoSys) CA Workload Automation AE - System Agent (AutoSys) CA Workload Automation AE - Scheduler (AutoSys) Workload Automation Agent Autosys Workload Automation

Issue/Introduction

After upgrading WCC to version 11.4.7 the Forecast function does not work.

When trying to run a forecast this error appears:

2021-01-04 10:39:16,771 @forecast <127.0.0.1 X239134 ~DE5> [] ERROR #ReportsCommandServiceImpl          # Invalid time zone, using GMT offset.

I have confirmed WCC is set to the local timezone.  I even tried switching from "America/New York" to "US/Eastern".

 

Environment

Workload Automation AE (AutoSys)

Resolution

The WCC ECLI worked fine but the Forecast tab did not.
When we attempted to generate reports we would see errors such as
ERROR #ReportsCommandServiceImpl # Invalid time zone, using GMT offset.
in the /opt/CA/WorkloadCC/log/application/forecast/forecast.log

We went into WCC -> Configuration -> Servers -> ABCDEF (the server definition).
There we needed to set the "Time Zone", and save it.

Once this was done the errors about invalid time zone stopped but the reports still resulted in errors.
This time nothing was written to the logs.
We went to
/opt/CA/WorkloadCC/log/application/forecast/log4j.properties
and enabled:
log4j.logger.com.ca.wcc=DEBUG
log4j.logger.audit=debug, audit
Saved the file and you re-ran the report.
This time the forecast.log showed the true error.
The forecast command was not found.
The message was valid as we checked the as_server machines and the command was not present.

NOTE -
The "forecast" utility requires database interactions similar to the application server and the scheduler. It is distributed with the server installation and not with the Command Line Utilities.