SoapUI "failed to load url" error when loading WSDL
Solution 1
I have had similar problems and worked around them by saving the WSDL locally. Don't forget to save any XSD files as well. You may need to edit the WSDL to specify an appropriate location for XSDs.
Solution 2
I have had the same problem. I resolved it by disabling the proxy in the SoapUI preferences. (source : http://www.eviware.com/forum/viewtopic.php?f=13&t=12460)
Solution 3
In my case the server were the service was installed was configured only for TLS. SSL was not allowed. So you have to update SoapUI vmoptions file by adding
-Dsoapui.https.protocols=TLSv1.2
You can find vmoptions file under SoapUI installation folder:
C:\Program Files (x86)\SmartBear\SoapUI-5.0.0\bin\soapUI-5.0.0.vmoptions
OR change your server setting to allow SSL
Solution 4
I got this error when trying to load a WebService implemented in MS Dynamics AX. Because I was connecting via VPN to my network, something went wrong with IPv6 settings. After Googling, I found the solution here: http://support.microsoft.com/kb/929852
Solution 5
In my case the
Error loading [https://.../token?wsdl]: java.lang.Exception: Failed to load url; https://.../token?wsdl, 0
was caused by fake certificate. If you get the following in browser
"There is a problem with this website’s security certificate."
this is the case.
The resolution was to import a certificate to
C:\Program Files (x86)\SmartBear\SoapUI-5.0.0\jre\lib\security\cacerts
Which is default java used by SOAPUI
Pancho
Updated on October 11, 2020Comments
-
Pancho over 3 years
I keep having some weird problems. The main one is that I keep getting the following error when trying to add a WSDL to a new project:
Error loading [https://.../token?wsdl]: java.lang.Exception: Failed to load url; https://.../token?wsdl, 0 -
Here's the message recorded in the error.log file:
java.lang.Exception: Failed to load url; https://.../token?wsdl, 0 - at com.eviware.soapui.impl.wsdl.support.wsdl.UrlWsdlLoader.load(UrlWsdlLoader.java:184) at com.eviware.soapui.impl.wsdl.support.wsdl.WsdlLoader.loadXmlObject(WsdlLoader.java:121) at com.eviware.soapui.impl.wsdl.support.xsd.SchemaUtils.getDefinitionParts(SchemaUtils.java:535) at com.eviware.soapui.impl.wsdl.support.xsd.SchemaUtils.getDefinitionParts(SchemaUtils.java:524) at com.eviware.soapui.impl.support.definition.support.AbstractDefinitionCache.update(AbstractDefinitionCache.java:97) at com.eviware.soapui.impl.support.definition.support.AbstractDefinitionContext$Loader.construct(AbstractDefinitionContext.java:226) at com.eviware.soapui.support.swing.SwingWorkerDelegator.construct(SwingWorkerDelegator.java:46) at com.eviware.soapui.support.swing.SwingWorker$2.run(SwingWorker.java:149) at java.lang.Thread.run(Unknown Source)
I verified that the application at that URL is up and running, and I can get to the WSDL from a web browser, but I keep getting this error message no matter what. I am using SoapUI 4.5.0 (32-bit) on a Windows 7 box. I've also tried the 64-bit version with the same results. It happens whether I am on VPN or not.
Do you know why I might be getting this error?
-
Pancho almost 12 yearsThank you! I had tried to load the WSDL directly before but I had completely forgotten about the XSD. It works now!
-
Jason about 11 yearsSame problem for me on 4.5.1 Win 32. The proxy was enabled and set to port 8081. Disabling the proxy in
Files->Preferences->Proxy Settings
allowed it all to work. -
Mark Cooper about 11 yearsYou can also quickly disable / enable the proxy via the proxy icon on the tool bar (a server with a red or green dot)
-
Nagarajan S R over 10 yearsHi chrismead, Even I am doing the same.
-
Robert Strauch almost 8 yearsThis solved the problem in my case. Additionally I had to enable client authentication in the soapUI preferences as the web server requires it.
-
Yurii almost 8 yearsNot so nice workaround. Disabling proxy (see next answer) helped a lot better.
-
Piotr Olaszewski almost 8 yearsUbuntu on 5.2.1
File -> Preferences -> Proxy Settings
set toNone
. -
EdGruberman almost 8 yearsThis worked like a charm for my situation. Thank you! It is frustrating SoapUI doesn't make this more of an obvious option/error message.
-
Bee over 7 yearsThat was the exact problem. :)
-
Mark Hughes about 7 yearsmacOS users will have to modify soapui.sh in
/Applications/SoapUI-5.3.0.app/Contents/java/app/bin/soapui.sh
(and other .sh scripts in the same directory) Add:JAVA_OPTS="$JAVA_OPTS -Dsoapui.https.protocols=TLSv1.2"
Above:$JAVA $JAVA_OPTS -cp $SOAPUI_CLASSPATH com.eviware.soapui.SoapUI "$@"
-
mlhDev almost 7 yearsDon't change your server to allow SSL. Maintain some dignity.
-
user7294900 over 6 yearsThe link is borken and changing proxy to None didn't help. do you have different steps of fixing this issue?
-
Igor Semin about 6 yearsDon't know why is this answer not in the top!?
-
Lina over 5 yearsI am new for these please let me know where to add xsd file
-
sk23 about 5 yearsThis worked for me for SoapUI version 5.3.0. I got this error [link] (i.imgur.com/R8L2Kxm.jpg). Added (-Dsoapui.https.protocols=TLSv1.2) to the vmoptions file. Only thing had to close SoapUI and restart again.
-
Rafael Andrade over 4 yearsnice one. But why ipv6 adress has this problem ?
-
MauroB about 3 yearsThank you! I supposed it did not work due to https, so i tried to import the certificate before. Bad choice! Your solution worked for me!