SharePoint Restore Error: Your backup is from a different version of Microsoft SharePoint Foundation and cannot be restored to a server running the current version. The backup file should be restored to a server with version '14.0.0.5050' or later.

http://ranaictiu-technicalblog.blogspot.com/2010/11/sharepoint-restore-error-your-backup-is.html
I had needed to move my dev environment from one Virtual machine to another. So I took backup from source server and tried to restore the backup in new server. However, I have got the error “Your backup is from a different version of Microsoft SharePoint Foundation and cannot be restored to a server running the current version. The backup file should be restored to a server with version '14.0.0.5050' or later.” I was totally confused as I had the same version of SharePoint in both server. Then I double checked the version and it was 14.0.4762.1000 for both servers.
Getting confused I googled and found that solution. This is a bug which is fixed by SharePoint 2010 August cumulative update. The updates are available in the following link:

• For SharePoint Foundation http://support.microsoft.com/kb/2266423
• For SharePoint Server http://support.microsoft.com/kb/2276339

SharePoint Configuration Wizard errors

http://support.microsoft.com/kb/944267

After you install one of the following updates or service packs on a computer that is running Windows SharePoint Services 3.0 or SharePoint Server 2007, you may have to rerun the SharePoint Products and Technologies Configuration Wizard (Psconfig.exe):

• Windows SharePoint Services 3.0 software update
• Windows SharePoint Services 3.0 service pack
• SharePoint Server 2007 software update
• SharePoint Server 2007 service pack

If the SharePoint Products and Technologies Configuration Wizard detects a problem, the wizard does not finish. Also, users who try to visit the SharePoint Web site may receive "404" errors. These errors occur until the wizard has finished successfully.

To troubleshoot this problem, obtain the following SharePoint log files:

• PSCDiagnostics_Datecode.log
  By default, this file is located in the "Program Files\Common Files\Microsoft Shared\Web server extensions\12\LOGS" folder.
• Upgrade.log
  By default, this file is located in the "Program Files\Common Files\Microsoft Shared\Web server extensions\12\LOGS" folder.

Back to the top

How to identify and resolve the problem

This section lists various problems that may be detected by the SharePoint Products and Technologies Configuration Wizard. Symptoms are listed for each problem to help you identify it.

The Web.config file is read-only

Symptoms

If the Web.config file is read-only, the Upgrade.log file will contain an error message that resembles the following:

[IisWebSiteSequence] [ERROR] [10/17/2007 11:38:22 AM]: Access to the path 'C:\Inetpub\wwwroot\wss\VirtualDirectories\5003\web.config' is denied.

Cause

This problem occurs when the Web.config file has been configured as read-only. This problem may also occur when a custom management program or a virus scan program locks the Web.config file.

Resolution

Make sure that everyone has write access to this file before you run the SharePoint Products and Technologies Configuration Wizard. Also make sure that the read-only check box is not enabled in the Web.config file properties dialog box and that no other process locks the Web.config file.

ASP.NET is registered incorrectly in the Internet Information Services (IIS) metabase

Symptoms

If ASP.NET is registered incorrectly in the IIS metabase, the Upgrade.log file will contain an error message that resembles the following:

[SPIisWebSiteWssSequence] [ERROR] [10/10/2007 10:21:25 AM]: Action 3.0.3.0 of Microsoft.SharePoint.Upgrade.SPIisWebSiteWssSequence failed. [SPIisWebSiteWssSequence] [ERROR] [10/10/2007 10:21:25 AM]: InstallAspNet 566609673 failed. [SPIisWebSiteWssSequence] [ERROR] [10/10/2007 10:21:25 AM]: at Microsoft.SharePoint.Upgrade.EnsureAspNetScriptMapInstalled.Upgrade() at Microsoft.SharePoint.Upgrade.SPActionSequence.Upgrade()

In this case, the number between "InstallAspNet" and "failed" in this message is the ID of the affected IIS Web site.

Cause

