Hi,
How do I disable in sql server -- ansi quote identifiers in sql server.
ansi nulls, padding, warnings.
I set up an ODBC connection If I turn these off -- doesn't work , It works
it tehy are checked.
Any ideas?
Thanks
Set up what kind of ODBC connection - where did you set this
up? If it's a DSN, you can turn them on in the ODBC
Administrator applet. When you configure the DSN, it's on
the screen after you select the authentication method.
It's generally better to manage the settings you need from
the client side. A client connection settings for these
override the server settings.
If you wanted to change them at the server level, you can
use sp_configure to change the user options. If you change
the settings at the server level, it will only take affect
for new logins.
-Sue
On Mon, 2 Apr 2007 17:33:53 -0400, "mecn"
<mecn2002@.yahoo.com> wrote:
>Hi,
>How do I disable in sql server -- ansi quote identifiers in sql server.
> ansi nulls, padding, warnings.
>I set up an ODBC connection If I turn these off -- doesn't work , It works
>it tehy are checked.
>Any ideas?
>Thanks
>
Showing posts with label connections. Show all posts
Showing posts with label connections. Show all posts
Monday, March 26, 2012
ODBC connections error
Hi,
How do I disable in sql server -- ansi quote identifiers in sql server.
ansi nulls, padding, warnings.
I set up an ODBC connection If I turn these off -- doesn't work , It works
it tehy are checked.
Any ideas?
ThanksSet up what kind of ODBC connection - where did you set this
up? If it's a DSN, you can turn them on in the ODBC
Administrator applet. When you configure the DSN, it's on
the screen after you select the authentication method.
It's generally better to manage the settings you need from
the client side. A client connection settings for these
override the server settings.
If you wanted to change them at the server level, you can
use sp_configure to change the user options. If you change
the settings at the server level, it will only take affect
for new logins.
-Sue
On Mon, 2 Apr 2007 17:33:53 -0400, "mecn"
<mecn2002@.yahoo.com> wrote:
>Hi,
>How do I disable in sql server -- ansi quote identifiers in sql server.
> ansi nulls, padding, warnings.
>I set up an ODBC connection If I turn these off -- doesn't work , It works
>it tehy are checked.
>Any ideas?
>Thanks
>
How do I disable in sql server -- ansi quote identifiers in sql server.
ansi nulls, padding, warnings.
I set up an ODBC connection If I turn these off -- doesn't work , It works
it tehy are checked.
Any ideas?
ThanksSet up what kind of ODBC connection - where did you set this
up? If it's a DSN, you can turn them on in the ODBC
Administrator applet. When you configure the DSN, it's on
the screen after you select the authentication method.
It's generally better to manage the settings you need from
the client side. A client connection settings for these
override the server settings.
If you wanted to change them at the server level, you can
use sp_configure to change the user options. If you change
the settings at the server level, it will only take affect
for new logins.
-Sue
On Mon, 2 Apr 2007 17:33:53 -0400, "mecn"
<mecn2002@.yahoo.com> wrote:
>Hi,
>How do I disable in sql server -- ansi quote identifiers in sql server.
> ansi nulls, padding, warnings.
>I set up an ODBC connection If I turn these off -- doesn't work , It works
>it tehy are checked.
>Any ideas?
>Thanks
>
ODBC connections and SSIS
so im trying to connect to an odbc source and use ado.net to pass some sql queries and then write back into this odbc connection. i am aware that ssis does not have direct capabilities to do this, but i wanted to see if anyone knew of generic help docs/url's that show how to do this? i am new to ssis, and am just trying to get general information.
See Douglas post here:http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=70469&SiteID=1
The code is also in SQL Books Online.|||
to be honest with you, i did see that thread you mention above, probably the only thread with realistic information. I am looking for something specifically in C#.
I am also wondering if there is any way to not have the SQL Command line filled for the ODBC connection source and use ODBC and a combination of ADO.net? Anyone have success with this?
I did search books online for the particualar phrase mentioned in the above thread..not too helpful.
Just wondering if anyone has had success writing C# ado.net to read and write using ODBC as a source?
thanks!
|||If that's what you are after then I would try a dev forum if I were you: http://forums.microsoft.com/MSDN/default.aspx?ForumGroupID=12&SiteID=1
-Jamie
sqlodbc connections
A colleague of mine has a problem;
"Has anyone ever experienced the problem of creating a System ODBC and it doesn't display in the ODBC administrator applet?"
was hoping someone here could help...What is your exact problem?|||the problem was that when created a new odbc connection this was not displayed...i have since discovered a reboot fixed it-i was under the impression that the sql server would have been rebooted first...dont worry about it!
thanks though
"Has anyone ever experienced the problem of creating a System ODBC and it doesn't display in the ODBC administrator applet?"
was hoping someone here could help...What is your exact problem?|||the problem was that when created a new odbc connection this was not displayed...i have since discovered a reboot fixed it-i was under the impression that the sql server would have been rebooted first...dont worry about it!
thanks though
ODBC connections
I have been asked to develop some security software that includes detection
of what ODBC connections to SQL Server databases exist. I think that it is
not useful, at least for security purposes, to determine what ODBC
connections exist for a database. Am I wrong?
One reason it is not useful is that a connection can be created dynamicly
anytime. I know that, since I do it. The person asking for this project is
not familiar with such things but I have already explained this much to him.
I don't know about SQL Server security enough to be sure, but it is my
understanding that it has it's own security that is much more effective than
attempts to prevent access by limiting ODBC connections.
I am not asking what other solutions exist; if I am correct in what I say
here, then I will pursue the other solutions myself and when necessary in
another thread.>I have been asked to develop some security software that includes detection
>of what ODBC connections to SQL Server databases exist. I think that it is
>not useful, at least for security purposes, to determine what ODBC
>connections exist for a database. Am I wrong?
You are correct. The person requesting this may not be familiar with SQL
Server data access architecture and now it relates to security. ODBC is
just one data access API of many. There are also others, such as OLE DB,
SQL Native Client. It does not makes sense to me that one would care, at
least from a security perspective, which API is used to connect to SQL
Server. All APIs can access SQL Server without a pre-configured DSN.
> I don't know about SQL Server security enough to be sure, but it is my
> understanding that it has it's own security that is much more effective
> than attempts to prevent access by limiting ODBC connections.
Absolutely. SQL Server security is the primary place security needs to be
implemented. Logins, database users and object permissions all provide
various levels of security. Given a login with appropriate permissions, one
could write a simple VBScript using Notepad to access and manipulate
database data.
Hope this helps.
Dan Guzman
SQL Server MVP
"Sam Hobbs" <samuel@.social.rr.com_change_social_to_socal> wrote in message
news:%23GT8ACP%23FHA.3340@.TK2MSFTNGP12.phx.gbl...
>I have been asked to develop some security software that includes detection
>of what ODBC connections to SQL Server databases exist. I think that it is
>not useful, at least for security purposes, to determine what ODBC
>connections exist for a database. Am I wrong?
> One reason it is not useful is that a connection can be created dynamicly
> anytime. I know that, since I do it. The person asking for this project is
> not familiar with such things but I have already explained this much to
> him.
> I don't know about SQL Server security enough to be sure, but it is my
> understanding that it has it's own security that is much more effective
> than attempts to prevent access by limiting ODBC connections.
> I am not asking what other solutions exist; if I am correct in what I say
> here, then I will pursue the other solutions myself and when necessary in
> another thread.
>|||Yes, Dan, that definitely helps; thank you.
of what ODBC connections to SQL Server databases exist. I think that it is
not useful, at least for security purposes, to determine what ODBC
connections exist for a database. Am I wrong?
One reason it is not useful is that a connection can be created dynamicly
anytime. I know that, since I do it. The person asking for this project is
not familiar with such things but I have already explained this much to him.
I don't know about SQL Server security enough to be sure, but it is my
understanding that it has it's own security that is much more effective than
attempts to prevent access by limiting ODBC connections.
I am not asking what other solutions exist; if I am correct in what I say
here, then I will pursue the other solutions myself and when necessary in
another thread.>I have been asked to develop some security software that includes detection
>of what ODBC connections to SQL Server databases exist. I think that it is
>not useful, at least for security purposes, to determine what ODBC
>connections exist for a database. Am I wrong?
You are correct. The person requesting this may not be familiar with SQL
Server data access architecture and now it relates to security. ODBC is
just one data access API of many. There are also others, such as OLE DB,
SQL Native Client. It does not makes sense to me that one would care, at
least from a security perspective, which API is used to connect to SQL
Server. All APIs can access SQL Server without a pre-configured DSN.
> I don't know about SQL Server security enough to be sure, but it is my
> understanding that it has it's own security that is much more effective
> than attempts to prevent access by limiting ODBC connections.
Absolutely. SQL Server security is the primary place security needs to be
implemented. Logins, database users and object permissions all provide
various levels of security. Given a login with appropriate permissions, one
could write a simple VBScript using Notepad to access and manipulate
database data.
Hope this helps.
Dan Guzman
SQL Server MVP
"Sam Hobbs" <samuel@.social.rr.com_change_social_to_socal> wrote in message
news:%23GT8ACP%23FHA.3340@.TK2MSFTNGP12.phx.gbl...
>I have been asked to develop some security software that includes detection
>of what ODBC connections to SQL Server databases exist. I think that it is
>not useful, at least for security purposes, to determine what ODBC
>connections exist for a database. Am I wrong?
> One reason it is not useful is that a connection can be created dynamicly
> anytime. I know that, since I do it. The person asking for this project is
> not familiar with such things but I have already explained this much to
> him.
> I don't know about SQL Server security enough to be sure, but it is my
> understanding that it has it's own security that is much more effective
> than attempts to prevent access by limiting ODBC connections.
> I am not asking what other solutions exist; if I am correct in what I say
> here, then I will pursue the other solutions myself and when necessary in
> another thread.
>|||Yes, Dan, that definitely helps; thank you.
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 :-
>
>
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 :-
>
>
Friday, March 23, 2012
ODBC Connection to SQL Server
I am setting up SQL Server ODBC connections on 5 machines
and everything has gone fine until I came to the last
machine.
When I go to choose the server I want to connect to from
the server drop down list, it isn't there. There other
machines listed, but not the one that I want.
The only difference is that this one has 2000 pro, while
all of the others have XP pro. I am assuming that I need
to update something on the 2000 machine, but don't know
what. Can anyone help me with this?
Thanks in advance.You should check the MDAC version, installation on the
machine that's having problems. If the versions are
different between the xp machines and the 2000 machine,
you'd want to upgrade the 2000 machine to the same MDAC
version.
You can download the MDAC component checker
from:
http://msdn.microsoft.com/data/down...ls/default.aspx
-Sue
On Fri, 16 Apr 2004 07:52:32 -0700, "Mark Kovach"
<anonymous@.discussions.microsoft.com> wrote:
>I am setting up SQL Server ODBC connections on 5 machines
>and everything has gone fine until I came to the last
>machine.
>When I go to choose the server I want to connect to from
>the server drop down list, it isn't there. There other
>machines listed, but not the one that I want.
>The only difference is that this one has 2000 pro, while
>all of the others have XP pro. I am assuming that I need
>to update something on the 2000 machine, but don't know
>what. Can anyone help me with this?
>Thanks in advance.|||Thanks. I downloaded MDAC 2.8 and installed it. It
works great now.
Thank you for the help.
>--Original Message--
>You should check the MDAC version, installation on the
>machine that's having problems. If the versions are
>different between the xp machines and the 2000 machine,
>you'd want to upgrade the 2000 machine to the same MDAC
>version.
>You can download the MDAC component checker
>from:
>http://msdn.microsoft.com/data/down...ools/default.as
px
>-Sue
>On Fri, 16 Apr 2004 07:52:32 -0700, "Mark Kovach"
><anonymous@.discussions.microsoft.com> wrote:
>
machines[vbcol=seagreen]
from[vbcol=seagreen]
while[vbcol=seagreen]
need[vbcol=seagreen]
>.
>
and everything has gone fine until I came to the last
machine.
When I go to choose the server I want to connect to from
the server drop down list, it isn't there. There other
machines listed, but not the one that I want.
The only difference is that this one has 2000 pro, while
all of the others have XP pro. I am assuming that I need
to update something on the 2000 machine, but don't know
what. Can anyone help me with this?
Thanks in advance.You should check the MDAC version, installation on the
machine that's having problems. If the versions are
different between the xp machines and the 2000 machine,
you'd want to upgrade the 2000 machine to the same MDAC
version.
You can download the MDAC component checker
from:
http://msdn.microsoft.com/data/down...ls/default.aspx
-Sue
On Fri, 16 Apr 2004 07:52:32 -0700, "Mark Kovach"
<anonymous@.discussions.microsoft.com> wrote:
>I am setting up SQL Server ODBC connections on 5 machines
>and everything has gone fine until I came to the last
>machine.
>When I go to choose the server I want to connect to from
>the server drop down list, it isn't there. There other
>machines listed, but not the one that I want.
>The only difference is that this one has 2000 pro, while
>all of the others have XP pro. I am assuming that I need
>to update something on the 2000 machine, but don't know
>what. Can anyone help me with this?
>Thanks in advance.|||Thanks. I downloaded MDAC 2.8 and installed it. It
works great now.
Thank you for the help.
>--Original Message--
>You should check the MDAC version, installation on the
>machine that's having problems. If the versions are
>different between the xp machines and the 2000 machine,
>you'd want to upgrade the 2000 machine to the same MDAC
>version.
>You can download the MDAC component checker
>from:
>http://msdn.microsoft.com/data/down...ools/default.as
px
>-Sue
>On Fri, 16 Apr 2004 07:52:32 -0700, "Mark Kovach"
><anonymous@.discussions.microsoft.com> wrote:
>
machines[vbcol=seagreen]
from[vbcol=seagreen]
while[vbcol=seagreen]
need[vbcol=seagreen]
>.
>
ODBC Connection to SQL Server
I am setting up SQL Server ODBC connections on 5 machines
and everything has gone fine until I came to the last
machine.
When I go to choose the server I want to connect to from
the server drop down list, it isn't there. There other
machines listed, but not the one that I want.
The only difference is that this one has 2000 pro, while
all of the others have XP pro. I am assuming that I need
to update something on the 2000 machine, but don't know
what. Can anyone help me with this?
Thanks in advance.
You should check the MDAC version, installation on the
machine that's having problems. If the versions are
different between the xp machines and the 2000 machine,
you'd want to upgrade the 2000 machine to the same MDAC
version.
You can download the MDAC component checker
from:
http://msdn.microsoft.com/data/downl...s/default.aspx
-Sue
On Fri, 16 Apr 2004 07:52:32 -0700, "Mark Kovach"
<anonymous@.discussions.microsoft.com> wrote:
>I am setting up SQL Server ODBC connections on 5 machines
>and everything has gone fine until I came to the last
>machine.
>When I go to choose the server I want to connect to from
>the server drop down list, it isn't there. There other
>machines listed, but not the one that I want.
>The only difference is that this one has 2000 pro, while
>all of the others have XP pro. I am assuming that I need
>to update something on the 2000 machine, but don't know
>what. Can anyone help me with this?
>Thanks in advance.
|||Thanks. I downloaded MDAC 2.8 and installed it. It
works great now.
Thank you for the help.
>--Original Message--
>You should check the MDAC version, installation on the
>machine that's having problems. If the versions are
>different between the xp machines and the 2000 machine,
>you'd want to upgrade the 2000 machine to the same MDAC
>version.
>You can download the MDAC component checker
>from:
>http://msdn.microsoft.com/data/downl...ols/default.as
px[vbcol=seagreen]
>-Sue
>On Fri, 16 Apr 2004 07:52:32 -0700, "Mark Kovach"
><anonymous@.discussions.microsoft.com> wrote:
machines[vbcol=seagreen]
from[vbcol=seagreen]
while[vbcol=seagreen]
need
>.
>
sql
and everything has gone fine until I came to the last
machine.
When I go to choose the server I want to connect to from
the server drop down list, it isn't there. There other
machines listed, but not the one that I want.
The only difference is that this one has 2000 pro, while
all of the others have XP pro. I am assuming that I need
to update something on the 2000 machine, but don't know
what. Can anyone help me with this?
Thanks in advance.
You should check the MDAC version, installation on the
machine that's having problems. If the versions are
different between the xp machines and the 2000 machine,
you'd want to upgrade the 2000 machine to the same MDAC
version.
You can download the MDAC component checker
from:
http://msdn.microsoft.com/data/downl...s/default.aspx
-Sue
On Fri, 16 Apr 2004 07:52:32 -0700, "Mark Kovach"
<anonymous@.discussions.microsoft.com> wrote:
>I am setting up SQL Server ODBC connections on 5 machines
>and everything has gone fine until I came to the last
>machine.
>When I go to choose the server I want to connect to from
>the server drop down list, it isn't there. There other
>machines listed, but not the one that I want.
>The only difference is that this one has 2000 pro, while
>all of the others have XP pro. I am assuming that I need
>to update something on the 2000 machine, but don't know
>what. Can anyone help me with this?
>Thanks in advance.
|||Thanks. I downloaded MDAC 2.8 and installed it. It
works great now.
Thank you for the help.
>--Original Message--
>You should check the MDAC version, installation on the
>machine that's having problems. If the versions are
>different between the xp machines and the 2000 machine,
>you'd want to upgrade the 2000 machine to the same MDAC
>version.
>You can download the MDAC component checker
>from:
>http://msdn.microsoft.com/data/downl...ols/default.as
px[vbcol=seagreen]
>-Sue
>On Fri, 16 Apr 2004 07:52:32 -0700, "Mark Kovach"
><anonymous@.discussions.microsoft.com> wrote:
machines[vbcol=seagreen]
from[vbcol=seagreen]
while[vbcol=seagreen]
need
>.
>
sql
Wednesday, March 21, 2012
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]
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
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
Monday, March 12, 2012
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.
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.
Friday, March 9, 2012
ODBC
I go to install sql server 2000 in one of our servers, would like to
know if after the installation I lose connections ODBC that already I
possess using SQL Server 7If the database names and the servernames are the same ( like in an
upgrade ) the ODBC DSNs need not be changed. Otherwise you'll have to click
configure and reset the values.
--
- Anith
( Please reply to newsgroups only )
know if after the installation I lose connections ODBC that already I
possess using SQL Server 7If the database names and the servernames are the same ( like in an
upgrade ) the ODBC DSNs need not be changed. Otherwise you'll have to click
configure and reset the values.
--
- Anith
( Please reply to newsgroups only )
Wednesday, March 7, 2012
Obtaining Scripts
I need to script a couple of things that I do through enterprise manager...is there a way to do a process (such as clear connections/detach database) through enterprise manager and then copy the script that sql ran in the back ground?
Best way is to run profiler and capture the commands while performing your tasks on Ent. Manager.
"Jamie Elliott" wrote:
> I need to script a couple of things that I do through enterprise manager...is there a way to do a process (such as clear connections/detach database) through enterprise manager and then copy the script that sql ran in the back ground?
|||Standart Trace template will be fine ..
"Jamie Elliott" wrote:
[vbcol=seagreen]
> when setting up profiler...is there any certain setting I should give it?
> "Umut Nazlica" wrote:
Best way is to run profiler and capture the commands while performing your tasks on Ent. Manager.
"Jamie Elliott" wrote:
> I need to script a couple of things that I do through enterprise manager...is there a way to do a process (such as clear connections/detach database) through enterprise manager and then copy the script that sql ran in the back ground?
|||Standart Trace template will be fine ..
"Jamie Elliott" wrote:
[vbcol=seagreen]
> when setting up profiler...is there any certain setting I should give it?
> "Umut Nazlica" wrote:
Obtaining Scripts
I need to script a couple of things that I do through enterprise manager...i
s there a way to do a process (such as clear connections/detach database) th
rough enterprise manager and then copy the script that sql ran in the back g
round?Best way is to run profiler and capture the commands while performing your t
asks on Ent. Manager.
"Jamie Elliott" wrote:
> I need to script a couple of things that I do through enterprise manager...is ther
e a way to do a process (such as clear connections/detach database) through enterpri
se manager and then copy the script that sql ran in the back ground?|||Standart Trace template will be fine ..
"Jamie Elliott" wrote:
[vbcol=seagreen]
> when setting up profiler...is there any certain setting I should give it?
> "Umut Nazlica" wrote:
>
s there a way to do a process (such as clear connections/detach database) th
rough enterprise manager and then copy the script that sql ran in the back g
round?Best way is to run profiler and capture the commands while performing your t
asks on Ent. Manager.
"Jamie Elliott" wrote:
> I need to script a couple of things that I do through enterprise manager...is ther
e a way to do a process (such as clear connections/detach database) through enterpri
se manager and then copy the script that sql ran in the back ground?|||Standart Trace template will be fine ..
"Jamie Elliott" wrote:
[vbcol=seagreen]
> when setting up profiler...is there any certain setting I should give it?
> "Umut Nazlica" wrote:
>
Subscribe to:
Posts (Atom)