I am trying to login using asdm and i keep getting the error ASDM unable to load the firewall configuration.
The firewall is running ASA version 9.5(1) and the ASDM version is 7.5(1).
Java version installed is java 8 update 60 I was on windows 7 but now moved to windows 10 so not really sure what could be the issue.
I can however access on a mac fine but need this to be working on windows 10 any help appreciated?
Solved! Go to Solution.
The version of java that is currently in use is the latest version java 8 update 60.
Tried again and no luck it is still not working. It will only allow me to monitor the configuration tab is greyed out.
The correct answer has not been given how can i change the post to reflect this?
Please refer the following link for compatibility,
In case you are facing issue even after configuring all the required parameters, then it would be good if you open a case with TAC and work on the issue.
I have completed everything as per the release notes on 3 different machines running windows 10 and the same issue with each of them.
I will try on a windows 7 machine and see if that improves the issue.
But clearly there is some issue as more people will want to use windows 10 in the future
I tried the ASDM 751 and ASA 951 on Windows 10 with Java update : Version 8 update 60 and i did not face any issue in launching the ASDM.
Probably there is some configuration present on your device due to which the ASDM is failing to launch on your device.
You can share your config or you can directly reach out to TAC for this issue.
I have the same issue with the latest Java and ASDM - I did a bit of trouble shooting as well and found that the client loads fine as well - This only when the SFR module is unreachable or bypassing the SFR Load.
If you try load the ASDM with SFR then the configuration fails to load, and the ASDM becomes unusable.
Please help with this!
Thank you for the update.
I just want to understand what do you mean by
"This only when the SFR module is unreachable or bypassing the SFR Load"
Were you able to load asdm after bypassing sfr?
I tried accessing ASDM with SFR module (version 5.4) and I did not face any issue.
I think there might be some configuration which is causing issue in your setup, either you can share your config or
open a TAC case to get the issue resolved.
I am saying if I unplug the management port on the ASA5506X and load the ASDM client - then it loads fine without loading the Source Fire config.
As soon as I load it with the management plugged in and the ASDM tries to build the tools for Firepower then it fails. (Please see the attachment)
I don't think it is a configuration issue - it was working fine. I am on another site and now have the same issue with the device here as well. So I think it has something to do with the Java or Windows 10 update. It works fine on Windows server and windows 7 and 8.
Are you sure it is working on your system - have you got a 5506x device?
MEAT-ASA-01# show module sfr details
Getting details from the Service Module, please wait...
Card Type: FirePOWER Services Software Module
Hardware version: N/A
Serial Number: JA#########
Firmware version: N/A
Software version: 5.4.1-211
MAC Address Range: a46c.######### to a46c.#######
App. name: ASA FirePOWER
App. Status: Up
App. Status Desc: Normal Operation
App. version: 5.4.1-211
Data Plane Status: Up
Console session: Ready
DC addr: No DC Configured
Mgmt IP addr: 192.168######
Mgmt Network mask: 255.255.255.0
Mgmt Gateway: 192.168######
Mgmt web ports: 443
Mgmt TLS enabled: true
I want to also confirm, Windows 10 and ASDM with FirePower configured on ASA5506-X (with FirePower interface UP) gives the above error.
If the FirePower interface is disconnected or Down, ASDM continues to run.
A workaround is to use Windows 7 in my case.
I have the same problem working on Windows 7 and Java 8.60. I'm running ASA 9.4(1) and ASDM 7.4(3) on a ASA5506-X
Some days ago it worked fine.
ASA5506-X, ASA 9.5(1) and ASDM 7.5(1) here with Windows 10 and Java 8 Update 6, same problem. Identity certificate is in place, and I can access ASDM via another computer with Windows 8.1 & Java 8 Update 45 (both ASDM Launcher & Web Start)
Noticed that when opening Java Console, there is an error line mentioning supported operating system: "Caused by: com.teamdev.jxbrowser.chromium.internal.EnvironmentException: Unsupported operating system. Supported OS: Windows XP (SP2), 7, 8, Vista, 2003 (SP1), 2008, 2012, Mac OS X & Linux. Current OS: Windows 10"
This is consitent with the current release notes, where they not list Windows 10 as supported OS for ASDM, currently.
R.Seth as you seem to be the only one that seems to have this working would you like to share you system setup outputs from the java log and rest to see what the differences are which other users on windows 10 are experiencing
I tried the setup with sfr running on ASA5500-x device and not on 5506 device.
So i am not sure if there is any change in the behaviour in terms of ASDM operation.
I will try to look into this.
I'm also having the same problem.
-Java version 8 update 60
-ASA 5506-X with FirePOWER services
-Cisco Adaptive Security Appliance Software Version 9.5(1)
-Device Manager Version 7.5(1)
Whoever is running into this problem , can use this workaround:-
Rollback Java on Windows 10 to Java 8u51 or prior releases.
Thanks and Regards,
Downgrading to Java 8u51 seems to have done the trick.
I can access the SFR via asdm now with no issues. I suspect an update will be produced to allow use of the latest java in time?
That's great. Yes , this is a known issue and we don't support WIndows 10 with the latest Java for the moment. So , would request you to use this workaround for the moment.
Thanks and Regards,
I also had this issue with W7 64bits an Java 8u60. Downgrading Java to 8u51 also solved the issue.
Some details: I have both Java 8u60 x86 and Java8u51 64 bits installed. 8u60 for up-to-date security when using Firefox (32 bits). Beside, I have adjusted ASDM run.bat to ensure ASDM is using 8u51, see run.bat extract below:
start "" "C:\Program Files\Java\jre1.8.0_51\bin\javaw.exe" -Xms64m -Xmx1G ...etc
Hope this helps,
any plans to update the error one receives? Ie rather than , unable to load configuration.
Java incompatability in the error message?
I have the same problem - works for me on Windows 7 but not Windows 10. It's all about whether the FirePOWER tabs need to be loaded (at least for admin access). Pretty sure Cisco will have to fix this.
If you don't always need admin access to the FirePOWER module, one option might be to configure a user with a priv level below 15. On Win 10 such a user can log in and work with the ASA in ASDM.
The problem is windows 10 and the Java version.
If you spin up windows 7 and 51u8 java it works .
Kind of silly Cisco keeps attaching to this java junk .