The message you get is a very general message that the client application
can't find the SQL Server. It can come up when the SQL Server is not
started, or the name is wrong, or the protocols don't work, etc.
Some ideas to start with:
Using SQL Server Configuration Manager, check to see that SQL Server 2005 is
installed, and running, and is in fact the default (un-named) instance.
Check that the protocols for the client tools are enabled.
Try starting the SQL Server Browser Service if it is not enabled.
--
Rick Byham (MSFT)
This posting is provided "AS IS" with no warranties, and confers no rights.
[quoted text, click to view] "Doug Forman" <DougForman@discussions.microsoft.com> wrote in message
news:8CD982E3-D0EE-4D12-AB1A-FAB372DA31CF@microsoft.com...
> Recently we upgraded our Windows 2000 with SQL Server 2000 to Windows
> Server
> SBE 2003 with SQL Server 2005 (sp2).
>
> The upgrade was successful, and we have been using our shared application
> which uses the SQL 2005 Server ever since.
>
> Tonight I removed the old SQL Server 2000 using Add/Remove Applications as
> it was no longer in use. After removing it, SQL Server 2005 can no longer
> connect to the local instance of the server (which we named simply
> "SERVER").
>
> In MS SQL Server Management Studio, on the left I see a heading "Database
> Engine".
> Underneath, in order:
> server (with a white circle next to it)
> server\sbsmonitoring (with a red circle)
> server\sharepoint (with a green circle)
> server\wsus (with a green circle)
>
> When I attempt to connect to the server item, I get an error message "An
> error has occurred while establishing a connection to the server..." and
> further info about SQL Server not allowing remote connections by default.
> (this is a local instance I am trying to connect to).
>
> I'm stuck! I would greatly appreciate any thoughts or suggestions!
>
> -doug
>
