AutoSys Workload Automation

We have 3 WAAE 11.3.6 instances configured across primary/shadow servers and we have WCC primary and secondary servers managed by apache configuration. When you go direct to primary WCC we can access all instances through the quickview tab but when we try that on the WCC secondary server we can only see jobs for 2 instances and not the 3rd. We get the following error messages;

CAUAJM_E_10062 - Failed to get initial configurationfrom CA CAAE Application servers

E139012 AutoSys error response

E131003 Error loading job: E180010 could not establish connection to CA Workload AutomationAE; invalid server context.

Not sure if this is an EEM issue!

Hi Michael,

When you say "WCC primary and secondary servers managed by apache configuration.", you mean a load-balancer like configuration and you are not using the native WCC HA? If not native-WCC HA, then each WCC is using its separate database? In this case you need to validate all AE servers configured in each WCC servers directly.

The "invalid server context" could happen for various reasons, including:

https://comm.support.ca.com/kb/login-failed-returned-in-quickview-job-search/kb000007024

https://comm.support.ca.com/kb/quickview-error-cauajm-e-10045-an-invalid-encryption-key-was-specified/kb000100236

https://comm.support.ca.com/kb/wcc-quickview-cauajm-e-10045-an-invalid-encryption/kb000106753

I'd start with comparing the configuration between the working and non-working WCC and also the credentials. Pay attention to the Encryption type and EEM Enabled fields.

I hope this helps.

Cheers,

Chandru

@Michael,

It'd be nice if you could post an update on this if the reported behavior has been addressed. Please share the resolution so others could learn.

Thank you,

Chandru

Hi Michael,

Are you still seeking responses on this query? If your concern is addressed, please share the solution for other members' benefits.

Thank you,

chandru

Hi  Michael,

There is different solutions to suggest for this issue.

- what needs to be done is to clear the monitoring cache and let it reload from autosys.

To do so you will need to run the following command: $CA_WCC_INSTALL_LOCATION/bin/wcc_monitor.sh -u commander_level_username -p password -d ALL (OR server name)

-  confirm the csampmux settings are equal on both the server and client.

https://comm.support.ca.com/kb/getting-errors-while-issuing-jil/kb000091783

- apply the latest WCC testfix T6FU003 which fixes many issue for

WCC QUICK EDIT, MONITORING & REPORTING FIXES

to get this fixe you need to open a new case and ask the testfixe to be uploaded under the case

Please let us know what is the solution you will apply to resolve this problem

Thanks and best regards,

faouzia

I would add to the CSAM verification that you are able to communicate on port 7163 bi-directional from WCC to that AE server.

Regards,

Mike