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

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.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

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

Connecting to Local Database after Application Install

I have created an application which uses a SQL Express database. The program runs fine on the the computer where I built the app, however when I install the app on another computer I get an error telling me that under default SQL Express does not allow remote connections. The problem is that I dont want a remote connection I want a local connection, the database file is on the commputer. How can do get my application to look for the database on the local machine.

My connection string is:

Data Source=(local)\SQLEXPRESS;Initial Catalog="C:\DOCUMENTS AND SETTINGS\ADMINISTRATOR\PLDAQ.MDF";Integrated Security=True

I have made sure that the file is in the correct directory.

Any help would be greatly appretiated

hi,

the folder you are referencing is not a "standard" one in the "traditional" sense of SQL Server, and you can get problems if the account running the instance is not able to access that path... and anyway you should reference the intital catalog in the connection string via the "logical" name and not the physical primary data file name, thus
Data Source=(local)\SQLEXPRESS;Initial Catalog=dbLogicalFileName;Integrated Security=True
or use the AttachDBFilename feature of the User Instances mode..

try modifying the connection string to see if you are granted connection to the instance you are dealing with, as the exception you are reporting is quite a generic connection exception..

regards

|||

Andrea

I still have the same problem, I have updated my connection string to this:

Data Source = .\SQLEXPRESS;AttachDBFilename = [DataDirectory]\PLDaq.mdf;Integrated Security = True; UserInstance = False

I have managed to get arround the error by changeing the name of the non-design computer to mach the name of the design computer, this however, as I am sure you will agree, is only temporary as I don't want to have to change the name of every computer that I install this application on, what do I need to do to rectify this situation.

|||

hi,

as you are not using "User Instances", I'd not go for the AttachDBFileName property of the connection string.. I'd attach/create the database once and then I'd go for the "traditional" Database=yourDbName property of the connection string...

I have managed to get arround the error by changeing the name of the non-design computer to mach the name of the design computer

do you mean by that you "named" the destination computer the same as your dev pc? this is obviously not "mandatory"...

what is your |DataDirectory| value?

regards

|||

do you mean by that you "named" the destination computer the same as your dev pc? this is obviously not "mandatory"...

Unfortunatly this is the only way it will not generate the error posted above. Like I said the program is looking for a remote connection but I want a local one. So I tricked it into thinking that it was running on the dev computer by changeing the name. I will agree that this is obviously not convient, but that is why I am posting I just cant figure out how to fix it.

The |DataDirectory| tells the connection to look in the bin\debug folder during dev time, and also to look into the bin\data folder at run time, after installation obviously. So when the program is installed and all data files are stored in the (AppPath)\bin\data directory and that is where the program is supposed to look for the data files (e.g. Database and Log files), however, if the non dev computer has a different name it trys to find the dev computer to connect to the database, a remote connection, It cant do this as it is not connected to any network.

I have tryed the traditional Database = yourDbName and that causes the same problem

Also There may come a time when I want to use User Instances, but for the time being I just want the thing to work.

|||

PEng1 wrote:

Unfortunatly this is the only way it will not generate the error posted above. Like I said the program is looking for a remote connection but I want a local one. So I tricked it into thinking that it was running on the dev computer by changeing the name. I will agree that this is obviously not convient, but that is why I am posting I just cant figure out how to fix it.

the fix is using

Data Source = .\SQLEXPRESS or Data Source = (Local)\SQLEXPRESS property in the connection string...

here you have to specify the instance you have to connect to, and you can provide "." and/or "(Local)" for "local" connections"...

The |DataDirectory| tells the connection to look in the bin\debug folder during dev time, and also to look into the bin\data folder at run time, after installation obviously. So when the program is installed and all data files are stored in the (AppPath)\bin\data directory and that is where the program is supposed to look for the data files (e.g. Database and Log files), however, if the non dev computer has a different name it trys to find the dev computer to connect to the database, a remote connection, It cant do this as it is not connected to any network.

pay attention to your "custom data folder"... consider that the account running the SQLExpress intstance required adeguate NTFS permissions to that folder.. and consider Vista "headaches"/requirements with regard writing in Program Files folder...

regards

|||

Andrea,

I guess that I had the answer for a while and just didn't bother to check if it would work with a different name, or I changed something and just don't remeber what, probably the latter of the two, either way, the problem is resolved and I am greatly indebted for all of your help. Thanks a lot.

This program will be run on Windows 2000 for quite a while but it will eventually have to be moved to Vista or higher, what "headaches" are you refering to, I am not at all familiar with Vista since the company I work for still has some machines that are running 95 and One that is running DOS, yeah thats right I said DOS. I guess however that I should probably read up on the New OS any recomended reading?

