ODBC Error

I'm getting an error message I've never seen before when I installed my
application on a client's machine.
I've got seven machines at this location that all work fine, when I install
on a new machine, I can connect through ODBC Administrator; but, when I try
to connect through the program I get this error message:
[ODBC SQL Server Driver][TCP/IP Sockets]SSL Security Error
[ODBC SQL Server Driver][TCP/IP
Sockets]ConnectionOpen(SECDoClientHandsh
ake()).
I've looked on KB and have not been able to find anything specific on this
problem.
Any ideas?
Thanks in advance.This might be the same issue reported in the KB article at the link
http://support.microsoft.com/defaul...b;en-us;Q322144
Regards,
--
This posting is provided "AS IS" with no warranties, and confers no rights.
Regards,
Uwa Agbonile[MSFT]
"Dennis Powell" <dennis.powell@.monroe.XXXXXXXXX> wrote in message
news:OA6%23L0fYFHA.2128@.TK2MSFTNGP15.phx.gbl...
> I'm getting an error message I've never seen before when I installed my
> application on a client's machine.
> I've got seven machines at this location that all work fine, when I
install
> on a new machine, I can connect through ODBC Administrator; but, when I
try
> to connect through the program I get this error message:
> [ODBC SQL Server Driver][TCP/IP Sockets]SSL Security Error
> [ODBC SQL Server Driver][TCP/IP
> Sockets]ConnectionOpen(SECDoClientHandsh
ake()).
> I've looked on KB and have not been able to find anything specific on
this
> problem.
> Any ideas?
> Thanks in advance.
>

ODBC Connections

I have a network with 6 machines sitting on it.
All PC`s are configued in the same way. 5 of the machines connect to a SQL
server via ODBC with no problems.
The sixth PC however does not connect to the server giving the following :-
Connection Failed
SQL State '01000;
SQL Server Error: 11001
TCP/IP Sockets Connection Open
GetHosting Name
General network error.
I`m connecting via aTCP/IP on port 1433.
Does anyone have any idea why I am encountering these problems ?did you try 'telnet YourDBServerIP 1433'?
"Simon" wrote:

> I have a network with 6 machines sitting on it.
> All PC`s are configued in the same way. 5 of the machines connect to a SQL
> server via ODBC with no problems.
> The sixth PC however does not connect to the server giving the following :
-
> Connection Failed
> SQL State '01000;
> SQL Server Error: 11001
> TCP/IP Sockets Connection Open
> GetHosting Name
> General network error.
>
> I`m connecting via aTCP/IP on port 1433.
>
> Does anyone have any idea why I am encountering these problems ?
>|||I`m probably being a sponge but I don`t seem to get anything using that
command from any of the PC`s.
"AAO" wrote:
[vbcol=seagreen]
> did you try 'telnet YourDBServerIP 1433'?
> "Simon" wrote:
>|||You should get an error if SQL Server isn't listening on
1433. Or you should blank screen with the title of the
window changing to Telnet <Your Server> if you have
successfully established a telnet connection on that port.
It just sounds like you are connecting.
-Sue
On Fri, 12 May 2006 07:22:02 -0700, Simon
<Simon@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>I`m probably being a sponge but I don`t seem to get anything using that
>command from any of the PC`s.
>"AAO" wrote:
>|||Firewall?
/Henning
"Simon" <Simon@.discussions.microsoft.com> skrev i meddelandet
news:1359348E-85DA-43DD-AA79-313F4F92DF94@.microsoft.com...[vbcol=seagreen]
> I`m probably being a sponge but I don`t seem to get anything using that
> command from any of the PC`s.
> "AAO" wrote:
>
SQL[vbcol=seagreen]
following :-[vbcol=seagreen]|||The firewall setup is the same accross all the machines so I don`t think is
causing the problem.
"Henning" wrote:

> Firewall?
> /Henning
> "Simon" <Simon@.discussions.microsoft.com> skrev i meddelandet
> news:1359348E-85DA-43DD-AA79-313F4F92DF94@.microsoft.com...
> SQL
> following :-
>
>

ODBC Connection to SQL

