02-02-2017 11:50 PM - edited 03-12-2019 01:52 AM
Hi,
i encountered an unusual problem with the ASDM while logging into the ASA. I have 2 5515-X ASA's running 9.4.3 OS with ASDM 7.6.2 version. The problem is the ASDM shows the message "Getting updated software" and when it says "Software update completed", it gets stuck there. I tried almost everything, such as putting a new ASDM version on the active and the standby unit, reinstalling/installing older versions of java (currently using java 8), setting up java with recommended setting for ASDM (lower security and exceptions list), using 128-bit ciphers on the ASA but still nothing... Tested on Windows 7 x32 and Windows 10 x64. Does someone perhaps have any idea?
Best regards,
Zach
02-03-2017 04:57 AM
I have this problem too..but for me, it says "Contacting" and it never works.
A workaround I found is that you can run perhaps "ASDM as Java Web start application". That worked for me..:)
Best Regards,
Rikshit
02-03-2017 05:21 AM
I forgot to mention that i'v tried that too, but still, it doesn't work :/.
02-03-2017 05:50 AM
What is the error?? if it is a java error then perhaps you should give the IP address as an exception in the exception list in Java.Go to Programme, Java and then in Security and then add the management IP address of your ASA firewall. for eg.
https://x.x.x.x
02-03-2017 09:21 AM
I did that already before, but still, didn't help. Here is the java console output:
Using JRE version 1.8.0_121 Java HotSpot(TM) Client VM
User home directory = C:\Users\Test
----------------------------------------------------
c: clear console window
f: finalize objects on finalization queue
g: garbage collect
h: display this help message
m: print memory usage
q: hide console
s: dump system properties
----------------------------------------------------
Application Logging Started at Fri Feb 03 18:13:13 CET 2017
---------------------------------------------
Local Launcher Version = 1.8.0
Local Launcher Version Display = 1.8(0)
Cannot read profile file C:\Users\Test\.asdm\data\deviceinfo.conf.
OK button clicked
Trying for ASDM Version file; url = https://x.x.x.x/admin/
Server Version = 7.7(1)
Server Launcher Version = 1.8.0, size = 774656 bytes
invoking SGZ Loader..
Cache location = C:/Users/Test/.asdm/cache
2017-02-03 18:18:00,662 [ERROR] CLI-PASSTHROUGH-DEBUG Inside doInitialProcessing:
0 [SGZ Loader: launchSgzApplet] ERROR com.cisco.pdm.headless.startup - CLI-PASSTHROUGH-DEBUG Inside doInitialProcessing:
CLI-PASSTHROUGH-DEBUG Inside doInitialProcessing:
2017-02-03 18:18:01,037 [ERROR] CLI-PASSTHROUGH-DEBUG Inside doInitialProcessing messenger: cjk@121fe98
375 [SGZ Loader: launchSgzApplet] ERROR com.cisco.pdm.headless.startup - CLI-PASSTHROUGH-DEBUG Inside doInitialProcessing messenger: cjk@121fe98
CLI-PASSTHROUGH-DEBUG Inside doInitialProcessing messenger: cjk@121fe98
Exception in thread "SGZ Loader: launchSgzApplet" java.lang.NullPointerException
at m1.a(m1.java:263)
at m1.a(m1.java:140)
at com.cisco.pdm.PDMApplet.start(PDMApplet.java:155)
at com.cisco.nm.dice.loader.Loader$1.run(Unknown Source)
02-03-2017 09:35 AM
Did you try to downgrade to Java 7. I had similar problem which was fixed when downgraded to Java7
02-03-2017 09:36 AM
Tried that too, didn't work. I'v tried even with java 6, but nothing...
03-08-2017 11:26 AM
Any news on this topic ?
07-23-2017 10:10 AM
Stuck with same problem.
Any info about how to avoid this will be helpful.
07-23-2017 10:16 AM
It has been fixed in the recent ASDM version. Good luck :)
02-18-2018 12:46 AM
Thanks for advising problem solved by sing ADSM version 7.7(1)
Trying for ASDM Version file; url = https://192.168.1.140/admin/
Server Version = 7.7(1)
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