[thelist] MOSS 2007 Configuration Problem
jslist at sbcglobal.net
Wed Aug 19 10:07:37 CDT 2009
Thanks for responding. I will check windows event log and the MOSS tracing log.
My server guy started setting up MOSS and ran into trouble - then he handed it over to me. I will be administrating it. I set up WSS 3.0 with SQLExpress successfully. To finish the installation I used these 2 sites for reference.
----- Original Message ----
From: Ken Schaefer <Ken at adOpenStatic.com>
To: "thelist at lists.evolt.org" <thelist at lists.evolt.org>
Sent: Tuesday, August 18, 2009 10:36:28 PM
Subject: Re: [thelist] MOSS 2007 Configuration Problem
From: thelist-bounces at lists.evolt.org [mailto:thelist-bounces at lists.evolt.org] On Behalf Of j s
Sent: Wednesday, 19 August 2009 4:20 AM
To: thelist at lists.evolt.org
Subject: [thelist] MOSS 2007 Configuration Problem
> Anyone out there good with setup of MOSS 2007? I'm getting an error - that I can't track down an answer for. "Cannot connect to the configuration database."
MOSS 2007 setup creates a Shared_Config database. Seems like your MOSS server can't connect to that anymore (e.g. it's not there, or your installation account or the MOSS Farm account can't connect to it)
> Created Farm with SQL server and a Windows 2008 server. The default "SharedServices1" has an error:
> (Provisioning failed: The SELECT permission was denied on the object 'sysusers', database 'mssqlsystemresource', schema 'sys'.)
Where are you seeing this error?
I see this error from the Central Adminstration site, On the left side menu it has
Central Administration / Operations / Application Management
Shared Services Administration / SharedServices1 <-- When I click on Shared Services Administration (not SharedServices1) then I see
Manage this Farm's Shared Services
X SharedServices1(Default) (Provisioning failed: The SELECT permission was denied on the object 'sysusers', database 'mssqlsystemresource', schema 'sys'.)
> The configuration SQL database has a domain admin user setup that has access to both servers.
This part is confusing me. What configuration database? And what are the "both servers" that you refer to?
MOSS is on 1 box and SQL Server is on another box. There is a network user that has domain administration on both servers.
Also, there are two places you should look for MOSS errors:
a) Windows Event Log
b) MOSS has a tracing log (by default I think the log is in %systemdrive%\program files\common files\microsoft shared\web server extensions\12\logs)
* * Please support the community that supports you. * *
For unsubscribe and other options, including the Tip Harvester
and archives of thelist go to: http://lists.evolt.org
Workers of the Web, evolt !
More information about the thelist