I have a network with 6 machines sitting on it.
All PC`s are configued in the same way. 5 of the machines connect to a SQL
server via ODBC with no problems.
The sixth PC however does not connect to the server giving the following :-
Connection Failed
SQL State '01000;
SQL Server Error: 11001
TCP/IP Sockets Connection Open
GetHosting Name
General network error.
I`m connecting via aTCP/IP on port 1433.
Does anyone have any idea why I am encountering these problems ?Is there error actually GetHostByName?
On the PC that can't connect, try pinging the server by
server name and try pinging the server by IP and see if
there are any issues with pinging by name. If there are then
check that client for network issues as it's having problems
resolving the server name.
Otherwise, the issue you are seeing is often due to MDAC
issues. Try updating or reinstalling on that PC. You may
also
want to check the MDAC installation using component
checker. You can download component checker and MDAC
versions from:
http://msdn.microsoft.com/data/mdac...ds/default.aspx
-Sue
On Fri, 12 May 2006 01:17:02 -0700, Simon
<Simon@.discussions.microsoft.com> wrote:

>I have a network with 6 machines sitting on it.
>All PC`s are configued in the same way. 5 of the machines connect to a SQL
>server via ODBC with no problems.
>The sixth PC however does not connect to the server giving the following :-
>Connection Failed
>SQL State '01000;
>SQL Server Error: 11001
>TCP/IP Sockets Connection Open
>GetHosting Name
>General network error.
>
>I`m connecting via aTCP/IP on port 1433.
>
>Does anyone have any idea why I am encountering these problems ?
>

ODBC Connection Hangs after 15 minutes of non-use

I have several workstations that login to a WIN_2000 Server and Connect just
fine to a SQL-2000 Server (different machines) over a dedicated VPN....
They have a x.x.2.1 addressing scheme and we have x.x.1.1 addressing scheme.
Everything works beautifully for a while.
My application runs a MailMerge with Word and Access 9.0 with tables linked
to the SQL Server 2000 server.... The code uses a pre set up ODBC
connection (SQL Server) that connects just fine right after start up...
Code works and ODBC connection works.... However, after 15-45 minutes the
ODBC connection stops working... This can be verified by testing the ODBC
applet which hangs
I have 50 local users who have no issues with the setup - only these few
remote users.
I have set the server autoconfigure to never disconnect. (I can still
browse the servers)..
Any clues as to why the ODBC connection would become disabled after a short
period of time - requiring a reboot to work again?To me this sounds like an issue with the VPN not ODBC and SQL Server.
Mike O.
"Bob" <rrowe68@.hotmail.com> wrote in message
news:%23jMJEVX1DHA.536@.tk2msftngp13.phx.gbl...

quote:

---

> I have several workstations that login to a WIN_2000 Server and Connect

---

just

quote:

---

> fine to a SQL-2000 Server (different machines) over a dedicated VPN....
> They have a x.x.2.1 addressing scheme and we have x.x.1.1 addressing

---

scheme.

quote:

---

> Everything works beautifully for a while.
> My application runs a MailMerge with Word and Access 9.0 with tables

---

linked

quote:

---

> to the SQL Server 2000 server.... The code uses a pre set up ODBC
> connection (SQL Server) that connects just fine right after start up...
> Code works and ODBC connection works.... However, after 15-45 minutes

---

the

quote:

---

> ODBC connection stops working... This can be verified by testing the ODBC
> applet which hangs
> I have 50 local users who have no issues with the setup - only these few
> remote users.
> I have set the server autoconfigure to never disconnect. (I can still
> browse the servers)..
> Any clues as to why the ODBC connection would become disabled after a

---

short

quote:

---

> period of time - requiring a reboot to work again?
>
>

---

ODBC Connect Problem w/2005

I have attempted to establish ODBC connections w/ the Microsoft SQL
Native Client Version 09.00.1399 (from 2 different machines) and get the
following error:
Connection Failed:
SQLState: '08001'
SQL Server Error: 1326
[Microsoft][SQL Native Client]Named Pipes Provider: Could not open a
connection to SQL Server [1326]
Connectio Failed:
SQLState: 'HYT00'
SQL Server Error: 0
[Microsoft][SQL Native Client]Login Timeout Expired
Connection Failed:
SQLState: '08001'
SQL Server Error: 1326
Microsoft][SQL Native Client]An error has occurred while establishing a
connection to the server. When connecting to SQL Server 2005, this
failure
may be caused by the fact that under the default setting SQL Server does
not allow remote connections.
* Win2003 Server 64bit; SQL Server 2005 x64
* SQL Server authentication
* Allow Remote connections is checked on the SQL Server
* The clients show driver ver 09.00.1399 in the ODBC Sources, the
Server's ODBC Sources shows ver 09.00.1399.00, although the SQL Server
2005 shows 09.00.1399.06.
thanks!
GregC
Hi,
Following things you need to check:
1. If SQL Browser is enabled and started.
2. If firewall is on, you need to put sql server and sql browser in
exception list. Regarding this, you may refer to following two method:
#1. Get IP and port of target SQL Server, suppose it is 123.123.123.123 and
1433 ->
Test connect using osql and target of Stcp:123.123.123.123,1433, like
so:
osql -Stcp:123.123.123.123,1433 -E
#2. Try telnet to port as well, if this fails it is firewall:
telnet 123.123.123.123 1433
Best regards,
Vincent Xu
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 this issue.
================================================== ====
This posting is provided "AS IS" with no warranties,and confers no rights.
================================================== ====
--[vbcol=seagreen]
19:52:44 CST)[vbcol=seagreen]
TK2MSFTNGXA03.phx.gbl!TK2MSFTNGP08.phx.gbl!newsfee d00.sul.t-online.de!t-onli
ne.de!border2.nntp.dca.giganews.com!nntp.giganews. com!cyclone.austin.rr.com!
news.rr.com!tornado.texas.rr.com.POSTED!53ab2750!n ot-for-mail[vbcol=seagreen]

