DBA Lockdown

Go, SharePoint!

Last post 10-16-2007 8:29 AM by Chris Quick. 1 replies.

Page 1 of 1 (2 items)
	Sort Posts: Previous Next

10-15-2007 10:44 AM

wkocak
Joined on 10-15-2007

DBA Lockdown

Reply Contact

I am quite new to SharePoint and MOSS; yet, I have been assigned to a client site tomorrow for troubleshooting security permession issues. Looking for any insight or pointers.

Basically, the client installed WSS 3 and MOSS 2007 just fine. Post installation the client's DBAs lockdown the database according to their corporate polices. Now, the WSS 3 only sites run fine but the MOSS specific sites are all throwing errors left and right.

This is all the detail that I have at this point... Could anyone recommend a decent plan of attack? Should I setup a SQL Trace? Is there something glaring between WSS only sites versus MOSS specific sites? (Does this even makes sense?)

Kindest Regards,

WKocak

Filed under: administration, SQL Server 2000, MOSS 2007, WSS 3.0, Error, MOSS, administration Authentication Providers delete, authentication, deployment, Event Log Errors, SharePoint 2007, permissions, WSS 3.0 MOSS, SQL, SQL 2005, Architecture, database, permission access forbid, configuration

10-16-2007 8:29 AM In reply to

Chris Quick
Joined on 06-21-2007
Texas, U.S.A.

Re: DBA Lockdown

Reply Contact

It would help if you could post some of the error messages as there are a few different ways that MOSS can interact with other databases besides the SharePoint databases (for instance, MOSS can make use of a BDC to connect to another SQL db).

Page 1 of 1 (2 items)

Need SharePoint Training? Attend a SharePoint Bootcamp!