|||

hi,

PEng1 wrote:

Andrea,

I guess that I had the answer for a while and just didn't bother to check if it would work with a different name, or I changed something and just don't remeber what, probably the latter of the two, either way, the problem is resolved and I am greatly indebted for all of your help. Thanks a lot.

This program will be run on Windows 2000 for quite a while but it will eventually have to be moved to Vista or higher, what "headaches" are you refering to, I am not at all familiar with Vista since the company I work for still has some machines that are running 95 and One that is running DOS, yeah thats right I said DOS. I guess however that I should probably read up on the New OS any recomended reading?

start reading at http://technet.microsoft.com/en-us/windowsvista/aa905108.aspx, http://technet.microsoft.com/en-us/windowsvista/aa906021.aspx, ....

and look in this forum for Vista troubles with UAC..

regards

Connecting to Local Database after Application Install

I have created an application which uses a SQL Express database. The program runs fine on the the computer where I built the app, however when I install the app on another computer I get an error telling me that under default SQL Express does not allow remote connections. The problem is that I dont want a remote connection I want a local connection, the database file is on the commputer. How can do get my application to look for the database on the local machine.

My connection string is:

Data Source=(local)\SQLEXPRESS;Initial Catalog="C:\DOCUMENTS AND SETTINGS\ADMINISTRATOR\PLDAQ.MDF";Integrated Security=True

I have made sure that the file is in the correct directory.

Any help would be greatly appretiated

hi,

the folder you are referencing is not a "standard" one in the "traditional" sense of SQL Server, and you can get problems if the account running the instance is not able to access that path... and anyway you should reference the intital catalog in the connection string via the "logical" name and not the physical primary data file name, thus
Data Source=(local)\SQLEXPRESS;Initial Catalog=dbLogicalFileName;Integrated Security=True
or use the AttachDBFilename feature of the User Instances mode..

try modifying the connection string to see if you are granted connection to the instance you are dealing with, as the exception you are reporting is quite a generic connection exception..

regards

|||

Andrea

I still have the same problem, I have updated my connection string to this:

Data Source = .\SQLEXPRESS;AttachDBFilename = [DataDirectory]\PLDaq.mdf;Integrated Security = True; UserInstance = False

I have managed to get arround the error by changeing the name of the non-design computer to mach the name of the design computer, this however, as I am sure you will agree, is only temporary as I don't want to have to change the name of every computer that I install this application on, what do I need to do to rectify this situation.

|||

hi,

as you are not using "User Instances", I'd not go for the AttachDBFileName property of the connection string.. I'd attach/create the database once and then I'd go for the "traditional" Database=yourDbName property of the connection string...

I have managed to get arround the error by changeing the name of the non-design computer to mach the name of the design computer

do you mean by that you "named" the destination computer the same as your dev pc? this is obviously not "mandatory"...

what is your |DataDirectory| value?

regards

|||

do you mean by that you "named" the destination computer the same as your dev pc? this is obviously not "mandatory"...

Unfortunatly this is the only way it will not generate the error posted above. Like I said the program is looking for a remote connection but I want a local one. So I tricked it into thinking that it was running on the dev computer by changeing the name. I will agree that this is obviously not convient, but that is why I am posting I just cant figure out how to fix it.

The |DataDirectory| tells the connection to look in the bin\debug folder during dev time, and also to look into the bin\data folder at run time, after installation obviously. So when the program is installed and all data files are stored in the (AppPath)\bin\data directory and that is where the program is supposed to look for the data files (e.g. Database and Log files), however, if the non dev computer has a different name it trys to find the dev computer to connect to the database, a remote connection, It cant do this as it is not connected to any network.

I have tryed the traditional Database = yourDbName and that causes the same problem

Also There may come a time when I want to use User Instances, but for the time being I just want the thing to work.

|||

PEng1 wrote:

Unfortunatly this is the only way it will not generate the error posted above. Like I said the program is looking for a remote connection but I want a local one. So I tricked it into thinking that it was running on the dev computer by changeing the name. I will agree that this is obviously not convient, but that is why I am posting I just cant figure out how to fix it.

the fix is using

Data Source = .\SQLEXPRESS or Data Source = (Local)\SQLEXPRESS property in the connection string...

here you have to specify the instance you have to connect to, and you can provide "." and/or "(Local)" for "local" connections"...

The |DataDirectory| tells the connection to look in the bin\debug folder during dev time, and also to look into the bin\data folder at run time, after installation obviously. So when the program is installed and all data files are stored in the (AppPath)\bin\data directory and that is where the program is supposed to look for the data files (e.g. Database and Log files), however, if the non dev computer has a different name it trys to find the dev computer to connect to the database, a remote connection, It cant do this as it is not connected to any network.

