Friday, 11 December 2009 2:31 AMI have question regarding SQL permissions when setting up Project Server 2007 on WSS3 in a shared, locked dwon SQL environment.
I'm currently trying to setup Project Server 2007 for a customer and have been given a Dev environment, which consists of a Web/App server (W2K8 SP1) and a shared SQL 2005environment.
The customer's DBA has created the required DBs and assigned the domain level setup account to the dbowner role.
I'm at the stage where I've managed to setup the WSS3 site after a lot of work and am ready to create a Project Server site.
Each time I try and create the site either via the Web interface or STSADM projcreatepwainstance I get the following error:
Provisioning '/Projects': Failed to provision databases. An exception occurred: Database provisioning failed. User must be in both dbcreator and securityadmin server roles or be dbowner on each of the databases..
Is it sufficient for the setup account to only have dbowner privileges or does it really require dbcreator and securityadmin rights on the SQL server? It has been made clear to me that there is no way that this elevated level will be assigned to the account, so if it's required I'm not sure how I can finish the implementation.
The dbowner privilege was enough to setup the Config, Content and SSP DBs, so I would presume the same is true for the 4 Project Server DBs (Archive, Draft, Published, Reporting).
Any help would be appreciated, it's had me stumped for a couple of days, and I reckon I've trawled the Internet and read enough technical articles to think that something is missing.
To confuse matters even more the DBA assigned the user to the dbcreator fixed server role and I still get the "User must be in both dbcreator and securityadmin server roles or be dbowner on each of the databases.." error.
Note that the securityadmin fixed server role has not been assigned.
Friday, 11 December 2009 3:02 PM
This question should be in the project forms (Pre-2010)
but to answer your question.
It looks like you don't have rights to create the databse. Make sure the installation logon has access to the database.
You could create the databases prior to the provisioning and have all the appropriate security rights setup prior to provisioning.
Michael Wharton, MBA, PMP, MCT, MCSD, MCDBA, MCSE+I
- Marked As Answer by Patrick Conlan [MSFT]Microsoft Employee, Moderator Friday, 11 December 2009 4:24 PM
Friday, 11 December 2009 4:24 PMModeratorAs Michael say - in this case you can ask the DBA team to pre-create the databases and then use them in the provisioning UI or powershell script. The schema in the Draft, Published and Archive db are static, however we do create objects on the fly in the Reporting db (the column pool tables used as as you add custom fields)
Friday, 27 April 2012 4:33 PMThe way it looks to me, you probably answered your own question - saying the securityadmin role wasn't assigned. It's a Dev environment, you said, so assign that and see what happens.