If you get an error when adding a new SOAP project in SoapUI, it’s best to try and open the wsdl in a browser first. That way you can see the errors related to the wsdl file. Don’t forget to set customErrors to Off in the web.config file.
<customErrors mode=”Off” />
You can also have a setting includeExceptionDetailInFaults in your serviceBehaviors. When you set this setting to false, you will get the following non descriptive error: “The server was unable to process the request due to an internal error. For more information about the error, either turn on IncludeExceptionDetailInFaults (either from ServiceBehaviorAttribute or from the <serviceDebug> configuration behavior) on the server in order to send the exception information back to the client, or turn on tracing as per the Microsoft .NET Framework SDK documentation and inspect the server trace logs.”
This message is OK in a production situation, because for security reasons you don’t want your service to expose detail information about the error.
When you are debugging however, it’s wise to turn on includeExceptionDetailInFaults to get the actual error details.
<!– To receive exception details in faults for debugging purposes, set the value below to true.
Set to false before deployment to avoid disclosing exception information –>
<serviceDebug includeExceptionDetailInFaults=”True” />