Connect to SQL Server

Tuesday, March 27, 2012

Connecting to SQL Server 2005

Hello!
I was wondering if I need to install something on the client in order to
establish ODBC/OLEDB connection to SQL Server 2005. Currently, I have ADO
2.6 installed. Are there any changes in ODBC/OLEDB drivers for SQL Server
2005?
Thanks,
IgorHi
It is best to use MDAC 2.8, but 2.6 will connect to SQL Server 2005, but you
will not be able to use the new datatypes that SQL Server 2005 has
introduced.
The ODBC/OLEDB drivers no longer ship with SQL Server, as it is now a
function of the Operating System to update them.
The new way to connect to SQL Server 2005 is SQL Native Client (SQLNCLI)
"Provider=SQLNCLI"
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/
"imarchenko" <igormarchenko@.hotmail.com> wrote in message
news:ulvm%23pcCGHA.2300@.TK2MSFTNGP15.phx.gbl...
> Hello!
> I was wondering if I need to install something on the client in order
> to establish ODBC/OLEDB connection to SQL Server 2005. Currently, I have
> ADO 2.6 installed. Are there any changes in ODBC/OLEDB drivers for SQL
> Server 2005?
> Thanks,
> Igor
>|||"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:%2326c1IiCGHA.3984@.TK2MSFTNGP14.phx.gbl...
> Hi
> It is best to use MDAC 2.8, but 2.6 will connect to SQL Server 2005, but
> you will not be able to use the new datatypes that SQL Server 2005 has
> introduced.
> The ODBC/OLEDB drivers no longer ship with SQL Server, as it is now a
> function of the Operating System to update them.
> The new way to connect to SQL Server 2005 is SQL Native Client (SQLNCLI)
> "Provider=SQLNCLI"
>
This is not quite right. MDAC is part of the operating system, but SQL
Native Client is not.
The SQL Native Client is a seperate install. It is included in the SQL
Server distribution and available here:
http://msdn.microsoft.com/data/sqlnative/default.aspx
There are now 3! OleDb providers for SQL Server. Two in MDAC: MSDASQL
(deprecated) and SQLOLEDB (current). Plus one in the SQL Native Client
(SQLNCLI). SQLNCLI is the best, but you must install it.
SQL Native Client also has a new ODBC driver.
David|||David,
I am able to connect to SQL Server 2005 using SQL Native Client but
I got en error 'Server unavailable or access denied ...' when trying to
connect using Microsoft OLE DB provider for SQL Server. I am trying to
connect by setting up properties of UDL file on the same box where SQL
Server is installed. Did I get it right that I have to install latest
drivers on client computers from the link your provided?
Thanks,
Igor
"David Browne" <davidbaxterbrowne no potted meat@.hotmail.com> wrote in
message news:O$2MO8jCGHA.2664@.TK2MSFTNGP15.phx.gbl...
> "Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
> news:%2326c1IiCGHA.3984@.TK2MSFTNGP14.phx.gbl...
>> Hi
>> It is best to use MDAC 2.8, but 2.6 will connect to SQL Server 2005, but
>> you will not be able to use the new datatypes that SQL Server 2005 has
>> introduced.
>> The ODBC/OLEDB drivers no longer ship with SQL Server, as it is now a
>> function of the Operating System to update them.
>> The new way to connect to SQL Server 2005 is SQL Native Client (SQLNCLI)
>> "Provider=SQLNCLI"
> This is not quite right. MDAC is part of the operating system, but SQL
> Native Client is not.
>
> The SQL Native Client is a seperate install. It is included in the SQL
> Server distribution and available here:
> http://msdn.microsoft.com/data/sqlnative/default.aspx
> There are now 3! OleDb providers for SQL Server. Two in MDAC: MSDASQL
> (deprecated) and SQLOLEDB (current). Plus one in the SQL Native Client
> (SQLNCLI). SQLNCLI is the best, but you must install it.
> SQL Native Client also has a new ODBC driver.
> David
>|||David,
I wa able to connect by enabling remote connections using Surface Area.
Thanks,
Igor
"imarchenko" <igormarchenko@.hotmail.com> wrote in message
news:%23t2FLdxCGHA.724@.TK2MSFTNGP10.phx.gbl...
> David,
> I am able to connect to SQL Server 2005 using SQL Native Client but
> I got en error 'Server unavailable or access denied ...' when trying to
> connect using Microsoft OLE DB provider for SQL Server. I am trying to
> connect by setting up properties of UDL file on the same box where SQL
> Server is installed. Did I get it right that I have to install latest
> drivers on client computers from the link your provided?
> Thanks,
> Igor
>
> "David Browne" <davidbaxterbrowne no potted meat@.hotmail.com> wrote in
> message news:O$2MO8jCGHA.2664@.TK2MSFTNGP15.phx.gbl...
>> "Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
>> news:%2326c1IiCGHA.3984@.TK2MSFTNGP14.phx.gbl...
>> Hi
>> It is best to use MDAC 2.8, but 2.6 will connect to SQL Server 2005, but
>> you will not be able to use the new datatypes that SQL Server 2005 has
>> introduced.
>> The ODBC/OLEDB drivers no longer ship with SQL Server, as it is now a
>> function of the Operating System to update them.
>> The new way to connect to SQL Server 2005 is SQL Native Client (SQLNCLI)
>> "Provider=SQLNCLI"
>>
>> This is not quite right. MDAC is part of the operating system, but SQL
>> Native Client is not.
>>
>> The SQL Native Client is a seperate install. It is included in the SQL
>> Server distribution and available here:
>> http://msdn.microsoft.com/data/sqlnative/default.aspx
>> There are now 3! OleDb providers for SQL Server. Two in MDAC: MSDASQL
>> (deprecated) and SQLOLEDB (current). Plus one in the SQL Native Client
>> (SQLNCLI). SQLNCLI is the best, but you must install it.
>> SQL Native Client also has a new ODBC driver.
>> David
>

