ODBC Connection failure

My application (written in a proprietary old 4GL) is connecting to a SQL 2000 database via ODBC

This works fine nearly all the time, but occasionally, it throws the following error when trying to connect :

Connection Failed

SQLState '01000'

SQL Server Error: 10060

[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]Connection Open(Connect()).

Connection Failed:

SQLState '08001'

SQL Server Error: 17

[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]SQL Server does not exist or access denied.

This error is displayed in a Windows dialog box. When the OK button on this dialog is clicked, it throws up a login/password box. When this is filled in and submitted, the connection is usually made cleanly and the application continues.

The big problem is that the application is an unattended service, and this dialog can go unnoticed for quite a while.

If these dialogs are 'Cancelled' rather than 'OK'd, the 4GL receives the error and arranges to re-try the connection itself.

Is ODBC responsible for popping up the interactive dialog, and, if so, can I do anything to force it to return an error instead ?

Hi Steve,

Interesting situation. The error 10060 means this: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. So you are probably experiencing a timeout in one of the socket-relation ops, most probably connect() (different from the SQL netlib's Connect() mentioned above).

The login popup is implemented by the SQL ODBC driver. You are probably using SQLDriverConnect in ODBC? It has a parameter "DriverCompletion", which could be:

SQL_DRIVER_PROMPT
SQL_DRIVER_COMPLETE
SQL_DRIVER_COMPLETE_REQUIRED
SQL_DRIVER_NOPROMPT

You probably have passed the first one (SQL_DRIVER_PROMPT). In order to make sure the SQLDriverConnect fails without popping up the troublesome dialog, you need to pass the SQL_DRIVER_NOPROMPT. I truly hope you are able to modify the 4GL application?

HTH,
Jivko Dobrev - MSFT
--
This posting is provided "AS IS" with no warranties, and confers no rights.

|||

Thanks a lot Jivko.

Unfortunately, the only parameter the 4GL allows me to specify is the DSN name.

I'll be on to the vendor's support desk rather forcefully first thing on Monday morning - thanks for the Ammo!

ODBC Connection Failure

Hi,
I'm trying to create a ODBC connection to SQL server 2000 using SQL server authentication. I have login id "lucky9797" and password "tool" but I'm keep getting the following error message:
Connection Failed:
SQLState:'28000'
SQL Server Error: 18456
[Microsoft][ODBC SQL Server Driver][SQL Server]Login Failed for user "lucky9797"
Could someone please tell me why am I getting this error message? Thanks.
Message posted via http://www.sqlmonster.com
1) It might be that the collation sequence indicated at installation time is
case insensitive. Try typing "TOOL" instead of "tool"
"syed rahman via SQLMonster.com" <forum@.SQLMonster.com> wrote in message
news:0e43caa46e9040489d8c88e56a57a606@.SQLMonster.c om...
> Hi,
> I'm trying to create a ODBC connection to SQL server 2000 using SQL server
authentication. I have login id "lucky9797" and password "tool" but I'm keep
getting the following error message:
> Connection Failed:
> SQLState:'28000'
> SQL Server Error: 18456
> [Microsoft][ODBC SQL Server Driver][SQL Server]Login Failed for
user "lucky9797"
> Could someone please tell me why am I getting this error message? Thanks.
> --
> Message posted via http://www.sqlmonster.com

ODBC connection failure

After upgrading to Windows 2003 Server, I can no longer
access SQL Server via ODBC. It says the SQL Server
doesn't exist or access denied. None of the settings have
changed after the upgrade.
Is there a fix to this?
Thanks in advance.(a) stop using ODBC, it's been deprecated. OLEDB is much preferred.
(b) SQL Server authentication? Windows authentication? What is the
username you are using? What kind of account is it? Have you tried a
different authentication method and/or a different user?
(c) http://support.microsoft.com/?kbid=328306
http://www.aspfaq.com/
(Reverse address to reply.)
"Mike" <anonymous@.discussions.microsoft.com> wrote in message
news:19b9c01c44d6d$b0030b20$a401280a@.phx
.gbl...
> After upgrading to Windows 2003 Server, I can no longer
> access SQL Server via ODBC. It says the SQL Server
> doesn't exist or access denied. None of the settings have
> changed after the upgrade.
> Is there a fix to this?
> Thanks in advance.|||How would I switch to the OLEDB method? It's SQL Server
auth., and also tried different methods and users.
Also, I found that the ODBC Driver versions are different
on the client machines. Would I need to update the
clients to the new version?

>--Original Message--
>(a) stop using ODBC, it's been deprecated. OLEDB is much
preferred.
>(b) SQL Server authentication? Windows authentication?
What is the
>username you are using? What kind of account is it?
Have you tried a
>different authentication method and/or a different user?
>(c) http://support.microsoft.com/?kbid=328306
>--
>http://www.aspfaq.com/
>(Reverse address to reply.)
>
>
>"Mike" <anonymous@.discussions.microsoft.com> wrote in
message
> news:19b9c01c44d6d$b0030b20$a401280a@.phx
.gbl...
have[vbcol=seagreen]
>
>.
>|||> How would I switch to the OLEDB method?
That really depends... what application/language are you using for the
client applications?

> Also, I found that the ODBC Driver versions are different
> on the client machines. Would I need to update the
> clients to the new version?
Yes, apply the latest MDAC all around. You should try to avoid mismatched
versions between client and server.
85d0506396c&DisplayLang=en" target="_blank">http://www.microsoft.com/downloads/...&DisplayLang=en
http://www.aspfaq.com/
(Reverse address to reply.)|||Installing the MDAC results in the same SQL Server does
not exist error.
All of the clients are using Windows XP Pro to connect to
the SQL Server.

>--Original Message--
>That really depends... what application/language are you
using for the
>client applications?
>
different[vbcol=seagreen]
>Yes, apply the latest MDAC all around. You should try to
avoid mismatched
>versions between client and server.
>http://www.microsoft.com/downloads/details.aspx?
FamilyID=6c050fe3-c795-4b7d-b037-
185d0506396c&DisplayLang=en
>--
>http://www.aspfaq.com/
>(Reverse address to reply.)|||> All of the clients are using Windows XP Pro to connect to
> the SQL Server.
That's the operating system, but it doesn't tell me anything about the
application that is attempting to make a connection. Are you trying to
connect from Excel, notepad, ColdFusion, Query Analyzer, the ODBC control
panel applet, ... ?
Have you gone through http://support.microsoft.com/?kbid=328306 ?
http://www.aspfaq.com/
(Reverse address to reply.)|||I'm trying to connect from the ODBC Control Panel.
Yes, I have through the 328306 article and haven't found
any resolutions.
Would the easiest thing to do be revert back to Windows
2000 when this all worked correctly?

>--Original Message--
to[vbcol=seagreen]
>That's the operating system, but it doesn't tell me
anything about the
>application that is attempting to make a connection. Are
you trying to
>connect from Excel, notepad, ColdFusion, Query Analyzer,
the ODBC control
>panel applet, ... ?
>Have you gone through http://support.microsoft.com/?
kbid=328306 ?
>--
>http://www.aspfaq.com/
>(Reverse address to reply.)
>
>.
>|||> I'm trying to connect from the ODBC Control Panel.
Why? And then what are you going to do with it once you've connected?
Typically this is used to create a DSN for some other application, like an
ASP page or VB app. In which case, you are much better off connecting
through OLEDB. I can't tell you how to do that until you provide more
information.

> Yes, I have through the 328306 article and haven't found
> any resolutions.
Can you tell us what you tried, with regard to each article listed at that
link? I'm guessing you didn't inspect every single article listed there,
since it has been less than an hour, and you'd have to be Number 5 from
Short Circuit to have read all of the content already.

> Would the easiest thing to do be revert back to Windows
> 2000 when this all worked correctly?
No, that's silly. Windows XP is not to blame; you have a configuration
issue, that's all. If you tell us everything you tried regarding 328306,
you will leave the remaining potential options.
http://www.aspfaq.com/
(Reverse address to reply.)|||I need the DSN to run Crystal Reports.
As for KB #328306, I tried everything under the Server-
Related Causes. The protocols are all ok, port 1433 is
the same on each machine, and tried giving the server a
new alias.
As for the Client/App-Related Causes, the protocols don't
change, no network adaptor issues, not worried about MDAC
connections, and Named Pipes don't apply.
There was nothing applicable under the Network Causes as
everything is run locally.

>--Original Message--
>Why? And then what are you going to do with it once
you've connected?
>Typically this is used to create a DSN for some other
application, like an
>ASP page or VB app. In which case, you are much better
off connecting
>through OLEDB. I can't tell you how to do that until you
provide more
>information.
>
>Can you tell us what you tried, with regard to each
article listed at that
>link? I'm guessing you didn't inspect every single
article listed there,
>since it has been less than an hour, and you'd have to be
Number 5 from
>Short Circuit to have read all of the content already.
>
>No, that's silly. Windows XP is not to blame; you have a
configuration
>issue, that's all. If you tell us everything you tried
regarding 328306,
>you will leave the remaining potential options.
>--
>http://www.aspfaq.com/
>(Reverse address to reply.)
>
>.
>|||So what name are you using to refer to the local server? Have you tried
"LOCALHOST", "(LOCAL)", "127.0.0.1", the actual server name, the actual IP
address?
http://www.aspfaq.com/
(Reverse address to reply.)
"Mike" <anonymous@.discussions.microsoft.com> wrote in message
news:199ec01c44d7f$b2851cf0$a301280a@.phx
.gbl...[vbcol=seagreen]
> I need the DSN to run Crystal Reports.
> As for KB #328306, I tried everything under the Server-
> Related Causes. The protocols are all ok, port 1433 is
> the same on each machine, and tried giving the server a
> new alias.
> As for the Client/App-Related Causes, the protocols don't
> change, no network adaptor issues, not worried about MDAC
> connections, and Named Pipes don't apply.
> There was nothing applicable under the Network Causes as
> everything is run locally.
>
> you've connected?
> application, like an
> off connecting
> provide more
> article listed at that
> article listed there,
> Number 5 from
> configuration
> regarding 328306,

ODBC Connection failure

Hello there!

This is my issue: I do have a database which back end is in SQL Server 2005 and front end is in ACCESS 2003. When one of the forms is trying to write duplicate information in any of the tables, there is a message coming "ODBC -- call failure", I wrote code trying to avoid that situation, but is keeps on coming. Does anybody have any idea about how to handle this exception? I would really appreciate a help on this subject.

Thanks;

Luisofo

One approach is to add an On Error handler to the Access Form. http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vbaac11/html/achowRuntimeErrorHandling_HV05186924.asp In the On Error handler you can use the Err object to determine the source of the error and provide useful information to the user to correct the problem.

If you are ok with duplicates in the table (not usually the situation) you can remove the constraints on the SQLServer 2005 datgbase tables.

HTH.

sql

ODBC Connection Failure

I am having a problem getting the ODBC driver to connect.

I just installed VS2005 and can't connect to my SQL2000 server. It is there. I can't connect using either one of the mix mode authentication.

I can login to SQL from another pc when logged in with this user name. It has to be something on this pc blocking it.

Iam not rying to do this from a ASP web page just trying to setup a ODBC driver and I get these errors.

I get the error:" Login failed for user (null)" Not associated with a trusted connection

Thanks

Mike

I downloaded and installed manager studio and I can see the server in the network tab but still can't connect. I get the error 11001

Any Ideas?

Thanks

|||

Let's see your connection string. I would also read: http://betav.com/blog/billva/2006/06/getting_and_staying_connected.html

|||

This link was broken for a while and I could not reply.

William,

Little background. I have had this application up and running since Oct 05 with the connection string on several different pc's.

There is no problem with the connection string.

I recently had difficulty on two new PC, one laptop and one desktop. Neither could access SQL2000 running on another PC. Both could run the application and connection string locally if I copied the DB down to express. This application is a smart client app not an ASP app.

Both instances had newly installed VS2005 and SQL Express installed on them.

I could not even set up a DSN using ODBC manager. It would not connect to the SQL 2000 server.

When I tried using SQL Mgr Studio Express, it could see the SQL 2000 server but not connect to it.

I always got some kind of connection error.

Thanks.

ODBC connection failure

After upgrading to Windows 2003 Server, I can no longer
access SQL Server via ODBC. It says the SQL Server
doesn't exist or access denied. None of the settings have
changed after the upgrade.
Is there a fix to this?
Thanks in advance.
(a) stop using ODBC, it's been deprecated. OLEDB is much preferred.
(b) SQL Server authentication? Windows authentication? What is the
username you are using? What kind of account is it? Have you tried a
different authentication method and/or a different user?
(c) http://support.microsoft.com/?kbid=328306
http://www.aspfaq.com/
(Reverse address to reply.)
"Mike" <anonymous@.discussions.microsoft.com> wrote in message
news:19b9c01c44d6d$b0030b20$a401280a@.phx.gbl...
> After upgrading to Windows 2003 Server, I can no longer
> access SQL Server via ODBC. It says the SQL Server
> doesn't exist or access denied. None of the settings have
> changed after the upgrade.
> Is there a fix to this?
> Thanks in advance.
|||How would I switch to the OLEDB method? It's SQL Server
auth., and also tried different methods and users.
Also, I found that the ODBC Driver versions are different
on the client machines. Would I need to update the
clients to the new version?

>--Original Message--
>(a) stop using ODBC, it's been deprecated. OLEDB is much
preferred.
>(b) SQL Server authentication? Windows authentication?
What is the
>username you are using? What kind of account is it?
Have you tried a
>different authentication method and/or a different user?
>(c) http://support.microsoft.com/?kbid=328306
>--
>http://www.aspfaq.com/
>(Reverse address to reply.)
>
>
>"Mike" <anonymous@.discussions.microsoft.com> wrote in
message[vbcol=seagreen]
>news:19b9c01c44d6d$b0030b20$a401280a@.phx.gbl...
have
>
>.
>
|||> How would I switch to the OLEDB method?
That really depends... what application/language are you using for the
client applications?

> Also, I found that the ODBC Driver versions are different
> on the client machines. Would I need to update the
> clients to the new version?
Yes, apply the latest MDAC all around. You should try to avoid mismatched
versions between client and server.
http://www.microsoft.com/downloads/d...DisplayLang=en
http://www.aspfaq.com/
(Reverse address to reply.)
|||Installing the MDAC results in the same SQL Server does
not exist error.
All of the clients are using Windows XP Pro to connect to
the SQL Server.

>--Original Message--
>That really depends... what application/language are you
using for the[vbcol=seagreen]
>client applications?
different
>Yes, apply the latest MDAC all around. You should try to
avoid mismatched
>versions between client and server.
>http://www.microsoft.com/downloads/details.aspx?
FamilyID=6c050fe3-c795-4b7d-b037-
185d0506396c&DisplayLang=en
>--
>http://www.aspfaq.com/
>(Reverse address to reply.)
|||> All of the clients are using Windows XP Pro to connect to
> the SQL Server.
That's the operating system, but it doesn't tell me anything about the
application that is attempting to make a connection. Are you trying to
connect from Excel, notepad, ColdFusion, Query Analyzer, the ODBC control
panel applet, ... ?
Have you gone through http://support.microsoft.com/?kbid=328306 ?
http://www.aspfaq.com/
(Reverse address to reply.)
|||I'm trying to connect from the ODBC Control Panel.
Yes, I have through the 328306 article and haven't found
any resolutions.
Would the easiest thing to do be revert back to Windows
2000 when this all worked correctly?
[vbcol=seagreen]
>--Original Message--
to
>That's the operating system, but it doesn't tell me
anything about the
>application that is attempting to make a connection. Are
you trying to
>connect from Excel, notepad, ColdFusion, Query Analyzer,
the ODBC control
>panel applet, ... ?
>Have you gone through http://support.microsoft.com/?
kbid=328306 ?
>--
>http://www.aspfaq.com/
>(Reverse address to reply.)
>
>.
>
|||> I'm trying to connect from the ODBC Control Panel.
Why? And then what are you going to do with it once you've connected?
Typically this is used to create a DSN for some other application, like an
ASP page or VB app. In which case, you are much better off connecting
through OLEDB. I can't tell you how to do that until you provide more
information.

> Yes, I have through the 328306 article and haven't found
> any resolutions.
Can you tell us what you tried, with regard to each article listed at that
link? I'm guessing you didn't inspect every single article listed there,
since it has been less than an hour, and you'd have to be Number 5 from
Short Circuit to have read all of the content already.

> Would the easiest thing to do be revert back to Windows
> 2000 when this all worked correctly?
No, that's silly. Windows XP is not to blame; you have a configuration
issue, that's all. If you tell us everything you tried regarding 328306,
you will leave the remaining potential options.
http://www.aspfaq.com/
(Reverse address to reply.)
|||I need the DSN to run Crystal Reports.
As for KB #328306, I tried everything under the Server-
Related Causes. The protocols are all ok, port 1433 is
the same on each machine, and tried giving the server a
new alias.
As for the Client/App-Related Causes, the protocols don't
change, no network adaptor issues, not worried about MDAC
connections, and Named Pipes don't apply.
There was nothing applicable under the Network Causes as
everything is run locally.

