One thing I noticed today was that I couldn't launch Cisco's ASDM from my laptop running a clean install of Vista SP1. I noticed the same error on my desktop at work as well, right after login, I'd get this:
ASDM is unable to continue loading. Click OK to exit from ASDM.
Unconnected sockets not implemented.
I was trying to connect to an ASA5505 and an ASA5510, both running 8.0(2) and ASDM 6.0(2). Well after half an hour of research, and not finding a fix, I started troubleshooting on my own. I found the problem to be the Java runtime version I was using. It seems ASDM is incompatible with JRE 6u10. I uninstalled it and installed JRE 6u7 and then ASDM came right up with no errors.
So there you go, if you're running Vista SP1, ASDM will not work with JRE 6u10, try 6u7 instead.
-Rick Estrada
EDIT 2008/11/26@08.14
I had a question about where to download JRE6u7, so here it is:
Go to this page, and click the "Download JRE" link, then select your platform and language, and you should be presented with the online and offline installers.
Also, remember to disable automatic updating of your Java engine by going to "Control Panel" > "Java" icon > "Update" tab > and uncheck "Check for updates automatically". The "Java" icon appears in the control panel only when it is in "classic view", both in XP and Vista.
-Rick Estrada
I've been getting a lot of possitive feedback on this one, so I enabled commenting for the blog.
ReplyDeleteI really appreciate everyone's input.
-Rick Estrada
Great ! This helped me out to get in ASDM on a PIX 515.
ReplyDeleteThanks.
THANKS! This also fixed the same symptom on Windows XP SP3 running JRE6u10. removing that and installing JRE6u7 fixed the problem.
ReplyDeleteThanks a bunch!
Don M. - Columbia, MO
Thank you! this fixed the ASDM problem
ReplyDeleteThanks! Fixed it for me too. This also appears to be the fix when ASDM won't start on Server 2008. However on this OS there is no error message the ASDM just never appears.
ReplyDeleteThanks! Problem solved!
ReplyDeleteGreetings!
Michel,
The Netherlands.
Thanks... I just got the "unconnected sockets" error while trying to run ASDM and yours is the first page on a Google search to find the problem... thanks for the solution!
ReplyDeleteThomas Dzubin
Canada
Very cool....thanks for the tip.
ReplyDeleteThankyou for this fix :-D Java bring pain!
ReplyDeleteAppreciate help we were sweating issues this am and couldn't use the "easy" interface.
ReplyDeleteI feel stupid asking this question, but where is everyone getting JRE 6u7? I've been poking around Sun's site and googling it, but I can't find it.
ReplyDeleteThe only JRE 6u7 I could find was for Itanium machines.
thx，I find the same mistakes that you talk. I uninstalled the JRE 6u10 and then ASDM get right.
ReplyDeleteThanks very much on the ASDM Java tip! Worked great after installing 6u7 instead of 6u10 which was blowing up.
ReplyDeleteSaved me hours of time.
Thanks again!
Thank you. This helped me.
ReplyDeleteI discovered the same issue few days ago. With JRE6u7 properly works on XP SP3 and Vista SP1 also.
ReplyDeleteThanks buddy. This was a great help after beating around the bush for 2 days.
ReplyDeleteIt works for me. Thanks for sharing
ReplyDeleteIt works! Thanks a lot!
ReplyDeleteThanks a million! I was having the problem on WinSvr2008x64. Uninstalling 6u10 and replacing it with 6u7 got it to work.
ReplyDeleteJava lives to gank everyone for another day. That fixed it for me. Cheers
ReplyDeleteFixed for me! Thanks a lot, you saved me a lot of time
ReplyDeleteI heard that Java Version 6 Update 11 is out, so maybe that'll fix it. But another workaround instead of uninstalling is disabling 6u10 in the control panel (good for the web ASDM) and changing java version in HKEY_LOCAL_MACHINE\SOFTWARE\JavaSoft\Java Runtime Environment\1.6\JavaHome and HKEY_LOCAL_MACHINE\SOFTWARE\JavaSoft\Java Runtime Environment\1.6\RuntimeLib (good for ASDM launcher). You can check by doing java -version and prompt. May wish to change the java executables in system32 to be complete, but not necessary.
ReplyDeleteThere is a new ASDM in the Interim Releases that supposedly fixes this problem, but I can't get it to login to my ASAs.
ReplyDeleteThanks. This was a great solution. Let me add something. I am running Vista 64-bit, so if you go to get Java 6.7 make sure you do not download and install the 64-bit Jave version. Get the standard version 32-bit version because the ASDM is looking for Java in the x86 program files of Vista x64.
ReplyDeleteAnother grateful admin. Thanks for the tip!
ReplyDeleteFixed me too. Thanks!
ReplyDeleteYou have to love Cisco and Sun! Cisco for wanting to use old Java and Sun for making new ones that don't work with older versions!
ReplyDeleteAnd, BTW, update 11 doesn't work either!
I had the problem start happening out of nowhere. I had JRE v10 installed. I tried the JRE v11 upgrade but that didn't help either. I removed JRE v11 and went back to JRE v7 and it works great now. I've made sure to disable automatic updates now as well.
ReplyDeleteThanks for the post. Hopefully Sun / CISCO will fix this.
Thanks a lot Rick,
ReplyDeleteYour post resolved my problem ;-)
Here's another little nugget of knowledge..
ReplyDeleteTurns out PDM doesn't like JRE 7, although it worked fine with 10 (not sure about 11)! So you can't have an install that works with both PDM, and ASDM!
Just can't win with these guys!
Glad we have this thing called 'Virtualization'!
:)
Cisco has a fix! See CSCsv12681.
ReplyDeleteHere are the releases it is fixed in:
6.2(0.70)
6.2(0.71)
6.1(1.55)F
5.2(4.51)
6.1(5.51)
Thanks for the great info! The workaround got me going while I was chasing the fixes.
Jason
Thank you so much for that i have been working on that for about a week and am due to go out on business soon. many thanks
ReplyDeleteSame problem on fresh XP SP3, Java 6 Update 11 and latest ASDM 6.1.5. AFAIR, didn't have any problems on Java 6 Update 3.
ReplyDeletejust download the latest ASDM an install it on your firewall.
ReplyDeleteThanks, that saved me today.
ReplyDeleteAnother quick trick is to use ASDM as an applet instead of using the launcher. The control panel let's you pick what version of Java to use for applets. You can have multi version on java running that way.
ReplyDeletehello
ReplyDeleteI installed the 6.1(5.51) but i can't connect to my asa
but the cisco patch resolve juste one thing : there is no error message
ASDM load but stop when "software update completed"
Yet another satisfied anonymous internet person.
ReplyDeleteI have enough to deal with without having to figure out why I can't even access the web admin page, you saved me much frustration.
jetjet51: I believe this is probably due to Java 6 Update 11. I couldn't find a copy of 10 to download to actually verify, but Update 7 still works to get around this problem. It looks like Cisco has an ASDM 6.1(5.57) out under the interim releases category now as well -- I suspect this may further fix things, however, my blasted Pix at work is jammed up now with some ghost connections, so I can't erase the older 6.1(5.51) from flash and put .57 in to see if it fixes things any further.
ReplyDeleteSuffice it to say, if I had the energy, I'd be writing some really nasty hatemail to Cisco AND Sun right about now...
Rick: Thanks for the information it helped me out to get acces to my ASA 5010.
ReplyDeleteRicardo Castrejon
After looking at the strings in in the ASDM-Launcher.exe executable, I found I could set the version of java that the ASDM launcher was using by adding a line "javapath c:\Program Files\Java\jre1.6.0_07\bin\client\jvm.dll" to the asdm-launcher.config file. That lets me leave my default JRE as 1.6.0_11.
ReplyDeleteVerified that v11 still causes this issue, rollback to 7 works great. Kudos for the informative, respectful blog.
ReplyDeleteThanks for the information this did the trick for me as well. I used the info from Tim Braun and it worked like a champ :)
ReplyDeleteHey, folks - thanks for the help!! This jumped out at me from nowhere, too, and I had no idea what was going on. As soon as I got rid of update 11, all was well.
ReplyDeleteAppreciate it!!
Jon Koelker
Oyster River Co-operative School District
Durham, NH
Hey, folks - thanks for the help!! This jumped out at me from nowhere, too, and I had no idea what was going on. As soon as I got rid of update 11, all was well.
ReplyDeleteAppreciate it!!
Jon Koelker
Oyster River Co-operative School District
Durham, NH
This saved a lot of time as came up in the top on my Google search and worked great. Thanks for taking the time to write up.
ReplyDeleteMuchas gracias, me ha servido de maravillas, me salvaste la vida.
ReplyDeleteThanks soo much, your save my life....
just wanted to join the long list of people who are saying thanks!
ReplyDeleteso.... THANKS!
*sighs* This always happens with Cisco PDM/ASDM. Back when I had an old school 520 PIX I couldn't upgrade my Java beacuse of the same problems with incompatability.
ReplyDeleteThanks for the observation and documenting the fix.
-Nick
Thanks,
ReplyDeleteIt works for me. There is some bug in JRE update 11 which cause this problem when lanching ADSM.
From Tacoma, WA.
ReplyDeleteFixed my ASDM error, also.
From San Jose, Costa Rica
ReplyDeleteThanks a lot man! It solved my ASDM problem as well.
Juan P.
Yups it works... Thanks
ReplyDeleteI getting same error for my both PC when connecting from ASDM to ASA5505.
ReplyDeleteFirst PC:
Windows XP Pro with SP3 install with Java Run Time 6 update 11
Second PC:
Windows Vista Businese with SP1 install with Java Run Time 6 update 12
After downgrade to Java Run Time 6 update 7 the error disapear and both running fine.
You may download the Java Run Time 6 update 7 at http://java.sun.com/products/archive/j2se/6u7/index.html
Thanks a lot guys for help :) Me too having same prob..... that darn JVM :)
ReplyDeleteWOW! - I'm using Vista 64bit and had similar troubles with ASDM (java null pointer exceptions and ASDM hangs). After installing 6u7 ... it works!!!
ReplyDeleteI cannot believe that newer versions of Java are producing such errors ... really bad backward compatibility!
Thanks for sharing your expirience!
Philipp
Thanks a ton. I was misinfomed that the issue is with Java 6 and only Java 5 is compatible with Win Vista.
ReplyDeleteGot this issue solved by upgrading asdm client to version 6.1(5)
ReplyDeleteWhack the following in a batch file, and run it - the last line of the 3 is pretty much just what's in the asdm-launcher.config file - substitute path's as required - I'm happily running the ADSM with update 7 and another Java based program (in-house app) using update 12 simultaneously using this method:
ReplyDeletePATH="c:\Program Files\Java\jre1.6.0_07\bin"
cd "C:\Program Files\Cisco Systems\ASDM"
java -cp lzma.jar;jploader.jar;asdm-launcher.jar;. -Xms64M -Xmx256M -Dsun.swing.enableImprovedDragGesture=true com.cisco.launcher.Launcher
Thank you for saving me the hassle of troubleshooting this! I found this solution quickly thanks to your post.
ReplyDeleteGreat, 10x!
ReplyDeleteThanks I am now able to run a demo version of ASDM6.1(5)in windows vista.
ReplyDeleteJave update 6 hint helped and saved lot of time... Thanks for the post
ReplyDeleteNaresh
instead of uninstalling the J-upd you can go into control panel, change the used JRE to an older version, and use JAVA webstart to launch ASDM from the browser (https://ur_fw_ip/admin/) - that will work, however might be a hassle.
ReplyDeleteThank you very much for this post.
ReplyDeleteThanks for the comments here guys but I had the same problem, downgraded and now have another problem - once it gets to the "software update completed" bit, it just hang waiting.
ReplyDeleteWon't let me post the log stuff I'm afraid
Any ideas?
George
Hey George,
ReplyDeleteI think I saw this once at a remote site once on an ASA 5505. I belive what resolved the issue was updating the ASDM code on the ASA itself, then reloading the ASA. I remember trying to troubleshoot the issue on my laptop, but the problem was actually the ASA.
Hope this helps!
Fixed mine too... thanks a bunch!!!
ReplyDelete- V
I all the sudden started having the same problem and I am on 6u12 of Java.
ReplyDeleteProblem is my company doesn't allow a downgrade.
Thanks for troubleshooting this out for all of us who don't have that Java skillset!
ReplyDeleteAhhhhhhhhhh! You absolute beauty! Thanks so much for the heads up on this one. Perect answer and problem solved. If ony Cisco support was this good. Thanks!
ReplyDeleteThis is actually a known bug with Cisco. The fix for this is to use ASDM image 6.1.5.57 this version of the ASDM will work with even the newer versions of Java (I am using version 6 u13 (released April 2009).
ReplyDeleteSee this link for bug info: http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl
Bug ID code: CSCsv12681
Before you upgrade the ASDM, I would also upgrade to ASA 8.04 as well.
I found this info to be very helpful. However, I just came across another instance where this method doesn't really apply. In my case, I have an ASA5510 and ASDM was working perfectly until a few days ago. It acted like I had the wrong java engine again. After researching I found that the ASA5510 won't respond to the ASDM if it has been live for over one years time. My ASA was live for 367 days without a reload. I reloaded the ASA and now ASDM works like a charm again.
ReplyDeleteYou, sir, are the jiggity-jam! I had a suspicion that it was the newer version of Java, but your help here not only confirmed it but save my bacon as well.
ReplyDeleteThanks a bunch and keep up the good work!
Hi folks...
ReplyDeleteThanks for your help. I can get a solution with jre-6u7-windows-i586-p on WinXP SP3.
http://cds.sun.com/is-bin/INTERSHOP.enfinity/WFS/CDS-CDS_Developer-Site/en_US/-/USD/VerifyItem-Start/jre-6u7-windows-i586-p-iftw.exe?BundledLineItemUUID=quJIBe.nZLoAAAEgP_drhbBq&OrderID=BCRIBe.ntywAAAEgMvdrhbBq&ProductID=BUtIBe.pr_UAAAEaTTMke7Zb&FileName=/jre-6u7-windows-i586-p-iftw.exe
Thanks Rick, for the original article, and Tim Braun for an excellent, specific, workaround.
ReplyDeleteThanks a bunch - even our Cisco supporters did not have a clear answer to this one, apart from it being java related - you just saved my day! Best regards, Flemming Pedersen
ReplyDeleteJust got an early release of 1.6.0_14 and this resolved the ASDM issue for our environment. We had to use at least 1.6.0_13 which fails and we cannopt roll back to update 7 due to standards.
ReplyDeletethanks a lot - saved me in the mids of an asa upgrade :) also useful to note is that on 64bit systems, you need to use the 32bit version of java or ASDM won't run at all.
ReplyDeleteThanks, that java downgrade did the trick
ReplyDeleteFlemming
Denmark
Thanks man
ReplyDeletejust what i was looking 4
Nice, works for me too!
ReplyDeleteThanks...you just got me up and running!
ReplyDeleteThanks so much!!!!
ReplyDeleteIt really works fine, you are so cool sharing this ;)
Obrigado cara.
ReplyDeleteEu estava com o JRE 6u13, então removi e instalei a versão 6u7.
Ficou funcionando perfeitamente.
Obrigado
I just updated to the latest asdm 6.1.5 and ASA 8.0(4)and as stated above it runs Java 6.14 JUST peachy. So if you can upgrade that solves everything, otherwise you are stuck at 6.10 for java.
ReplyDeleteThanks a lot, no doubt thats really works.
ReplyDeleteThis blog was a great find. Had 6.11, uninstalled and re-installed 6.7 and ASDM now working again.
ReplyDeleteOk, I'm using 64bit XP. I have downloaded and installed both jre6u7 for 32bit and 64bit. But, I'm still getting this error.
ReplyDelete"ASDM cannot be loaded. Click OK to exit ASDM"
"Unconnected sockets not implemented"
Any ideas anyone?
I actually had an entirely different version of the ASDM and JRE (newer), but the same theory applied: It would throw out the error you described and bomb out, but then I applied the updated Java stuff and it fired up fine. Thanks for your help.
ReplyDeleteThanx you so much, Rick!
ReplyDeleteI have an ASA 5510 newest, from box, and ASDM from cd does not work, just only opened a logon form, and close. my jdk is latest from java downloads, and im tryed some googling, and nobody knows what to do with this.
but you are realy help me to fix this problem, you are great! greetz from Kiev, Ukrain ;)
Thanks, man. It works now!
ReplyDeleteWorks sweet on Windows 7 64-bit too. We had the same problem with update 10. Awesome, thanks heaps!!!!
ReplyDelete