ODBC Connect Problem w/2005

I have attempted to establish ODBC connections w/ the Microsoft SQL
Native Client Version 09.00.1399 (from 2 different machines) and get the
following error:
Connection Failed:
SQLState: '08001'
SQL Server Error: 1326
[Microsoft][SQL Native Client]Named Pipes Provider: Could not open a
connection to SQL Server [1326]
Connectio Failed:
SQLState: 'HYT00'
SQL Server Error: 0
[Microsoft][SQL Native Client]Login Timeout Expired
Connection Failed:
SQLState: '08001'
SQL Server Error: 1326
Microsoft][SQL Native Client]An error has occurred while establishing a
connection to the server. When connecting to SQL Server 2005, this
failure
may be caused by the fact that under the default setting SQL Server does
not allow remote connections.
* Win2003 Server 64bit; SQL Server 2005 x64
* SQL Server authentication
* Allow Remote connections is checked on the SQL Server
* The clients show driver ver 09.00.1399 in the ODBC Sources, the
Server's ODBC Sources shows ver 09.00.1399.00, although the SQL Server
2005 shows 09.00.1399.06.
thanks!
GregCHi,
Following things you need to check:
1. If SQL Browser is enabled and started.
2. If firewall is on, you need to put sql server and sql browser in
exception list. Regarding this, you may refer to following two method:
#1. Get IP and port of target SQL Server, suppose it is 123.123.123.123 and
1433 ->
Test connect using osql and target of Stcp:123.123.123.123,1433, like
so:
osql -Stcp:123.123.123.123,1433 -E
#2. Try telnet to port as well, if this fails it is firewall:
telnet 123.123.123.123 1433
Best regards,
Vincent Xu
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 this issue.
========================================
==============
This posting is provided "AS IS" with no warranties,and confers no rights.
========================================
==============
--[vbcol=seagreen]
19:52:44 CST)[vbcol=seagreen]
TK2MSFTNGXA03.phx.gbl!TK2MSFTNGP08.phx.gbl!newsfeed00.sul.t-online.de!t-onli
ne.de!border2.nntp.dca.giganews.com!nntp.giganews.com!cyclone.austin.rr.com!
news.rr.com!tornado.texas.rr.com.POSTED!53ab2750!not-for-mail[vbcol=seagreen]sql

odbc call to sql 7 fails

Have 3 XP machines running Office XP Pro. The odbc file
dsn sits in same file as the mdb on a server (on purpose
so it gets backed up regularly). The odbc file connects
to an SQL 7 database on an NT4 machine. All sql driver
versions are 2000.81.9042.00 The authentication is an
sql account - not windows.
Two people can open and connect fine. One gets a login
failure.
If we place the 'failed' user into the domain
administrator account and he logs in at another machine,
he connects fine. If he tries to login from his machine,
still fails.
Two questions:
Why does it fail in either scenario at his machine?
Using sql authentication, how can I let him connect
WITHOUT being a member of the admin group?
Many thanks for any help!
(P.S. Same account works fine through an asp page on the
web without the user having to be in the administrator's
group.)At some level, Named Pipes connections still do make NT calls to see if you
have Windows rights on the other machine.
My suggestion is to either share a network drive or find a network drive
that you don't mind this person connecting to. Make sure they can connect
to that shared drive. Then see how that affects the SQL connection attempt.
Unshare the drive. See what happens to the SQL connection attempt.
Suggestion #2 is to go into SQL Enterprise manager and add a Windows NT
authentication entry for his user account. Maybe that will help.
****************************************
***************************
Andy S.
MCSE NT/2000, MCDBA SQL 7/2000
andymcdba1@.NOMORESPAM.yahoo.com
Please remove NOMORESPAM before replying.
Always keep your antivirus and Microsoft software
up to date with the latest definitions and product updates.
Be suspicious of every email attachment, I will never send
or post anything other than the text of a http:// link nor
post the link directly to a file for downloading.
This posting is provided "as is" with no warranties
and confers no rights.
****************************************
***************************
"Janet" <janetb@.mtn.ncahec.org> wrote in message
news:27f501c3e104$cfd509b0$a501280a@.phx.gbl...