>--Original Message--
>Why? And then what are you going to do with it once
you've connected?
>Typically this is used to create a DSN for some other
application, like an
>ASP page or VB app. In which case, you are much better
off connecting
>through OLEDB. I can't tell you how to do that until you
provide more
>information.
>
>Can you tell us what you tried, with regard to each
article listed at that
>link? I'm guessing you didn't inspect every single
article listed there,
>since it has been less than an hour, and you'd have to be
Number 5 from
>Short Circuit to have read all of the content already.
>
>No, that's silly. Windows XP is not to blame; you have a
configuration
>issue, that's all. If you tell us everything you tried
regarding 328306,
>you will leave the remaining potential options.
>--
>http://www.aspfaq.com/
>(Reverse address to reply.)
>
>.
>
|||So what name are you using to refer to the local server? Have you tried
"LOCALHOST", "(LOCAL)", "127.0.0.1", the actual server name, the actual IP
address?
http://www.aspfaq.com/
(Reverse address to reply.)
"Mike" <anonymous@.discussions.microsoft.com> wrote in message
news:199ec01c44d7f$b2851cf0$a301280a@.phx.gbl...[vbcol=seagreen]
> I need the DSN to run Crystal Reports.
> As for KB #328306, I tried everything under the Server-
> Related Causes. The protocols are all ok, port 1433 is
> the same on each machine, and tried giving the server a
> new alias.
> As for the Client/App-Related Causes, the protocols don't
> change, no network adaptor issues, not worried about MDAC
> connections, and Named Pipes don't apply.
> There was nothing applicable under the Network Causes as
> everything is run locally.
> you've connected?
> application, like an
> off connecting
> provide more
> article listed at that
> article listed there,
> Number 5 from
> configuration
> regarding 328306,

ODBC connection failure

