WCC login stuck on Loading User Interface...

[Jim Spath]

After patching AutoSys to 11.3.6.SP1 and applying the attendant required WCC patch, I cannot connect to WCC on 2 different browsers (IE8/FF38) on my PC, can connect on a different browser on a different machine (IE10), and cannot connect on yet another machine (IE8).  One colleague gets the same fault on his PC (IE?), while another has no issue on her PC (IE10).

 

We do have a ticket open, but meanwhile, this does seem like a browser cache issue, or something.

 

Have tried:

 

• Rebooting PC
• Clearing browser cache, history, cookies, etc.
• Rebooting WCC server (had to for SP1 patch anyway, but twice now).

 

Head scratching time.  What else can we look at?

 

[Steve Carrobis]

here's what to do.

• take a step back
• breathe
• remember its M$
• make sure firefox works and chrome.
• then ask about java versions
• then check settings
• then contact the windows support team and make sure they didnt disable anything necessary when they pushed that version out.
• I have seen this before.. its a royal PITA

[Steve Carrobis]

make sure that user doesnt have more than one version of java and have IE/java redeployed..

[Chandru.Venkataraman]

For IE, please try enabling compatibility mode.

[Jim Spath]

• Have done the Java shuffle (and Flash to boot); removed unsafe versions, activated latest and greatest
• Firefox also does not work for me (Chrome not installed yet)
• Compatibility mode setting changes had no effect
• Windows patching is probably not related due to timing (but who knows)

[Steve Carrobis]

ok if firefox isnt working. then it maybe firewall or internal settings.. especially if you are at a firm that doesnt let you admin the browser.

CA usually says IE is not their primary browser to make work. and i have seen it as so. BUT i have seen that settings is what does it..

 

Look at that.. because typically FIREFOX always works. so this is either a huge bug or something your firm is doing to hamstring your browsers..

go to the person not having problems.. and see if firefox works. if it does then its absolutely how browsers are being deployed and could be a certificate or firewall type issue..

sometimes you have to pla.. which one of these things doesnt belong with the other..

[Jim Spath]

As another data point, I can connect to 2 WCC instances that are still at 11.3.6 without issue on either IE or FF on my PC.

 

Will see if Slot A can reach Tab B.

[Steve Carrobis]

you patched? and rebooted? maybe try uninstall reinstall ;-)  as painful as that may be ..

Good luck..

[Chandru.Venkataraman]

On the PC you’re still able to access, does it work after clearing cache? Maybe the patch didn’t go in well and your PC picked up the latest while the still-working PC is holding on to the good version. Please validate the fix using patchtool VERIFY.

[Jim Spath]

The RO80613 patch went in, but not cleanly, it appears.  The install log didn't complain at the end (only in the middle).

 

= =

[...]

 

2015-06-10 15:33:28 Error copying 2_6.cache.js to []\tomcat\webapps\wcc\launcher\deferredjs\[].cache.js: No such file or directory

2015-06-10 15:33:28 CA-wcc-services Service starting

2015-06-10 15:33:31 CA-wcc-services Service started

2015-06-10 15:33:31 CA-wcc Service starting

2015-06-10 15:33:36 CA-wcc Service started

2015-06-10 15:33:36 Total copied files: 105

2015-06-10 15:33:36 Total backed up files: 86

2015-06-10 15:33:36 Total deleted files: 86

2015-06-10 15:33:36 WCCPatchTool:  Complete.

2015-06-10 15:33:36 The logs have been saved in []patches\logs\WCCPatchTool_20150610_153230_RO80613_INSTALL.log.

 

= =

 

2015-06-16 09:47:19 RO80613 patch has not been installed correctly.

2015-06-16 09:47:19 Number of files that may not be installed correctly based on filesize = 17

 

= =

 

Back to the CA ticket queue.  Thanks all.

[Steve Carrobis]

dont you love when that happens.. GOOD LUCK.

[Legacy User]

Enabling the parameter described below resolved a similar issue with my WCC environment on Red Hat 6.5 and WCC 11.3.6 Incremental 3.

 

 

 

un-commenting the line below in "wrapper.conf" and restart WCC

 

#wrapper.java.additional.101=-Djava.security.egd=file:/dev/./urandom

 

You will need to un-comment the above line in both "wrapper.conf" files, that is in:

$CA_WCC_INSTALL_LOCATION/tomcat_32/conf/wrapper.conf

$CA_WCC_INSTALL_LOCATION/tomcat/conf/wrapper.conf

[Jim Spath]

CA provided a modified patch RO806013 that worked.

 

The original version had problems, but exited without complaint.  That's a bug.

 

The verify patch command did complain about the first version not being installed completely.  We'll add this step to every future patch.

[Steve Carrobis]

thanx!