This problem occurs because ASP.NET is registered incorrectly in the IIS metabase.

Resolution

To resolve this problem, follow these steps:

1. Click Start, click Run, type cmd, and then click OK.
2. At the command prompt, move to the following folder:
   %windir%\Microsoft.net\framework\v2.0.50727
3. At the command prompt, type the following command, and then press ENTER:
   aspnet_regiis.exe –s W3SVC/number/ROOT
   Note number is the ID of the affected IIS Web site.

A second cause can be a timing issue in the Windows SharePoint Administration service. To address this cause, set the following registry subkey:

Software\Microsoft\Shared Tools\Web Server Extensions\12.0\WSS\SPAdmin

DWORD value: SleepOnStart set to 20000 decimal

The Web Service Instance has not provisioned successfully

Symptoms

The following error message is logged in the Application log on the computer that is running Windows SharePoint Services 3.0 or SharePoint Server 2007:

Event Type: Error
Event Source: Windows SharePoint Services 3
Event Category: Topology
Event ID: 6800 Date: 10/17/2007
Time: 8:09:40 PM
User: N/A
Computer: ComputerName
Description: The database WSS_Content on ComputerName\Microsoft##SSEE is not accessible to missing Windows Internal Database signatures.

Also, the Upgrade.log file contains the following error message:

[SPServerSequence] [DEBUG] [10/22/2007 7:44:21 AM]: Web service Instance SPWebServiceInstance Parent=SPServer Name=ComputerName not added. Status = Provisioning

Cause

This problem occurs when the initial provisioning of the Web service instance has not completed successfully. This behavior causes the upgrade process to skip the Web service instance.

Resolution

To resolve this problem, follow these steps:

1. Click Start, click Run, type cmd, and then click OK.
2. Locate the "Program Files\Common Files\Microsoft Shared\Web server extensions\12\BIN" folder.
3. At the command prompt, type the following commands, and then press ENTER after each command:
   stsadm -o provisionservice -action stop -servicetype spwebservice -servicename ""
   stsadm -o provisionservice -action start -servicetype spwebservice -servicename ""
4. After the SPWebService service is started, type the following command at the command prompt, and then press ENTER:
   psconfig -cmd upgrade -inplace b2b -wait -force

The Web.config file is missing

Symptoms

The Upgrade.log file contains an error that resembles the following:

[AssemblyReferenceFixUp] [3.0.4.0] [ERROR] [10/18/2007 11:47:40 AM]: Application Web Config for this IIS site (944564711) could not be found at \wwwroot\wss\VirtualDirectories\5003\web.config.

Cause

This behavior occurs when the Web.config file has been deleted or moved.

Resolution

To resolve this problem, make sure that the Web.config file is located in the Wwwroot\Wss\VirtualDirectories\xxxx folder before you run the SharePoint Products and Technologies Configuration Wizard.

Note xxxx represents the virtual server physical location for the SharePoint Web application. In IIS, the virtual server physical location is listed next to Local path on the Home Directory tab in the virtual server properties dialog box.

The SharePoint Products and Technologies Configuration Wizard does not finish successfully

Symptoms

You run the SharePoint Products and Technologies Configuration Wizard (PSConfigui.exe) to upgrade the databases. When you do this, the wizard does not finish successfully. Also, the following error message is logged:  

Date Time 8 ERR An exception of type Microsoft.SharePoint.Administration.SPUpdatedConcurrencyException was thrown.
Additional exception information: An update conflict has occurred, and you must re-try this action. The object DiagnosticsService Parent=SPFarm Name=SharePoint_Config is being updated by Domain\User, in the w3wp process, on machine SERVER.
View the tracing log for more information about the conflict.
Microsoft.SharePoint.Administration.SPUpdatedConcurrencyException: An update conflict has occurred, and you must re-try this action. The object DiagnosticsService Parent=SPFarm Name=SharePoint_Config is being updated by Domain\User, in the w3wp process, on machine SERVER.
View the tracing log for more information about the conflict.

