Post reply

connecting to x64 bit from 32 bit client

  • July 6, 2005 at 10:04 am

    #165247

    We're running W2003 x64 bit OS (which includes SP1) and June CTP of SQL 2005 x64 bit version. I cannot connect to any SQL database on this machine from a client PC, although I can connect to AS cubes from the client PC.

    I can connect from this server to a 32 bit version running on another machine just fine (W2003, no SP1, 32 bit OS).

    Surface Area Configurator does not work on this platform (x64 bit), and SQL Server Configuration Manager is set to allow np and tcp/ip. The Windows Firewall is also off.

    Here is the error when trying to create an ODBC connection:

    Microsoft SQL Native Client Version 09.00.1187

    Running connectivity tests...

    Attempting connection

    [Microsoft][SQL Native Client]Named Pipes Provider: Could not open a connection to SQL Server [233].

    [Microsoft][SQL Native Client]Client unable to establish connection

    [Microsoft][SQL Native Client]Login timeout expired

    TESTS FAILED!

    Any ideas where to look?

    Thanks, Greg

  • July 7, 2005 at 10:23 am

    #571946

    I 'm pretty sure you use the SQL Native Client provider to connect only to SQL 2005 instances., but I thought the native client had a dependancy to the .NET 2.0 framework.

    the client machines would probably have to have .NET 2.0 installed in order to use the SQL Native Client, but you can connect to a 2005 database with the SQLOLEDB driver with no problem as well.

     

    Lowell

    --help us help you! If you post a question, make sure you include a CREATE TABLE... statement and INSERT INTO... statement into that table to give the volunteers here representative data. with your description of the problem, we can provide a tested, verifiable solution to your question! asking the question the right way gets you a tested answer the fastest way possible!

  • July 7, 2005 at 10:37 am

    #571955

    I got it up and running. The x64 bit version of SQL 2005 is Developer Edition. It installs and does not allow remote access unless there was a previous version of SQL installed. Surface Area Configurator also generates an error (known bug). I manually verified named pipes and tcp/ip were turned on. I also added reg key IsListenerActive in and rebooted. Now it works fine.

    I'll have to check out the sqloledb - installing the 2.0 framework is a hefty obstacle.

    Thanks, GE

Viewing 3 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply