Comment 2 for bug 1160336

We seem to be experiencing the same problem. In our case, it is both the SoapClient and the SoapServer class which fail to load wsdl files (with the same error message as above), regardless of where the files are located on our server. I found a workaround which is allowing the wsdl files to be loaded, but which may be causing unwanted changes in how our SOAP objects are delivered.

I changed:

$server = new SoapServer('/path/to/wsfile.wsdl');

to:

$server = new SoapServer(null, array('uri' => '/path/to/wsfile.wsdl'));

For the SoapClient code, I changed:

$client = new SoapClient('https://domain/path/to/wsfile.wsdl');

to:

$client = new SoapClient(null, array('uri' => 'https://domain/path/to/wsfile.wsdl', location => 'https://domain/path/to/wsfile.wsdl'));

This got our client code tests to successfully return SOAP objects, but one of our customers using existing client side code (which has not been changed) has been experiencing errors when attempting to parse the objects they are receiving.