Crystal Reports 2011 cannot connect to Salesforce - Unexpected Error

Question

I am unable to connect to salesforce from Cystal Reports 2011. I get a dialogue saying
Failed to Open the connection
Details:Unexpected Error
-I have increased the JVMMaxHeap in CRCONFIG.XML to 512000000
-I have appended the security token to the password
-I am not going through a proxy server
I am able to login successfully to the salesforce account using Crystal Reports 2008.
In order to narrow the issue down and exclude any issues related to custom objects on our corporate acount I created a clean , out of the box dev account on salesforce. Again I can connect to it with 2008 but not 2011 on whcih I get the same error
I can verify that a login succesfully occured in salesforce, the login in history shows the connections are being made.
In order to reproduce simply create a salesforce dev account, install CR 2011 SP02 and attempt to create a database connection to the salesforce account
Crystal Reports Log is as follows
011-9-30-15-14-27     10176     .\xml.cpp     112     Leaving DllMain()      20
2011-9-30-15-14-27     10176     .\jdbc.cpp     172     Leaving DllMain()      20
2011-9-30-15-14-27     10176     .\crdb_sforce.cpp     127     Leaving DllMain()      20
2011-9-30-15-14-27     10176     .\javabeans.cpp     113     In DllMain()      20
2011-9-30-15-14-27     10176     .\javabeans.cpp     136     Leaving DllMain()      20
2011-9-30-15-14-27     10176     .\xml.cpp     112     Leaving DllMain()      20
2011-9-30-15-14-27     10176     .\jdbc.cpp     172     Leaving DllMain()      20
2011-9-30-15-14-27     10176     .\crdb_sforce.cpp     127     Leaving DllMain()      20
2011-9-30-15-14-27     10176     .\javabeans.cpp     113     In DllMain()      20
2011-9-30-15-14-27     10176     .\javabeans.cpp     136     Leaving DllMain()      20
2011-9-30-15-14-32     10176     .\crdb_sforce.cpp     464     The ErrorArray exception thrown from the function DbLogonServer()     1
2011-9-30-15-14-32     10176     .\crdb_sforce.cpp     661     In DbFreeLogonInfo()     20
2011-9-30-15-14-32     10176     .\crdb_sforce.cpp     667     Leaving DbFreeLogonInfo()     20
2011-9-30-15-14-32     10176     .\crdb_sforce.cpp     2567     In DbFreeErrorInfo()     20
2011-9-30-15-14-32     10176     .\crdb_sforce.cpp     2570     Leaving DbFreeErrorInfo()     20
2011-9-30-15-14-32     10176     ..\cserrinf.cpp     523     Error 31837 (..\..\src\data\queryenghelp.cpp, 554): Failed to open the connection.: Unexpected error     1
2011-9-30-15-14-51     10176     .\javabeans.cpp     113     In DllMain()      20
2011-9-30-15-14-51     10176     .\javabeans.cpp     136     Leaving DllMain()      20
2011-9-30-15-14-51     10176     .\crdb_sforce.cpp     127     Leaving DllMain()      20
Any other ideas on what I can try here?

Answer 1

Hi Vitaly
I did some further playing based on the information you provided; that it should not differ between 2008 and 2011. I currently have both Crystal 2008 SP3 and 2011 SP2 installed so I went through and looked at the CRConfig files for both applications and could not see any major differences other then where they configure as the JVM and classpath.
I have managed to get Crystal 2011 to connect to salesforce after making one small edit to the 2011 CRConfig, changing the classpath to use the 2008 version of CRDBSForceServer.jar
I removed the entry within classpath for the CR2011 CRDBSForceServer.jar
F:\Program Files (x86)\SAP BusinessObjects 4
SAP BusinessObjects Enterprise XI 4.0\java/lib/CRDBSForceServer.jar;
and replaced it to point at the 2008 version
F:\Program Files (x86)\Business Objects\Common\4.0\java/lib/CRDBSForceServer.jar;
When I do this I am able to establish a connection to the salesforce DB without any other changes in the CRConfig. This does not solve my problem as I am still unable to run a deployed version of the report as I assume the latest 2011 version of the JAR is also part of the BO4 server and is getting the same connection problem on the server side but this may narrow it down enough for you to be able to provide further clarification on what the issue is.
thanks,
Brendan