Crystal Reports 2013 ODBC issue

[wendy_douglass2]

Our analysts upgraded from Crystal Reports 2008 to Crystal Reports 2013 SP2.  After the upgrade the previous ODBC connections do not work (see errors below).  I am using the correct credentials and all the ODBC tests for the connection show successful.  The ODBC connection is a System DSN connecting to a SQL Server 2008 database.  I am unable to connect either with existing reports that connected without issue in CR 2008 or in trying to create a new report in CR 2013.  The drivers tried and errors are below.  

Microsoft SQL Driver (this was the driver previously used with no issues):

Logon Failed.  Database Connector Error: 'IM006:[Microsoft][ODBC Driver Manager] Driver's SQLSetConnctorAttr failed[Database Vendor Code 18]. Database Connector Error: '01000:[Microsoft][ODBC SQL Server Driver][DBNETLIB]Connection Open (SECCreateCredentials()). [Database Vendor Code 18].

Microsoft SQL Server Native Client 10.0:

Logon failed. Details: IM004:[Microsoft][ODBC Driver Manager] Driver's SQLAllocHandle on SQL_HANDLE_ENV failed

Any help is appreciated.

[former_member11696]

Hi Wendy,

What version of SQL Server are you using?

Did you update the DSN to use the SQL Native 10 client dll?

Once updated did you do a Verify database in CRD?

Did you install the 32 bit SQL Server Client?

Are you using the 32 bit ODBC Administrator from \windows\syswow64 folder?

Don

[wendy_douglass2]

Hi Don,

- SQL server 2008

- Yes, SQL Server Native Client 10 produces error noted above

- Yes, tried to verify database in CR. Login is rejected so unable to verify

- No, I did not install a 32 bit SQL server client.  Are you asking about  separate SQL install or was it something in the upgrade?  The same machine was working and connecting with the same report and database before the upgrade. I've never had to install a SQL server client in order to use Crystal reports before.

- Yes, I'm using the 32 bit ODBC Administrator from the windows\syswow64 folder.  The laptop for the install is not a 64 bit machine.

Thanks for your insight!

[former_member11696]

Hi Wendy,

The reason you now have to install the SQL Native 10 client is MS does not fully support MDAC drivers to SQL 2008 and above.

Look an MS's Site for more info on the limitations.

The error being generated is simply being passed through from the DB client, CR has nothing to do with that error: ..."SQLSetConnctorAttr failed[Database Vendor Code 18]"

So after looking for the error code you are getting I found a few links:

Seems you have a problem with your MS SQL Client installs, or lack of...

Don

[wendy_douglass2]

Hi Don,

The SQL Native 10 Client driver is already installed.  It is one of the drivers I already tried that will not connect. The ODBC Login Fails Everytime with CR 2011 is related to Oracle not SQL (the other link is to my problem) , but I read up at the MS site as well as suggested.  I even downloaded the new MSODBCSQL11 to see if it would work with no luck.  What else am I missing?

Thanks,

Wendy

[former_member11696]

Hi Wendy,

OK but the error is still a ODBC/Client error. CR is not generating it, we are just passing it along from the client.

So when CR tries to connect it's running into this error.

Try this, open CR Designer and then connect, do not open a report first. See if that works?

If it does then open a report and see what happens.

Don

[wendy_douglass2]

Thanks Don.  I tried your suggestion.  Just opened Crystal no report, File > Log OnorOff Sever.  Same results, same error.  It wouldn't connect.   I also downloaded a newer version of SQL Native Client 10 earlier to make sure that wasn't the issue. No change.

I tried SAP support today as well.  They said install was not done as Administrator, even though I had screen shots showing it was.....Anyway uninstalled, did the registry deletes, confirmed I was admin on machine, re-installed doing the right click Run as Administrator on the the setup.  Same results.  I'm out of ideas.  Can you think of anything else?  We have 15 analysts that cannot use the new version of the software.

Thanks

[former_member11696]

Hi Wendy,

What is the case number? I'll have a look and possibly take it over. Can you enable ODBC tracing and attach the log to the case for review. It may give us more info on what CR is passing to the driver.

What OS are you using?

Don

[wendy_douglass2]

Don,

Incident# 874243/2015

I no longer have the laptop.  The user needed it back to continue working  (can still use CR 2008) so  I will need to wait until I can get one of the other analyst's laptops to continue working on this.    We are using Windows 7 OS.  As soon as I can either get the same laptop back or one of the other analyst's laptop with same issue, I will enable ODBC tracing and attach the log file to the incident.  Thank you for your help.

[former_member11696]

Case was auto closed after using SQLCON to test connection, no update from Wendy.