pay attention to your "custom data folder"... consider that the account running the SQLExpress intstance required adeguate NTFS permissions to that folder.. and consider Vista "headaches"/requirements with regard writing in Program Files folder...

regards

|||

Andrea,

I guess that I had the answer for a while and just didn't bother to check if it would work with a different name, or I changed something and just don't remeber what, probably the latter of the two, either way, the problem is resolved and I am greatly indebted for all of your help. Thanks a lot.

This program will be run on Windows 2000 for quite a while but it will eventually have to be moved to Vista or higher, what "headaches" are you refering to, I am not at all familiar with Vista since the company I work for still has some machines that are running 95 and One that is running DOS, yeah thats right I said DOS. I guess however that I should probably read up on the New OS any recomended reading?

|||

hi,

PEng1 wrote:

Andrea,

I guess that I had the answer for a while and just didn't bother to check if it would work with a different name, or I changed something and just don't remeber what, probably the latter of the two, either way, the problem is resolved and I am greatly indebted for all of your help. Thanks a lot.

This program will be run on Windows 2000 for quite a while but it will eventually have to be moved to Vista or higher, what "headaches" are you refering to, I am not at all familiar with Vista since the company I work for still has some machines that are running 95 and One that is running DOS, yeah thats right I said DOS. I guess however that I should probably read up on the New OS any recomended reading?

start reading at http://technet.microsoft.com/en-us/windowsvista/aa905108.aspx, http://technet.microsoft.com/en-us/windowsvista/aa906021.aspx, ....

and look in this forum for Vista troubles with UAC..

regards

Connecting to Local Database after Application Install

I have created an application which uses a SQL Express database. The program runs fine on the the computer where I built the app, however when I install the app on another computer I get an error telling me that under default SQL Express does not allow remote connections. The problem is that I dont want a remote connection I want a local connection, the database file is on the commputer. How can do get my application to look for the database on the local machine.

My connection string is:

Data Source=(local)\SQLEXPRESS;Initial Catalog="C:\DOCUMENTS AND SETTINGS\ADMINISTRATOR\PLDAQ.MDF";Integrated Security=True

I have made sure that the file is in the correct directory.

Any help would be greatly appretiated

hi,

the folder you are referencing is not a "standard" one in the "traditional" sense of SQL Server, and you can get problems if the account running the instance is not able to access that path... and anyway you should reference the intital catalog in the connection string via the "logical" name and not the physical primary data file name, thus
Data Source=(local)\SQLEXPRESS;Initial Catalog=dbLogicalFileName;Integrated Security=True
or use the AttachDBFilename feature of the User Instances mode..

try modifying the connection string to see if you are granted connection to the instance you are dealing with, as the exception you are reporting is quite a generic connection exception..

regards

|||

Andrea

I still have the same problem, I have updated my connection string to this:

Data Source = .\SQLEXPRESS;AttachDBFilename = [DataDirectory]\PLDaq.mdf;Integrated Security = True; UserInstance = False

I have managed to get arround the error by changeing the name of the non-design computer to mach the name of the design computer, this however, as I am sure you will agree, is only temporary as I don't want to have to change the name of every computer that I install this application on, what do I need to do to rectify this situation.

|||

hi,

as you are not using "User Instances", I'd not go for the AttachDBFileName property of the connection string.. I'd attach/create the database once and then I'd go for the "traditional" Database=yourDbName property of the connection string...

I have managed to get arround the error by changeing the name of the non-design computer to mach the name of the design computer

do you mean by that you "named" the destination computer the same as your dev pc? this is obviously not "mandatory"...

what is your |DataDirectory| value?

regards

|||

do you mean by that you "named" the destination computer the same as your dev pc? this is obviously not "mandatory"...

Unfortunatly this is the only way it will not generate the error posted above. Like I said the program is looking for a remote connection but I want a local one. So I tricked it into thinking that it was running on the dev computer by changeing the name. I will agree that this is obviously not convient, but that is why I am posting I just cant figure out how to fix it.

The |DataDirectory| tells the connection to look in the bin\debug folder during dev time, and also to look into the bin\data folder at run time, after installation obviously. So when the program is installed and all data files are stored in the (AppPath)\bin\data directory and that is where the program is supposed to look for the data files (e.g. Database and Log files), however, if the non dev computer has a different name it trys to find the dev computer to connect to the database, a remote connection, It cant do this as it is not connected to any network.

I have tryed the traditional Database = yourDbName and that causes the same problem

Also There may come a time when I want to use User Instances, but for the time being I just want the thing to work.

|||

PEng1 wrote:

Unfortunatly this is the only way it will not generate the error posted above. Like I said the program is looking for a remote connection but I want a local one. So I tricked it into thinking that it was running on the dev computer by changeing the name. I will agree that this is obviously not convient, but that is why I am posting I just cant figure out how to fix it.

the fix is using

Data Source = .\SQLEXPRESS or Data Source = (Local)\SQLEXPRESS property in the connection string...

here you have to specify the instance you have to connect to, and you can provide "." and/or "(Local)" for "local" connections"...

The |DataDirectory| tells the connection to look in the bin\debug folder during dev time, and also to look into the bin\data folder at run time, after installation obviously. So when the program is installed and all data files are stored in the (AppPath)\bin\data directory and that is where the program is supposed to look for the data files (e.g. Database and Log files), however, if the non dev computer has a different name it trys to find the dev computer to connect to the database, a remote connection, It cant do this as it is not connected to any network.

pay attention to your "custom data folder"... consider that the account running the SQLExpress intstance required adeguate NTFS permissions to that folder.. and consider Vista "headaches"/requirements with regard writing in Program Files folder...

regards

|||

Andrea,

I guess that I had the answer for a while and just didn't bother to check if it would work with a different name, or I changed something and just don't remeber what, probably the latter of the two, either way, the problem is resolved and I am greatly indebted for all of your help. Thanks a lot.

This program will be run on Windows 2000 for quite a while but it will eventually have to be moved to Vista or higher, what "headaches" are you refering to, I am not at all familiar with Vista since the company I work for still has some machines that are running 95 and One that is running DOS, yeah thats right I said DOS. I guess however that I should probably read up on the New OS any recomended reading?

|||

hi,

PEng1 wrote:

Andrea,

I guess that I had the answer for a while and just didn't bother to check if it would work with a different name, or I changed something and just don't remeber what, probably the latter of the two, either way, the problem is resolved and I am greatly indebted for all of your help. Thanks a lot.

This program will be run on Windows 2000 for quite a while but it will eventually have to be moved to Vista or higher, what "headaches" are you refering to, I am not at all familiar with Vista since the company I work for still has some machines that are running 95 and One that is running DOS, yeah thats right I said DOS. I guess however that I should probably read up on the New OS any recomended reading?

start reading at http://technet.microsoft.com/en-us/windowsvista/aa905108.aspx, http://technet.microsoft.com/en-us/windowsvista/aa906021.aspx, ....

and look in this forum for Vista troubles with UAC..

regards

Connecting to Database On windows 5.0 CE Device.

I'm a beginner in the Visual Studio Development for Mobile Devices.

I'm trying to develop a small program for a PSC Falcon handheld Scanner.

Particluars are

VS 2005 SP1

SQL Compact Edition

Windows CE 5.0

The test program is just a datagrid viewing data from the database

when the form loads with the following code:

Me.TblDetailsTableAdapter.Fill(Me.Test3DataSet.tblDetails)

trapping the error I get

Error Code: 8007000E

Message :

Minor Code:0

Source : SQL Server Compact Edition ADO.NET Data Provider

The interesting thing is that if I have the Database open in Query Analyzer 3.0.

The program works fine.

Maybe this is relevant: SqlCeCommand objects are not automatically disposed if you use a SqlCeDataAdapter object

http://support.microsoft.com/default.aspx/kb/824462

|||

Thanks for the timely response.

Being under a ending time schedule.

I went in a different direction to collect the scanned data.

Collecting in a Dataset and writing to a txt file.

I'll keep this in mind for future development.

Connecting to an SQL Server using a workgroup

I am trying to I am trying to connect to an SQL Server using a vb.net program. It works if
I put it on the SQL Server computer, but will not connect over my local
network that is set up as a workgroup. I get the following message:
Login failed for user 'DELL4100\Guest'

DELL4100 is the computer name where the sql server is on.

The connection string is:
Data Source=dell4100;Database=dbname;User ID=dbn;Password=password;
I have also tried Integrated Security=SSPI; instead of the User ID &
Password.

I do not know why it is using Guest instead of the User ID that I specified.
So, I created a Login name in the SQL Server called Guest with no password.
I also activated the Guest account in XP for both machines. Still the same
message.

I created accounts for dbn on both computers and gave them the same
password. I logged in under dsn and ran the program, but I still get the
same error.

I turned off the Windows firewall on both computers. I can share files and
printers between computers, just not access the SQL Server.

Can anyone help?

Thanks

Tim
using a vb.net program. It works if
I put it on the SQL Server computer, but will not connect over my local
network that is set up as a workgroup. I get the following message:
Login failed for user 'DELL4100\Guest'