After upgrading to Windows 2003 Server, I can no longer
access SQL Server via ODBC. It says the SQL Server
doesn't exist or access denied. None of the settings have
changed after the upgrade.
Is there a fix to this?
Thanks in advance.(a) stop using ODBC, it's been deprecated. OLEDB is much preferred.
(b) SQL Server authentication? Windows authentication? What is the
username you are using? What kind of account is it? Have you tried a
different authentication method and/or a different user?
(c) http://support.microsoft.com/?kbid=328306
--
http://www.aspfaq.com/
(Reverse address to reply.)
"Mike" <anonymous@.discussions.microsoft.com> wrote in message
news:19b9c01c44d6d$b0030b20$a401280a@.phx.gbl...
> After upgrading to Windows 2003 Server, I can no longer
> access SQL Server via ODBC. It says the SQL Server
> doesn't exist or access denied. None of the settings have
> changed after the upgrade.
> Is there a fix to this?
> Thanks in advance.|||How would I switch to the OLEDB method? It's SQL Server
auth., and also tried different methods and users.
Also, I found that the ODBC Driver versions are different
on the client machines. Would I need to update the
clients to the new version?
>--Original Message--
>(a) stop using ODBC, it's been deprecated. OLEDB is much
preferred.
>(b) SQL Server authentication? Windows authentication?
What is the
>username you are using? What kind of account is it?
Have you tried a
>different authentication method and/or a different user?
>(c) http://support.microsoft.com/?kbid=328306
>--
>http://www.aspfaq.com/
>(Reverse address to reply.)
>
>
>"Mike" <anonymous@.discussions.microsoft.com> wrote in
message
>news:19b9c01c44d6d$b0030b20$a401280a@.phx.gbl...
>> After upgrading to Windows 2003 Server, I can no longer
>> access SQL Server via ODBC. It says the SQL Server
>> doesn't exist or access denied. None of the settings
have
>> changed after the upgrade.
>> Is there a fix to this?
>> Thanks in advance.
>
>.
>|||> How would I switch to the OLEDB method?
That really depends... what application/language are you using for the
client applications?
> Also, I found that the ODBC Driver versions are different
> on the client machines. Would I need to update the
> clients to the new version?
Yes, apply the latest MDAC all around. You should try to avoid mismatched
versions between client and server.
http://www.microsoft.com/downloads/details.aspx?FamilyID=6c050fe3-c795-4b7d-b037-185d0506396c&DisplayLang=en
--
http://www.aspfaq.com/
(Reverse address to reply.)|||Installing the MDAC results in the same SQL Server does
not exist error.
All of the clients are using Windows XP Pro to connect to
the SQL Server.
>--Original Message--
>> How would I switch to the OLEDB method?
>That really depends... what application/language are you
using for the
>client applications?
>> Also, I found that the ODBC Driver versions are
different
>> on the client machines. Would I need to update the
>> clients to the new version?
>Yes, apply the latest MDAC all around. You should try to
avoid mismatched
>versions between client and server.
>http://www.microsoft.com/downloads/details.aspx?
FamilyID=6c050fe3-c795-4b7d-b037-
185d0506396c&DisplayLang=en
>--
>http://www.aspfaq.com/
>(Reverse address to reply.)|||> All of the clients are using Windows XP Pro to connect to
> the SQL Server.
That's the operating system, but it doesn't tell me anything about the
application that is attempting to make a connection. Are you trying to
connect from Excel, notepad, ColdFusion, Query Analyzer, the ODBC control
panel applet, ... ?
Have you gone through http://support.microsoft.com/?kbid=328306 ?
--
http://www.aspfaq.com/
(Reverse address to reply.)|||I'm trying to connect from the ODBC Control Panel.
Yes, I have through the 328306 article and haven't found
any resolutions.
Would the easiest thing to do be revert back to Windows
2000 when this all worked correctly?
>--Original Message--
>> All of the clients are using Windows XP Pro to connect
to
>> the SQL Server.
>That's the operating system, but it doesn't tell me
anything about the
>application that is attempting to make a connection. Are
you trying to
>connect from Excel, notepad, ColdFusion, Query Analyzer,
the ODBC control
>panel applet, ... ?
>Have you gone through http://support.microsoft.com/?
kbid=328306 ?
>--
>http://www.aspfaq.com/
>(Reverse address to reply.)
>
>.
>|||> I'm trying to connect from the ODBC Control Panel.
Why? And then what are you going to do with it once you've connected?
Typically this is used to create a DSN for some other application, like an
ASP page or VB app. In which case, you are much better off connecting
through OLEDB. I can't tell you how to do that until you provide more
information.
> Yes, I have through the 328306 article and haven't found
> any resolutions.
Can you tell us what you tried, with regard to each article listed at that
link? I'm guessing you didn't inspect every single article listed there,
since it has been less than an hour, and you'd have to be Number 5 from
Short Circuit to have read all of the content already.
> Would the easiest thing to do be revert back to Windows
> 2000 when this all worked correctly?
No, that's silly. Windows XP is not to blame; you have a configuration
issue, that's all. If you tell us everything you tried regarding 328306,
you will leave the remaining potential options.
--
http://www.aspfaq.com/
(Reverse address to reply.)|||I need the DSN to run Crystal Reports.
As for KB #328306, I tried everything under the Server-
Related Causes. The protocols are all ok, port 1433 is
the same on each machine, and tried giving the server a
new alias.
As for the Client/App-Related Causes, the protocols don't
change, no network adaptor issues, not worried about MDAC
connections, and Named Pipes don't apply.
There was nothing applicable under the Network Causes as
everything is run locally.
>--Original Message--
>> I'm trying to connect from the ODBC Control Panel.
>Why? And then what are you going to do with it once
you've connected?
>Typically this is used to create a DSN for some other
application, like an
>ASP page or VB app. In which case, you are much better
off connecting
>through OLEDB. I can't tell you how to do that until you
provide more
>information.
>> Yes, I have through the 328306 article and haven't found
>> any resolutions.
>Can you tell us what you tried, with regard to each
article listed at that
>link? I'm guessing you didn't inspect every single
article listed there,
>since it has been less than an hour, and you'd have to be
Number 5 from
>Short Circuit to have read all of the content already.
>> Would the easiest thing to do be revert back to Windows
>> 2000 when this all worked correctly?
>No, that's silly. Windows XP is not to blame; you have a
configuration
>issue, that's all. If you tell us everything you tried
regarding 328306,
>you will leave the remaining potential options.
>--
>http://www.aspfaq.com/
>(Reverse address to reply.)
>
>.
>|||So what name are you using to refer to the local server? Have you tried
"LOCALHOST", "(LOCAL)", "127.0.0.1", the actual server name, the actual IP
address?
--
http://www.aspfaq.com/
(Reverse address to reply.)
"Mike" <anonymous@.discussions.microsoft.com> wrote in message
news:199ec01c44d7f$b2851cf0$a301280a@.phx.gbl...
> I need the DSN to run Crystal Reports.
> As for KB #328306, I tried everything under the Server-
> Related Causes. The protocols are all ok, port 1433 is
> the same on each machine, and tried giving the server a
> new alias.
> As for the Client/App-Related Causes, the protocols don't
> change, no network adaptor issues, not worried about MDAC
> connections, and Named Pipes don't apply.
> There was nothing applicable under the Network Causes as
> everything is run locally.
> >--Original Message--
> >> I'm trying to connect from the ODBC Control Panel.
> >
> >Why? And then what are you going to do with it once
> you've connected?
> >Typically this is used to create a DSN for some other
> application, like an
> >ASP page or VB app. In which case, you are much better
> off connecting
> >through OLEDB. I can't tell you how to do that until you
> provide more
> >information.
> >
> >> Yes, I have through the 328306 article and haven't found
> >> any resolutions.
> >
> >Can you tell us what you tried, with regard to each
> article listed at that
> >link? I'm guessing you didn't inspect every single
> article listed there,
> >since it has been less than an hour, and you'd have to be
> Number 5 from
> >Short Circuit to have read all of the content already.
> >
> >> Would the easiest thing to do be revert back to Windows
> >> 2000 when this all worked correctly?
> >
> >No, that's silly. Windows XP is not to blame; you have a
> configuration
> >issue, that's all. If you tell us everything you tried
> regarding 328306,
> >you will leave the remaining potential options.
> >
> >--
> >http://www.aspfaq.com/
> >(Reverse address to reply.)
> >
> >
> >.
> >|||The actual server name is what I'm using.
>--Original Message--
>So what name are you using to refer to the local server?
Have you tried
>"LOCALHOST", "(LOCAL)", "127.0.0.1", the actual server
name, the actual IP
>address?
>--
>http://www.aspfaq.com/
>(Reverse address to reply.)
>
>
>"Mike" <anonymous@.discussions.microsoft.com> wrote in
message
>news:199ec01c44d7f$b2851cf0$a301280a@.phx.gbl...
>> I need the DSN to run Crystal Reports.
>> As for KB #328306, I tried everything under the Server-
>> Related Causes. The protocols are all ok, port 1433 is
>> the same on each machine, and tried giving the server a
>> new alias.
>> As for the Client/App-Related Causes, the protocols
don't
>> change, no network adaptor issues, not worried about
MDAC
>> connections, and Named Pipes don't apply.
>> There was nothing applicable under the Network Causes as
>> everything is run locally.
>> >--Original Message--
>> >> I'm trying to connect from the ODBC Control Panel.
>> >
>> >Why? And then what are you going to do with it once
>> you've connected?
>> >Typically this is used to create a DSN for some other
>> application, like an
>> >ASP page or VB app. In which case, you are much better
>> off connecting
>> >through OLEDB. I can't tell you how to do that until
you
>> provide more
>> >information.
>> >
>> >> Yes, I have through the 328306 article and haven't
found
>> >> any resolutions.
>> >
>> >Can you tell us what you tried, with regard to each
>> article listed at that
>> >link? I'm guessing you didn't inspect every single
>> article listed there,
>> >since it has been less than an hour, and you'd have to
be
>> Number 5 from
>> >Short Circuit to have read all of the content already.
>> >
>> >> Would the easiest thing to do be revert back to
Windows
>> >> 2000 when this all worked correctly?
>> >
>> >No, that's silly. Windows XP is not to blame; you
have a
>> configuration
>> >issue, that's all. If you tell us everything you tried
>> regarding 328306,
>> >you will leave the remaining potential options.
>> >
>> >--
>> >http://www.aspfaq.com/
>> >(Reverse address to reply.)
>> >
>> >
>> >.
>> >
>
>.
>|||So, try the others...
--
http://www.aspfaq.com/
(Reverse address to reply.)
"Mike" <anonymous@.discussions.microsoft.com> wrote in message
news:199f801c44d81$97deaf90$a301280a@.phx.gbl...
> The actual server name is what I'm using.
> >--Original Message--
> >So what name are you using to refer to the local server?
> Have you tried
> >"LOCALHOST", "(LOCAL)", "127.0.0.1", the actual server
> name, the actual IP
> >address?
> >
> >--
> >http://www.aspfaq.com/
> >(Reverse address to reply.)
> >
> >
> >
> >
> >"Mike" <anonymous@.discussions.microsoft.com> wrote in
> message
> >news:199ec01c44d7f$b2851cf0$a301280a@.phx.gbl...
> >> I need the DSN to run Crystal Reports.
> >>
> >> As for KB #328306, I tried everything under the Server-
> >> Related Causes. The protocols are all ok, port 1433 is
> >> the same on each machine, and tried giving the server a
> >> new alias.
> >>
> >> As for the Client/App-Related Causes, the protocols
> don't
> >> change, no network adaptor issues, not worried about
> MDAC
> >> connections, and Named Pipes don't apply.
> >>
> >> There was nothing applicable under the Network Causes as
> >> everything is run locally.
> >>
> >> >--Original Message--
> >> >> I'm trying to connect from the ODBC Control Panel.
> >> >
> >> >Why? And then what are you going to do with it once
> >> you've connected?
> >> >Typically this is used to create a DSN for some other
> >> application, like an
> >> >ASP page or VB app. In which case, you are much better
> >> off connecting
> >> >through OLEDB. I can't tell you how to do that until
> you
> >> provide more
> >> >information.
> >> >
> >> >> Yes, I have through the 328306 article and haven't
> found
> >> >> any resolutions.
> >> >
> >> >Can you tell us what you tried, with regard to each
> >> article listed at that
> >> >link? I'm guessing you didn't inspect every single
> >> article listed there,
> >> >since it has been less than an hour, and you'd have to
> be
> >> Number 5 from
> >> >Short Circuit to have read all of the content already.
> >> >
> >> >> Would the easiest thing to do be revert back to
> Windows
> >> >> 2000 when this all worked correctly?
> >> >
> >> >No, that's silly. Windows XP is not to blame; you
> have a
> >> configuration
> >> >issue, that's all. If you tell us everything you tried
> >> regarding 328306,
> >> >you will leave the remaining potential options.
> >> >
> >> >--
> >> >http://www.aspfaq.com/
> >> >(Reverse address to reply.)
> >> >
> >> >
> >> >.
> >> >
> >
> >
> >.
> >

