10-21-2013 11:03 AM
I had to roll back the Java JRE7u45 back to u40.
If anyone finds out the config mod to make u45 work, please, post.
update 45 is again a significant update and it would be good to have it work with UCSM.
Cisco should get rid of Java based Manager as it is inherently insecure and leaves a large gapping hole in security for little monetary savings it gives in Manager development for Cisco. Vmware is moving toward browser based manager. It really is time to bury Java.
10-21-2013 01:37 PM
Problems exist with u45 and 2.1(2a) as well.
10-21-2013 04:04 PM
Ran into this issue this morning as well. I also had to completely uninstall Java and reinstall an older verison.
For everyones' convenience, here's a direct link to the 32-bit package I used (since I have a 32-bit brower on a 64-bit Windows system) that got everything working:
Other versions are of course on the same page:
http://www.oracle.com/technetwork/java/javase/downloads/java-archive-downloads-javase7-521261.html
Hope this helps!
10-30-2013 06:47 AM
It's a current bug between UCSM and Java 1.7 U45. It is something we are working to address with upcoming UCS Manager releases to fix the bug between UCSM and Java 1.7 U45.
11-11-2013 01:00 PM
Is there an ETA for this update?
12-13-2013 10:35 AM
Any eta on the application installation issues with 1.7U45?
12-13-2013 12:30 PM
Any further updates?
12-13-2013 01:34 PM
Actually, this is fixed in the 2.2 release that came out earlier this week. I haven't seen anything about a fix for 2.1 and earlier.
12-13-2013 01:36 PM
Thanks for the updates
05-05-2014 11:49 AM
Issue resolved.
Upgrade to UCSM 2.2 and install jre-7u45 it fixes the login problem.
07-10-2014 03:57 PM
As an update, in the 2.1 tree, this is fixed in 2.1(3d), according to the release notes:
02-16-2015 12:18 PM
Is there some way to hack together custom JNLP files in case you are unable to change either the UCS or the Java version on the workstation? I have Java8 installed, and Oracle is intent on burying any earlier versions into the deepest possible hole. In addition, the UCS systems are managed by an entirely different group, and we would not be able to get them upgraded (2.1 (3a)). so short of having a VM that *ONLY* runs UCS client (a serious waste of time, resources, and an absolute PITA) how do we get around this?
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide