Error connecting to configdb during install of second WFE
I have WSS installed on a 2003R2 server (32-bit) as a WFE talking to a SQL2005 Cluster. I am having trouble getting a second WFE to install. The WFE machineshave identical hardware and software configurations. Getting this in the log of the second WFE when it fails at step 2 of the Sharepoint Configuration Wizard. The servers are on the same network segment, so no firewall issues. I have verified permissions on the SQL server for the account that I am trying to use (same as on the first WFE). Any ideas as to what may be causing it? <code> 03/21/2008 21:10:05 8 INF Leaving function Farm.TryIsJoinedToFarm03/21/2008 21:10:05 8 INF Leaving function Farm.IsJoinedToFarm03/21/2008 21:10:05 8 INF Creating connection string for config db PIQ_Sharepoint_Config server FRADC-SQLVS203/21/2008 21:10:05 8 INF Creating connection string for admin content db SharePoint_AdminContent_a686fe30-8368-4d2f-a617-98fe55072227 server FRADC-SQLVS203/21/2008 21:10:05 8 INF Using NTLM for sql connection string03/21/2008 21:10:05 8 INF Openning configdb so that I can join it at server FRADC-SQLVS2 database PIQ_Sharepoint_Config in farm mode03/21/2008 21:10:05 8 INF Now joining to farm at server FRADC-SQLVS2 database PIQ_Sharepoint_Config03/21/2008 21:10:15 8 ERR Task configdb has failed with an unknown exception 03/21/2008 21:10:15 8 ERR Exception: System.Security.SecurityException: Access denied. at Microsoft.SharePoint.Administration.SPPersistedObject.Update() at Microsoft.SharePoint.Administration.SPServer.Update() at Microsoft.SharePoint.Administration.SPFarm.Join() at Microsoft.SharePoint.PostSetupConfiguration.ConfigurationDatabaseTask.CreateOrConnectConfigDb() at Microsoft.SharePoint.PostSetupConfiguration.ConfigurationDatabaseTask.Run() at Microsoft.SharePoint.PostSetupConfiguration.TaskThread.ExecuteTask()The Zone of the assembly that failed was:MyComputer03/21/2008 21:10:15 8 INF Entering function Common.BuildExceptionMessage03/21/2008 21:10:15 8 INF Entering function StringResourceManager.GetResourceString03/21/2008 21:10:15 8 INF Resource id to be retrieved is ExceptionInfo for language English (United States)03/21/2008 21:10:15 8 INF Resource retrieved id ExceptionInfo is An exception of type {0} was thrown. Additional exception information: {1}03/21/2008 21:10:15 8 INF Leaving function StringResourceManager.GetResourceString03/21/2008 21:10:15 8 INF Leaving function Common.BuildExceptionMessage03/21/2008 21:10:15 8 INF Entering function Common.BuildExceptionInformation03/21/2008 21:10:15 8 INF Entering function Common.BuildExceptionMessage03/21/2008 21:10:15 8 INF Entering function StringResourceManager.GetResourceString03/21/2008 21:10:15 8 INF Resource id to be retrieved is ExceptionInfo for language English (United States)03/21/2008 21:10:15 8 INF Resource retrieved id ExceptionInfo is An exception of type {0} was thrown. Additional exception information: {1}03/21/2008 21:10:15 8 INF Leaving function StringResourceManager.GetResourceString03/21/2008 21:10:15 8 INF Leaving function Common.BuildExceptionMessage03/21/2008 21:10:15 8 INF Leaving function Common.BuildExceptionInformation03/21/2008 21:10:15 8 ERR An exception of type System.Security.SecurityException was thrown. Additional exception information: Access denied.System.Security.SecurityException: Access denied. at Microsoft.SharePoint.Administration.SPPersistedObject.Update() at Microsoft.SharePoint.Administration.SPServer.Update() at Microsoft.SharePoint.Administration.SPFarm.Join() at Microsoft.SharePoint.PostSetupConfiguration.ConfigurationDatabaseTask.CreateOrConnectConfigDb() at Microsoft.SharePoint.PostSetupConfiguration.ConfigurationDatabaseTask.Run() at Microsoft.SharePoint.PostSetupConfiguration.TaskThread.ExecuteTask()The Zone of the assembly that failed was:MyComputer03/21/2008 21:10:15 8 INF Entering function Common.BuildExceptionInformation03/21/2008 21:10:15 8 INF Entering function Common.BuildExceptionMessage03/21/2008 21:10:15 8 INF Entering function StringResourceManager.GetResourceString03/21/2008 21:10:15 8 INF Resource id to be retrieved is ExceptionInfo for language English (United States)03/21/2008 21:10:15 8 INF Resource retrieved id ExceptionInfo is An exception of type {0} was thrown. Additional exception information: {1}03/21/2008 21:10:15 8 INF Leaving function StringResourceManager.GetResourceString03/21/2008 21:10:15 8 INF Leaving function Common.BuildExceptionMessage03/21/2008 21:10:15 8 INF Leaving function Common.BuildExceptionInformation03/21/2008 21:10:15 8 INF Entering function TaskBase.OnTaskStop03/21/2008 21:10:15 8 INF Creating the OnTaskStop event for task configdb03/21/2008 21:10:15 8 ERR Task configdb has failed03/21/2008 21:10:15 8 INF friendlyMessage for task configdb is An exception of type System.Security.SecurityException was thrown. Additional exception information: Access denied.03/21/2008 21:10:15 8 INF debugMessage for task configdb is An exception of type System.Security.SecurityException was thrown. Additional exception information: Access denied.System.Security.SecurityException: Access denied. at Microsoft.SharePoint.Administration.SPPersistedObject.Update() at Microsoft.SharePoint.Administration.SPServer.Update() at Microsoft.SharePoint.Administration.SPFarm.Join() at Microsoft.SharePoint.PostSetupConfiguration.ConfigurationDatabaseTask.CreateOrConnectConfigDb() at Microsoft.SharePoint.PostSetupConfiguration.ConfigurationDatabaseTask.Run() at Microsoft.SharePoint.PostSetupConfiguration.TaskThread.ExecuteTask()The Zone of the assembly that failed was:MyComputer</code>
March 21st, 2008 11:46pm

