Fatal error: Call to a member function describeSObjects() on a non-object in /home/USERNAME/public_html/drupal/sites/all/modules/salesforce/salesforce_api/salesforce_api.module on line 339
Please Help! Thanks in advance :)
Fatal error: Call to a member function describeSObjects() on a non-object in /home/USERNAME/public_html/drupal/sites/all/modules/salesforce/salesforce_api/salesforce_api.module on line 339
Please Help! Thanks in advance :)
Comments
Comment #1
aaronbaumanThis means your salesforce_api_connect call is returning FALSE, which means that your Drupal config is not set up properly, your SalesForce account does not allow API connections, your network is not allowing the connection, or... there's something wrong w/ the connection.
However, even with better error handling, your connection will still fail in this situation.
Check your watchdog logs and make sure you've got SF configured on the Drupal side of things at admin/settings/salesforce. Also, make sure your SalesForce instance is set up to accept API connections and you're using the proper username/password/token.
Comment #2
cport1 commentedDoes the demo work with API?
Comment #3
aaronbaumanYes, the SalesForce API demo in the salesforce_api module works with SalesForce API.
Please make sure you have set up a SalesForce account via salesforce.com or developer.salesforce.com, and make sure you enter your username, password, and API token on your Drupal site.
If you are still getting such an error after you have properly configured your SalesForce credentials in your Drupal install, please report back.
Comment #4
cport1 commentedYea I seem to still be getting this error.
Comment #5
cport1 commentedI really don't know why, but I can't make a connection with the salesforce API. Is there something that I am missing?
Comment #6
aaronbaumanI don't know what else to tell you on this one - it's working a-ok for me and presumably everyone else who's using this module.
I would suggest one or all of the following:
1. Set up a sandbox account on developer.salesforce.com and use the new credentials (username/password/token) to set up your Drupal Salesforce api instance to see if your SalesForce account could be the issue.
2. Try the basic PHP example provided by SalesForce (outside of Drupal) to see if your PHP setup could be the issue.
3. Install a fresh copy of Drupal with ONLY the SalesForce modules enabled to see if you Drupal install could be the issue.
Beyond this, I really can't support your specific setup any further without more details about your particular Drupal stack and SalesForce install.
Comment #7
Anonymous (not verified) commentedI am getting the same error as well. I followed the readme and have a pretty solid drupal development setup.
I am using the trial account at the moment, and the correct credentials. php-pear php-soap are installed as well. Even restarted apache.
The Server OS is Fed 8.
Ideas?
Update:
Returns a white page with zero source on it. Here is my PHP conf
Comment #8
aaronbaumanshould have asked earlier -
did you install the SalesForce php toolkit as per the README?
Comment #9
Anonymous (not verified) commentedYep sure did, PHPtoolkit 13 to be exact.
Comment #10
aaronbaumanI *just* installed a *fresh* drupal 6.10, SalesForce API 6.x-dev, SF PHP toolkit v.13, and SalesForce developer sandbox and the demo works fine.
Have you tried the SalesForce example scripts that come w/ the toolkit to verify that your PHP / SalesForce setup is ok?
Unless you can provide *exact* steps to reproduce this error on another machine,
there's not much that can be done to support your specific instance.
Comment #11
Bevan commentedPlease update this issue if you find a solution.
Comment #12
rj commentedI had this same problem and solved it by 1) creating a SF developer account that was separate from my admin account, 2) creating a new token for that account, and then 3) updating salesforce API settings on admin/settings/salesforce.
Comment #13
asifnoor commentedYes, i too had the same problem until i create a developer account. I am facing following issues with the SF module.
1. I had mapped drupal page with a campaign of salesforce and then created a page and click on "Export to salesforce". It says export successfully, but i don't see it in my campaigns page of my developer SF account.
2. When i try to delete the field maps which are created, it is giving the following error
undefined function db_querey() in /var/www/html/mydrupal/modules/salesforce/salesforce_api/salesforce_api.module on line 325
3. I am able to view only 3 salesforce objects Campaign, contact and lead. Are the objects in development or am i missing something here?
Looking forward for your thoughts on how to go forward with this.
Thanks
Comment #14
joshk commentedFixed the "db_querey" typo.
Setting up additional objects is issue #476978: Implement "Object Setup" Feature
People getting white-screen failures are likely operating in environments where error reporting is suppressed, and you're getting a problem with the soap cache and WSDL. This is addressed in issue #473822: Need a "Clear Cache" option for Salesforce/SOAP cache
Comment #15
smn0 commentedI have this error too...
We have a Professional Edition, is this module works with this edition ?
The API connection could not be available for me ?
Also, I have no connection with a developer account.
I run Drupal on a Windows based server. I tried to install the module on a linux server and it works fine. I think there is a php module (like pear or soap) that doesn't work properly on my windows server.
Comment #16
Bevan commentedAny instances of 'fatal error' need to:
* include the PHP error message
* be using latest DRUPAL-6--2 code on new install (upgrade paths not yet supported)
* confirmation whether you were able to successfully;
* save credentials
* login to https://login.salesforce.com/ with those credentials
* load the test/demo page
* create a fieldmap
Comment #17
aaronbaumanre: #16
Maybe some disclaimer like this should go in a README or on the project page?
Comment #18
Bevan commentedAaron. Yes, good idea. Though a lot of those items only apply while SF API module is still in dev. Issue submission guidelines are also useful, though the issue queue is still manageable for now...
Comment #19
kenorb commented