.NET Tutorials, Forums, Interview Questions And Answers
Welcome :Guest
Sign In
Win Surprise Gifts!!!

Top 5 Contributors of the Month
david stephan
Gaurav Pal
Post New Web Links

Upgrade fails: "SQL Server 2008 R2 Feature Upgrade"

Posted By:      Posted Date: October 01, 2010    Points: 0   Category :Sql Server

Shouldn't I be able to upgrade to 2008 R2?

Current version:

Microsoft SQL Server 2008 (SP1) - 10.0.2531.0 (X64)   Mar 29 2009 10:11:52   Copyright (c) 1988-2008 Microsoft Corporation  Standard Edition (64-bit) on Windows NT 6.1 <X64> (Build 7600: )

View Complete Post

More Related Resource Links

Upgrade to SQL 2008 R2 Enterprise fails

Trying to upgrade one of my SQL 2008 SP1 Enterprise (v 10.0.2531.0) edition to SQL 2008 R2 Enterprise, the OS is Windows Server 2008 (x64) SP1.  The process fails with no explanation beyond this:   Description:   SQL Server 2008 R2 Setup has encountered an error.   Problem signature:   Problem Event Name: SQL100MSI   Problem Signature 01: 10.50.1600.1   Problem Signature 02: Unknown   Problem Signature 03: SqlSupport.msi   Problem Signature 04: 0x162A16FE   Problem Signature 05: 0x1645   Problem Signature 06: Install_SqlSupport   OS Version:      6.0.6001.   Locale ID:           1033   Additional information about the problem:   LCID:    1033 I tried running the installation through Remote Desktops with Administrator login and also through Remote Desktop Connection with Administrator login, I got the same error each time.  There are no users connected to the database.  The installation is English. I have viewed the thread on Connect and it is not applicable as I'm running an English installation, not Italian and I am using the Administrator login. I saw another on another thread where they

SQL Job Running the Upgrade Step, but the Step Fails