Bump. Has anyone else had issues connecting a second WFE to a farm?
Free Windows Admin Tool Kit Click here and download it now
March 24th, 2008 5:44pm

I had the same problem installing a second WFE. Installing WSS 3.0 SP1 resolved the issue: http://www.microsoft.com/downloads/details.aspx?FamilyId=4191A531-A2E9-45E4-B71E-5B0B17108BD2&displaylang=en
March 25th, 2008 8:59pm

Anyone ever get a solution to this? I have a fully patched (SP1) system, I am trying to add this machine to the farm and I get the same error trace as the first post. I have wiped this box twice to make sure the install was not bad. I have verified all SQL and Windows permissions. Absolutely no idea what is causing this. There is no really usefull error messages to help you figure out why it is getting an access denied.
Free Windows Admin Tool Kit Click here and download it now
August 7th, 2008 4:14pm

Has anyone figured out the solution to this problem?We arein the process of adding a server to our SharePoint farm using the configuration wizard and we are getting an error in step 2.We aregetting the same error in the logs that is posted here. We are using the MOSS with SP1 installer so the lack of service pack is not the issue.In the SharePoint configuration wizard, we are using the server farm account to connect to the database and this accounthas dbcreator and security admin rights in SQL.
September 9th, 2008 7:57pm

We installed the infrastructure update (which our farm was missing) and it seemed to fix itself.
Free Windows Admin Tool Kit Click here and download it now
September 9th, 2008 8:04pm

I am having the same issue with MOSS 2007 SP1 x64, fully patched. Has anyone figured this out? All patches are installed on the system.
February 11th, 2009 7:54pm

I also have the similar Problem fully patched MOSS 2007 SP1 64x, any solutions?
Free Windows Admin Tool Kit Click here and download it now
March 4th, 2009 12:16pm

In my experience, this is a problem with the new server being at a different patch/SP level than the rest of the servers in the farm.In Central Administration->Operations->Servers in Farm, it lists the version of all the servers. They should all be the same.For the server that hasn't joined the farm, you can still find what version it is running. Go to Start->settings->Control Panel->Add/Remove Programs. Highlight "Microsoft Office SharePoint Server 2007" and click on "click here for support information." A box will pop up with the version number. If it is not the same as the numbers on the servers in the farm, install the appropriate service packs/patches on either the farm servers or the new server so they are the same.Here is a list of SP/patch level those numbers translate to: http://sharepointhawaii.com/wenhe/Lists/Posts/Post.aspx?ID=27Having all the servers at the same version number should make this error go away.
March 15th, 2009 5:57am

I am having the same issue, MOSS 2007 SP1 x64 full patched.I have all the passwords correct, I am running the Sharepoint Technologies Configuration Wizard as the service account (tried my farm admin user account, no diffrence).ALL SERVERS ARE SAME VERSION, and have all the same patches.. to include the new WFE that is failing to configure. So I take it there is no solution yet? I reallllly don't want to install SP2 due to all of it's issues..
Free Windows Admin Tool Kit Click here and download it now
June 9th, 2009 11:08pm

does any one got resolution on this issue. I am also facing the same issue.Khare
August 9th, 2009 2:01am

I am also facing the same issue, we are using WSS 3.0 SP2. Has anybody resolved this issue?
Free Windows Admin Tool Kit Click here and download it now
October 27th, 2009 10:37pm

We are also facing the same issue using MOSS 2007 SP2. We are trying to install the WFE for use with reporting services so we are trying to configure it on the same server as the SQL Server, same error as the original poster.
December 16th, 2009 7:45pm

Hate to bring an old thread back to life, but to solve this problem, I logged on to the box as the sytem account, with local admin rights, and sysadim rights on the SQL cluster and re-installed sharepoint and re-ran the config wizard and the box joing the farm with no issues. I suspect it was something permissions related to the SQL server. Once again: Do NOT propose your own posts as answers. See longer message in another thread from you today,
Free Windows Admin Tool Kit Click here and download it now
February 18th, 2011 7:11pm

Hate to bring an old thread back to life, but to solve this problem, I logged on to the box as the sytem account, with local admin rights, and sysadim rights on the SQL cluster and re-installed sharepoint and re-ran the config wizard and the box joing the farm with no issues. I suspect it was something permissions related to the SQL server.
February 18th, 2011 11:41pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics