469,573 Members | 1,681 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 469,573 developers. It's quick & easy.

Can't use 'local' to find sql server instances on local machine


My computer (connected to a domain) is having trouble connecting to the
local MSDE when using 'local' or '(local)' as server name. The only way I
can connect to server through Visual Studio or DTS in Enterprise manager is
when using domainname\localcomputername format. Also when I try to install
the starter kits from asp.net, the installer in each kit fails to find sql
server instances. I am pretty sure it's related to fact the installer is
probably using 'local' or a derivative for the local server name which does
not work.

Any ideas?

Karim
Nov 17 '05 #1
1 7365
There is always option to run SQL scripts manually.
It's documented in the readme file. I recal i did not have any problem.

George.

"Greg Burns" <gr********@hotmail.com> wrote in message
news:eE**************@tk2msftngp13.phx.gbl...
If you installed the MSDE version for Visual Studios is doesn't create a
"default instance" of MSDE. The instance name is something like,
computername\VSdotNET. (SQL server 2000 allows multiple instances to be
installed and running on one computer).

I remember I had the same problem trying to install the starter kits on my
computer prior to installing a default instance. Maybe somebody could chip
in, as to how to install the starter kits to a named instance.

BTW, if you install MSDE from the SQL SP3 desktop patch it installs as the
default instance.

HTH,
Greg

"karim" <ka*******@11yahoo11.com> wrote in message
news:51******************************@free.teranew s.com...

My computer (connected to a domain) is having trouble connecting to the
local MSDE when using 'local' or '(local)' as server name. The only way I can connect to server through Visual Studio or DTS in Enterprise manager

is
when using domainname\localcomputername format. Also when I try to install the starter kits from asp.net, the installer in each kit fails to find sql server instances. I am pretty sure it's related to fact the installer is
probably using 'local' or a derivative for the local server name which

does
not work.

Any ideas?

Karim


Nov 17 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

1 post views Thread by Raquel | last post: by
7 posts views Thread by David Thielen | last post: by
18 posts views Thread by =?Utf-8?B?SGVyYg==?= | last post: by
reply views Thread by suresh191 | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.