ODBC connection Failure

We have group added in SQL Server, this group had a 5 AD accounts. We grante
d
access to the SQL Server to that group.
Two people able to successfully created ODBC connection from work station A.
Other three was not able to create ODBC connection fron any workstation. It
is working for all other people from any workstation, only these three peopl
e
had a problem from any workstation:
The error meaggage in SQL Server Error Log:
Message
The login packet used to open the connection is structurally invalid; the
connection has been closed. Please contact the vendor of the client library.
[CLIENT: 192.168.149.4]
Message
Error: 17832, Severity: 20, State: 8.
any help will be appreciated.THis is SQL Server 2005 SP1.
"Sri" wrote:

> We have group added in SQL Server, this group had a 5 AD accounts. We gran
ted
> access to the SQL Server to that group.
> Two people able to successfully created ODBC connection from work station
A.
> Other three was not able to create ODBC connection fron any workstation. I
t
> is working for all other people from any workstation, only these three peo
ple
> had a problem from any workstation:
> The error meaggage in SQL Server Error Log:
> Message
> The login packet used to open the connection is structurally invalid; the
> connection has been closed. Please contact the vendor of the client librar
y.
> [CLIENT: 192.168.149.4]
> Message
> Error: 17832, Severity: 20, State: 8.
> any help will be appreciated.|||It looks more likely related to PC and not the people in particular.
Did you check MDAC on the machines? You can use component checker to
verity the MDAC versions and installations:
You can download the tool from:
http://msdn2.microsoft.com/en-us/data/aa937730.aspx
Have you looked for other configuration, service pack differences for
the PCs?
-Sue
On Mon, 12 Mar 2007 10:51:33 -0700, Sri
<Sri@.discussions.microsoft.com> wrote:

>We have group added in SQL Server, this group had a 5 AD accounts. We grant
ed
>access to the SQL Server to that group.
>Two people able to successfully created ODBC connection from work station A
.
>Other three was not able to create ODBC connection fron any workstation. It
>is working for all other people from any workstation, only these three peop
le
>had a problem from any workstation:
>The error meaggage in SQL Server Error Log:
>Message
>The login packet used to open the connection is structurally invalid; the
>connection has been closed. Please contact the vendor of the client library
.
>[CLIENT: 192.168.149.4]
>Message
>Error: 17832, Severity: 20, State: 8.
>any help will be appreciated.

ODBC Connection Failure

Hi,
I'm trying to create a ODBC connection to SQL server 2000 using SQL server a
uthentication. I have login id "lucky9797" and password "tool" but I'm keep
getting the following error message:
Connection Failed:
SQLState:'28000'
SQL Server Error: 18456
[Microsoft][ODBC SQL Server Driver][SQL Server]Login Failed for
user "lucky9797"
Could someone please tell me why am I getting this error message? Thanks.
Message posted via http://www.droptable.com1) It might be that the collation sequence indicated at installation time is
case insensitive. Try typing "TOOL" instead of "tool"
"syed rahman via droptable.com" <forum@.droptable.com> wrote in message
news:0e43caa46e9040489d8c88e56a57a606@.SQ
droptable.com...
> Hi,
> I'm trying to create a ODBC connection to SQL server 2000 using SQL server
authentication. I have login id "lucky9797" and password "tool" but I'm keep
getting the following error message:
> Connection Failed:
> SQLState:'28000'
> SQL Server Error: 18456
> [Microsoft][ODBC SQL Server Driver][SQL Server]Login Failed for

user "lucky9797"
> Could someone please tell me why am I getting this error message? Thanks.
> --
> Message posted via http://www.droptable.comsql

ODBC Connect Failure for SQL 2005

