Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements
Step-by-Step Configuration and Troubleshooting Best Practices for the NGFW, NGIPS and AMP Technologies A Visual Guide to the Cisco Firepower Threat Defense (FTD)
Community Member

ASDM "Cannot launch device manager from x.x.x.x" Windows 8 - Java 7u25

I had Windows 7 with Java7u25 installed on my laptop 2 weeks ago, and my ASDM connection worked fine.

But I have reformatted and installed Windows 8 on my laptop, and since then I can't connect to either of my ASAs.

Colleagues are able to connect from thier systems (win7 java7u25) and my desktop works fine (again Win7 Java7u25)

So, what is it that is missing from my Windows 8 install that this isn't working? I have removed and reinstalled Java...had 64bit....but reinstalled 32bit only...it didn't work...so then I reinstalled 64bit (to have both).

When I try to run ASDM from the web link I get a JAVA error:

(Exception)      

com.sun.deploy.net.FailedDownloadException: Unable to load resource: https://10.155.10.10/admin/public/asdm.jnlp

    at com.sun.deploy.net.DownloadEngine.actionDownload(Unknown Source)

    at com.sun.deploy.net.DownloadEngine.downloadResource(Unknown Source)

    at com.sun.deploy.cache.ResourceProviderImpl.getResource(Unknown Source)

    at com.sun.deploy.cache.ResourceProviderImpl.getResource(Unknown Source)

    at com.sun.javaws.Launcher.updateFinalLaunchDesc(Unknown Source)

    at com.sun.javaws.Launcher.prepareToLaunch(Unknown Source)

    at com.sun.javaws.Launcher.prepareToLaunch(Unknown Source)

    at com.sun.javaws.Launcher.launch(Unknown Source)

    at com.sun.javaws.Main.launchApp(Unknown Source)

    at com.sun.javaws.Main.continueInSecureThread(Unknown Source)

    at com.sun.javaws.Main.access$000(Unknown Source)

    at com.sun.javaws.Main$1.run(Unknown Source)

    at java.lang.Thread.run(Unknown Source)

(Wrapped Exception)

java.net.ConnectException: connect: Address is invalid on local machine, or port is not valid on remote machine

    at java.net.DualStackPlainSocketImpl.connect0(Native Method)

    at java.net.DualStackPlainSocketImpl.socketConnect(Unknown Source)

    at java.net.AbstractPlainSocketImpl.doConnect(Unknown Source)

    at java.net.AbstractPlainSocketImpl.connectToAddress(Unknown Source)

    at java.net.AbstractPlainSocketImpl.connect(Unknown Source)

    at java.net.PlainSocketImpl.connect(Unknown Source)

    at java.net.SocksSocketImpl.connect(Unknown Source)

    at java.net.Socket.connect(Unknown Source)

    at sun.security.ssl.SSLSocketImpl.connect(Unknown Source)

    at sun.security.ssl.BaseSSLSocketImpl.connect(Unknown Source)

    at sun.net.NetworkClient.doConnect(Unknown Source)

    at sun.net.www.http.HttpClient.openServer(Unknown Source)

    at sun.net.www.http.HttpClient.openServer(Unknown Source)

    at sun.net.www.protocol.https.HttpsClient.<init>(Unknown Source)

    at sun.net.www.protocol.https.HttpsClient.New(Unknown Source)

    at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.getNewHttpClient(Unknown Source)

    at sun.net.www.protocol.http.HttpURLConnection.plainConnect(Unknown Source)

    at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(Unknown Source)

    at sun.net.www.protocol.https.HttpsURLConnectionImpl.connect(Unknown Source)

    at com.sun.deploy.net.BasicHttpRequest.doRequest(Unknown Source)

    at com.sun.deploy.net.BasicHttpRequest.doRequest(Unknown Source)

    at com.sun.deploy.net.BasicHttpRequest.doGetRequest(Unknown Source)

    at com.sun.deploy.net.DownloadEngine.actionDownload(Unknown Source)

    at com.sun.deploy.net.DownloadEngine.downloadResource(Unknown Source)

    at com.sun.deploy.cache.ResourceProviderImpl.getResource(Unknown Source)

    at com.sun.deploy.cache.ResourceProviderImpl.getResource(Unknown Source)

    at com.sun.javaws.Launcher.updateFinalLaunchDesc(Unknown Source)

    at com.sun.javaws.Launcher.prepareToLaunch(Unknown Source)

    at com.sun.javaws.Launcher.prepareToLaunch(Unknown Source)

    at com.sun.javaws.Launcher.launch(Unknown Source)

    at com.sun.javaws.Main.launchApp(Unknown Source)

    at com.sun.javaws.Main.continueInSecureThread(Unknown Source)

    at com.sun.javaws.Main.access$000(Unknown Source)

    at com.sun.javaws.Main$1.run(Unknown Source)

    at java.lang.Thread.run(Unknown Source)

Everyone's tags (3)
9 REPLIES
Hall of Fame Super Silver

ASDM "Cannot launch device manager from x.x.x.x" Windows 8 - Jav

Have you tried using the Java Web Start version as opposed to the full ASDM Launcher local installation? Some folks have reported success with that.

Personally I just stick with Java 1.6. Version 1.7 (aka Java 7) just breaks too many Cisco apps.

Community Member

Re: ASDM "Cannot launch device manager from x.x.x.x" Windows 8 -

Yes, the java output from my post is when I try to use WEBSTART....if I just try to use ASDM itself it only says 'cannot launch device manager on x.x.x.x'

