Try adding the Instance name to your server registration in Enterprise Manager.
"(local)\sharepoint"
"(local)" would connect you to the default instance, and it sounds like you only have named instances set up.
On the Action Menu, select "New Registration"
[quoted text, click to view] On 08/16/2006 01:04:43 "Rick Barwig"<nouser@nodomain.com> wrote:
> I have a SBS2003 server that required a re-install of Sharepoint. I had 2
> databases that are part of a document locator application, the application
> made its' connection using sa and the associated password. I removed and
> reinstalled Sharepoint and upgraded the sharepoint instance to SQL std as
> recommended by MS. Now I must be missing something, I got as far as
> re-installing SQL std and upgraded the instance of sharepoint, I did not
> upgrade sbs monitoring. In services I see 2 services (mssql$sharepoint
> and mssql$sbsmonitoring) both are started. I have installed SQL SP-4, but
> the system tray icon shows "not connected" , there are no errors in the
> event logs. I open enterprise manager to restore the 2 databases I backed
> up and I do not have the ability
> to restore them. What I see is the SQL server group and (LOCAL) under it,
> if I click on it, I get "The SQL Server \\(LOCAL) is not known to be
> running. Are you sure you wish to connect?, if I click Yes, I get "A
> connection could not be established to(LOCAL). Reason: SQL server does
> not exist or access denied. ConnectionOpen (Connect()).. Please verify
> SQL server is running and check your SQL server registration properties
> (by right clicking on the (LOCAL) node) and try again.
> Any ideas on this?
--
Glenn Adams
Tiber Creek Consulting
http://www.tibercreek.com glenn@tibercreek.com ----------------------------------------------
Please DO NOT respond to me directly but post all responses here in the newsgroup so that all can share the information.