quote:

---

> Have 3 XP machines running Office XP Pro. The odbc file
> dsn sits in same file as the mdb on a server (on purpose
> so it gets backed up regularly). The odbc file connects
> to an SQL 7 database on an NT4 machine. All sql driver
> versions are 2000.81.9042.00 The authentication is an
> sql account - not windows.
> Two people can open and connect fine. One gets a login
> failure.
> If we place the 'failed' user into the domain
> administrator account and he logs in at another machine,
> he connects fine. If he tries to login from his machine,
> still fails.
> Two questions:
> Why does it fail in either scenario at his machine?
> Using sql authentication, how can I let him connect
> WITHOUT being a member of the admin group?
> Many thanks for any help!
> (P.S. Same account works fine through an asp page on the
> web without the user having to be in the administrator's
> group.)
>

---

|||Andy,
Many thanks for the reply.
I know this isn't the popular thinking, but I had set up
sql to take sql authentication only for security
purposes. That way, if someone compromises the network
he/she couldn't by default get to sql data and;
conversly, if someone compromises sql he/she couldn't by
default get to network files.
But, the only way I could get this guy connected was to
use Windows Authentication on a group, put him in it, and
then everything worked fine. I think it's because our pc
machines are XP and the server is still NT/sql7. (The
servers will be updated to 2003 soon with Active
Directory, so maybe this will "all go away".) So, by
default and no matter what you specify, authentication is
by Windows, not sql.
Again, thanks for your reply. If I continue to have
problems after the upgrade, I will be sure to try your
suggestion.
Janet

quote:

---

>--Original Message--
>At some level, Named Pipes connections still do make NT

---

calls to see if you

quote:

---

>have Windows rights on the other machine.
>My suggestion is to either share a network drive or find

---

a network drive

quote:

---

>that you don't mind this person connecting to. Make

---

sure they can connect

quote:

---

>to that shared drive. Then see how that affects the SQL

---

connection attempt.

quote:

---

>Unshare the drive. See what happens to the SQL

---

connection attempt.

quote:

---

>Suggestion #2 is to go into SQL Enterprise manager and

---

add a Windows NT

quote:

---

>authentication entry for his user account. Maybe that

---

will help.

quote:

---

>--
> ****************************************
*****************

---

**********

quote:

---

>Andy S.
>MCSE NT/2000, MCDBA SQL 7/2000
>andymcdba1@.NOMORESPAM.yahoo.com
>Please remove NOMORESPAM before replying.
>Always keep your antivirus and Microsoft software
>up to date with the latest definitions and product

---

updates.

quote:

---

>Be suspicious of every email attachment, I will never

---

send

quote:

---

>or post anything other than the text of a http:// link

---

nor

quote:

---

>post the link directly to a file for downloading.
>This posting is provided "as is" with no warranties
>and confers no rights.
> ****************************************
*****************

---

**********

quote:

---

>"Janet" <janetb@.mtn.ncahec.org> wrote in message
>news:27f501c3e104$cfd509b0$a501280a@.phx.gbl...
file[QUOTE]
purpose[QUOTE]
connects[QUOTE]
machine,[QUOTE]
machine,[QUOTE]
the[QUOTE]
administrator's[QUOTE]
>
>.
>

---

