Cannot import WSDL file in SOAPUI - NT authentication pop up (Error loading WSDL)

问题

I never faced similar problem before,

I tried with SOAP 4.0.1 and also with SOAP 5.1.2. I tried it on my windows but also and on Windows Server 2008 I try to import WSDL: NT Authentication dialog is presented: Specify NT Authentication Credentials to populate Username,Password,Domain

I am able to open the WSDL definition in Firefox:

http://192.168.0.242/SO/Services/ScheduleService.svc?wsdl

after entering username and password

but when trying to import WSDL file or when trying to import wsdl file using location URL

Error loading WSDL
There was something wrong with the WSDL you are trying to import

    Error loading
 [http://192.168.0.242/SO/Services/ScheduleService.svc?wsdl=wsdl0]: org.apache.xmlbeans.XmlException: 
org.apache.xmlbeans.XmlException: error: Reference to undefined entity: raquo

回答1:

I got same error using latest Soap UI 5.3. No hacking with configuration helped (proxy none, authenticate preemptively etc). In the end I imported WSDL from disk. Calling of operations through NTLM then worked without any problems. It seems like a bug in SoapUI when importing WSDL through NTLM in some environments.

Update: tested that enabling anonymous auth and disabling windows auth in IIS resolves the issue with import in SoapUI. So it is definitely some kind of bug in SoapUI during import through NTLM.

回答2:

You change the proxy settings under Preferences>Proxy Setting> to none this should solve the authentication issue which you are facing.

回答3:

Try to open this WSDL with any XML validator and see if it passes thru. The error message say

Reference to undefined entity: raquo

so you need to be sure that this entity is presented in your WSDL or imported schemas.

If your WSDL is 100% correct and "raquo" is there then I can only suggest you to download WSDL to local file with all schemas, change schemaLocation to local relative paths and try importing this local file.

回答4:

had the same problem here, with a WSDL that works on a different system. It was the proxy setting that was causing the problem, and as I don't need the proxy server, just disabling it through the browser menu solved it for me.