DELL4100 is the computer name where the sql server is on.

The connection string is:
Data Source=dell4100;Database=dbname;User ID=dbn; Password=password;
I have also tried Integrated Security=SSPI; instead of the User ID &
Password.

I do not know why it is using Guest instead of the User ID that I specified.
So, I created a Login name in the SQL Server called Guest with no password.
I also activated the Guest account in XP for both machines. Still the same
message.

I created accounts for dbn on both computers and gave them the same
password. I logged in under dsn and ran the program, but I still get the
same error.

I turned off the Windows firewall on both computers. I can share files and
printers between computers, just not access the SQL Server.

Can anyone help?

Thanks

TimSomehow my message got mangled. I was editing the message and the time limit expired.

I wanted to add that the SQL Server is on an XP pro sp2 machine and that tcp/ip and Names Pipes are enabled and that it is listening on port 1433.|||I have the same issue, is there already an solution ?|||Try to create DSN to the server on your computer. If it doesn't work then it is not your code is a problem.
It is my only guess your SQL drivers are corrupt.|||I have the same question too. I just had to reinstall SQL server on a lab server that crashed, used to have a 'domain' windows 2003 setup but for some reason was set up as a peer-to-peer workgroup. Old way was to create sqlserver logins like: Workstation1\JoeDoe... now it says that is not a legal login, and I can;t 'find' anything but the server name? (I can otherwise access shared files between machines, etc.) . Is there some sql server issue with peer-to-peer networks?

Connecting to AdventureWorks2000_Data.mdf

When I try to connect to this AdventureWorks2000_Data.mdf, I get the following message:

The file "C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\AdventureWorks2000_Data.mdf" is compressed but does not reside in a read-only database or filegroup. The file must be decompressed.

Could not open new database 'AdventureWorks2000'. CREATE DATABASE is aborted. (Microsoft SQL Server, Error: 5118)

Any ideas on how to get the local version installed of SQL Server to open this db? I'm trying to follow along with the examples in the book "Beginning Transact-SQL with SQL Server 2000 and 2005".

Thanks,

Vanzant

Run a sp_helpdb to check all the databases in your server just to make sure you do have the AdventureWorks2000 database. If not, you can download it from

http://www.microsoft.com/downloads/details.aspx?FamilyID=487C9C23-2356-436E-94A8-2BFB66F0ABDC&displaylang=en

|||

Is C: a compressed volume? If so, SQL Server does not support compressed volumes.

Read SQL Server databases are not supported on compressed volumes

|||http://blogs.msdn.com/sanchan/archive/2006/06/04/617585.aspx FYI.|||

I don't think C: is a compressed volume. The only thing I know to check is the disk properties when right click on C:. It isn't selected on the "compress drive to save disk space". If there is another place to check/correct, please let me know.

I can open the AdventureWorks_Data.mdf. I don't know if this matters but I have SQL Server 2005 and SQL Server Express installed on my local PC. This is where I'm trying to look at the files. I'm not sure the differences between the AdventureWorks_Data and AdventureWorks2000_Data, but I don't understand why I can't open the '2000' version.

Any ideas/help would be greatly appreciated.

Thanks,

Vanzant

|||

I think I've figured it out. There are two folders (MSSQL and MSSQL.1) under the Microsoft SQL Server folder. I attached the 2000 db in the MSSQL folder and it worked. I guess it is a newbie issue.

Thanks for inputs!

CONNECTING SQL 2005 TO SYSTEM DNS ODBC?

Hi

I have a server with SQL 2005 and I have second server with spesial database program on it from IBM and I have installed a spesial ODBC DRIVER from IBM so I can make a connection in system dns.

On my server 1 where I have the sql 2005 I have made a connection in system dns.

HOW CAN I TELL SQL 2005 TO CONNECT TO MY CONNECTION AND GET DATA FROM DER?

It's DSN rather than DNS.

Please check this page for connection string using DSN: http://www.connectionstrings.com/?carrier=dsn

CONNECTING SQL 2005 TO SYSTEM DNS ODBC?

Hi

I have a server with SQL 2005 and I have second server with spesial database program on it from IBM and I have installed a spesial ODBC DRIVER from IBM so I can make a connection in system dns.

On my server 1 where I have the sql 2005 I have made a connection in system dns.

HOW CAN I TELL SQL 2005 TO CONNECT TO MY CONNECTION AND GET DATA FROM DER?

It's DSN rather than DNS.

Please check this page for connection string using DSN: http://www.connectionstrings.com/?carrier=dsn

Connecting a SQL-DMO 7 client program to a sql 2K server

Hi,
We are running a client program on NT 4 using SQL-DMO objects. We have
upgraded the server (on another box) from NT4/Sqlserver 7 to WS
2003/Sqlserver 2K. Our Sql-DMO program is now returning an error.
We would like to avoid to upgrade the NT4 client box for stability reasons.
The doc is unclear to say if the sql-dmo 7 is compatible with sqlserver 2K.
Does somebody as tested this configuration ? What can we test to track down
this problem ?
Thanks in advance for your help.
Hi
DMO v7.0 is not compatible with DMO 2000.
You need to upgrade in any case due to the end of support for NT 4.0 by
Microsoft.
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/
"Phil" <PhilG@.newgroups.nospam> wrote in message
news:2CE0791B-7D6F-4160-BC7B-CA87C469AF99@.microsoft.com...
> Hi,
> We are running a client program on NT 4 using SQL-DMO objects. We have
> upgraded the server (on another box) from NT4/Sqlserver 7 to WS
> 2003/Sqlserver 2K. Our Sql-DMO program is now returning an error.
> We would like to avoid to upgrade the NT4 client box for stability
> reasons.
> The doc is unclear to say if the sql-dmo 7 is compatible with sqlserver
> 2K.
> Does somebody as tested this configuration ? What can we test to track
> down
> this problem ?
> Thanks in advance for your help.

Connecting a SQL-DMO 7 client program to a sql 2K server

Hi,
We are running a client program on NT 4 using SQL-DMO objects. We have
upgraded the server (on another box) from NT4/Sqlserver 7 to WS
2003/Sqlserver 2K. Our Sql-DMO program is now returning an error.
We would like to avoid to upgrade the NT4 client box for stability reasons.
The doc is unclear to say if the sql-dmo 7 is compatible with sqlserver 2K.
Does somebody as tested this configuration ? What can we test to track down
this problem ?
Thanks in advance for your help.Hi
DMO v7.0 is not compatible with DMO 2000.
You need to upgrade in any case due to the end of support for NT 4.0 by
Microsoft.
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/
"Phil" <PhilG@.newgroups.nospam> wrote in message
news:2CE0791B-7D6F-4160-BC7B-CA87C469AF99@.microsoft.com...
> Hi,
> We are running a client program on NT 4 using SQL-DMO objects. We have
> upgraded the server (on another box) from NT4/Sqlserver 7 to WS
> 2003/Sqlserver 2K. Our Sql-DMO program is now returning an error.
> We would like to avoid to upgrade the NT4 client box for stability
> reasons.
> The doc is unclear to say if the sql-dmo 7 is compatible with sqlserver
> 2K.
> Does somebody as tested this configuration ? What can we test to track
> down
> this problem ?
> Thanks in advance for your help.

Connect via workgroup

I am trying to connect to an SQL Server using a vb.net program. It works if
I put it on the SQL Server computer, but will not connect over my local
network that is set up as a workgroup. I get the following message:
Login failed for user 'DELL4100\Guest'
DELL4100 is the computer name where the sql server is on.
The connection string is:
Data Source=dell4100;Database=dbname;User ID=dbn;Password=password;
I have also tried Integrated Security=SSPI; instead of the User ID &
Password.
I do not know why it is using Guest instead of the User ID that I specified.
So, I created a Login name in the SQL Server called Guest with no password.
I also activated the Guest account in XP for both machines. Still the same
message.
I created accounts for dbn on both computers and gave them the same
password. I logged in under dsn and ran the program, but I still get the
same error.
I turned off the Windows firewall on both computers. I can share files and
printers between computers, just not access the SQL Server.
Can anyone help?
Thanks
Tim
You don't mention the editions of the operating systems
involved. With XP home, authentication is done using the
guest account as simple file sharing is always enabled on XP
Home. You could hit the issue with XP Pro if simple file
sharing is used. How you address the issue depends somewhat
on what specific operating systems are involved. Refer to
the following for more info:
SQL Server clients are authenticated as guests if Simple
File Sharing is enabled
http://support.microsoft.com/?id=831133
That's one of the issues...
For a connection string, you supply the user and password if
you are using SQL authentication. You use Integrated
Security=SSPI if you want to connect using Windows
Authentication. That's the purpose of switching those
around.
Then...if you want to use Windows Authentication, you aren't
in a domain so credentials aren't passed. You need to have
the same windows accounts with the same passwords on both
boxes.
-Sue
On Fri, 3 Nov 2006 13:16:38 -0700, ".netnew"
<vbopen@.yahoo.com> wrote:

