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

[karim]

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

[George Ter-Saakov]

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" <greg_burns@hotmail.com> wrote in message
news:eEIQtbCPDHA.3836@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" <karim3411@11yahoo11.com> wrote in message
> news:51d7328dd12955b6cb66750b28df488b@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

>
>