Connecting to SQL Server 2005

I have successfully installed SQL Server 2005 on a server that also has SQL
Server 2000. Using SQL Server 2005 interface, how could I connect to a
named instance of a SQL Server 2005 database? As I try, it keeps connecting
me to the SQL Server 2000 db. Is this something you set up in CLient tools?
Please let me know, I connect to the SQL Server using a temp dns name.
Thanks,
Here is what I what to achieve:
category1
content2
content3
content4
content5
content6Please disregard this text. Came from an old message.
"Here is what I what to achieve:
category1
content2
content3
content4
content5
content6"
<programmingcodeATjards.com> wrote in message
news:e83mL7OrGHA.4864@.TK2MSFTNGP03.phx.gbl...
>I have successfully installed SQL Server 2005 on a server that also has SQL
>Server 2000. Using SQL Server 2005 interface, how could I connect to a
>named instance of a SQL Server 2005 database? As I try, it keeps
>connecting me to the SQL Server 2000 db. Is this something you set up in
>CLient tools? Please let me know, I connect to the SQL Server using a temp
>dns name.
> Thanks,
>
> Here is what I what to achieve:
> category1
> content2
> content3
> content4
> content5
> content6
>
>|||<programmingcodeATjards.com> wrote in message
news:e83mL7OrGHA.4864@.TK2MSFTNGP03.phx.gbl...
> I have successfully installed SQL Server 2005 on a server that also has
SQL
> Server 2000. Using SQL Server 2005 interface, how could I connect to a
> named instance of a SQL Server 2005 database? As I try, it keeps
connecting
> me to the SQL Server 2000 db. Is this something you set up in CLient
tools?
> Please let me know, I connect to the SQL Server using a temp dns name.
> Thanks,
>
Not sure what you're trying, but generally it's servername\instancename. If
not instance name is provided it deafults to the default instance.
>
> Here is what I what to achieve:
> category1
> content2
> content3
> content4
> content5
> content6
>
>sql sql

Connecting to SQL Server 2005

Hi,
I am having ongoing problems connecting to the server. I thought I had it
solved thanks to help from a prev post:
C:\>sqlcmd -S dimension9150\SQLExpress
HResult 0xFFFFFFFF, Level 16, State 1
SQL Network Interfaces: Error Locating Server/Instance Specified
[xFFFFFFFF].
Sqlcmd: Error: Microsoft SQL Native Client : An error has occurred while
establi
shing a connection to the server. When connecting to SQL Server 2005, this
failu
re may be caused by the fact that under the default settings SQL Server does
not
allow remote connections..
Sqlcmd: Error: Microsoft SQL Native Client : Login timeout expired.
C:\>sqlcmd -S dimension9150\SQLExpress,1433
1> exit
C:\>
Now at least i can connect to the server using the sqlcmd utility however I
am unable to get a connection string to connect.
cmdCommand.ActiveConnection =
" Server=dimension9150;Database=IPS;Truste
d_Connection=True"
This simply returns an error number -2147467259
As with the sqlcmd utility do I need to specify port 1433 in my connection
sting ?
I am not running the SQL Browser service as I understand it is better not to
for security reasons and understand this makes connecting harder ?
I am running a firewall program on the server "Norton Internet Security"
however as it was not stopping sqlcmd from working I had assumed it would
not be a problem for my connection string either.
Any help would be greatly appreciated.
Thanks in advance...If you don't use the SQL Browser service, you would need to specify the port
in your case.
Linchi
"McHenry" wrote:

> Hi,
> I am having ongoing problems connecting to the server. I thought I had it
> solved thanks to help from a prev post:
> C:\>sqlcmd -S dimension9150\SQLExpress
> HResult 0xFFFFFFFF, Level 16, State 1
> SQL Network Interfaces: Error Locating Server/Instance Specified
> [xFFFFFFFF].
> Sqlcmd: Error: Microsoft SQL Native Client : An error has occurred while
> establi
> shing a connection to the server. When connecting to SQL Server 2005, this
> failu
> re may be caused by the fact that under the default settings SQL Server do
es
> not
> allow remote connections..
> Sqlcmd: Error: Microsoft SQL Native Client : Login timeout expired.
> C:\>sqlcmd -S dimension9150\SQLExpress,1433
> 1> exit
> C:\>
>
> Now at least i can connect to the server using the sqlcmd utility however
I
> am unable to get a connection string to connect.
> cmdCommand.ActiveConnection =
> " Server=dimension9150;Database=IPS;Truste
d_Connection=True"
> This simply returns an error number -2147467259
> As with the sqlcmd utility do I need to specify port 1433 in my connection
> sting ?
> I am not running the SQL Browser service as I understand it is better not
to
> for security reasons and understand this makes connecting harder ?
> I am running a firewall program on the server "Norton Internet Security"
> however as it was not stopping sqlcmd from working I had assumed it would
> not be a problem for my connection string either.
> Any help would be greatly appreciated.
>
> Thanks in advance...
>
>|||I have exactly the same problem.
I had SQL SERVER 2005 running but I cleaned all out for a reinstall
and now I get exactly the error you get.
c:\sqlcmd -S dimension9150\SQLExpress,1433 gets the same error
I have set shared memory, pipes, tcp/ip, set ports to no avail
"McHenry" wrote:

> Hi,
> I am having ongoing problems connecting to the server. I thought I had it
> solved thanks to help from a prev post:
> C:\>sqlcmd -S dimension9150\SQLExpress
> HResult 0xFFFFFFFF, Level 16, State 1
> SQL Network Interfaces: Error Locating Server/Instance Specified
> [xFFFFFFFF].
> Sqlcmd: Error: Microsoft SQL Native Client : An error has occurred while
> establi
> shing a connection to the server. When connecting to SQL Server 2005, this
> failu
> re may be caused by the fact that under the default settings SQL Server do
es
> not
> allow remote connections..
> Sqlcmd: Error: Microsoft SQL Native Client : Login timeout expired.
> C:\>sqlcmd -S dimension9150\SQLExpress,1433
> 1> exit
> C:\>
>
> Now at least i can connect to the server using the sqlcmd utility however
I
> am unable to get a connection string to connect.
> cmdCommand.ActiveConnection =
> " Server=dimension9150;Database=IPS;Truste
d_Connection=True"
> This simply returns an error number -2147467259
> As with the sqlcmd utility do I need to specify port 1433 in my connection
> sting ?
> I am not running the SQL Browser service as I understand it is better not
to
> for security reasons and understand this makes connecting harder ?
> I am running a firewall program on the server "Norton Internet Security"
> however as it was not stopping sqlcmd from working I had assumed it would
> not be a problem for my connection string either.
> Any help would be greatly appreciated.
>
> Thanks in advance...
>
>