Does Java 6 work on Win8? I thought I read where Win8 support was just added at J7u10.

Thanks,

Dirk

EDIT: I removed all J7 installs....and installed J6u45 (the final J6 update) and what do you know!?!?!? It works....so now Cisco...the question is...what is it about Win8 and the J7 combo that is breaking ASDM? And is it fixed with Win8.1?

Community Member

ASDM "Cannot launch device manager from x.x.x.x" Windows 8 - Jav

It's apparently not fixed in 8.1 because I had the same issue. Thanks for the tip on downgrading to J6u45.

Community Member

ASDM "Cannot launch device manager from x.x.x.x" Windows 8 - Jav

I decided to try again with the newly updated J7u51...same result.

So keep in mind that if you get an update to ASDM you may need to redo the shortcut to point to your J6u45.

There is an article, I think it is on this forum that details how to change the shortcut to point to another version of Java that will work.

Community Member

ASDM "Cannot launch device manager from x.x.x.x" Windows 8 - Jav

Hi,

May I know which version of ASDM and exact version of java on your windows 8 PC?

- Prateek Verma

Community Member

Re: ASDM "Cannot launch device manager from x.x.x.x" Windows 8 -

Running windows 8.1 with j7u51 and initially had the same problem.  Apparently Java is now doing some strict name checking when using SSL and in my case there were two things that I had to do to get it working:

1) Use the fqdn of the ASA when connecting

2) Trust the root ca cert in windows

1) Verify the fqdn of the ASA and make sure that you can resolve to it using DNS.  Open a browser and go to https:///admin and verify that you don't get any browser warning about certificates.  If you do, examine the certificate and look at the subject name and/or subject alternate name under details.  DNS needs to resolve to the fqdn listed on the cert.  In my case, I used the fqdn value under the subject alternate name and updated my DNS server with the name.  If you don't have a private DNS server, you can update the host file in windows with the name and IP.

2) You'll also have to trust the root CA in the chain.  Export the root ca certificate by looking at the ASA certificate, going to the certificate path tab and then selecting the root cert and then view it.  You can copy the cert to a file under the details tab of the root ca cert.  Trust the root CA of the ASA by importing the root certificate into the trusted root certification authorities/certificates container in Windows.  To do this, launch "mmc" and add the certificates snap-in.  Expand the Trusted Root Certification folder and right click on Certificates and select "All Tasks\Import".  Browse to the root certificate that you exported earlier and import it in.  You'll need to acknowledge that you want to trust the cert and put it in the correct key container.

Once the browser shows no certificate warnings, you should be able to launch the ASDM using the same fqdn that you did in the browser.

Hope this helps.

Community Member

Re: ASDM "Cannot launch device manager from x.x.x.x" Windows 8 -

Hi,

There is bug with ASDM not running with java version 7 update 51. I would suggest you to downgrade the java version to version 7 update 40 or 45, it would work.

- Prateek Verma

Cisco Employee

ASDM "Cannot launch device manager from x.x.x.x" Windows 8 - Jav

All - please note that we have been tracking this issue via bug CSCum46193, which has since been resolved in ASDM version 7.1.5.100.

I am including the Release Note from the bug below:

Symptom:
After installing the Java 7 upgrade 51, ASDM cannot be launched from the browser because it is being blocked by Java due to the JAR file manifest missing the Permissions attribute.  

Please note that the same problem is affecting in a Web deployment of AnyConnect.  While the problem is the same, AnyConnect is a different application from ASDM and will be handled separately.

Conditions:
All versions of ASDM while Java version 7u51 is running on the client computer.

Workaround:
In order to be able to launch ASDM from the browser, upgrade to ASDM 7.1.5.100.  

Since ASDM Launcher does not work with Java version 7u51 (see CSCum57517), upgrading ASDM can be done in one of the following two ways:

1. Manual upgrade via CLI:
    - Download 7.1.5.100 ASDM image from cisco.com to you local computer
    - Upload it to the ASA (see http://www.cisco.com/en/US/docs/security/asa/asa91/configuration/general/admin_swconfig.html#wp1625334 on how to upload a file to the ASA)
    - Issue "asdm image asdm-715100.bin" to set the new image as the ASDM image
    - Issue "write mem" to save configuration

2. Add a security exception for the ASA in the Java Control Panel, so that you could launch the current ASDM image and upgrade it from within ASDM:
    - Open Java Control Panel 
        * on Windows: Start > Control Panel > Java Control Panel
        * on Mac: click on Java icon in System Preferences
    - Go to the Security tab
    - In the Exception Site List section at the bottom, click Edit Site List and add the ASA you want to manage with ASDM: 
            https://
        where  is the IP address of the ASA

Further Problem Description:
Please note that ASDM Launcher does not work with Java 7 update 51.  The only way to launch ASDM under Java 7u51 is to use the workaround above and launch ASDM from the browser.

Sincerely,


David.

Community Member

Re: ASDM "Cannot launch device manager from x.x.x.x" Windows 8 -

Thanks for the information David.

I was able to successfully run asdm gui 7.1.5.100 using the steps I specified earlier. Once DNS was updated and the root ca cert trusted (or the self-signed cert if not using an enterprise PKI), everything works with no issue, including running the installed ASDM (not from the browser).

I suspect that customers running in an enterprise CA environment where the root ca cert is already trusted, and are already using the fqdn to access the ASA, will not see any issues.  The 7.1.5.100 does fix the permissions manifest warning that kept displaying which will make sure that this still works once oracle prevents java apps from running without it.

22627
Views
5
Helpful
9
Replies
CreatePlease to create content