SoapUI "failed to load url" error when loading WSDL

Question

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?

score 80 · Answer 1 · answered Jul 27 '12 at 09:57

80

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)

answered Jul 27 '12 at 09:57

alex88

843
1
5
8

11

Same 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. – Jason Apr 17 '13 at 14:03
7

You can also quickly disable / enable the proxy via the proxy icon on the tool bar (a server with a red or green dot) – Mark Cooper May 15 '13 at 08:39
2

Ubuntu on 5.2.1 `File -> Preferences -> Proxy Settings` set to `None`. – Piotr Olaszewski Jul 19 '16 at 17:53
1

That was the exact problem. :) – Bee Sep 05 '16 at 05:46
3

The link is borken and changing proxy to None didn't help. do you have different steps of fixing this issue? – Ori Marko Oct 24 '17 at 13:23
Thank 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! – MauroB Apr 23 '21 at 10:52

sree · Answer 2 · 2022-12-02T00:56:48.573

43

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 the server TLS version

-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

edited Dec 02 '22 at 00:56

answered Mar 18 '16 at 05:25

sree

2,287
28
26

This solved the problem in my case. Additionally I had to enable client authentication in the soapUI preferences as the web server requires it. – Robert Strauch Jun 17 '16 at 11:30
This worked like a charm for my situation. Thank you! It is frustrating SoapUI doesn't make this more of an obvious option/error message. – EdGruberman Jul 27 '16 at 00:30
2

macOS 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 "$@"` – Mark Hughes Apr 03 '17 at 03:18
1

Don't change your server to allow SSL. Maintain some dignity. – mlhDev May 18 '17 at 19:12
1

Don't know why is this answer not in the top!? – Igor Semin Apr 11 '18 at 07:47
This worked for me for SoapUI version 5.3.0. I got this error [link] (https://i.imgur.com/R8L2Kxm.jpg). Added (-Dsoapui.https.protocols=TLSv1.2) to the vmoptions file. Only thing had to close SoapUI and restart again. – sk23 Mar 03 '19 at 18:29

score 24 · Accepted Answer · answered Jun 18 '12 at 22:28

24

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.

answered Jun 18 '12 at 22:28

chrismead

2,163
3
24
36

Thank you! I had tried to load the WSDL directly before but I had completely forgotten about the XSD. It works now! – Pancho Jun 19 '12 at 04:22
Hi chrismead, Even I am doing the same. – Nagarajan S R Jan 07 '14 at 09:39
2

Not so nice workaround. Disabling proxy (see next answer) helped a lot better. – Yurii Jun 26 '16 at 11:25
I am new for these please let me know where to add xsd file – Lina Nov 13 '18 at 08:21

score 2 · Answer 4 · edited Jul 24 '20 at 12:16

2

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

edited Jul 24 '20 at 12:16

Dharman

30,962
25
85
135

answered Oct 02 '12 at 09:08

Tassisto

9,877
28
100
157

score 1 · Answer 5 · answered Oct 22 '14 at 14:48

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

score 1 · Answer 6 · edited Jun 30 '15 at 22:23

1

This could be a problem with IPV6 address SOAP UI picking. Adding the following JVM option fixed it for me:

-Djava.net.preferIPv4Stack=true

I added it here:

C:\Program Files\SmartBear\soapUI-4.5.2\bin\soapUI-4.5.2.vmoptions

edited Jun 30 '15 at 22:23

Jens Hoffmann

6,699
2
25
31

answered Jun 30 '15 at 21:19

user5067156

11
1

nice one. But why ipv6 adress has this problem ? – Rafael Andrade Jan 17 '20 at 17:43

score 1 · Answer 7 · answered Sep 08 '16 at 05:41

Inside the wsdl file look for the import element, which looks like this :

`<import  namespace="nameSpaceValue" location="Users/myname/.../targetxsdName.xsd"/>`

Change the location attribute in the above element to the location of your xsd files stored locally, and it should work.

score 1 · Answer 8 · answered Apr 10 '17 at 20:10

1

The following solution helped me:

-Djsse.enableSNIExtension=false

In SoapUI-5.3.0.vmoptions.

answered Apr 10 '17 at 20:10

X-factor

183
7

score 1 · Answer 9 · answered Jul 14 '22 at 23:07

This error is due to an erroneous schemaLocation in the WSDL file.

Indicate the correct location (either path on the disk or xsd url) of the xsd file in the wsdl file

exp

<xsd:import namespace="http://xyz:8080/" schemaLocation="http://172.17.16.53:9080/auth/authorizationBS?xsd=1"></xsd:import>

score 0 · Answer 10 · edited Jul 24 '20 at 12:14

0

If you are running your Web Application with the default port of 8080, please try to change the port to some other value and run your application again and trigger again your SOAPUI request. As you might have history projects in your SOAP UI workspace with port number 8080, might create issues.

edited Jul 24 '20 at 12:14

Dharman

30,962
25
85
135

answered May 26 '14 at 08:13

user3675584

1

score 0 · Answer 11 · answered Jan 31 '17 at 09:38

0

I had this issue when trying to use a SOCKS proxy. It appears that SoapUI does not support SOCKS proxys. I am using the Boomerang Chrome app instead.

answered Jan 31 '17 at 09:38

Rob

353
4
16

score 0 · Answer 12 · edited Jul 24 '20 at 12:15

0

My solution was to modify the java.security file:

\SoapUI-5.3.0\jre\lib\security\java.security

Comment code syntax:

#jdk.certpath.disabledAlgorithms=MD2, DSA, RSA keySize < 2048
#jdk.certpath.disabledAlgorithms=MD2, RSA keySize < 1024

edited Jul 24 '20 at 12:15

Dharman

30,962
25
85
135

answered Feb 08 '17 at 16:31

Miraval Carrillo Jacinto

130
1
4

score 0 · Answer 13 · answered Feb 24 '17 at 00:18

I had this error and in my case, the problem was that I was using "localhost" in the URL.
I resolved that changing the localhost word for the respective IP, (Windows + R -> cmd -> ipconfig) then read the IP and write it to the URL replacing the "localhost" word

score 0 · Answer 14 · answered Oct 27 '17 at 08:41

0

Close and reopen soapui. Probably is a bug of the application

answered Oct 27 '17 at 08:41

Ciro

253
2
5
23

score 0 · Answer 15 · edited Jul 24 '20 at 12:15

0

For java version above 1.8, Use below command to setup soapUI jar

java -jar --add-modules java.xml.bind --add-modules java.xml.ws <path for jar file+jar file name.jar>

edited Jul 24 '20 at 12:15

Dharman

30,962
25
85
135

answered Jul 18 '19 at 08:15

MSD

9
3

score 0 · Answer 16 · answered Feb 28 '20 at 10:30

0

Update SoapUI version to SoapUI 5.5.0. This error causes when I tried to load wsdl, because of old SoapUI version

answered Feb 28 '20 at 10:30

SanduniC

41
5

SoapUI "failed to load url" error when loading WSDL

16 Answers16

Linked