sql server connect: Cannot connect to the configuration database. -- sql server connect

RE: Cannot connect to the configuration database.

Todd C
4/18/2007 4:54:01 AM

Martin:

Did you cross-post this in the SBS section? This sounds more like a
SharePoint issue than SQL Server issues. Did you install the SharePoint
options when you installed SBS? I'm guessing not if you don't see those two
services on the server.

HTH
--
Todd C

[If this response was helpful, please indicate by clicking the appropriate
answer at the bottom]

[quoted text, click to view]

RE: Cannot connect to the configuration database.

Martin Taylor
4/18/2007 5:02:02 AM

Both SQL and Sharepoint services are running.

[quoted text, click to view]

RE: Cannot connect to the configuration database.

Todd C
4/18/2007 5:06:02 AM

Then what did you mean by "Niether of these are listed in my services."?

--
Todd C

[quoted text, click to view]

RE: Cannot connect to the configuration database.

Martin Taylor
4/18/2007 5:12:02 AM

I have just learned that niether ar listed as MSSQLSERVER or MSSQL$SHAREPOINT
any longer but instead are simply listed as SQLSERVER and SHAREPOINT SEVICES.

Martin

[quoted text, click to view]

RE: Cannot connect to the configuration database.

Todd C
4/18/2007 5:34:04 AM

OK. So the SQL Service and SharePoint services are installed and running.

To see if SharePoint's config database is there and accepting connections:

Open a command prompt. Type: sqlcmd <enter> (or osql <enter>)
If you get 1> as a return, then type the following:

1> select name from sys.databases
2>go

Look for a database name with 'config' in the name. My guess is that you
will have a bunch with <cCompany Name> followed by _PROF, _SERV, _SITE, and
_Config.

Still in your SQLCMD prompt, type this:
1> use <config database name>
2> go

Return should be "Changed database context to '<config database name>'. "

Now type:
1> select name from sys.tables
2> go

If you don't get error messages, then the config database is up and running
and accepting connections. Therefore, the problem would lie eslewhere.

(to get out of the SQLCMD, type EXIT)

Let me know how it goes.

--
Todd C

[If this response was helpful, please indicate by clicking the appropriate

Got something to say? Click here to post a reply to this thread.

Don't see what you're looking for? Try a search.

View other messages in the sql server connect group.