Verify again that you are using 'C: Windows SysWOW64 javaw.exe' in the 'Target' field. On my system it's in 'C: Program Files (x86) Cisco Systems ASDM ' (within quotes). Change 'Start in' back to the path to your Cisco ASDM folder. If you found this helpful, maybe you'd like to send a? During your course of troubleshooting, you must have put 'C: Windows SysWOW64 javaw.exe' in the 'Start in:' field instead of the 'Target:' field. In that case, I recommend pointing your shortcut(s) directly to the version 1.6/6 JRE instead: 'C: Program Files Java jre6 bin javaw.exe' Hope this helps someone else out there. Think you might have a slow or broken connection to your authentication server? First, On your MAC install the ASDM launcher by connecting to an. If you have upgraded your JRE, you probably saw a recurrence of this issue.Ĭisco's Adaptive Security Device Manager (ASDM) is the GUI tool used. Now everything is working great! UPDATE : So the pain continues with Java 7. The ultimate fix ended up being updating all my ASDM shortcuts to use 'C: Windows SysWOW64 javaw.exe'. The dm-launcher installer launched the java app using 'C: Windows SysWOW64 javaw.exe', whereas the shortcut would use 'C: Windows system32 javaw.exe'. A quick check with Process Explorer revealed the issue. Subsequent launches from the application shortcuts failed. Opening the java console revealed another error which didn't get me any useful results on Google: Exception in thread 'AWT-EventQueue-0' : 509TrustManagerImpl cannot be cast to .509ExtendedTrustManager However, if I 're-installed' ASDM via the 'dm-launcher.msi', the first time it was spawned by the installer, everything worked fine. Launching the application from a shortcut, and attempting to connect resulted in the launcher halting on 'Contacting the device. I recently ran into an issue on Windows 7 64-bit where ADSM-ISM Launcher failed to connect to my ASAs.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |