function readOnly(count){ }
Sign Up ›
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
Learn More

Browse by Topic
ShowAll Questionssorted byDate Posted
+ Start a Discussion
chessbasechessbase 

Sandbox Problem!!!

Hi there,
 
I have an issue with client sandbox. My Salesforce.com connector works fine with production account but when I try to test my connection with client sandbox (test account) it doesn't work at all. I checked the login history and there is no entry for API login. My question is sandbox allow API calls? If yes then what am I missing here?
 
I have tried hardcoded URL in my connector but no luck. I have even replace production WSDL with test one but no luck. Any pointer or help will be apprieciated
 
Reply to me as soon as you can please...
 
Amit Suri
jeremyfrey1jeremyfrey1
User accounts are unique across organizations.  E.g., if you have an integration_user@yourcompany.net account, this is specific to your production instance, and trying to use it to log into a sandbox instance or use it to log into the sandbox API will fail.  Chances are, you can get around this by appending .test at the end of the user name.
 
I've encountered this problem many times by accident, and that's usually the issue.
chessbasechessbase
Thanks for the reply. Just a small update that when I replace production WSDL with test WSDL the login works fine because it take <soap:address location="https://test.salesforce.com/services/Soap/u/12.0" />
instead of
<soap:address location="https://www.salesforce.com/services/Soap/u/12.0" /> 
 
I have hardcoded the .URL property as shown below but kept production WSDL as web reference but login still fails.

binding = new sforcePartner.SforceService();

binding.Url = "https://test.salesforce.com";

This is what I use for other integration but this is not working with Salesforce.com and I don't know why. Just to remind you again replacing production WSDL with test WSDL works for me.

Waiting for you reply,

Amit
chessbasechessbase

Ok it is working now. I was passing the https://test.salesforce.com whereas it should have been https://test.salesforce.com/services/Soap/u/12.0