Connecting to SQL Server 2000 via VB6 program on Vista

I am having difficulty connecting to SQL Server 2000 on one of our
servers via a VB6 program on Vista. I can connect fine to a different
server, but it gives me the following error with the server in
question:
"Unable to connect to database. Please check your internet connection
Error# -2147467259
[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or
access denied"
Using the program, I am able to access the database just fine while
running on Windows XP, but when I run the program on Vista, it gives
me that error message for that server. If I change the connection
string to a different server address, it works fine on Vista. What
differences in the servers might cause this?
Here is my connection string:
"driver={SQL Server};Server=ipaddress;Uid=userID;Pwd=pwd;databa se=db"
Is the firewall open for port 1433?
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant, Dad, Grandpa
Microsoft MVP
INETA Speaker
www.betav.com
www.betav.com/blog/billva
www.hitchhikerguides.net
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
------
"TerpZebra" <terpzebra@.gmail.com> wrote in message
news:1184775545.291016.192510@.i38g2000prf.googlegr oups.com...
>I am having difficulty connecting to SQL Server 2000 on one of our
> servers via a VB6 program on Vista. I can connect fine to a different
> server, but it gives me the following error with the server in
> question:
> "Unable to connect to database. Please check your internet connection
> Error# -2147467259
> [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or
> access denied"
> Using the program, I am able to access the database just fine while
> running on Windows XP, but when I run the program on Vista, it gives
> me that error message for that server. If I change the connection
> string to a different server address, it works fine on Vista. What
> differences in the servers might cause this?
> Here is my connection string:
> "driver={SQL Server};Server=ipaddress;Uid=userID;Pwd=pwd;databa se=db"
>
|||TerpZebra (terpzebra@.gmail.com) writes:
> I am having difficulty connecting to SQL Server 2000 on one of our
> servers via a VB6 program on Vista. I can connect fine to a different
> server, but it gives me the following error with the server in
> question:
> "Unable to connect to database. Please check your internet connection
> Error# -2147467259
> [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or
> access denied"
> Using the program, I am able to access the database just fine while
> running on Windows XP, but when I run the program on Vista, it gives
> me that error message for that server. If I change the connection
> string to a different server address, it works fine on Vista. What
> differences in the servers might cause this?
> Here is my connection string:
> "driver={SQL Server};Server=ipaddress;Uid=userID;Pwd=pwd;databa se=db"
Difficult to say. Is SQL Server running on port 1433 on both servers?
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
|||The SQL Server Config tools will tell you what port(s) have been assigned.
SS 2000 broadcasts and handles the incoming requests and maps to the ports,
but if the firewall blocks them...
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant, Dad, Grandpa
Microsoft MVP
INETA Speaker
www.betav.com
www.betav.com/blog/billva
www.hitchhikerguides.net
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
------
"Erland Sommarskog" <esquel@.sommarskog.se> wrote in message
news:Xns9971F1A126FADYazorman@.127.0.0.1...
> TerpZebra (terpzebra@.gmail.com) writes:
> Difficult to say. Is SQL Server running on port 1433 on both servers?
>
>
> --
> Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
> Books Online for SQL Server 2005 at
> http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
> Books Online for SQL Server 2000 at
> http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
|||On Jul 18, 3:50 pm, "William Vaughn" <billvaNoS...@.betav.com> wrote:[vbcol=seagreen]
> Is the firewall open for port 1433?
> --
> ____________________________________
> William (Bill) Vaughn
> Author, Mentor, Consultant, Dad, Grandpa
> Microsoft MVP
> INETA Speakerwww.betav.comwww.betav.com/blog/billvawww.hitchhikerguides.netwww.betav.com/blog/billvawww.betav.com
> Please reply only to the newsgroup so that others can benefit.
> This posting is provided "AS IS" with no warranties, and confers no rights.
> __________________________________
> Visitwww.hitchhikerguides.netto get more information on my latest book:
> Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
> and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
> ------
> "TerpZebra" <terpze...@.gmail.com> wrote in message
> news:1184775545.291016.192510@.i38g2000prf.googlegr oups.com...
>
>
Yes, it is open for port 1433. I can connect to a separate Server
using the same connection string, except for the IP address, and it
works fine.
I can also connect to both Servers using the application on Windows XP
|||So, there is something different about this particular server--assuming you
can connect to other servers from the client.
Have you run the surface area config tool on the target server?
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant, Dad, Grandpa
Microsoft MVP
INETA Speaker
www.betav.com
www.betav.com/blog/billva
www.hitchhikerguides.net
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
------
"TerpZebra" <terpzebra@.gmail.com> wrote in message
news:1184866009.025953.319470@.q75g2000hsh.googlegr oups.com...
> On Jul 18, 3:50 pm, "William Vaughn" <billvaNoS...@.betav.com> wrote:
> Yes, it is open for port 1433. I can connect to a separate Server
> using the same connection string, except for the IP address, and it
> works fine.
> I can also connect to both Servers using the application on Windows XP
>
|||William Vaughn (billvaNoSPAM@.betav.com) writes:
> So, there is something different about this particular server--assuming
> you can connect to other servers from the client. Have you run the
> surface area config tool on the target server?
As that server is running SQL 2000, there is not likely to be a surface-
area config tool.
But, yes, something appears to be special with that server.
TerpZebra, could you post the first 50 lines or so of the error log
for that server instance?
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
|||The SQL Server configuation tools will have to do. Make sure the defaults
are over-ridden to make the server visible. Since SP3a SQL Server 2000 is
configured to be invisible to the net. The TCP/IP protocol is disabled. See
http://www.databasejournal.com/features/mssql/article.php/3334851. He
discusses the SQL Server Network Utility that's used to make these
configuration changes.
hth
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant, Dad, Grandpa
Microsoft MVP
INETA Speaker
www.betav.com
www.betav.com/blog/billva
www.hitchhikerguides.net
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
------
"Erland Sommarskog" <esquel@.sommarskog.se> wrote in message
news:Xns9972E8971EADFYazorman@.127.0.0.1...
> William Vaughn (billvaNoSPAM@.betav.com) writes:
> As that server is running SQL 2000, there is not likely to be a surface-
> area config tool.
> But, yes, something appears to be special with that server.
> TerpZebra, could you post the first 50 lines or so of the error log
> for that server instance?
>
> --
> Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
> Books Online for SQL Server 2005 at
> http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
> Books Online for SQL Server 2000 at
> http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx

Connecting to SQL Server 2000 via VB6 program on Vista

I am having difficulty connecting to SQL Server 2000 on one of our
servers via a VB6 program on Vista. I can connect fine to a different
server, but it gives me the following error with the server in
question:
"Unable to connect to database. Please check your internet connection
Error# -2147467259
[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or
access denied"
Using the program, I am able to access the database just fine while
running on Windows XP, but when I run the program on Vista, it gives
me that error message for that server. If I change the connection
string to a different server address, it works fine on Vista. What
differences in the servers might cause this?
Here is my connection string:
"driver={SQL Server};Server=ipaddress;Uid=userID;Pwd=
pwd;database=db"Is the firewall open for port 1433?
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant, Dad, Grandpa
Microsoft MVP
INETA Speaker
www.betav.com
www.betav.com/blog/billva
www.hitchhikerguides.net
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
----
---
"TerpZebra" <terpzebra@.gmail.com> wrote in message
news:1184775545.291016.192510@.i38g2000prf.googlegroups.com...
>I am having difficulty connecting to SQL Server 2000 on one of our
> servers via a VB6 program on Vista. I can connect fine to a different
> server, but it gives me the following error with the server in
> question:
> "Unable to connect to database. Please check your internet connection
> Error# -2147467259
> [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist o
r
> access denied"
> Using the program, I am able to access the database just fine while
> running on Windows XP, but when I run the program on Vista, it gives
> me that error message for that server. If I change the connection
> string to a different server address, it works fine on Vista. What
> differences in the servers might cause this?
> Here is my connection string:
> "driver={SQL Server};Server=ipaddress;Uid=userID;Pwd=
pwd;database=db"
>|||TerpZebra (terpzebra@.gmail.com) writes:
> I am having difficulty connecting to SQL Server 2000 on one of our
> servers via a VB6 program on Vista. I can connect fine to a different
> server, but it gives me the following error with the server in
> question:
> "Unable to connect to database. Please check your internet connection
> Error# -2147467259
> [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist o
r
> access denied"
> Using the program, I am able to access the database just fine while
> running on Windows XP, but when I run the program on Vista, it gives
> me that error message for that server. If I change the connection
> string to a different server address, it works fine on Vista. What
> differences in the servers might cause this?
> Here is my connection string:
> "driver={SQL Server};Server=ipaddress;Uid=userID;Pwd=
pwd;database=db"
Difficult to say. Is SQL Server running on port 1433 on both servers?
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx|||The SQL Server Config tools will tell you what port(s) have been assigned.
SS 2000 broadcasts and handles the incoming requests and maps to the ports,
but if the firewall blocks them...
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant, Dad, Grandpa
Microsoft MVP
INETA Speaker
www.betav.com
www.betav.com/blog/billva
www.hitchhikerguides.net
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
----
---
"Erland Sommarskog" <esquel@.sommarskog.se> wrote in message
news:Xns9971F1A126FADYazorman@.127.0.0.1...
> TerpZebra (terpzebra@.gmail.com) writes:
> Difficult to say. Is SQL Server running on port 1433 on both servers?
>
>
> --
> Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
> Books Online for SQL Server 2005 at
> http://www.microsoft.com/technet/pr...oads/books.mspx
> Books Online for SQL Server 2000 at
> http://www.microsoft.com/sql/prodin...ions/books.mspx|||On Jul 18, 3:50 pm, "William Vaughn" <billvaNoS...@.betav.com> wrote:[vbcol=seagreen]
> Is the firewall open for port 1433?
> --
> ____________________________________
> William (Bill) Vaughn
> Author, Mentor, Consultant, Dad, Grandpa
> Microsoft MVP
> INETA Speakerwww.betav.comwww.betav.com/blog/billvawww.hitchhikerguides.ne
twww.betav.com/blog/billvawww.betav.com
> Please reply only to the newsgroup so that others can benefit.
> This posting is provided "AS IS" with no warranties, and confers no rights
.
> __________________________________
> Visitwww.hitchhikerguides.netto get more information on my latest book:
> Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
> and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
> ----
---
> "TerpZebra" <terpze...@.gmail.com> wrote in message
> news:1184775545.291016.192510@.i38g2000prf.googlegroups.com...
>
>
>
>
Yes, it is open for port 1433. I can connect to a separate Server
using the same connection string, except for the IP address, and it
works fine.
I can also connect to both Servers using the application on Windows XP|||So, there is something different about this particular server--assuming you
can connect to other servers from the client.
Have you run the surface area config tool on the target server?
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant, Dad, Grandpa
Microsoft MVP
INETA Speaker
www.betav.com
www.betav.com/blog/billva
www.hitchhikerguides.net
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
----
---
"TerpZebra" <terpzebra@.gmail.com> wrote in message
news:1184866009.025953.319470@.q75g2000hsh.googlegroups.com...
> On Jul 18, 3:50 pm, "William Vaughn" <billvaNoS...@.betav.com> wrote:
> Yes, it is open for port 1433. I can connect to a separate Server
> using the same connection string, except for the IP address, and it
> works fine.
> I can also connect to both Servers using the application on Windows XP
>|||William Vaughn (billvaNoSPAM@.betav.com) writes:
> So, there is something different about this particular server--assuming
> you can connect to other servers from the client. Have you run the
> surface area config tool on the target server?
As that server is running SQL 2000, there is not likely to be a surface-
area config tool.
But, yes, something appears to be special with that server.
TerpZebra, could you post the first 50 lines or so of the error log
for that server instance?
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx|||The SQL Server configuation tools will have to do. Make sure the defaults
are over-ridden to make the server visible. Since SP3a SQL Server 2000 is
configured to be invisible to the net. The TCP/IP protocol is disabled. See
http://www.databasejournal.com/feat...le.php/3334851. He
discusses the SQL Server Network Utility that's used to make these
configuration changes.
hth
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant, Dad, Grandpa
Microsoft MVP
INETA Speaker
www.betav.com
www.betav.com/blog/billva
www.hitchhikerguides.net
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
----
---
"Erland Sommarskog" <esquel@.sommarskog.se> wrote in message
news:Xns9972E8971EADFYazorman@.127.0.0.1...
> William Vaughn (billvaNoSPAM@.betav.com) writes:
> As that server is running SQL 2000, there is not likely to be a surface-
> area config tool.
> But, yes, something appears to be special with that server.
> TerpZebra, could you post the first 50 lines or so of the error log
> for that server instance?
>
> --
> Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
> Books Online for SQL Server 2005 at
> http://www.microsoft.com/technet/pr...oads/books.mspx
> Books Online for SQL Server 2000 at
> http://www.microsoft.com/sql/prodin...ions/books.mspx

Connecting to SQL Server 2000 via VB6 program on Vista

"Unable to connect to database. Please check your internet connection
Error# -2147467259
[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or
access denied"

Using the program, I am able to access the database just fine while
running on Windows XP, but when I run the program on Vista, it gives
me that error message for that server. If I change the connection
string to a different server address, it works fine on Vista. What
differences in the servers might cause this?

Here is my connection string:
"driver={SQL Server};Server=ipaddress;Uid=userID;Pwd=pwd;databa se=db"Is the firewall open for port 1433?

--
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant, Dad, Grandpa
Microsoft MVP
INETA Speaker
www.betav.com
www.betav.com/blog/billva
www.hitchhikerguides.net
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
------------------------------------

"TerpZebra" <terpzebra@.gmail.comwrote in message
news:1184775545.291016.192510@.i38g2000prf.googlegr oups.com...

Quote:

Originally Posted by

>I am having difficulty connecting to SQL Server 2000 on one of our
servers via a VB6 program on Vista. I can connect fine to a different
server, but it gives me the following error with the server in
question:
>
"Unable to connect to database. Please check your internet connection
Error# -2147467259
[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or
access denied"
>
Using the program, I am able to access the database just fine while
running on Windows XP, but when I run the program on Vista, it gives
me that error message for that server. If I change the connection
string to a different server address, it works fine on Vista. What
differences in the servers might cause this?
>
Here is my connection string:
"driver={SQL Server};Server=ipaddress;Uid=userID;Pwd=pwd;databa se=db"
>

|||TerpZebra (terpzebra@.gmail.com) writes:

Quote:

Originally Posted by

Difficult to say. Is SQL Server running on port 1433 on both servers?

"Erland Sommarskog" <esquel@.sommarskog.sewrote in message
news:Xns9971F1A126FADYazorman@.127.0.0.1...

Quote:

Originally Posted by

TerpZebra (terpzebra@.gmail.com) writes:

Quote:

Originally Posted by

>I am having difficulty connecting to SQL Server 2000 on one of our
>servers via a VB6 program on Vista. I can connect fine to a different
>server, but it gives me the following error with the server in
>question:
>>
>"Unable to connect to database. Please check your internet connection
> Error# -2147467259
>[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or
>access denied"
>>
>Using the program, I am able to access the database just fine while
>running on Windows XP, but when I run the program on Vista, it gives
>me that error message for that server. If I change the connection
>string to a different server address, it works fine on Vista. What
>differences in the servers might cause this?
>>
>Here is my connection string:
>"driver={SQL Server};Server=ipaddress;Uid=userID;Pwd=pwd;databa se=db"

>
Difficult to say. Is SQL Server running on port 1433 on both servers?
>
>
>
>
--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
>
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx

|||On Jul 18, 3:50 pm, "William Vaughn" <billvaNoS...@.betav.comwrote:

Quote:

Originally Posted by

Is the firewall open for port 1433?
>
--
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant, Dad, Grandpa
Microsoft MVP
INETA Speakerwww.betav.comwww.betav.com/blog/billvawww.hitchhikerguides.netwww.betav.com/blog/billvawww.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visitwww.hitchhikerguides.netto get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
------------------------------------
>
"TerpZebra" <terpze...@.gmail.comwrote in message
>
news:1184775545.291016.192510@.i38g2000prf.googlegr oups.com...
>

Quote:

Originally Posted by

Quote:

Originally Posted by

"Unable to connect to database. Please check your internet connection
Error# -2147467259
[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or
access denied"

Quote:

Originally Posted by

Quote:

Originally Posted by

Here is my connection string:
"driver={SQL Server};Server=ipaddress;Uid=userID;Pwd=pwd;databa se=db"

Yes, it is open for port 1433. I can connect to a separate Server
using the same connection string, except for the IP address, and it
works fine.

I can also connect to both Servers using the application on Windows XP|||So, there is something different about this particular server--assuming you
can connect to other servers from the client.
Have you run the surface area config tool on the target server?

"TerpZebra" <terpzebra@.gmail.comwrote in message
news:1184866009.025953.319470@.q75g2000hsh.googlegr oups.com...

Quote:

Originally Posted by

On Jul 18, 3:50 pm, "William Vaughn" <billvaNoS...@.betav.comwrote:

Quote:

Originally Posted by

>Is the firewall open for port 1433?
>>
>--
>____________________________________
>William (Bill) Vaughn
>Author, Mentor, Consultant, Dad, Grandpa
>Microsoft MVP
>INETA
>Speakerwww.betav.comwww.betav.com/blog/billvawww.hitchhikerguides.netwww.betav.com/blog/billvawww.betav.com
>Please reply only to the newsgroup so that others can benefit.
>This posting is provided "AS IS" with no warranties, and confers no
>rights.
>__________________________________
>Visitwww.hitchhikerguides.netto get more information on my latest book:
>Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
>and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
>------------------------------------
>>
>"TerpZebra" <terpze...@.gmail.comwrote in message
>>
>news:1184775545.291016.192510@.i38g2000prf.googlegr oups.com...
>>

Quote:

Originally Posted by

Quote:

Originally Posted by

"Unable to connect to database. Please check your internet connection
Error# -2147467259
[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or
access denied"

Quote:

Originally Posted by

Quote:

Originally Posted by

Here is my connection string:
"driver={SQL Server};Server=ipaddress;Uid=userID;Pwd=pwd;databa se=db"

>
Yes, it is open for port 1433. I can connect to a separate Server
using the same connection string, except for the IP address, and it
works fine.
>
I can also connect to both Servers using the application on Windows XP
>

|||William Vaughn (billvaNoSPAM@.betav.com) writes:

Quote:

Originally Posted by

So, there is something different about this particular server--assuming
you can connect to other servers from the client. Have you run the
surface area config tool on the target server?

As that server is running SQL 2000, there is not likely to be a surface-
area config tool.

But, yes, something appears to be special with that server.

TerpZebra, could you post the first 50 lines or so of the error log
for that server instance?

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx|||The SQL Server configuation tools will have to do. Make sure the defaults
are over-ridden to make the server visible. Since SP3a SQL Server 2000 is
configured to be invisible to the net. The TCP/IP protocol is disabled. See
http://www.databasejournal.com/feat...cle.php/3334851. He
discusses the SQL Server Network Utility that's used to make these
configuration changes.

hth

"Erland Sommarskog" <esquel@.sommarskog.sewrote in message
news:Xns9972E8971EADFYazorman@.127.0.0.1...

Quote:

Originally Posted by

William Vaughn (billvaNoSPAM@.betav.com) writes:

Quote:

Originally Posted by

>So, there is something different about this particular server--assuming
>you can connect to other servers from the client. Have you run the
>surface area config tool on the target server?

>
As that server is running SQL 2000, there is not likely to be a surface-
area config tool.
>
But, yes, something appears to be special with that server.
>
TerpZebra, could you post the first 50 lines or so of the error log
for that server instance?
>
>
>
--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
>
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx

Tuesday, March 27, 2012

Connecting to SQL Server 2005

Connecting to SQL Server 2005

Connecting to SQL Server 2005

Connecting to SQL Server 2005

Connecting to SQL Server 2000 via VB6 program on Vista

Connecting to SQL Server 2000 via VB6 program on Vista

Connecting to SQL Server 2000 via VB6 program on Vista

Connect to SQL Server

Blog Archive

About Me