Skip to main content

Upgrade fails from SharePoint 2007 to SharePoint 2010 on a server farm

On a server farm, you cannot upgrade Microsoft Office SharePoint Server 2007 to Microsoft SharePoint Server 2010 or Microsoft SharePoint Foundation 2010. The installation fails, and an error is logged in the upgrade-*.log file that resembles the following:


[psconfigui] [SPUpgradeSession] [ERROR] [TimeDate_Stamp]: Inner Exception: The password for the account Domain_Name\Account_Name, as currently stored in SharePoint, is not the same as the current password for the account within Active Directory. To fix this with PowerShell, run Set-SPManagedAccount -UseExistingPassword. This log file is located at %Commonprogramfiles%\Microsoft Shared\Web server extensions\14\logs\upgrade-*.log.

[psconfigui] [SPUpgradeSession] [ERROR] [TimeDate_Stamp]: at Microsoft.SharePoint.Administration.SPWindowsServiceInstance.Start()

at Microsoft.SharePoint.Administration.SPWindowsServiceInstance.Provision(Boolean start)

at Microsoft.SharePoint.Search.Administration.SPSearchServiceInstance.Provision()

at Microsoft.SharePoint.Search.Upgrade.ProvisionSearchService.Upgrade()

at Microsoft.SharePoint.Upgrade.SPActionSequence.Upgrade()

[psconfigui] [SPUpgradeSession] [ERROR] [TimeDate_Stamp]: Exception: Action 4.0.2.0 of Microsoft.SharePoint.Search.Upgrade.SPServerSequence failed.

[psconfigui] [SPUpgradeSession] [ERROR] [TimeDate_Stamp]: at Microsoft.SharePoint.Upgrade.SPActionSequence.Upgrade()

at Microsoft.SharePoint.Upgrade.SPUpgradeSession.Upgrade(Object o, Boolean bRecurse)

[psconfigui] [SPUpgradeSession] [DEBUG] [TimeDate_Stamp]: Elapsed time upgrading [SPServer Name=LIPINGL-755-VM1]: 00:00:37.

[psconfigui] [SPManager] [INFO] [TimeDate_Stamp]: Resetting the status of PersistedUpgradableObject: SPServer Name=LIPINGL-755-VM1 to Online.

[psconfigui] [SPManager] [ERROR] [TimeDate_Stamp]: SPManager.InplaceUpgradeAdministrationWebApplication failed.

[psconfigui] [SPManager] [ERROR] [TimeDate_Stamp]: Inner Exception: The password for the account Domain_Name\Account_Name, as currently stored in SharePoint, is not the same as the current password for the account within Active Directory. To fix this with PowerShell, run Set-SPManagedAccount -UseExistingPassword.

[psconfigui] [SPManager] [ERROR] [TimeDate_Stamp]: at Microsoft.SharePoint.Administration.SPWindowsServiceInstance.Start()

at Microsoft.SharePoint.Administration.SPWindowsServiceInstance.Provision(Boolean start)

at Microsoft.SharePoint.Search.Administration.SPSearchServiceInstance.Provision()

at Microsoft.SharePoint.Search.Upgrade.ProvisionSearchService.Upgrade()

at Microsoft.SharePoint.Upgrade.SPActionSequence.Upgrade()

[psconfigui] [SPManager] [ERROR] [TimeDate_Stamp]: Exception: Action 4.0.2.0 of Microsoft.SharePoint.Search.Upgrade.SPServerSequence failed.

[psconfigui] [SPManager] [ERROR] [TimeDate_Stamp]: at Microsoft.SharePoint.Upgrade.SPActionSequence.Upgrade()

at Microsoft.SharePoint.Upgrade.SPUpgradeSession.Upgrade(Object o, Boolean bRecurse)

at Microsoft.SharePoint.Administration.SPPersistedUpgradableObject.Upgrade(Boolean recursively)

at Microsoft.SharePoint.Upgrade.SPManager.InplaceUpgradeAdministrationWebApplication()


This issue occurs for one of the following reasons:
  • The existing service account that is used in the server farm has expired credentials.
  • The service account is missing certain user rights and does not have the correct access level to perform the upgrade.
  • The service account is in a locked-out state.
When existing service accounts that are used in the server farm do not work correctly, errors occur when you try to upgrade to SharePoint 2010.

In case you find it difficult to correct the problem with the service account, see kb981495.

Comments

Popular posts from this blog

SQL Azure Error - 40544

If the size of your database reaches its MAXSIZE you will receive an error code 40544. You cannot insert or update data, or create new objects (such as tables, stored procedures, views, and functions).To fix this issue either increase your database size or delete data. For increasing/decreasing SQL Azure database size, you can use this command on the Master database. Alter DATABASE database_name MODIFY (MAXSIZE = {1|5|10|20|30… 150}GB); example: ALTER DATABASE sampleDB MODIFY (MAXSIZE = 5gb);

Hardware DEP (Data Execution Prevention), NX, XD & EVP

A processor can be instructed to designate regions of memory as non-executable. This means that the memory can be used to store reference data to be read and written, but that the processor cannot treat the contents of the memory as program code to be directly executed. Intel calls this capability in their newer processors XD for “eXecute Disable” and AMD refers to it as NX for “No eXecute.” AMD's marketing materials also sometimes refer to this capability by the term EVP for Enhanced Virus Protection.
As a hardware capability of modern processors this addition is important, but its use depends entirely upon support from the operating system. So when Microsoft introduced support for this into their operating systems, they termed it Hardware DEP for Data Execution Prevention. Support for hardware DEP was introduced into the 32-bit versions of Windows XP with Service Pack 2, into Windows 2003 Server with Service Pack 1, and has always been present in Windows Vista. Hardware DEP does …