Errors on Log
amariotti - October 30, 2008 - 22:23
| Project: | Salesforce Webform Lead Form Integration |
| Version: | 5.x-1.2 |
| Component: | Miscellaneous |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed |
Jump to:
Description
I started getting this error in my watchdog log as of 1:15pm today. The error is still happening 3.5 hours later. Any ideas? :)
SoapClient::__doRequest() [<a href='function.--doRequest'>function.--doRequest</a>]: connect() failed: Connection refused in /srv/www/htdocs/drupal_root/sites/all/modules/salesforcewebform/includes/soapclient/SforceBaseClient.php on line 155.
I'll do some more digging and see if I can find anything else that might have set it off.
#1
After some further investigation it looks like when you submit the form it sends you to a blank screen. I need to try and find out what exact output is, how would I go about doing that? For now I think I'm going to shut off the Salesforce submission on the form. That way I can still import the leads manually with a CSV file once the issue is fixed.
After tracking down line 155 this is what I see:
$result = $this->sforce->login(array ('username' => $username,
'password' => $password
));
I'm going to go and check to see if the username/password is incorrect... will report back.
Reporting Back...
I changed the username and password to mine just to see if it was an issue with the one we were using and it's still doing the same thing. I also tried resetting my security token from Salesforce to see if that made a difference and it didn't. Any ideas Bryan?
#2
The error message seems to be that the SOAP server is denying the request (connection refused). Is Salesforce doing any maintenance, or experiencing any type of outage?
#3
I know that they recently did an upgrade to their SF application. I wonder if there's a new PHP API available to download that might fix this. I'll go take a look.
SF is a very reliable service so for it to be down this long (and I can verify that it's still not working today) doesn't make sense. Not sure what's going on here, but I'm hoping that a simple update in the PHP API might fix it.
#4
I'm thinking that this issue is a little deeper than the module, so disregard this for a while. The server is having some issues with any outgoing requests on our firewall. We made a few changes a few days ago and are seeing some interesting issues. Standby...