MSSQL2K ODBC in WinXP Pro

MSSQL2K ODBC in WinXP Pro

Post by Larry Stal » Wed, 06 Aug 2003 23:42:05


Recently upgraded a development station from Win2K Pro to
WinXP Pro. It has a MSSQL2K Personal Edition running so
it can be used for development when not connected to the
company domain (with MSSQL2K servers). It is used for
VStudio 6.0 and VStudio.Net development.

Recently, while not connected to the network, I found
that when I tried to make a new DSN in ODBC for SQL
Server, NO servers were enumerated, not even "(local)".
If I force "(local)" as the server, the connection is
established. However, if I use Query Builder in VStudio
6, unless I use the prevously created DSN, no servers are
enumerated. The worst part is using VB.Net, I get OLEDB
data objects instead of SQL. I tried re-installing
VStudio.Net, .Net Framework, and MSSQL2K and SP3, but no
change.

When I'm off the domain, the log-in switched to "Fast
User Switching" mode. COuld this be the source of the
problem??
 
 
 

MSSQL2K ODBC in WinXP Pro

Post by Larry Stal » Thu, 07 Aug 2003 03:15:18

Tried shutting off "fast user switching", but still have
the same problem.

 
 
 

MSSQL2K ODBC in WinXP Pro

Post by billchn » Fri, 08 Aug 2003 02:07:40

Hi Larry,

It seems that you want Query Builder in VStudio 6 and VB.Net to enumerate
SQL Server instances on the network. Am I right? If so, it seems that the
problem is the functionality of these specific tools and I would suggest
that you check with newsgroups specific to these tools, e.g.
microsoft.public.vsnet.ide.


Bill Cheng
Microsoft Online Partner Support

Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
--------------------
| Content-Class: urn:content-classes:message
| From: "Larry Stall" < XXXX@XXXXX.COM >
| Sender: "Larry Stall" < XXXX@XXXXX.COM >
| Subject: MSSQL2K ODBC in WinXP Pro
| Date: Tue, 5 Aug 2003 07:42:05 -0700
| Lines: 20
| Message-ID: <0dd501c35b5f$bd8c38d0$ XXXX@XXXXX.COM >
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="iso-8859-1"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
| Thread-Index: AcNbX72JlEoeybbQSVu/wDnRHzxzZg==
| Newsgroups: microsoft.public.sqlserver.odbc
| Path: cpmsftngxa06.phx.gbl
| Xref: cpmsftngxa06.phx.gbl microsoft.public.sqlserver.odbc:39377
| NNTP-Posting-Host: TK2MSFTNGXA11 10.40.1.163
| X-Tomcat-NG: microsoft.public.sqlserver.odbc
|
| Recently upgraded a development station from Win2K Pro to
| WinXP Pro. It has a MSSQL2K Personal Edition running so
| it can be used for development when not connected to the
| company domain (with MSSQL2K servers). It is used for
| VStudio 6.0 and VStudio.Net development.
|
| Recently, while not connected to the network, I found
| that when I tried to make a new DSN in ODBC for SQL
| Server, NO servers were enumerated, not even "(local)".
| If I force "(local)" as the server, the connection is
| established. However, if I use Query Builder in VStudio
| 6, unless I use the prevously created DSN, no servers are
| enumerated. The worst part is using VB.Net, I get OLEDB
| data objects instead of SQL. I tried re-installing
| VStudio.Net, .Net Framework, and MSSQL2K and SP3, but no
| change.
|
| When I'm off the domain, the log-in switched to "Fast
| User Switching" mode. COuld this be the source of the
| problem??
|
 
 
 

MSSQL2K ODBC in WinXP Pro

Post by Larry Stal » Fri, 08 Aug 2003 03:18:02

1) The VS tools used to work fine before I upgraded to
Win XP.
2) They also work fine on 2003 Server platform.
3) Also, the ODBC administration tool is unable to find
the SQL instance.

I don't believe it's a VStudio or VS.Net problem.

Thanks anyway.

VB.Net to enumerate
it seems that the
I would suggest
e.g.
confers no rights.
V5.50.4910.0300
microsoft.public.sqlserver.odbc:39377
to
so
the
even "(local)".
VStudio
are
OLEDB
no
 
 
 

MSSQL2K ODBC in WinXP Pro

Post by Larry Stal » Sat, 09 Aug 2003 22:41:41

ill,

The problem occurs in ODBC administrator (which VStudio
and VS.Net use to establish DB connections). NO sql
servers are enumerated in the "Server list" of the DSN or
connection configuration. I should at least
see "(local)".

I have removed and re-installed all components and SP's.
I have upgraded to MDAC 2.8. I have tried multiple
instances of SQL Server. I have used the "rebuild damaged
registry hive" in the SQL Server setup program. All to no
avail.

The only program that appears to be aware that MSSQL is
on the machine is the MSSQL MMC itself. One thing I've
noticed is that after installing MSSQL on this machine,
when I open MSSQL Enterprise Manager and attempt to add
the local registration, it does NOT list it as (local),
only by the computer name. And if I try to connect using
Windows security account (instead of SQL Server
authentication), the registration fails.

Hopefully this will clarify the problem. Thanks for your
help!

I believe it's a MSSQL/ODBC/registry problem.

to how VS tools
correctly?
let VB.NET enumerate
confers no rights.
V5.50.4910.0300
microsoft.public.sqlserver.odbc:39393
find
so,
and
tools,
and
Pro
running
to
for
found
is
servers
but
to "Fast
the