I have this error how do i fix
Microsoft.SharePoint.Upgrade.SPUpgradeException: Action 3.0.2.0 of Microsoft.SharePoint.Upgrade.SPConfigurationDatabaseSequence2 failed. ---> System.ArgumentException: The id ac4f0012-2b5d-4b61-a683-5c5423e90b9b is in use. An Microsoft.SharePoint.Administration.SPServer named "<Localserver>" is using the same id as the new object named "<Localserver>" of type Microsoft.SharePoint.Administration.SPServer. Every object must contain a unique id. Either update the new object's id or delete the existing object and try again.
The unique thing its grow, is the problems.....

Update Microsoft.SharePoint.Administration.SPServer ???
SUMEET_1876
Thanks for the update wlee. I had the same issue (and lest anybody wonder, my app pool identity was most decidedly not local server). Reinstalling sans in-place upgrade avoided the apparently misguided check. It occurs to me that it may have been looking at some other web site and app pool, but hard to say since the error information is just a sad little stack crawl.
Jack
Chris Via
coresoul
Hi,
Iam facing the same issue
Microsoft.SharePoint.Upgrade.SPUpgradeException: Action 3.0.2.0 of Microsoft.SharePoint.Upgrade.SPConfigurationDatabaseSequence2 failed.
can any one help me on this.
Thanks in advance
R.Suresh
Joe Morel - MSFT
Hi Guys,
i got the solution for my issue , if you face the same problem you can refer the below url.
http://cosier.wordpress.com/2006/5/15/the-language-is-not-supported-on-the-server---office-sharepoint-server2007-installation/
May be the information mentioned in the above will help you to resolve your issue.
Thanks
R.Suresh
ryan101
AHA! That sounds like the answer to my problem. I'm having the same or similar problem upgrading to wss 3.0
How do i get to a point where i can do a gradual upgrade, seeing as i can't roll back the upgrade
Thomas Ivarsson
I'm also having a similar issue, my error reports as such:
03/05/2007 10:31:28 9 ERR An exception of type Microsoft.SharePoint.Upgrade.SPUpgradeException was thrown. Additional exception information: Action 3.0.2.0 of Microsoft.SharePoint.Upgrade.SPConfigurationDatabaseSequence2 failed.
Microsoft.SharePoint.Upgrade.SPUpgradeException: Action 3.0.2.0 of Microsoft.SharePoint.Upgrade.SPConfigurationDatabaseSequence2 failed. ---> System.ArgumentException: You cannot use Local System or Local Service as the application pool identity for Windows SharePoint Services.
at Microsoft.SharePoint.Administration.SPFarm.Create(SqlConnectionStringBuilder configurationDatabase, SqlConnectionStringBuilder administrationContentDatabase, IdentityType identityType, String farmUser, SecureString farmPassword)
at Microsoft.SharePoint.Upgrade.InitialFarmCreation.CreateFarm(SqlConnectionStringBuilder connectionString)
at Microsoft.SharePoint.Upgrade.InitialFarmCreation.Upgrade()
at Microsoft.SharePoint.Upgrade.SPActionSequence.Upgrade()
--- End of inner exception stack trace ---
at Microsoft.SharePoint.Upgrade.SPActionSequence.Upgrade()
at Microsoft.SharePoint.Upgrade.SPManager.Upgrade(Object o, Boolean bRecurse)
at Microsoft.SharePoint.Administration.SPPersistedUpgradableObject.Upgrade(Boolean recursively)
at Microsoft.SharePoint.Upgrade.SPManager.Initialize()
at Microsoft.SharePoint.PostSetupConfiguration.UpgradeBootstrapTask.Run()
at Microsoft.SharePoint.PostSetupConfiguration.TaskThread.ExecuteTask()
Anton Dimitrov
I just reviewed my install....apparently upgrade in place attempts to reuse the default web server (port 80). If you have some other site configured there, then it will try to create a new web MOSS web app in that site, reusing the existing site app pool and identity.
When you do a gradual upgrade, the existing default web site is stopped and a new site and app pool are created using network service as the identity. Obviously all of this rearranging without a heads up is not ideal, but there you have it.HedleySohn
Todd Burkholder
same prob here...
renamed server... no help
can't find 3.0 object id or how to upgrade...(make that...) update
can't find object id listed as used in registry or elsewhere
don't really want to delete anything until new 3.0 config wizard completes w/success...
David Ghikas
I can tell you that one thing you need to fix is your SQL 2000 backend. WSS 3.0 requires SQL Server 2000 SP4 or greater.