Go to Services and make sure the instance is installed and actually started.
You should see a service called MSSQL$InstanceName Started. Then go to the
Microsoft SQL Server folder under Programs, click on Server Network Utility
and make sure the TCP/IP port for that instance is enabled. If not, enable
it. Also, verify the port number. If that doesn't work, let us know how
you are trying to connect and the exact error you are getting. You also
might want to enable named pipes just for fun and see if that helps.
[quoted text, click to view] "Fredrik Wahlgren" <fredrik.p.wahlgren@mailbox.swipnet.se> wrote in message
news:eGbYjPe8EHA.3476@TK2MSFTNGP15.phx.gbl...
>
> "Charles Allen" <callen@bkd.com> wrote in message
> news:%23M2ZY3d8EHA.2276@TK2MSFTNGP09.phx.gbl...
> > I've got SQL 2000 Developer edition installed on Windows XP Pro.
> >
> > I'm trying to create a new instance. It seems to install fine but it
> always
> > returns an error saying it could not connect. I've noticed when I read
the
> > log file that the password it used to connect is blank, even though I
set
> > one in the installation.
> >
> > I've tried specifying and not specifying a port number.
> >
> > The instance never appears in add/remove programs which I think it's
> > supposed to do.
> >
> > I read an article (888228) that seems to address the issue. However, it
> > refers to specifying information and I can't figure out where you're
> > supposed to put that text.
> >
> > Thank you for any help.
> >
> > Charles
> >
>
> Are you doing some kind of remote installation?
>
> / Fredrik
>
>
