cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Crystal Reports 2013 SQL Server Connection Issues

Former Member
0 Likes
1,474

We have a Crystal Reports 2013 installation that does not want to connect to SQL Server. When connecting to a SQL Server DB we get the error message "Failed to open the connection." (see screenshot below).

There are no network connectivity issues with the DB, and we have tested the account, and other connection info in Management Studio with success. So I believe we are using the correct info for the connection string.

I have checked the CRConfig.xml file and if is configured properly, and all drivers are in the proper locations. As a side note, Oracle connections are working properly.

Any assistance, or suggestions would be appreciated.

Thanks.

View Entire Topic
DellSC
Active Contributor
0 Likes

Did you create the ODBC connections on the server as User DSNs or System DSNs?  They need to be System DSNs.

-Dell

Former Member
0 Likes

Not sure what you mean about the DSNs. How would you even differentiate them when you setup the connections in Crystal Reports?

DellSC
Active Contributor
0 Likes

If you're using ODBC you have to create the connections in the 32-bit ODBC Administrator on BOTH the workstation where you're creating the report and the server where CRS is installed.  The 64-bit version of the is available on the Windows "Administrative Tools" menu, but that won't work for reports.  Instead, you you have to run C:\Windows\syswow64\odbcad32.exe.

When you run this, it will open on the "User" tab, which is fine for the workstation where you're designing the report.  However, on the server where CRS is installed, you MUST change this to the "System" tab and create the connection there in order for CRS to be able to use it to run the report.

-Dell

Former Member
0 Likes

Thanks for the info, but I don't think this is the issue. We don't have a Crystal Reports Server. This is a standalone installation on a workstation. The workstation install is trying to connect directly to the SQL Server.

I was thinking it could be an issue with the CRConfig.xml file, but I have made sure that it is setup the exact same as other working installations.

Is there anything else you suggest checking?

Former Member
0 Likes

Hi Jeff

I am not sure what you mean by 'The workstation install is trying to connect directly to the SQL Server."

CR needs some sort of an intermediary / client to connect to any database. It may be a 32 bit ODBC connection that you have to configure, or OLE DB connection that once again you have to configure, or some database can be connected to using "native" drivers.

So, the 1st question would be; Are you using ODBC, OLE DB or other to connect CR to the database?

Then you need to keep the following in mind:

For OLE DB use:

MS SQL 2005 - OLE DB Provider

MS SQL 2008 - SQL Native 10

MS SQL 2013 - SQL Native 11

For ODBC use:

MS SQL 2005 - SQL Native

MS SQL 2008 - SQL Native 10

MS SQL 2013 - SQL Native 11

- Ludek

Senior Support Engineer Product Support, Global Support Center Canada

Chat with SAP  Support! See KBA 2213344 - Starting a chat with SAP Support [video]

Follow me on Twitter

Got Enhancement ideas? Use the SAP Idea Place

Former Member
0 Likes

I am not sure how to choose when you are setting up the connection. We are setting up a JDBC connection. I have configured the CRConfig.xml file to include any/all sqljdbc drivers.

Does that answer your question?

Former Member
0 Likes

See if this KBA will help:

1527666 - How to set up a successful JDBC connection in Crystal Reports?

Also, top right corner has a search box. Search for 'crystal jdbc' and you will get tons of KBAs, blogs and so on.

- Ludek

Former Member
0 Likes

I checked all the settings that are outlined in the KBA, and it doesn't appear to be helpful. Another note that might help. The connections to SQL Server DBs were working properly before on the system when it had Crystal Reports 2008. I had upgraded to Crystal Reports 2013. I have replicated the CRconfig setup, and made sure the same drivers are in the appropriate directory on the system.