Apex Code Development You need to sign in to do that
Don't have an account?
zbeckman Started happening today: PHP fatal error: 'uri' option is required in nonWSDL mode
Today, apparently spontaneously, our PHP front end to Salesforce started spewing the following errors:
[Mon Jun 18 17:22:24 2007] [error] PHP Fatal error: SoapClient::SoapClient() [function.SoapClient-SoapClient]: 'uri' option is requred in nonWSDL mode in /Library/WebServer/STI/soapclient/SforceBaseClient.php on line 57
The error corresponds to a line in the Salesforce PHP kit shown below, note the line with an asterisk:
public function createConnection($wsdl) {
$_SERVER['HTTP_USER_AGENT'] = 'Salesforce/PHPToolkit/1.0';
// Bug #36283 SOAPClient Compression Broken. Fix will be in the release after 5.1.2
// $this->sforce = new SoapClient($wsdl, array('compression' => SOAP_COMPRESSION_ACCEPT | SOAP_COMPRESSION_GZIP));
* $this->sforce = new SoapClient($wsdl, array('trace' => 1, 'encoding' => 'utf-8'));
return $this->sforce;
}
Not only has the code not changed, but it's not even ours (part of the PHP API kit from Salesforce). It's been running fine for over a year... can anyone offer pointers as to why our site is now suddently disfunctional?
As it's taken down our production system, this is a critical issue. I'd really appreciate any assistance.
[Mon Jun 18 17:22:24 2007] [error] PHP Fatal error: SoapClient::SoapClient() [function.SoapClient-SoapClient]: 'uri' option is requred in nonWSDL mode in /Library/WebServer/STI/soapclient/SforceBaseClient.php on line 57
The error corresponds to a line in the Salesforce PHP kit shown below, note the line with an asterisk:
public function createConnection($wsdl) {
$_SERVER['HTTP_USER_AGENT'] = 'Salesforce/PHPToolkit/1.0';
// Bug #36283 SOAPClient Compression Broken. Fix will be in the release after 5.1.2
// $this->sforce = new SoapClient($wsdl, array('compression' => SOAP_COMPRESSION_ACCEPT | SOAP_COMPRESSION_GZIP));
* $this->sforce = new SoapClient($wsdl, array('trace' => 1, 'encoding' => 'utf-8'));
return $this->sforce;
}
Not only has the code not changed, but it's not even ours (part of the PHP API kit from Salesforce). It's been running fine for over a year... can anyone offer pointers as to why our site is now suddently disfunctional?
As it's taken down our production system, this is a critical issue. I'd really appreciate any assistance.
Park
So, our site is still down (because Salesforce won't talk to it) and I've still no clue as to what broke yesterday. Everything seems to be pointing to Salesforce.com itself... has anyone else experienced similar problems?
Thanks to everyone for helping us find this. Turns out it was a DNS server problem on our end -- for some reason, the server was failing name resolution for salesforce.com. Once it was restarted, we got our connectivity back.