This message is logged in the following log file:

Drive:\Program Files\Common Files\Microsoft Shared\web server extensions\12\LOGS\PSCDiagnostics_Datecode

Cause

This issue occurs because a lock exists on the SPFarm object. Therefore, the SharePoint Products and Technologies Configuration Wizard cannot update the databases.

Resolution

To resolve this issue, clear the Windows SharePoint Services configuration cache.

For more information about how to do this, click the following article number to view the article in the Microsoft Knowledge Base:

939308  (http://support.microsoft.com/kb/939308/ ) Error message when you try to modify or to delete an alternate access mapping in Windows SharePoint Services 3.0: "An update conflict has occurred, and you must re-try this action"

You cannot browse a Central Administration or SharePoint website, and you receive a "Server Error" error message

Symptoms

When you try to browse a Central Administration website or a SharePoint website, you may receive the following error message:

Server Error: http://go.microsoft.com/fwlink?LinkID=96177 (http://go.microsoft.com/fwlink?LinkID=96177)

Or, the following message is logged in the Application log:

Event Type: Error
Event Source: Windows SharePoint Server
Event Category: Topology
Event lD: 5617
Description:
The schema version (3.x.x.x) of the database SharePoint_AdminContent_123fda45-f456-fad5-de45-7891d2asd455 on ComputerName is not consistent with the expected database schema version (3.x.x.x) on ComputerName. Connections to this database From this server have been blocked to avoid data loss. Upgrade the web Front end or the content database to ensure that these versions match.

Cause

This problem may occur when an upgrade fails to install either manually or through Windows Update. The installation failure puts the farm into an inconsistent state that must be resolved by a successful upgrade operation.

Resolution

To resolve this problem, follow these steps to run the upgrade:

1. Click Start, click Run, type cmd, and then click OK.
2. Locate the following folder:
   "%COMMONPROGRAMFILES%\Microsoft Shared\Web server extensions\12\BIN"
3. Open a Command Prompt window.
4. At the command prompt, type the following command, and then press ENTER:
   psconfig -cmd upgrade -inplace b2b -wait -force

After upgrade finishes, make sure that the upgrade was successful.

You cannot browse a Central Administration or SharePoint website, and you receive a "HTTP 404 Not Found" error message

Symptoms

When you try to browse a Central Administration website or a SharePoint website, you may receive the following error message:

HTTP 404 Not Found

Or, the following message is logged in the Application log:

Event Type: Error Event
Source: Windows SharePoint Services 3
Event Category: Topology
Event ID: 6800
Description: The database WSS_Content on ComputerName \Microsoft##SSEE is not accessible to missing Windows Internal Database signatures.

Cause

This problem may occur when you install a patch manually or through Windows Update. If another service has connected to the Windows Internal Database prior to the upgrade, SharePoint cannot make a connection, and the upgrade fails. This puts the farm into an inconsistent state that must be resolved by a successful upgrade operation.

Resolution

To resolve this problem, follow these steps to restart the SharePoint services and to complete upgrade:

1. Click Start, click Run, type cmd, and then click OK.
2. Locate the following folder:
   %COMMONPROGRAMFILES%\Microsoft Shared\Web server extensions\12\BIN
3. At a command prompt, type the following command, and then press ENTER:
   psconfig -cmd upgrade -inplace b2b -wait –force
4. If the upgrade does not complete succussfully, type the following commands at the command prompt, and press ENTER after each command:
   net stop MSSQL$MICROSOFT##SSEE
   net start MSSQL$MICROSOFT##SSEE
   psconfig -cmd upgrade -inplace b2b -wait -force

You cannot browse a Central Administration or SharePoint website, and you receive a "Cannot connect to the configuration database" error message

Symptoms

When you try to browse a Central Administration or SharePoint website, the following error message is logged in the Upgrade.log file on the computer that ran the upgrade for Windows SharePoint Services 3.0 or SharePoint Server 2007 by using the Windows Internal Database:

[SPManager] [ERROR] [6/14/2010 12:00:00 PM]: Upgrade [SPContentDatabase Name=ShareWebDb Parent=SPDatabaseServiceInstance Name=Microsoft##SSEE] failed. [SPManager] [ERROR] [6/14/2010 12:00:00 PM]: Database 'ShareWebDb' is already open and can only have one user at a time. [SPManager] [ERROR] [6/14/2010 12:00:00 PM]: at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj) at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj) at System.Data.SqlClient.SqlCommand.RunExecuteNonQueryTds(String methodName, Boolean async) at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result, String methodName, Boolean sendToPipe) at System.Data.SqlClient.SqlCommand.ExecuteNonQuery() at Microsoft.SharePoint.Utilities.SqlSession.ExecuteScript(TextReader textReader, Int32 commandTimeout) at Microsoft.SharePoint.Utilities.SqlSession.ExecuteScript(String path, Int32 commandTimeout) at Microsoft.SharePoint.Upgrade.SPUtility.ExecuteSqlFile(SqlSession sqlSession, ISqlSession isqlSession, SqlFile sqlFileId, Int32 timeOut) at Microsoft.SharePoint.Upgrade.SPUtility.ExecuteSqlFile(SqlSession sqlSession, SqlFile sqlFileId, Int32 timeOut) at Microsoft.SharePoint.Upgrade.SPContentDatabaseSequence.Upgrade() at Microsoft.SharePoint.Upgrade.SPManager.Upgrade(Object o, Boolean bRecurse)

Also, the following error message is logged in the psconfig.log file:

06/14/2010 12:00:00 1 ERR Failed to upgrade SharePoint Products and Technologies. Failed to upgrade SharePoint Products and Technologies. Further information regarding this failure can be found at C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\LOGS\Upgrade.log. An exception of type Microsoft.SharePoint.PostSetupConfiguration.PostSetupConfigurationTaskException was thrown. Additional exception information: The upgrade command is invalid or a failure has been encountered. Failed to upgrade SharePoint Products and Technologies. Microsoft.SharePoint.PostSetupConfiguration.PostSetupConfigurationTaskException: Exception of type 'Microsoft.SharePoint.PostSetupConfiguration.PostSetupConfigurationTaskException' was thrown. at Microsoft.SharePoint.PostSetupConfiguration.UpgradeTask.Run() at Microsoft.SharePoint.PostSetupConfiguration.TaskThread.ExecuteTask()

Also, the following error message may be logged in the Application log:

Event Type: Error
Event Source: Windows SharePoint Services 3
Event ID: 3760 Event Category: Database
Description: SQL Database 'SharePoint_Config_' on SQL Server instance 'ComputeName\Microsoft##SSEE' not found. Additional error information from SQL Server is included below. Cannot open database "SharePoint_Config_" requested by the login. The login failed.

Also, the following error message may be logged in Microsoft SQL Server Management Studio Express:

Cannot show requested dialog.
ADDITIONAL INFORMATION: Cannot show requested dialog. (Microsoft.SqlServer.Express.SqlMgmt)
An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.Express.ConnectionInfo)
Database 'SharePoint_Config_' is already open and can only have one user at a time. (Microsoft SQL Server, Error: 924)

Cannot connect to the configuration database.
The database SharePoint_Config_ is not accessible. (Microsoft.SqlServer.Express.ObjectExplorer)

Cause

This problem may occur when you install an update manually or through Windows Update. If another service has connected to the Windows Internal Database prior to the upgrade, SharePoint cannot make a connection, and the upgrade fails. This puts the farm into an inconsistent state that must be resolved by a successful upgrade operation.

Resolution

To resolve this problem, follow these steps to restart the SharePoint services and to complete upgrade:

1. Click Start, click Run, type cmd, and then click OK.
2. Locate the following folder:
   %COMMONPROGRAMFILES%\Microsoft Shared\Web server extensions\12\BIN
3. At a command prompt, type the following command, and then press ENTER:
   psconfig -cmd upgrade -inplace b2b -wait –force
4. If the upgrade does not complete succussfully, type the following commands at the command prompt, and press ENTER after each command:
   net stop MSSQL$MICROSOFT##SSEE
   net start MSSQL$MICROSOFT##SSEE
   psconfig -cmd upgrade -inplace b2b -wait -force

You are prompted for authentication on a SharePoint website

Symptoms

When you try to browse a SharePoint website, you are prompted for authentication.

Cause

Windows Server 2003 SP1 and Windows Server 2008 include a loopback check security feature that is designed to help prevent reflection attacks on your computer. Therefore, authentication fails if the FQDN or the custom host header that you use does not match the local computer name.

Resolution

1. Workaround
   
   
   There are two methods to work around this issue, use one of the following methods, as appropriate for your situation.
   
   
   
   Method 1: Specify host names (Preferred method if NTLM authentication is desired)
   
   To specify the host names that are mapped to the loopback address and can connect to Web sites on your computer, follow these steps:
   
   1.     Set the DisableStrictNameChecking registry entry to 1. For more information about how to do this, click the following article number to view the article in the Microsoft Knowledge Base:
   
   281308 (http://support.microsoft.com/kb/281308/)   (http://support.microsoft.com/kb/281308/ (http://support.microsoft.com/kb/281308/) ) Connecting to SMB share on a Windows 2000-based computer or a Windows Server 2003-based computer may not work with an alias name
   
   2.     Click Start, click Run, type regedit, and then click OK.
   
   3.     In Registry Editor, locate and then click the following registry key:
   
   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\MSV1_0
   
   4.     Right-click MSV1_0, point to New, and then click Multi-String Value.
   
   5.     Type BackConnectionHostNames, and then press ENTER.
   
   6.     Right-click BackConnectionHostNames, and then click Modify.
   
   7.       In the Value data box, type the host name or the host names for the sites that are on the local computer, each in a separate line, and then click OK.
   
   8.       Quit Registry Editor, and then restart the IISAdmin service. ()
   
   
   
   
   
   Method 2: Disable the loopback check (less-recommended method)
   
   The second method is to disable the loopback check by setting the DisableLoopbackCheck registry key.
   
   To set the DisableLoopbackCheck registry key, follow these steps:
   
   1.     Set the DisableStrictNameChecking registry entry to 1. For more information about how to do this, click the following article number to view the article in the Microsoft Knowledge Base:
   
   281308 (http://support.microsoft.com/kb/281308/)   (http://support.microsoft.com/kb/281308/ (http://support.microsoft.com/kb/281308/) ) Connecting to SMB share on a Windows 2000-based computer or a Windows Server 2003-based computer may not work with an alias name
   
   2.     Click Start, click Run, type regedit, and then click OK.
   
   3.     In Registry Editor, locate and then click the following registry key:
   
   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa
   
   4.     Right-click Lsa, point to New, and then click DWORD Value.
   
   5.     Type DisableLoopbackCheck, and then press ENTER.
   
   6.     Right-click DisableLoopbackCheck, and then click Modify.
   
   7.     In the Value data box, type 1, and then click OK.

Back to the top

How to force the Windows SharePoint Services 3.0 upgrade by using the Psconfig.exe tool at a command prompt

Perform the upgrade by running the Psconfig.exe tool at a command prompt. For example, type the following command:

psconfig -cmd upgrade -inplace b2b –force

How to troubleshoot common errors that occur when you run the SharePoint Products and Technologies Configuration Wizard on a computer that is running Windows SharePoint

http://support.microsoft.com/kb/944267

To resolve this issue, clear the file system cache on all servers in the server farm on which the Windows SharePoint Services Timer service is running. To do this, follow these steps:

1. Stop the Timer service. To do this, follow these steps:
   1. Click Start, point to Administrative Tools, and then click Services.
   2. Right-click Windows SharePoint Services Timer, and then click Stop.
   3. Close the Services console.
2. On the computer that is running Microsoft Office SharePoint Server 2007 and on which the Central Administration site is hosted, click Start, click Run, type explorer, and then press ENTER.
3. In Windows Explorer, locate and then double-click the following folder:
   Drive:\Documents and Settings\All Users\Application Data\Microsoft\SharePoint\Config\GUID
   Notes
   • The Drive placeholder specifies the letter of the drive on which Windows is installed. By default, Windows is installed on drive C.
   • The GUID placeholder specifies the GUID folder.
   • The Application Data folder may be hidden. To view the hidden folder, follow these steps:
     1. On the Tools menu, click Folder Options.
     2. Click the View tab.
     3. In the Advanced settings list, click Show hidden files and folders under Hidden files and folders, and then click OK.
   • In Windows Server 2008, the configuration cache is in the following location:
     Drive:\ProgramData\Microsoft\SharePoint\Config\GUID
4. Back up the Cache.ini file.
5. Delete all the XML configuration files in the GUID folder. Do this so that you can verify that the GUID folder is replaced by new XML configuration files when the cache is rebuilt.
   
   Note When you empty the configuration cache in the GUID folder, make sure that you do not delete the GUID folder and the Cache.ini file that is located in the GUID folder.
6. Double-click the Cache.ini file.
7. On the Edit menu, click Select All.
8. On the Edit menu, click Delete.
9. Type 1, and then click Save on the File menu.
10. On the File menu, click Exit.
11. Start the Timer service. To do this, follow these steps:
    1. Click Start, point to Administrative Tools, and then click Services.
    2. Right-click Windows SharePoint Services Timer, and then click Start.
    3. Close the Services console.
    Note The file system cache is re-created after you perform this procedure. Make sure that you perform this procedure on all servers in the server farm.
12.  Make sure that the Cache.ini file has been updated. For example it should no longer be 1 if the cache has been updated.
13. Click Start, point to Programs, point to Administrative Tools, and then click SharePoint 3.0 Central Administration.
14. Click the Operations tab, and then click Timer job status under Global Configuration.
15. In the list of timer jobs, verify that the status of the Config Refresh entry is Succeeded.
16. On the File menu, click Close.

SPUpdatedConcurrencyException While Installing SharePoint 2010 Service Pack 1

http://sajiviswam.wordpress.com/2012/03/01/spupdatedconcurrencyexception-while-installing-sharepoint-2010-service-pack-1-2/

After installing SharePoint 2010 Service Pack 1 for SharePoint Server, the SharePoint Products and Technologies Configuration Wizard (either from GUI or using PowerShell) may fail throwing the following exception.

An exception of type Microsoft.SharePoint.Administration.SPUpdatedConcurrencyException was thrown. Additional exception information: An update conflict has occurred, and you must re-try this action. The object SPUpgradeSession Name=Upgrade -20110924-194525-15 was updated by DOMAIN\ACCOUNT, in the PSCONFIG (7240) process, on machine SERVER. View the tracing log for more information about the conflict.
Total number of configuration settings run: 3
Total number of successful configuration settings: 2
Total number of unsuccessful configuration settings: 1
Successfully stopped the configuration of SharePoint Products.
Configuration of SharePoint Products failed. Configuration must be performed before you use SharePoint Products. For further details, see the diagnostic log located at [LOCATION OF LOG] and the application event log.

This KB article describes the cause and and solution for this issue. The suggested solution is to clear Windows SharePoint Services configuration cache. Unfortunately, this may not work in most of the cases. If it doesn’t work, there is another workaround. This is by setting the ‘command-line-upgrade-running’ configuration property to ‘No’ and running Configuration Wizard again. Entire steps are given below.

1. Open command prompt as administrator.
2. Type in the command: stsadm -o setproperty -pn command-line-upgrade-running -pv No
3. Restart IIS and SP Timer
4. Run configuration wizard: psconfig -cmd upgrade -inplace b2b -wait –force