>I am trying to connect to an SQL Server using a vb.net program. It works if
>I put it on the SQL Server computer, but will not connect over my local
>network that is set up as a workgroup. I get the following message:
>Login failed for user 'DELL4100\Guest'
>DELL4100 is the computer name where the sql server is on.
>The connection string is:
>Data Source=dell4100;Database=dbname;User ID=dbn;Password=password;
>I have also tried Integrated Security=SSPI; instead of the User ID &
>Password.
>I do not know why it is using Guest instead of the User ID that I specified.
>So, I created a Login name in the SQL Server called Guest with no password.
>I also activated the Guest account in XP for both machines. Still the same
>message.
>I created accounts for dbn on both computers and gave them the same
>password. I logged in under dsn and ran the program, but I still get the
>same error.
>I turned off the Windows firewall on both computers. I can share files and
>printers between computers, just not access the SQL Server.
>Can anyone help?
>Thanks
>Tim
>
>
>
|||Thanks for the reply.
The SQL Server is on XP pro and the workstation is XP Home. Reading the link
you provided, it seems my problem is related to the Simple File Sharing only
being able to log in as Guest. While this article describes the problem and
causes, it doesn't say if there is a solution.
Is there a way for XP Home to access SQL Server databases?
Tim
"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
news:089ok2tpemql016he2abrvgatopltrij76@.4ax.com...
> You don't mention the editions of the operating systems
> involved. With XP home, authentication is done using the
> guest account as simple file sharing is always enabled on XP
> Home. You could hit the issue with XP Pro if simple file
> sharing is used. How you address the issue depends somewhat
> on what specific operating systems are involved. Refer to
> the following for more info:
> SQL Server clients are authenticated as guests if Simple
> File Sharing is enabled
> http://support.microsoft.com/?id=831133
> That's one of the issues...
> For a connection string, you supply the user and password if
> you are using SQL authentication. You use Integrated
> Security=SSPI if you want to connect using Windows
> Authentication. That's the purpose of switching those
> around.
> Then...if you want to use Windows Authentication, you aren't
> in a domain so credentials aren't passed. You need to have
> the same windows accounts with the same passwords on both
> boxes.
> -Sue
> On Fri, 3 Nov 2006 13:16:38 -0700, ".netnew"
> <vbopen@.yahoo.com> wrote:
>
|||Try using SQL authentication instead. Otherwise you need to
enable the guest account which isn't a good idea.
-Sue
On Sun, 5 Nov 2006 15:36:20 -0700, ".netnew"
<vbopen@.yahoo.com> wrote:

>Thanks for the reply.
>The SQL Server is on XP pro and the workstation is XP Home. Reading the link
>you provided, it seems my problem is related to the Simple File Sharing only
>being able to log in as Guest. While this article describes the problem and
>causes, it doesn't say if there is a solution.
>Is there a way for XP Home to access SQL Server databases?
>Tim
>
>"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
>news:089ok2tpemql016he2abrvgatopltrij76@.4ax.com.. .
>

Connect via workgroup

I am trying to connect to an SQL Server using a vb.net program. It works if
I put it on the SQL Server computer, but will not connect over my local
network that is set up as a workgroup. I get the following message:
Login failed for user 'DELL4100\Guest'
DELL4100 is the computer name where the sql server is on.
The connection string is:
Data Source=dell4100;Database=dbname;User ID=dbn;Password=password;
I have also tried Integrated Security=SSPI; instead of the User ID &
Password.
I do not know why it is using Guest instead of the User ID that I specified.
So, I created a Login name in the SQL Server called Guest with no password.
I also activated the Guest account in XP for both machines. Still the same
message.
I created accounts for dbn on both computers and gave them the same
password. I logged in under dsn and ran the program, but I still get the
same error.
I turned off the Windows firewall on both computers. I can share files and
printers between computers, just not access the SQL Server.
Can anyone help?
Thanks
TimYou don't mention the editions of the operating systems
involved. With XP home, authentication is done using the
guest account as simple file sharing is always enabled on XP
Home. You could hit the issue with XP Pro if simple file
sharing is used. How you address the issue depends somewhat
on what specific operating systems are involved. Refer to
the following for more info:
SQL Server clients are authenticated as guests if Simple
File Sharing is enabled
http://support.microsoft.com/?id=831133
That's one of the issues...
For a connection string, you supply the user and password if
you are using SQL authentication. You use Integrated
Security=SSPI if you want to connect using Windows
Authentication. That's the purpose of switching those
around.
Then...if you want to use Windows Authentication, you aren't
in a domain so credentials aren't passed. You need to have
the same windows accounts with the same passwords on both
boxes.
-Sue
On Fri, 3 Nov 2006 13:16:38 -0700, ".netnew"
<vbopen@.yahoo.com> wrote:

