04-09-2013 09:47 AM - edited 03-11-2019 06:25 PM
I am receiving an exception error when launching ASDM. I have see on the web (and have experienced an issue similar to this before) where a reload resolves the issue. However, I did issue a reload and the error continues. Strange thing is, when I look at the uptime in SH TECH-SUPPORT it shows over a year . Now this firewall is on an active/passive cluster, so my question is, did the reload work on just one and the other took over and so a reload actually did not occur?
We have an issue going on right now where it would be extremely helpful to have this console working.
Thanks In Advance.
JT
Using JRE version 1.4.2 Java HotSpot(TM) Client VM
User home directory = C:\Documents and Settings\User
----------------------------------------------------
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
----------------------------------------------------
ASDM Application Logging Started at Tue Apr 09 09:45:02 PDT 2013
---------------------------------------------
Local DM Launcher Version = 1.5.22
Local DM Launcher Version Display = 1.5(22)
OK button clicked
Cache location = C:/Documents and Settings/User/.asdm/cache
Checking the DM Launcher Version; url = https://10.1.1.1/admin/
Server DM Version = 6.0(2)
Server DM Launcher Version = 1.5.22, size = 318464 bytes
DM Launcher version checking is successful.
invoking SGZ Loader..
java.lang.NumberFormatException: For input string: "1 year 16"
at java.lang.NumberFormatException.forInputString(Unknown Source)
at java.lang.Integer.parseInt(Unknown Source)
at java.lang.Integer.parseInt(Unknown Source)
at com.cisco.pdm.Check.h(DashoA10*..:1339)
at com.cisco.pdm.Check.c(DashoA10*..:842)
at com.cisco.pdm.Check.a(DashoA10*..:442)
at com.cisco.pdm.Check.<init>(DashoA10*..:221)
at com.cisco.pdm.PDMApplet.start(DashoA10*..:124)
at com.cisco.nm.dice.loader.r.run(DashoA19*..:410)
04-09-2013 03:04 PM
Hello Jason,
It could actually be that you reloaded the primary ASA and you are now looking at the secondary(now active) ASA.
do a "show version" and "fail exec mate sho ver" to see the up time for both active and standby ASAs.
You can also try switching to the primary (now standby ASA) using the command "no failover active" and try to access the ASDM again.
Regards,
Felipe
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