Our MOSS 2007 server recently went south, so I've reinstalled MOSS on a new server. Fortunately, the databases were stored on our SQL server, a different server, so those are all still intact.I installed MOSS 2007 and SP2 successfully and am now attempting to run the SharePoint Product and Technologies Configuration Wizard and connect to an existing server farm.The wizard locates my SQL server fine and populates the SharePoint_Config database when I click on Retrieve Database Names, as well as the MOSSFarmAdmin user. I have input the correct password.The wizard balks at Task 2, connecting to the configuration database. The following error is from the PSCDiagnostics file generated by the wizard:Task configdb has failed with an unknown exception 02/23/2010 16:26:10 8 ERR Exception: System.Security.SecurityException: Access denied.at Microsoft.SharePoint.Administration.SPPersistedObj ect.Update()at Microsoft.SharePoint.Administration.SPServer.Updat e()at Microsoft.SharePoint.Administration.SPFarm.Join()at Microsoft.SharePoint.PostSetupConfiguration.Config urationDatabaseTask.CreateOrConnectConfigDb()at Microsoft.SharePoint.PostSetupConfiguration.Config urationDatabaseTask.Run()at Microsoft.SharePoint.PostSetupConfiguration.TaskTh read.ExecuteTask()The Zone of the assembly that failed was:MyComputerI have added the MOSSFarmAdmin user to every security function I can think of in SQL Server.Any ideas?Thanks,Todd M Bowlsby

Alright, the issue here is Permission on the Database.Make sure that the service account MUST have DB Creator and Security Admin previliges on the SQl box.On Sharepoint Databases the account must be DBOWNER.Also, Make sure the Version of Sharepoint installed on the New Setup is exactly the same as in the Original Setup.Thanks! I LOVE MS..... Thanks and Regards, Kshitiz (Posting is provided "AS IS" with no warranties, and confers no rights.)

Hi Todd,just need to know if the old MOSS 2007 is the same version as the new,I mean that the old also SP2 Best Regards, Ammar MCT http://ahmed-ammar.blogspot.com Posting is provided "AS IS" with no warranties, and confers no rights.

Yes, the MOSSFarmAdmin user has all of those permissions. That's why I'm baffled.The version is identical.ToddTodd M Bowlsby Microsoft Practice Manager ISM

Yes, the old MOSS 2007 was on SP2, as well.ToddTodd M Bowlsby Microsoft Practice Manager ISM

Kshitiz:What do you mean by DBOWNER on SharePoint boxes? The SharePoint box is a different server than our SQL Server. In SQL Server Management Studio, MOSSFarmAdmin currently has db_owner and db_securityadmin on all of the SharePoint DBs, including the SharePoint_Config DB.I'm just not clear on whether that user needs additional rights on the SharePoint server based upon your comment.Thanks,Todd M Bowlsby Microsoft Practice Manager ISM

I am Sorry, I meant Sharepoint Databases.I LOVE MS..... Thanks and Regards, Kshitiz (Posting is provided "AS IS" with no warranties, and confers no rights.)

Account Must be DBO on the Sharepoint Databases.I LOVE MS..... Thanks and Regards, Kshitiz (Posting is provided "AS IS" with no warranties, and confers no rights.)

Okay. So the MOSSFarmAdmin has the security rights you outlined on all SharePoint and WSS DBs within SQL Server. The version we were running on was also the same as I've installed: MOSS 2007 SP2.Any other ideas as to why it won't connect to the existing SharePoint_Config?Thanks for your responses thus far.Regards,Todd M Bowlsby Microsoft Practice Manager ISM

A quick couple of questions here1. Are you logged in to the server as the service account or using another account?2. Are you running the configuration wizard using the service account?I think the access denied error could also be due to the fact that the account being used to run the wizard does not have permissions to connect to the SQL database. Try logging in to the server using the service account ( if that can be done) and run the wizard. Also, you may want to add the service account to the local administrators group on the SQL server.Let me know how it goes.

Hi, This may be caused by that you are logged into the server with an account, which does not have access to SQL server, please try the following steps to resolve the issue: 1. Make sure that both the SharePoint servers are on the same domain 2. Try to log off and login to the SharePoint server with the Service account 3. Add the service account in all the WPG groups 4. Using the SQL Express Management Studio we connect to the SQL server, and then give sysadmin, dbcreator and securityadmin rights to the account the client is logged on as. 5. Delete the databases that were created during the failing install. Hope it helps.Xue-Mei Chang