>I am trying to connect to an SQL Server using a vb.net program. It works if
>I put it on the SQL Server computer, but will not connect over my local
>network that is set up as a workgroup. I get the following message:
>Login failed for user 'DELL4100\Guest'
>DELL4100 is the computer name where the sql server is on.
>The connection string is:
>Data Source=dell4100;Database=dbname;User ID=dbn;Password=password;
>I have also tried Integrated Security=SSPI; instead of the User ID &
>Password.
>I do not know why it is using Guest instead of the User ID that I specified
.
>So, I created a Login name in the SQL Server called Guest with no password.
>I also activated the Guest account in XP for both machines. Still the same
>message.
>I created accounts for dbn on both computers and gave them the same
>password. I logged in under dsn and ran the program, but I still get the
>same error.
>I turned off the Windows firewall on both computers. I can share files and
>printers between computers, just not access the SQL Server.
>Can anyone help?
>Thanks
>Tim
>
>
>|||Thanks for the reply.
The SQL Server is on XP pro and the workstation is XP Home. Reading the link
you provided, it seems my problem is related to the Simple File Sharing only
being able to log in as Guest. While this article describes the problem and
causes, it doesn't say if there is a solution.
Is there a way for XP Home to access SQL Server databases?
Tim
"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
news:089ok2tpemql016he2abrvgatopltrij76@.
4ax.com...
> You don't mention the editions of the operating systems
> involved. With XP home, authentication is done using the
> guest account as simple file sharing is always enabled on XP
> Home. You could hit the issue with XP Pro if simple file
> sharing is used. How you address the issue depends somewhat
> on what specific operating systems are involved. Refer to
> the following for more info:
> SQL Server clients are authenticated as guests if Simple
> File Sharing is enabled
> http://support.microsoft.com/?id=831133
> That's one of the issues...
> For a connection string, you supply the user and password if
> you are using SQL authentication. You use Integrated
> Security=SSPI if you want to connect using Windows
> Authentication. That's the purpose of switching those
> around.
> Then...if you want to use Windows Authentication, you aren't
> in a domain so credentials aren't passed. You need to have
> the same windows accounts with the same passwords on both
> boxes.
> -Sue
> On Fri, 3 Nov 2006 13:16:38 -0700, ".netnew"
> <vbopen@.yahoo.com> wrote:
>
>|||Try using SQL authentication instead. Otherwise you need to
enable the guest account which isn't a good idea.
-Sue
On Sun, 5 Nov 2006 15:36:20 -0700, ".netnew"
<vbopen@.yahoo.com> wrote:

>Thanks for the reply.
>The SQL Server is on XP pro and the workstation is XP Home. Reading the lin
k
>you provided, it seems my problem is related to the Simple File Sharing onl
y
>being able to log in as Guest. While this article describes the problem and
>causes, it doesn't say if there is a solution.
>Is there a way for XP Home to access SQL Server databases?
>Tim
>
>"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
> news:089ok2tpemql016he2abrvgatopltrij76@.
4ax.com...
>

Connect to SQL2000 & SQL 2005

Our current program use ADO to connect oto SQL2000 and run fine.
We are planning to migrate to SQL2005.
When we clean install the SQL2005, create the database, set compatibility
level to 80 and generate the db structure, and migrate data.
When everything is done, we try to use our program to connect to SQL2005
database and find the connection fail.
Even when we use sa as login user and still fail to connect.
Is there any different in connection for SQL2000 & SQL2005?
I remember I have tried upgrade SQL2000 to SQL2005 before and the connection
had no problem to sql2005.
Is there something I forgot to set?
KanAm Tue, 29 Aug 2006 17:38:51 +0800 schrieb Ivan:

> Our current program use ADO to connect oto SQL2000 and run fine.
> We are planning to migrate to SQL2005.
> When we clean install the SQL2005, create the database, set compatibility
> level to 80 and generate the db structure, and migrate data.
> When everything is done, we try to use our program to connect to SQL2005
> database and find the connection fail.
> Even when we use sa as login user and still fail to connect.
> Is there any different in connection for SQL2000 & SQL2005?
> I remember I have tried upgrade SQL2000 to SQL2005 before and the connecti
on
> had no problem to sql2005.
> Is there something I forgot to set?
> Kan
If you did a standard installation then SQL2005 uses the named instance
SQLExpress wich you have to use in your connect string.
If your SQL2005 runs on the same machine as your SQL2000 then maybe SQL2005
listen on another port than the standard port.
And have you allowed remote access in SQL2005?
bye, Helmut|||No, MDAC will work fine with the SQL Server 2005 instance. Although you
can=B4t use some of the new cool features its compatible. Which error do
you get ? Is the SQL Server 2k5 located on the same machine as the 2k
instance ?
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
--