Re: I cannot Create an ODBC source for SQL server 2005

I'm having the same problem with several machines. For a couple of years - since the installation of an enterprise database using SQL server 2005 - we had no problems with the ODBC connection on clients. After installing a new PC last month, the connection failed. I eventually ended up wiping the hard drive and reinstalling everything. This time I didn't use connectcomputer to add it to the domain. No problems. I can still get to the next screen in the ODBC connection configuration wizard after entering user id sa and the password on this machine.

Yesterday, while trying to establish the connection on a laptop which has been on the domain for a couple of years, I was unable to get past the Login ID sa and password - SQL Server Error 6: Specified SQL server not found. I went through the ODBC settings side-by-side with someone who is able to connect to the SQL database. However, when she entered the Login ID sa and password, she also got the error screen.

The only substantial clues I'm getting from this is that the computers originally connected to the domain using connectcomputer are now unable to get past the login screen for Connect to SQL Server to obtain default settings for ... Could there be some security or software update that has been applied on the server in the past three-four months that is disallowing this connection? (A new computer installed about four months ago using connectcomputer had no problems with the ODBC connection.) I did try unchecking dynamically determine the port and specifically setting it to connect to port 1433.

Appreciate any thoughts/suggestions.

Cathy


"Tarh ik" <Tarhik@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:E38299B3-43BD-4966-86FA-2B4E88A8520E@xxxxxxxxxxxxxxxx

Hi Pagliaccio!

I had this same problem some years ago. To solve it, what I did was to
click on the "Client Configuration", and made sure that the server name was
correct, that it didn't dynamically dermine the port, and specifically set it
to connect to port 1433. That did the trick for me.

Hope it helps!!!!

Tarh Ik

PS: This posting has been posted "AS IS"



"Pagliaccio" wrote:

I really need help on this one.

I have a database application (SQL server 2005 vs Access 2003) that two
users need to access (let's call them A nad B.) In the deployment process,
one of them has successfully connected to the database but the other cannot
do it so. We are almost sure is a machine problem, since both of them can use
the application from another machine. We've tried to manually create the ODBC
in B's machine but the system doesn't allow us (B's OS is an XP Professional
SP2.) We've also reinstalled the drivers (MDAC v2.8) but the problem persists.

Thank you in advance for your help.

.

Relevant Pages

  • Re: My Book is Incomplete Regarding SQL Commands ;-(
    ... Hitchhiker's Guide to Visual Studio and SQL Server ... Create a Connection object and pass in a ConnectionString to ... manage the database table you reference. ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: (Newbie)Application Roles
    ... level: the database itself. ... SQL Server accommodates these needs through the use of application ... the user's connection through a specific application. ... the connection permanently loses all permissions applied to ...
    (microsoft.public.sqlserver.security)
  • Re: Help! Set up Windows Group to access application
    ... The connection string for a trusted connection is: ... --add login as database user ... SQL Server MVP ... If you have troubles with finding your ways in Crystal Reports, ...
    (microsoft.public.sqlserver.security)
  • Re: My Book is Incomplete Regarding SQL Commands ;-(
    ... Visual Studio but not to VS 2003. ... Create a Connection object and pass in a ConnectionString to address ... manage the database table you reference. ... Yep, my latest book can help too, but mostly if you're targeting SQL Server ...
    (microsoft.public.dotnet.framework.adonet)
  • RE: Logging in in background
    ... wold take all kinds of modifictions as I'd need to be checking that each SQL ... my database and all have connection strings associated with them. ... I suspect that there is also an issue on the SQL Server side as I keep ...
    (microsoft.public.access.modulesdaovba)