Cannot connect to SQL Server 2008 R2 with 32 bit ODBC (Needed by Crystal Reports 11)

Question

When my SQL Server 2008 trial expired I could no longer buy the developer edition of that product.  I was forced to buy 2008 R2, which I have done and installed.  Now I can no longer connect Crystal Reports to my SQL Server. As a provider of Crystal Report development to thousands of customers worldwide this is a problem. 

Does someone have a workaround/ something I could install to allow 32 bit connections of my 2008 R2 SQL Server?

Answer 1

When connecting *FROM* a SQL-Server to another database such as Access, there is difference of accessibility between 32 bit or 64 bit.

However, when connecting *TO* a SQL-Server using the TCP/IP protocol, there shouldn't be any difference at all about either 32 bit or 64 bit and I think it's the same thing with the Named Pipe protocol.  However, I'm not that sure about the Named Pipes protocol and I don't know either about the Shared Memory protocol.  (Personally, I always use the TCP/IP protocol).

Another potential problem would be the fact that you have now more than one single instance of SQL-Server installed on your machine or that you have a single instance but that this newer instance (the Developer Edition) is not set up as the default instance but as a Named instance.  If so, you should add the name of the instance after the adress of the server separated by a backslash:

    MyServer\MyInstanceName

You must also make sure that the SQL-Server Browsing is up and running. Instance of adding the instance name, you could also add its port number (separated by a comma) if you are using the TCP/IP protocol: MyServer,1234 for exemple.

---

Sylvain Lafontaine, ing.
MVP - Access
Blog/web site: http://coding-paparazzi.sylvainlafontaine.com
Independent consultant and remote programming for Access and SQL-Server (French)

<cyndi1976> wrote in message news:[e-mail]...

When my SQL Server 2008 trial expired I could no longer buy the developer edition of that product. I was forced to buy 2008 R2, which I have done and installed. Now I can no longer connect Crystal Reports to my SQL Server. As a provider of Crystal Report development to thousands of customers worldwide this is a problem.

Does someone have a workaround/ something I could install to allow 32 bit connections of my 2008 R2 SQL Server?

Answer 2

Sylvana,

I am using SQL Server 2008 R2 with dynamics GP. I try to access the data from Crystal Reports XI professional and when I try to create a new ODBC (RDO) connection to the data from within CR, I get error 2800, [18456] login failed for user 'sa'. I tried changing all the settings of the odbcad32.exe and still the same problem. It can connect on OLE connection but not ODBC. can you think of a reason?

Thanks

Answer 3

Hi I am having a same issue. I have a cloud server with Win Ent 2008 R2 with SQL 2008 R2. 

I use odbcad32.exe to create a 32 bit dsn to connect to SQL (this is for GP 2010). I am getting error as below. I have sql browser is also up and running. I am able to connect with 64 bit odbc system DSN but not 32 bit. 

_____Connection Failed ____

Microsoft SQL Server Native Client Version 10.50.1600

Running connectivity tests...

Attempting connection [Microsoft][SQL Server Native Client 10.0]

SSL Provider: The certificate chain was issued by an authority that is not trusted. [Microsoft]

[SQL Server Native Client 10.0]Client unable to establish connection Disconnecting from server

TESTS FAILED! _____end Error ___

____odbc setup_______

Microsoft SQL Server Native Client Version 10.50.1600 Data Source Name: GPodbc32 Data Source Description: GP odbc 32 bit Server: localhost Use Integrated Security: No Database: (Default) Language: (Default) Data Encryption: Yes Trust Server Certificate: No Multiple Active Result Sets(MARS): No Translate Character Data: Yes Log Long Running Queries: No Log Driver Statistics: No Use Regional Settings: No Use ANSI Quoted Identifiers: No Use ANSI Null, Paddings and Warnings: Yes ----end odbc set up ******

I also checked the ACL rules and allowed port 1433