Tuesday, March 27, 2012
Connecting to SQL Server 2000 via VB6 program on Vista
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
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
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.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"
>
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|||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.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
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:
>
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
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?
>
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?
--
____________________________________
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: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
>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:
>>
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
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?
>>
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
--
____________________________________
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.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
Sunday, March 25, 2012
Connecting to SQL 2005 via DBI Perl and Vista problems.
When the perl script is uploaded to my web server the connection is made with
no problems but if I download the file to my local machine and run the file I
get "[Microsoft][ODBC Driver Manager] Data source name not found and no
default driver specified (SQL-IM002)(DBD: db_login/SQLConnect err=-1);" I
have added the DSN into Vista 6 times and the test run fine but I can not run
this perl script, or any other perl script that uses DBI to get to the SQL
server. Can anyone help me?
Never Mind, found it. Why do the answers only show up after asking for help.
Found this site
http://msmvps.com/blogs/spywaresucks/archive/2007/05/11/897398.aspx
and whent via run command to the syswow64 version of ODBC and added it in
there and worked. But I find it really odd that when I when to the ODBC via
Admin Tools in Control Panel it was not working. O, well.
"Eagle_f90" wrote:
> I am trying to connect to a 2005 SQL server though perl using the DBI module.
> When the perl script is uploaded to my web server the connection is made with
> no problems but if I download the file to my local machine and run the file I
> get "[Microsoft][ODBC Driver Manager] Data source name not found and no
> default driver specified (SQL-IM002)(DBD: db_login/SQLConnect err=-1);" I
> have added the DSN into Vista 6 times and the test run fine but I can not run
> this perl script, or any other perl script that uses DBI to get to the SQL
> server. Can anyone help me?
Connecting to SQL 2005 via DBI Perl and Vista problems.
.
When the PERL script is uploaded to my web server the connection is made wit
h
no problems but if I download the file to my local machine and run the file
I
get "[Microsoft][ODBC Driver Manager] Data source name not found and
no
default driver specified (SQL-IM002)(DBD: db_login/SQLConnect err=-1);" I
have added the DSN into Vista 6 times and the test run fine but I can not ru
n
this PERL script, or any other PERL script that uses DBI to get to the SQL
server. Can anyone help me?Never Mind, found it. Why do the answers only show up after asking for help.
Found this site
http://msmvps.com/blogs/spywaresuck.../11/897398.aspx
and whent via run command to the syswow64 version of ODBC and added it in
there and worked. But I find it really odd that when I when to the ODBC via
Admin Tools in Control Panel it was not working. O, well.
"Eagle_f90" wrote:
> I am trying to connect to a 2005 SQL server though PERL using the DBI modu
le.
> When the PERL script is uploaded to my web server the connection is made w
ith
> no problems but if I download the file to my local machine and run the fil
e I
> get "[Microsoft][ODBC Driver Manager] Data source name not found a
nd no
> default driver specified (SQL-IM002)(DBD: db_login/SQLConnect err=-1);" I
> have added the DSN into Vista 6 times and the test run fine but I can not
run
> this PERL script, or any other PERL script that uses DBI to get to the SQL
> server. Can anyone help me?
Thursday, March 8, 2012
Connecting to an external SQL 2000 Server from a Vista machine with SQL 2005 installed
hi there - I'm praying someone here can shed some light on this - after many google and web searches, I have found users with similar issues, but have yet to find a solution.
Problem:I have recently upgraded my desktop from Windows XP to Windows Vista Ultimate (clean install) and have migrated my local machine to SQL Server 2005. However I have a number of .Net projects that access databased on another server running SQL Server 2000 - prior to my upgrade to Vista, I was running SQL Server 2000 on my desktop as well. During the install, everything seemed to go well, and I also installed the SQL Server 2005 Service pack as instructed via the MSDN site. However, when attempting to test my .net projects on my desktop pc (ie visithttp://localhost), I encounter the error:
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 settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
note that the server I am attempting to connectTO is the old SQL 2000 server - NOT 2005. I specify my connection info in the web.config - and it points to an external ip address on the web.
Can anyone shed some light on this? I've tried enabling remote access on my local SQL 2005 install, but I'm fairly sure thats for servers that want to connect to my desktop, rather than my desktop attempting to connect to external servers. Any help is greatly appreciated - I'm pulling my hair out over trying to figure this out! :)
To summarize my setup (if it helps)
Desktop PC:
Windows Vista (Ultimate)
SQL Server 2005
Visual Studio 2005
II 7.0
.Net 2.0 (ASP.Net Application)
External Server (co-located at a datacenter)
Windows Server 2003
SQL Server 2000
IIS 6.0
.Net 2.0 (ASP.Net Application)
Much appreciated,
Ted
http://forums.asp.net/thread/1476735.aspx|||
Hi Al - thanks for the reply!
I followed the instructions, but am still running into the error. To re-state, the server my code is trying to connect to is only running SQL Server 2000, not SQL Server 2005. Can you enlighten me as to why I'd be getting an error stating that it is trying to connect to a 2005 database?
Much appreciated!
|||Very confused, I believe there is a bug in the provider, I seen a post before with a msdn2 link. I'll try to find it and post it in this thread|||Did anyone here got hold of this issue. Could someone shed some light ?
|||I've just run into exactly the same issue as that described in the beginning of this thread. Is there a solution out there for this problem? I'm running Vista Ultimate and Visual Studio 2005, but only SQL Server Management Studio Express.
Wednesday, March 7, 2012
connecting to a distant SQL server installed on VISTA
I'm running an SQL server 2005 on a VISTA based machine.
When I use the management studio from the local machine everything
looks fine.
When I try to connect to that server using a managment tool from a
distant machine I'm able to do so but whan I connect to the server I
do not see the 'green play icon' but a white empty circle nor can I
stop\start that instance.
I'm able to connect to that server and use it from distant but the
connection is quite slow and has many unexplained delays.
tcp 1433 and udp 1434 are opened and both named pipes and TCP\IP are
enabled.
Am I missing something ?
thnak you for your response.
Gilad.
Gilad,
Can you give us more detail about what you mean when you say a distant
server? Are you connecting to a network through a VPN and connecting to a
server?
Can you connect to a distant server that has access to the SQL Server but
through its own local network? (for example with a remote desktop connection)
The connection is solid and if something happens to the connection, you can
log back into the machine on the local network and continue where you left
off.
A slow VPN that can be disconnected in the middle of a query is a shaky
method for doing remote work.
Regards,
Jamie
"Gilad" wrote:
> Hi,
> I'm running an SQL server 2005 on a VISTA based machine.
> When I use the management studio from the local machine everything
> looks fine.
> When I try to connect to that server using a managment tool from a
> distant machine I'm able to do so but whan I connect to the server I
> do not see the 'green play icon' but a white empty circle nor can I
> stop\start that instance.
> I'm able to connect to that server and use it from distant but the
> connection is quite slow and has many unexplained delays.
> tcp 1433 and udp 1434 are opened and both named pipes and TCP\IP are
> enabled.
> Am I missing something ?
> thnak you for your response.
> Gilad.
>
connecting to a distant SQL server installed on VISTA
I'm running an SQL server 2005 on a VISTA based machine.
When I use the management studio from the local machine everything
looks fine.
When I try to connect to that server using a managment tool from a
distant machine I'm able to do so but whan I connect to the server I
do not see the 'green play icon' but a white empty circle nor can I
stop\start that instance.
I'm able to connect to that server and use it from distant but the
connection is quite slow and has many unexplained delays.
tcp 1433 and udp 1434 are opened and both named pipes and TCP\IP are
enabled.
Am I missing something ?
thnak you for your response.
Gilad.Gilad,
Can you give us more detail about what you mean when you say a distant
server? Are you connecting to a network through a VPN and connecting to a
server?
Can you connect to a distant server that has access to the SQL Server but
through its own local network? (for example with a remote desktop connection)
The connection is solid and if something happens to the connection, you can
log back into the machine on the local network and continue where you left
off.
A slow VPN that can be disconnected in the middle of a query is a shaky
method for doing remote work.
--
Regards,
Jamie
"Gilad" wrote:
> Hi,
> I'm running an SQL server 2005 on a VISTA based machine.
> When I use the management studio from the local machine everything
> looks fine.
> When I try to connect to that server using a managment tool from a
> distant machine I'm able to do so but whan I connect to the server I
> do not see the 'green play icon' but a white empty circle nor can I
> stop\start that instance.
> I'm able to connect to that server and use it from distant but the
> connection is quite slow and has many unexplained delays.
> tcp 1433 and udp 1434 are opened and both named pipes and TCP\IP are
> enabled.
> Am I missing something ?
> thnak you for your response.
> Gilad.
>
Sunday, February 12, 2012
Connect to SQL Server from Vista Client Issues
A Couple of months ago I came with the issue of connecting to a SQL server instance from my vista machine (which is my dev machine)
It always gave me errors, and even after following microsofts instructions , couldnt get it to work.
However some fine print in some site (cant recall which site) instructed to turn off the windows firewall while connecting to sql server.
Has anyone come across this , and has found an alternative to this?
Seems if my clients turn to vista (Which unfortunately they are very keen to) might have to keep their firewalls off all the time.
ThanksUnfortunately I am not a network engineer but I think there is a possibility to configure a port through which connection should be established. Each server has a default port to go through but it possibly could be configured.
Don't ask me how to do it because I don't know... :)|||Sounds fair enough.
So now My target is to find which port is used to connect to the remote sql server. I presume I would have to look into network packet analyserz to find it out.
I can feel that i need to face my weakest problems (networking)
thanks a lot for that...sounds like a good direction|||Hi Again,
Followed your direction,
And installled wireshark, and got a few porst that ms sql server was trying to call. - around 3- 4 differetn ones
So went to the firewall and opened them.
Now when i retried connecting to sql server...it started to use some completely different ports...(so it port hopping or something)
There is this other wthing that i discovered, Once you turn your firewall off and connect to the remote sql, you can turn the firewall back on.
and it still works. Now if you disconnect the connection to the server, and then try to connect once again, it works fine
however if you close the management studio, then on restarting the studio, and then try connecting to the remote server, that fails.
So .... Anything that anyone can see?
Or do i post a topic on the networking forum?
cheers|||When you create DSN to the server it does show you port which server is using but I am not sure how it can help you.
I will go to work tomorrow (it is night in NY) and will ask couple of people who deal with it. If I will get more info I will get back to you.
Sorry I am not a big help here just trying to support you... :(|||Oh no...its not an issue
I have been very successful at letting my clients stick to XP, by the time the development time finishes they will still be using XP, so there isint really an issue.
But yea, thanks for your help in giving new a different perspective to this solution.|||
Quote:
Originally Posted by iburyak
When you create DSN to the server it does show you port which server is using but I am not sure how it can help you.
I will go to work tomorrow (it is night in NY) and will ask couple of people who deal with it. If I will get more info I will get back to you.
Sorry I am not a big help here just trying to support you... :(
Hi iburyak
Thanks for your reply, i chased this issue with your direction and found out the way out of it.
I have put it into an article (Waiting for the moderator to move it to the SQL server article -- yes im dumb, i put it into the .Net articles)
Connect Remote SQL instance from Vista Client
thanks a lot for the help :)|||Hey thanks for your respond.
I knew it could be done through port. :)
Be careful thou giving away port number even thou it is 1433 for SQL servers but not for Sybase, Oracle or as you said in cases when port has been changed.
I found easy way of finding port when you create a valid DSN to the server and go back to edit it in advanced screen it does show you a port number. :)
Anyway I am very happy that you solved this problem and didnt have to put your firewall down.
I knew about a port because I had to change some of my applications to Web Services which use a different port because my network administrators didnt wanted to open that port for a database access on servers.