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" wrote in message

>
> 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. but the problem
>> persists.
>>
>> Thank you in advance for your help.
 >> Stay informed about: I cannot Create an ODBC source for SQL server 2005 

Hi Cathy!

This is really weird... SQL 2005 has been giving me a hard time as
well. I'm no expect, but I would try the following:

* I'd ensure that both the User ID and Password are correct, keeping in
mind that (for some odd reason) SQL 2005 is case sensitive for both.
* I'd try using the IP address instead of the computer name. If that works,
then the problem is in the Domain Controller.
* I'd first connect to the Database Server by displaying a shared folder,
and then I'd try the connection again. This solve some authentication
barriers.
* I'd login using a Domain Administrator account and try creating an ODBC
connection using Windows Authentication.

I hope it helps!!!!

PS: This posting has been posted "AS IS"

"Cathy C" wrote:

> 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" wrote in message
>
> >
> > 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. but the problem
> >> persists.
> >>
> >> Thank you in advance for your help.
>
>
 >> Stay informed about: I cannot Create an ODBC source for SQL server 2005 

Tried all that - no luck. If you or anyone else have any other ideas, please
let me know. It's just strange that it only recently started. I have to
think it's because of some software update on the server. Now the user who
could previously connect to the database and whose settings I was mimicking
can't connect. We were careful to cancel out of the ODBC DSN wizard, but it
evidently was still enough to mess up the connection.

Thanks,
Cathy

"Tarh ik" wrote in message

>
> Hi Cathy!
>
> This is really weird... SQL 2005 has been giving me a hard time as
> well. I'm no expect, but I would try the following:
>
> * I'd ensure that both the User ID and Password are correct, keeping in
> mind that (for some odd reason) SQL 2005 is case sensitive for both.
> * I'd try using the IP address instead of the computer name. If that
> works,
> then the problem is in the Domain Controller.
> * I'd first connect to the Database Server by displaying a shared folder,
> and then I'd try the connection again. This solve some authentication
> barriers.
> * I'd login using a Domain Administrator account and try creating an ODBC
> connection using Windows Authentication.
>
> I hope it helps!!!!
>
> PS: This posting has been posted "AS IS"
>
> "Cathy C" wrote:
>
>> 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" wrote in message
>>
>> >
>> > 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. but the problem
>> >> persists.
>> >>
>> >> Thank you in advance for your help.
>>
>>
 >> Stay informed about: I cannot Create an ODBC source for SQL server 2005 

Thought you might like to know I finally found a solution at
http://geekswithblogs.net/azamsharp/archive/2005/07/27/48416.aspx . It may
be unorthodox, but it worked! Any ideas why??

[Hi
I have just spent the last 2 hours trying to get around this problem. I
looked at all the comments here (and elsewhere) and there are a lot of
people getting this error. My issue was 15 users could connect as they did
last Friday, but 3 users couldn't.
My fix was to use Named Pipes - this protocol is supported by default in SQL
(check in Server Network Utility) and presto - all is OK. I used Named Pipes
on the 3 clients that did not work.
It might not be the nicest, but it gets the clients up and working.
Hope it helps.

MKV]


"Cathy C" wrote in message

> Tried all that - no luck. If you or anyone else have any other ideas,
> please let me know. It's just strange that it only recently started. I
> have to think it's because of some software update on the server. Now the
> user who could previously connect to the database and whose settings I was
> mimicking can't connect. We were careful to cancel out of the ODBC DSN
> wizard, but it evidently was still enough to mess up the connection.
>
> Thanks,
> Cathy
>
> "Tarh ik" wrote in message
>
>>
>> Hi Cathy!
>>
>> This is really weird... SQL 2005 has been giving me a hard time as
>> well. I'm no expect, but I would try the following:
>>
>> * I'd ensure that both the User ID and Password are correct, keeping in
>> mind that (for some odd reason) SQL 2005 is case sensitive for both.
>> * I'd try using the IP address instead of the computer name. If that
>> works,
>> then the problem is in the Domain Controller.
>> * I'd first connect to the Database Server by displaying a shared folder,
>> and then I'd try the connection again. This solve some authentication
>> barriers.
>> * I'd login using a Domain Administrator account and try creating an ODBC
>> connection using Windows Authentication.
>>
>> I hope it helps!!!!
>>
>> PS: This posting has been posted "AS IS"
>>
>> "Cathy C" wrote:
>>
>>> 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" wrote in message
>>>
>>> >
>>> > 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. but the problem
>>> >> persists.
>>> >>
>>> >> Thank you in advance for your help.
>>>
>>>
>
 >> Stay informed about: I cannot Create an ODBC source for SQL server 2005