|||Unfortunately, SQL runs in mixed mode when it SQL security is used. If
someone compromises the administrative NT account, they'll get into Windows
and SQL. In that sense Windows NT authentication is secure.
To really secure your SQL server from a Windows perspective, always password
the SA account, consider restricting rights on xp_cmdshell (that procedure
in the master database grants DOS level access to administrators) and try
putting a proxy account for non-admin users for SQL Server agent.
The authentication models still get frustrating for me. I can't stand the
fact that when you restore a database to a separate server, the logins and
users can get out of sync requiring the procedure sp_change_users_login
auto_fix, user_id. (try restoring a database on a separate server), then
add a login with the user name of a user in the database. That is always a
minor annoyance.
****************************************
***************************
Andy S.
MCSE NT/2000, MCDBA SQL 7/2000
andymcdba1@.NOMORESPAM.yahoo.com
Please remove NOMORESPAM before replying.
Always keep your antivirus and Microsoft software
up to date with the latest definitions and product updates.
Be suspicious of every email attachment, I will never send
or post anything other than the text of a http:// link nor
post the link directly to a file for downloading.
This posting is provided "as is" with no warranties
and confers no rights.
****************************************
***************************
"Janet" <janetb@.mtn.ncahec.org> wrote in message
news:34f501c3e1d8$33367ba0$a601280a@.phx.gbl...[QUOTE]
> Andy,
> Many thanks for the reply.
> I know this isn't the popular thinking, but I had set up
> sql to take sql authentication only for security
> purposes. That way, if someone compromises the network
> he/she couldn't by default get to sql data and;
> conversly, if someone compromises sql he/she couldn't by
> default get to network files.
> But, the only way I could get this guy connected was to
> use Windows Authentication on a group, put him in it, and
> then everything worked fine. I think it's because our pc
> machines are XP and the server is still NT/sql7. (The
> servers will be updated to 2003 soon with Active
> Directory, so maybe this will "all go away".) So, by
> default and no matter what you specify, authentication is
> by Windows, not sql.
> Again, thanks for your reply. If I continue to have
> problems after the upgrade, I will be sure to try your
> suggestion.
> Janet
>
> calls to see if you
> a network drive
> sure they can connect
> connection attempt.
> connection attempt.
> add a Windows NT
> will help.
> **********
> updates.
> send
> nor
> **********
> file
> purpose
> connects
> machine,
> machine,
> the
> administrator's

ODBC - System DSN window is blank

We've run into a few XP machines in our organization that have some interesting quirk going on. We have several ODBC connections configured on the machines. However, when you go to ODBC connections, then click on the System DSN tab, it's empty. If we try to manually create a "missing" odbc, it says it already exists, do you want to overwrite, etc. We say yes, but it still doesn't appear. The main program being used has a dropdown box at the login screen that shows the various ODBC names to choose from. The ones from the System DSN tab (which is blank anyway) are not listed. However, if you manually type in the name of the ODBC that is supposedly configured but doesn't show up, it works. So, it sees the ODBC, but it won't display it to the human eye in the settings or drop down lists. What's up with that? We've tried reinstalling MDAC, java, windows updates, etc, etc. Only some machines are affected. I am unable to tell you what's been done to all these machines. The users are all set as admins on their machines. They all run similar software, etc. The only thing that happened around the time we started noticing this is that we added a couple new ODBCs and changed the settings in an existing one. We sent an exe to all users in the organization that auto configures these ODBC's so we don't have to do it manually. It works awesome, but I don't see how that exe could have caused this problem especially when the problem seems to have only shown up on about 1% of the PCs it was applied to.Found this at: http://www.dbforums.com/t1055278.html

01-01-05, 01:37
wconner50
Registered User

Join Date: Jan 2005
Posts: 2
System DSN not in ODBC Manager
You should export the registry entries for the ODBC.INI Data source and DataSet Names. Then edit the .reg exported file and see if there are any odd lines of text. I found a corrupt entry in the ODBC Data Source registry entry, all the missing system DSN's were right after the corrupt line. Delete corrupt line and deleted ODBC Data Source registry entry, then imported .reg file.

Problem was resolved.

Obscure linked server error

Hello,

I've got 2 SQL servers in a test environment - one is 2000 and the other is MSDE and they are seperate machines. I have added the MSDE server as a linked server to my 2000 box by issuing the following command:

EXEC sp_addlinkedserver '192.168.1.108', N'SQL Server'

I can query the database using an openquery in a select statement like so:

select * from openquery([192.168.1.108], 'select * from remote_test.dbo.products')

but when I try a direct query like the following:

select * from [192.168.1.108].remote_test.dbo.products

I get the following error:

An error occurred while executing batch. Error message is: Processing of results from SQL Server failed because of an invalid multipart name "192.168.1.108.remote_test.dbo.products", the current limit of "4" is insufficient.

I can't seem to figure out anything about this error. Anyone have any ideas?

Thanks,

Jeff Balcerzak

What about choosing another name than the IP ;-) ?

Jens K. Suessmeyer.

http://www.sqlserver2005.de
--|||That does work if I specify the server name on my local network. If the production server is not going to be in the local network, would I create an alias to it with the public IP address?|||What about using an entry in the lmhost file to the outside IP?

Jens K. Suessmeyer.

http://www.sqlserver2005.de
|||I actually added an entry in hosts file and created an alias to my public IP to test. I physically moved my test server to a different part of my network so it is not visible to the lan and created a port forward on my router to direct wan traffic on 1433 to the test server. Now when I execute the sp_addlinked server with the server name, it seems to work fine. Thanks for your help.