Saleforce login error

[Former Member]

Hello Experts,

I am working on a project where I need to connect to test.salesfoce.com through adapter.

The company uses transparent proxy server.

The API for the website is https://test.salesforce.com/services/soap/c/25.0

I read somewhere that BODS 3.2 does not accept 25.0 so I changed to 18.0

Everytime I try to connect through the adapter I get the same message.

8/23/12 9:07:21 AM Thread[Thread-26,5,main]   Starting the Salesforce.com session

8/23/12 9:07:21 AM Thread[Thread-26,5,main]   There was a communication error when talking to Salesforce.com: No operation available for request {urn:partner.soap.sforce.com}login

8/23/12 9:07:21 AM Thread[Thread-26,5,main]   Fault-tolerance-login-failed:There was a communication error when talking to Salesforce.com: No operation available for request {urn:partner.soap.sforce.com}login

8/23/12 9:07:21 AM Thread[Thread-26,5,main]   Retry:1. Waiting 5 mins before trying to login to Salesforce.com again.

8/23/12 9:07:51 AM Thread[Thread-23,5,main]   There was a communication error when talking to Salesforce.com: No operation available for request {urn:partner.soap.sforce.com}login

8/23/12 9:07:51 AM Thread[Thread-23,5,main]   Fault-tolerance-login-failed:There was a communication error when talking to Salesforce.com: No operation available for request {urn:partner.soap.sforce.com}login

8/23/12 9:07:51 AM Thread[Thread-23,5,main]   Retry:2. Waiting 15 mins before trying to login to Salesforce.com again.

But when I check login history, it says log in was success through APEX API

Source IP	Login Type	Status	Browser	Platform	Application	Client Version	API Type	API Version	Login URL
8/23/2012 8:38:20 AM PDT	204.11.170.48	Other APEX API	Success	IE 8	Win7	N/A	SOAP PARTNER	18.0	N/A

I don’t know what is wrong.

This is very urgent I cannot proceed without the adapter.

Any help would be greatly appreciated.

[Former Member]

Has this issue been resolved? I am facing the same error. I know for a fact that we dont have a proxy server. Could it be something on salesforce side?