I have reviewed the following thread (http://social.msdn.microsoft.com/Forums/en-US/sqldatabaseengine/thread/1c06be77-3fa9-42d8-9803-6649be65afd6), but I do not think it applies to my case, b/c I have no other processes running, except the RESTORE DATABASE process. In SSMS, when I EXEC spCent, the user-defined stored procedure runs successfully. When the same SQL command is executed from a SQL Job, the job fails, and job history is like the following: Message: Executed as user: NT AUTHORITY\NETWORK SERVICE. ...on file 1. [SQLSTATE 01000] (Message 4035) Processed 1 pages for database 'Cent', file 'Cent_log' on file 1. [SQLSTATE 01000] (Message 4035) Converting database 'Cent' from version 611 to the current version 655. [SQLSTATE 01000] (Message 944)  Database 'Cent' running the upgrade step from version 611 to version 621. [SQLSTATE 01000] (Message 951)  Database 'Cent' running the upgrade step from version 621 to version 622.     .     .     . [SQLSTATE 01000] (Message 951)  Database 'Cent' running the upgrade step from version 652 to version 653. [SQLSTATE 01000] (Message 951)  Database 'Cent' running the upgrade step from vers...  The step failed. As mentioned above, the stored proc can be successfully executed from within SSMS. The stored proc looks like this: ALTER PROCEDURE [dbo].[sp

Inplace upgrade from moss 2007 to 2010 fails

Hello experts I have tried without success to do an inplace upgarde of a moss 2007 installation that I would consider very basic. The upgrade process itself seems fine but after you finish the configuration wizard and it attempts to go to the upgrade status page you get The provider 'CurrentNavigation' specified for the defaultProvider does not exist in the providers collection. (C:\inetpub\wwwroot\wss\VirtualDirectories\39291\web.config line 385) When i check the upgrade errors logs im getting the following [OWSTIMER] [SPSiteWssSequence2] [INFO] [8/9/2010 2:18:36 PM]: SPSite Url=http://ehbmossserver/mysite [OWSTIMER] [SPSiteWssSequence2] [ERROR] [8/9/2010 2:18:36 PM]: Feature upgrade failed for Feature 'PremiumSite' (Id: '8581a8a7-cf16-4770-ac54-260265ddb0b2') in Site 'http://ehbmossserver/mysite'. [OWSTIMER] [SPSiteWssSequence2] [INFO] [8/9/2010 2:18:36 PM]: SPSite Url=http://ehbmossserver/mysite [OWSTIMER] [SPSiteWssSequence2] [ERROR] [8/9/2010 2:18:36 PM]: Exception: Dependency feature with id 4c42ab64-55af-4c7c-986a-ac216a6e0c0e for feature 'PremiumSite' (id: 8581a8a7-cf16-4770-ac54-260265ddb0b2) is not installed. [OWSTIMER] [SPSiteWssSequence2] [INFO] [8/9/2010 2:18:36 PM]: SPSite Url=http://ehbmossserver/mysite [OWSTIMER] [SPSiteWssSequence2] [ERROR] [8/9/2010 2:18:36 PM]: at Microsoft.SharePoint.SPFeature.HandleUpgradeException(Exception e, Boolean continue

SharePoint 2010 in-place upgrade fails



I have tried the in-place upgrade in a test site and its fails. When I remove the SSP the upgrade was succesfull.

In the error log there is a backup device reference 'C:\DATA\slq_Backup\INT_SharedServices_DB_backup.dat'. This file is missing now. Maybe this is a previous config, but I can't remember it. In the SQL Server 2008 I have not found any backup device. We use third partly backup solution. I don't know where the corresponding backup file is configured.

Error log:

[psconfigui] [SPConfigurationDatabaseSequence2] [INFO] [2010.09.22. 12:12:55]: SPConfigurationDatabase Name=INT_ConfigDB
[psconfigui] [SPConfigurationDatabaseSequence2] [WARNING] [2010.09.22. 12:12:55]: Object with Id 3db7b513-5995-460e-8eee-c9e9bb67cc7f and class id 92e1ba91-03dc-4d85-8978-8c6224d84d5e could not be deserialized. Most likely its type is no longer a sub class of SPPersistedObject.
[psconfigui] [SPConfigurationDatabaseSequence2] [INFO] [2010.09.22. 12:12:57]: SPConfigurationDatabase Name=INT_ConfigDB
[psconfigui] [SPConfigurationDatabaseSequence2] [WARNING] [2010.09.22. 12:12:57]: Object with Id a7966ae0-4cea-464e-8076-d0b44a9acd38 and class id 92e1ba91-03dc-4d85-8978-8c6224d84d5e could not be deserialized. Most likely its type is no longer a sub class of SPPersistedObject.
[psconfigui] [SPConfigurationDatabaseSequence2] [IN

MOSS 2007 to SharePoint 2010 Upgrade Fails - Object with Id 57bdacb5-31fe-4f4c-bdb3-3caf048474bd and


Ok apart from deleting these Classes and Objects what else can be done. Any one know a way around. Just to help you find them if you have a similar error look in the Classes and Objects Tables in the Offending database listed in the error message. In this error message below it is SharePoint_Config. How I found them,  yes its like looking for a needle in a hey stack see this post, very handly sql query.

I have a copy of a VM I can create again so I am going to try deleting these and if this works I will Answer my own post. This of course is unsupported and purely a hack hence why I am posting searching for enlightenment. Of course I have other errors so this may merely negate the first one.



[psconfigui] [SPConfigurationDatabaseSequence2] [INFO] [9/30/2010 3:44:42 PM]: SPConfigurationDatabase Name=SharePoint_Config
[psconfigui] [SPConfigurationDatabaseSequence2] [WARNING] [9/30/2010 3:44:42 PM]: Object with Id 57bdacb5-31fe-4f4c-bdb3-3caf048474bd and class id 92e1ba91-03dc-4d85-8978-8c6224d84d5e could not be deserialized. Most likely its type is no longer a sub class of SPPersistedObject.
[OWSTIMER] [UserProfileApplicationSequence] [INFO] [9/30/20

MOSS 2007 to SharePoint 2010 Upgrade Fails - Exception: The user or group 'wsaarole:wsaa administra


Ok the top part of the error I have tracked down to some entries in the SharePoint_Config database (Classes, Objects, TimerRunningJobs) and since I have a VM I am going to study them and try deleting them probably, if it dies I will delete this VM and roll up another VM in my case its a timer job that I am guessing the farm can live without.

The other error further down is more of a concern to me which is the one I listed above. The Group exists and it is in the farm and appears to be healthy no errors in preugrade check or the like or in the Farm. When upgrading the show stopper for me is that the content databases will not upgrade (assuming they upgrade FBA I can configure) the chicken and egg issue for me is this is an FBA farm, so is it the case that b/c FBA is missing not configured yet on the other side of the upgrade in 2010 that these content dbs connected to FBA (by FBA users in the content dbs) will upgrade affter FBA is configured ( I haven't tried this yet sorting my error log one error at a time). The Particular content dbs with an issue are shared services and the main site collection db which includes my sites site collections also.

[psconfigui] [SPConfigurationDatabaseSequence2] [INFO] [9/30/2010 3:44:42 PM]: SPConfigurationDatabase Name=SharePoint_Config
[psconfigui] [SPConfigurationDatabaseSequence2] [WARNING] [9/

Upgrade of SQL Server 2008 x64 Developer to 2008 R2 x64 developer fails - upgrade architecture misma


I'm trying to upgrade a SQL Server 2008 x64 Developer install to a 2008 R2 x64 Developer Install. Just before it actually upgrades, one of the upgrade rules fails - upgrade architecture mismatch.

Is there a way to check what is really causing this failure, so that it can be overcome?

Thank you.

SP3 Upgrade : SQLXML4 fails

I got the following error msg while upgrading to SP3 from SP2, Everything else succeeds but for SQLXML4. I was also able to apply the new MS09-52 patch later on (which takes sql to 4053). Needed some help on this error, thx.

Product                   : SQLXML4
Product Version (Previous): 3042
Product Version (Final)   :
Status                    : Failure
Log File                  : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\Redist9_Hotfix_KB955706_sqlxml4.msi.log
Error Number              : 1714
Error Description         : MSP Error: 1714  The older version of SQLXML4 cannot be removed.  Contact your technical support group. 

Upgrade from R2 evaluation to Workgroup fails with incorrect key message



I have just tried to upgrade an installation of SQL Server 2008 R2 Evaluation to a licensed copy of R2 Workgroup. When I go into the "Edition Upgrade" wizard and enter my product key the software informs me that:

"The SQL Server product key is not valid. To proceed, re-enter the product key values from the Certificate of Authenticity (COA) or SQL Server packaging".

I know that I haven't mis-typed the key because I have tried it many times and checked it character by character.

This upgrade option is essential for our deployment of SQL Server to our clients. If I perform a clean installation and enter the product key during setup the key is accepted.

Is this a known problem? What is the workaround?



Mike Ashton

SQL 2008 SP2 succefull but instance start fails - Script level upgrade for database 'master' faile


after installing SP2 instance starts and stops with error:

Script level upgrade for database 'master' failed because upgrade step 'sqlagent100_msdb_upgrade.sql' encountered error 5831, state 1, severity 16. This is a serious error condition which might interfere with regular operation and the database will be taken offline. If the error happened during upgrade of the 'master' database, it will prevent the entire SQL Server instance from starting. Examine the previous errorlog entries for errors, take the appropriate corrective actions and re-start the database so that the script upgrade steps run to completion.

Already tried without success:
- enabled SA account (was disabled) http://support.microsoft.com/kb/960781/en-us
- uninstalled SP2 -> other error, but same problems with running the script



Upgrade fails because of missing non custom site definitions.


Hi, we are trying to upgrade our MOSS 2007 installation. From the beginning i had lots of errors in the preupgradecheck and test-spcontentdb. But now i only have a few left, too bad they are making the whole "Mount-SPContentDB" to fail.

So first, a little overview of the environment:

Old MOSS: Windows Server 2008 x86, MOSS 2007 SP2 with October cumulutive hotfixes. Swedish Language Pack installed. Enterprise features enabled.
OLD DB: Windows Server 2008 x86, SQL 2005

New MOSS: Windows Server 2008 R2, Sharepoint Server 2010, Swedish Language Pack installed. Enterprise features enabled.
New DB: Windows Server 2008 R2, SQL 2008 R2

Here is the erros from the preupgradecheck:

 Issue : Missing server file or server configuration issues 
Server side files are referenced in the content databases, but are not installed on the server. Without these files, the sites may not function completely or the content may not render correctly. Also, upgrade or post upgrade issues may occur if these files are not available in the new version environment.The following web part(s) are referenced by the content, but they are not installed on the web server
Id = e6377261-6920-bbfe-501f-fda7a61db10f, Type = Unknown, Reference = 3, Status = Missing
Id = b03e1652-5399-916f-f123-46a028d419ac, Type = Unknown, Reference = 2

Upgrade from 2005 to 2008 fails with error MSSQLSERVER.INACTIVE

I am trying to upgrade my copy of SQL 2005 Ent edition to 2008, the first time i tried this it passed all checks and seemed to install ok.  When I tried to run it it was corupt.
I have since removed the 2008 install and tried to re-install but I keep getting the following message.
The Instance ID 'MSSQLSERVER' is already in use by SQL server instance 'MSSQLSERVER.INACTIVE'. To conrinue, specify a unique Instance ID
Help! how can I upgrade again, I can not get passed this error.

2008 R2 Upgrade Advisor from command prompt fails


I've run the 2008 R2 Upgrade Advisor (from the GUI) successfully, finding several upgrade issues in a run which takes around 20 minutes. When I run the command prompt version of the tool, using the config file created by the GUI run, it returns immediately with no error message and having created no report. Here's the command:

C:\>"C:\Program Files\Microsoft SQL Server 2008 R2 Upgrade Advisor\UpgradeAdvisorWizardCmd.exe" -ConfigFile "C:\Documents and Settings\MyLogin\My Documents\SQLServer 2008 R2 Upgrade Advisor Reports\MyServer\Config.xml"

Why is the command doing nothing? I need this to automate my pre-upgrade analysis work.

Best Way to Upgrade Using Web Setup Project


Hi there,

I am using VS2005.

I don't have much experience with web setup projects, but I now need to create a decent windows installer in order to allow customers to install one of our web applications. I have created a simple web setup project and it works fine, but not when it comes to upgrades of the application.

If for instance I install version 1.0 on a machine, and then later I try to install version 2.0, I don't seem to have the control that I would like... I can specify in the web setup project that the installer must enforce an uninstall of previous version, but then all application files and logs are uninstalled as well. If I let the application just install itself over the older version, it seems to leave some old DLL's there - it then causes issues in the application because DLL version conflicts.

My basic requirement is that I would like th installer to upgrade the old version with all the files required, but leave any application and log files in tact - this way the customer won't have to reconfigure the application after install.

What is the best way to handle this?

ToggleDebugCompilation fails trying to perform "an unauthorised operation"



We're having a problem with the Visual Studio 2008 RTW version of the web deployment projects on a colleagues machine. The project works fine if I run it on my machine, but when he tries to run it on his machine he gets:

<SNIP : Most output removed>
  Task "Exec"
    if exist ".\TempBuildDir\" rd /s /q ".\TempBuildDir\"
  Done executing task "Exec".
  Using "ToggleDebugCompilation" task from assembly "C:\Program Files\MSBuild\Microsoft\WebDeployment\v9.0\Microsoft.WebDeployment.Tasks.dll".
  Task "ToggleDebugCompilation"
    Updating Web.config <compilation> element debug attribute to 'True'.
    C:\Program Files\MSBuild\Microsoft\WebDeployment\v9.0\Microsoft.WebDeployment.targets(639,7): error : Attempted to perform an unauthorized operation.
    C:\Program Files\MSBuild\Microsoft\WebDeployment\v9.0\Microsoft.WebDeployment.targets(639,7): error MSB4018: The "ToggleDebugCompilation" task failed unexpectedly.
    C:\Program Files\MSBuild\Microsoft\WebDeployment\v9.0\Microsoft.WebDeployment.targets(639,7): error MSB4018: System.ArgumentNullException: Parameter "message" cannot be null.
    C:\Program Files\MSBuild\Microsoft\WebDeployment

ArrayList.ToArray fails!


In my app, I have code similar to the following:



               ArrayList alStartFrames = new ArrayList();
                byte[] abytTest = { 1, 2 };


                byte[] abytCombinedFrame = (byte[])alStartFrames.ToArray(typeof(byte));

            catch (Exception ex)

The call to ToArray always fails and the exception is caught even though I'm pretty sure alStartFrames is an array list of byte arrays. Anyone have any insight on why this is happening?! TIA

Who Goes There?: Upgrade Your Site's Authentication with the New ASP.NET 2.0 Membership API


Here Dino Esposito and Andrea Saltarello cover the plumbing of the Membership API and its inherently extensible nature, based on pluggable providers. To demonstrate the features, they take an existing ASP.NET 1.x authentication mechanism and port it to ASP.NET 2.0, exposing the legacy authentication mechanism through the new Membership API.

Dino Esposito and Andrea Saltarello

MSDN Magazine November 2005

ASP.NetWindows Application  .NET Framework  C#  VB.Net  ADO.Net  
Sql Server  SharePoint  Silverlight  Others  All   

Hall of Fame    Twitter   Terms of Service    Privacy Policy    Contact Us    Archives   Tell A Friend