Unable to open Salesforce Database in Crystal Reports

[codysmsta]

I just installed Crystal Reports 2020 and am trying to open a report that my supervisor uses. He saved the file in OneDrive. The file actually opens fine but when I try to print preview and authenticate with our salesforce credentials, I get the following error:

"Failed to open the connection.
Details: IM002:[Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified".

I have attempted some troubleshooting steps on my own by reading some other forums but have been unsuccessful. I am certain the the login information to the server is correct. Can an SAP technical support agent assist?

[DonWilliams]

See this KBA on how to connect to SalesForce:

https://userapps.support.sap.com/sap/support/knowledge/en/2245135

Crystal Reports no longer has an option to purchase a single support case, this Community is your only option except if you purchase Crystal Reports Server you will get access to Support Engineers for 1 year (last time I checked)

Go here for more info and possible purchase:

https://support.sap.com/en/product/support-by-product/01200314690800000350.html

[ido_millet]

With Crystal 2020 (64-bit) the report requires a 64-bit ODBC DSN. That DSN is missing on that machine.

Perhaps you have it as a 32-bit DSN but a 64-bit app cannot use a 32-bit DSN.

[codysmsta]

So, we've made progress but now I'm running into another issue. We were able to copy a registry file that included the database connector from my supervisor's machine. That was able to get us past the password part. But now, once it starts to load (at least it appears that it's getting past that) if freezes and says "not responding" and then the application crashes. It doesn't give me a crash report or anything. I installed my software on a different server, had to go through all the hoops again to load the database, same thing, the app ends up not responding and then crashes. Not sure what's going on now...

[DonWilliams]

The problem with just copying registrry keys is CR doesn't support manually copying files and keys around, you must use the installer to get it done properly. Ask your user where it works how they installed the client. CR is looking for more keys or dll's etc. which is why it's hanging.

Check the PC where it's working in Programs and Features, you should see CR installed and possibly other Clients, both should be the same.

Download a tool called Process Monitor from Microsoft and compare file when logging on, you will like find a lot of keys and other dll's are missing. And check out the KBA I posted previously on debugging connnection issues.