The ado connect string for SQL 2K is: strConnect = "driver={SQL
Server};server=" & ServerName & ";database= "yada yada yada".
What do I need to change to connect to SQL 2005 with the SQL Native Client?
Thanks in advance
Steve House
olorin@.tampabay.rr.comBTW, Currently, I am using VB6 to code, though I plan to use VB 2005 and
ASP.Net 2.0
"Steve House" <olorin@.tampabay.rr.com> wrote in message
news:Oze9v5UpFHA.3516@.TK2MSFTNGP15.phx.gbl...
> The ado connect string for SQL 2K is: strConnect = "driver={SQL
> Server};server=" & ServerName & ";database= "yada yada yada".
> What do I need to change to connect to SQL 2005 with the SQL Native
> Client?
> Thanks in advance
> Steve House
> olorin@.tampabay.rr.com
>|||Hi
You should be using the OLEDB for ASP by now too.
sConn = "Provider='SQLOLEDB';Data Source='MySqlServer';Initial
Catalog='TempDB';Integrated Security='SSPI';"
{sqlserver} is the ODBC driver.
SQLOLEDB will work for SQL Server 2000 and 2005.
SQL CLI:
sConn = "Provider='SQLNCLI';Data Source='MySqlServer';Initial
Catalog='TempDB';Integrated Security='SSPI';"
SQL Server 2005 questions to
http://communities.microsoft.com/ne...lcid=us

Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Steve House" <olorin@.tampabay.rr.com> wrote in message
news:O86CaAVpFHA.1088@.TK2MSFTNGP14.phx.gbl...
> BTW, Currently, I am using VB6 to code, though I plan to use VB 2005 and
> ASP.Net 2.0
> "Steve House" <olorin@.tampabay.rr.com> wrote in message
> news:Oze9v5UpFHA.3516@.TK2MSFTNGP15.phx.gbl...
>|||Hello,
For questions of SQL server 2005, please post at the following newsgroup:
Welcome to the Microsoft SQL Server 2005 Community Technology (CTP)
Newsgroups
<http://communities.microsoft.com/ne...sqlserver2005&s
lcid=us>
Thanks for cooperation.
Sophie Guo
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
========================================
=============
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.

ODBC Connect Failure for SQL 2005

The ado connect string for SQL 2K is: strConnect = "driver={SQL
Server};server=" & ServerName & ";database= "yada yada yada".
What do I need to change to connect to SQL 2005 with the SQL Native Client?
Thanks in advance
Steve House
olorin@.tampabay.rr.com
BTW, Currently, I am using VB6 to code, though I plan to use VB 2005 and
ASP.Net 2.0
"Steve House" <olorin@.tampabay.rr.com> wrote in message
news:Oze9v5UpFHA.3516@.TK2MSFTNGP15.phx.gbl...
> The ado connect string for SQL 2K is: strConnect = "driver={SQL
> Server};server=" & ServerName & ";database= "yada yada yada".
> What do I need to change to connect to SQL 2005 with the SQL Native
> Client?
> Thanks in advance
> Steve House
> olorin@.tampabay.rr.com
>
|||Hi
You should be using the OLEDB for ASP by now too.
sConn = "Provider='SQLOLEDB';Data Source='MySqlServer';Initial
Catalog='TempDB';Integrated Security='SSPI';"
{sqlserver} is the ODBC driver.
SQLOLEDB will work for SQL Server 2000 and 2005.
SQL CLI:
sConn = "Provider='SQLNCLI';Data Source='MySqlServer';Initial
Catalog='TempDB';Integrated Security='SSPI';"
SQL Server 2005 questions to
http://communities.microsoft.com/new...r2005&slcid=us
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Steve House" <olorin@.tampabay.rr.com> wrote in message
news:O86CaAVpFHA.1088@.TK2MSFTNGP14.phx.gbl...
> BTW, Currently, I am using VB6 to code, though I plan to use VB 2005 and
> ASP.Net 2.0
> "Steve House" <olorin@.tampabay.rr.com> wrote in message
> news:Oze9v5UpFHA.3516@.TK2MSFTNGP15.phx.gbl...
>
|||Hello,
For questions of SQL server 2005, please post at the following newsgroup:
Welcome to the Microsoft SQL Server 2005 Community Technology (CTP)
Newsgroups
<http://communities.microsoft.com/new...qlserver2005&s
lcid=us>
Thanks for cooperation.
Sophie Guo
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
================================================== ===
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.

ODBC communication link failure to SQL server

Okay-- if anyone can solve this they are truly the SQL genius! We are getting this error when we run a VB program that we use to access an SQL database on a server across our network on a workstation. In fact we get this same error when we even run the program on the server where the SQL database is running or on any of our workstations. Here is the error message:

08501:[Micorsoft][odbc sql server driver] communications link failure

Now the odd thing is that many other functions in the workstation application work fine and retrieve data from SQL but certain data requests by the workstation application fail with the above error message and we get this message consistently. Even though it appears that different workstations running the identical Vb application will get this error consistently but in different locations when running the application. We were running SQL 6.5 on an old server, with the workstation application for literally years without any problems. We also decided to upgrade to a new server, installed server 2000 operating system and the latest version of SQl -- moved all the databases pointed the workstations odbc at this new server and get exactly the same error in the same location in the workstation applications. The programmer that wrote the application and designed the database in SQL can't find the problem and a number of other computer "experts" also could not find the error. We did add a new linksys DSL router/firewall but everything kept working after this installation for several weeks so I don't know if this is the problem on the network. THe programmer also noted that he had problems using terminal services on our network to connect to his office computer and decided that there must be some network issues that are causing the ODBC communicaitions to fail and also terminal services to fail-- or of course they may be unrelated. Has anyone ever seen this ODBC communication error in their travels through SQL implementations? Any help will be greatly appreciated. If we can't fix this we will have to abandon a software application that has been used for over five years and just too complex to rewrite.

Jeff KilpatrickWell, this challenge is not really for a "true DBA", simply because it's related to ODBC driver for SQL Server. Link failure may be caused by several things, including improper closing of resultsets without notifying the server that no more records are needed. The definition ofthe error is:

The communication link between the driver and the data source to which the driver was connected failed before the function completed processing.

And that's what you need to investigate. The reason why it worked with 6.5 may be as simple as the version of the driver. So all the seeming mysteries are probably lying right in there.|||Not playing around with Windows XP SP2, are you?

Anyway, It sounds as though there is an ODBC DSN set up on each of these machines. Go through the configuration of this DSN on one of the affected machines, and see if the test connection button comes back successfully. If it is successful, then you may be looking at a client (i.e. VB Application) problem.

If the test is successful, have the programmer assemble all of his connection strings. If any of them specify PROVIDER as one of the attributes, then you may have your suspect. An ODBC DSN specifies PROVIDER and DATA SOURCE for most connection strings it is used in. Most often, it also specifies DATABASE. I have not experimented with it so much that I know if a connection string can override the DSN, or not, but it is worth a check. For this line of questioning, it would help if you could identify what functions seem to be erroring out. If it is random on each machine, and each attempt, then this will be a pain to figure out.

Another place to check is to make sure you have at least MDAC 2.7 on all of the machines. If you have applied SQL SP3 to the SQL box, then that box at least should have MDAC 2.7 sp1, I think. Microsoft has an MDAC version checker available on their website.

Hope this helps.|||We recently moved from an older (SQL 7 I think) server to SQL2000. Our VB application was using a DNS pointer to point to the SQL server.

This no longer worked once we moved the data to the SQL2000 server. As the poster above mentioned, I ran across a suggestion to run the MDAC patch. There is actually a newer version out now MDAC 2.8. I first ran this on my desktop and then we had to push it out and install it on all the clients which needed to connect to the new server.

Once we did that, we were able to connect to the SQL 2000 server without any problems using the DNS pointer.

A note, with ODBC, the pointer will not show up on your server list, you have to just type it in manually.

odbc communication link failure

Hello,

I have a problem in ODBC that when I open a call logging program, it display "08S01 communication link failure. However, the connection between the driver and data source (in Sydney) is ping ok and data source test successful.

My PC os : window xp professional sp2

ODBC drvier version : 2000.85.1117.00

Can anyone help me to solve the problem ?

Thanks

Rex Leung

Rex,

Could share out the exact error message from your odbc driver when connect fails? Also, is your server name instance and default instance. Is it listened on TCP or NP. can you connect to the server from the same machine. What exactly the connection string you were using for the local odbc connection?

Thanks,

Occasional Authentication Failure

This is an interesting problem. I've never seen this in 5+ years of SQL Server work.
I just started a new job and the folks tell me this happens once a month or so.
We use Trusted Connections for the bulk of work. For some reason one of the multiple SQL Servers we run will just stop recognizing trusted connections. Out of the blue you will just start getting the "Cannot associate user (null) with a trusted connecti
on". The server will log an error indicating it can't find the Domain Controller. The strange thing is only 1 of our SQL Server boxes are affected. There are at least 3 other machines that don't have this issue.
Reboot the server and it's fixed. But, obviously we don't like bouncing production servers. These are running on Server 2003.
I was curious if anyone had seen this before.
Well usually when it says Null as the user , it is a problem with Windows
Authentication itself, not a SQL issue
Check this article :
How to troubleshoot connectivity issues in SQL Server 2000
http://support.microsoft.com/default...b;en-us;827422
HTH
Dylan
"Shawn Brock" <Shawn Brock@.discussions.microsoft.com> wrote in message
news:B62E0490-D630-4378-A3B9-FE36378221CE@.microsoft.com...
> This is an interesting problem. I've never seen this in 5+ years of SQL
Server work.
> I just started a new job and the folks tell me this happens once a month
or so.
> We use Trusted Connections for the bulk of work. For some reason one of
the multiple SQL Servers we run will just stop recognizing trusted
connections. Out of the blue you will just start getting the "Cannot
associate user (null) with a trusted connection". The server will log an
error indicating it can't find the Domain Controller. The strange thing is
only 1 of our SQL Server boxes are affected. There are at least 3 other
machines that don't have this issue.
> Reboot the server and it's fixed. But, obviously we don't like bouncing
production servers. These are running on Server 2003.
> I was curious if anyone had seen this before.

Occasional Authentication Failure

This is an interesting problem. I've never seen this in 5+ years of SQL Ser
ver work.
I just started a new job and the folks tell me this happens once a month or
so.
We use Trusted Connections for the bulk of work. For some reason one of the
multiple SQL Servers we run will just stop recognizing trusted connections.
Out of the blue you will just start getting the "Cannot associate user (nu
ll) with a trusted connecti
on". The server will log an error indicating it can't find the Domain Contr
oller. The strange thing is only 1 of our SQL Server boxes are affected. T
here are at least 3 other machines that don't have this issue.
Reboot the server and it's fixed. But, obviously we don't like bouncing pro
duction servers. These are running on Server 2003.
I was curious if anyone had seen this before.Well usually when it says Null as the user , it is a problem with Windows
Authentication itself, not a SQL issue
Check this article :
How to troubleshoot connectivity issues in SQL Server 2000
http://support.microsoft.com/defaul...kb;en-us;827422
HTH
Dylan
"Shawn Brock" <Shawn Brock@.discussions.microsoft.com> wrote in message
news:B62E0490-D630-4378-A3B9-FE36378221CE@.microsoft.com...
> This is an interesting problem. I've never seen this in 5+ years of SQL
Server work.
> I just started a new job and the folks tell me this happens once a month
or so.
> We use Trusted Connections for the bulk of work. For some reason one of
the multiple SQL Servers we run will just stop recognizing trusted
connections. Out of the blue you will just start getting the "Cannot
associate user (null) with a trusted connection". The server will log an
error indicating it can't find the Domain Controller. The strange thing is
only 1 of our SQL Server boxes are affected. There are at least 3 other
machines that don't have this issue.
> Reboot the server and it's fixed. But, obviously we don't like bouncing
production servers. These are running on Server 2003.
> I was curious if anyone had seen this before.