August 5, 2010 at 3:20 am
Has anyone performed an upgrade of SQL 2008 to SQL 2008 R2?
I'm running SQL2008 sp1 EE and am planning upgrading to SQL 2008 R2 EE.
Are there any known issues or is this a straight forward processs?
August 5, 2010 at 3:35 am
First of all I would run the upgrade advisor (link below), once you have done this then test, test and more testing.
It should be straigth forward from a SQL point of view, but take into consideration 3rd party apps, SQL jobs etc.
In most of my upgrades they have not be inplace upgrade as I took the time to upgrade the h/w.
August 5, 2010 at 6:25 am
Total agreement on upgrading the hard way. I've only done a few 2008 to R2 upgrades, but they've been seemless to the point of no one noticing. I'd just be sure that the databases being upgraded are not running in a compatibility level. I think you'd be more likely to hit issues there.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
February 22, 2011 at 4:38 am
Hi There,
The SQL Upgrade Advisor doesn't work if I run it on my SQL 2008 instance.
It give the following error:
SQL Server version: 10.00.4000 is not supported by this release of Upgrade Advisor, only SQL2000 or SQL2005 is supported.
Do you have any idea how I can run it or why it is giving me this error? The current version is:
Microsoft SQL Server 2008 (SP2) - 10.0.4000.0 (X64) Sep 16 2010 19:43:16 Copyright (c) 1988-2008 Microsoft Corporation Standard Edition (64-bit) on Windows NT 6.1 <X64> (Build 7600: ) (VM)
February 22, 2011 at 6:01 am
Fox87 (2/22/2011)
Hi There,The SQL Upgrade Advisor doesn't work if I run it on my SQL 2008 instance.
It give the following error:
SQL Server version: 10.00.4000 is not supported by this release of Upgrade Advisor, only SQL2000 or SQL2005 is supported.
Do you have any idea how I can run it or why it is giving me this error? The current version is:
Microsoft SQL Server 2008 (SP2) - 10.0.4000.0 (X64) Sep 16 2010 19:43:16 Copyright (c) 1988-2008 Microsoft Corporation Standard Edition (64-bit) on Windows NT 6.1 <X64> (Build 7600: ) (VM)
I don't think there are any differences between 2008 & R2 for the upgrade advisor to deal with.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
August 1, 2011 at 1:57 pm
I am trying to upgrade from SQL 2008 to SQL 2008 R2 and it keeps failing to upgrade the database engine services. Can anyone help me figure out what I'm doing wrong?
Windows 7, 64 bit.
Running 2008 standard 2008 sp1 64 bit
upgrading to 2008 R2 standard 64 bit
Most of the upgrade succeeds but the database engine services fails to upgrade no matter what I do.
Thanks for any help!
-Mary
August 2, 2011 at 1:55 am
Thanks Grant,
I rebooted the server and changed the reg-edit files then it worked.
One thing I noticed the 2008 upgrade adviser doesn't pick up the custom assemblies issue as the R2 adviser.
August 2, 2011 at 2:02 am
Hi Mary,
Any other information in the Logs or Eventviewer?
August 2, 2011 at 2:06 am
Mary Truesdell (8/1/2011)
I am trying to upgrade from SQL 2008 to SQL 2008 R2 and it keeps failing to upgrade the database engine services. Can anyone help me figure out what I'm doing wrong?Windows 7, 64 bit.
Running 2008 standard 2008 sp1 64 bit
upgrading to 2008 R2 standard 64 bit
Most of the upgrade succeeds but the database engine services fails to upgrade no matter what I do.
Thanks for any help!
-Mary
Why did you change anything in the registry? It is not something good to do. You needed to have an upgrade advisor of 2008 R2 version. And while upgrading what errors did you encounter or did you happen to read the setup log that appears at the end of every upgrade(successful or failed). Post those logs for someone to give you some advice.
Chandan
August 2, 2011 at 9:40 am
I can copy and paste the info from the "summary" files in the installation log files. Would that help? Event viewer seemed to only give really vague errors.
Also, I didn't modify the registry, that was someone else who is having this problem.
August 2, 2011 at 12:16 pm
Mary Truesdell (8/2/2011)
I can copy and paste the info from the "summary" files in the installation log files. Would that help? Event viewer seemed to only give really vague errors.Also, I didn't modify the registry, that was someone else who is having this problem.
Yes that summary log will be helpful and I am sorry bout the registry thing, it was not meant for you.
Thanks
Chandan
August 2, 2011 at 12:32 pm
No worries. I just wanted to make sure we weren't getting confused.
This is the content from the plain summary file, there are two other summary files called global rules and component updates. Do you want those as well?
Overall summary:
Final result: SQL Server upgrade failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server using the following command line, and then rerun SQL Server Setup. Uninstall command line: setup /q /action=uninstall /instanceid=MSSQLSERVER /features=SQLEngine,Replication,FullText,AS,RS
Exit code (Decimal): -2068052377
Exit facility code: 1212
Exit error code: 1639
Exit message: SQL Server upgrade failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server using the following command line, and then rerun SQL Server Setup. Uninstall command line: setup /q /action=uninstall /instanceid=MSSQLSERVER /features=SQLEngine,Replication,FullText,AS,RS
Start time: 2011-07-21 10:56:38
End time: 2011-07-21 11:11:29
Requested action: Upgrade
Log with failure: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20110721_104721\sql_engine_core_inst_Cpu64_1.log
Exception help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=10.50.1600.1
Machine Properties:
Machine name: ITMTRUESDELL2
Machine processor count: 4
OS version: Windows 7
OS service pack:
OS region: United States
OS language: English (United States)
OS architecture: x64
Process architecture: 64 Bit
OS clustered: No
Product features discovered:
Product Instance Instance ID Feature Language Edition Version Clustered
Sql Server 2008 MSSQLSERVER MSSQL10.MSSQLSERVER Database Engine Services 1033 Standard Edition 10.2.4064.0 No
Sql Server 2008 MSSQLSERVER MSSQL10.MSSQLSERVER SQL Server Replication 1033 Standard Edition 10.2.4064.0 No
Sql Server 2008 MSSQLSERVER MSSQL10.MSSQLSERVER Full-Text Search 1033 Standard Edition 10.2.4000.0 No
Sql Server 2008 MSSQLSERVER MSAS10.MSSQLSERVER Analysis Services 1033 Standard Edition 10.2.4000.0 No
Sql Server 2008 MSSQLSERVER MSRS10.MSSQLSERVER Reporting Services 1033 Standard Edition 10.2.4064.0 No
Sql Server 2008 Management Tools - Basic 1033 Standard Edition 10.2.4064.0 No
Sql Server 2008 Management Tools - Complete 1033 Standard Edition 10.2.4064.0 No
Sql Server 2008 Client Tools Connectivity 1033 Standard Edition 10.2.4064.0 No
Sql Server 2008 Client Tools Backwards Compatibility 1033 Standard Edition 10.2.4064.0 No
Sql Server 2008 Client Tools SDK 1033 Standard Edition 10.2.4064.0 No
Sql Server 2008 Integration Services 1033 Standard Edition 10.2.4064.0 No
Package properties:
Description: SQL Server Database Services 2008 R2
ProductName: SQL Server 2008 R2
Type: RTM
Version: 10
SPLevel: 0
Installation location: \\eden.cincybible.priv\shares\Dept\IT\Techs\ISO Images\SQL 2008 R2 std proc\x64\setup Installation edition: STANDARD
User Input Settings:
ACTION: Upgrade
AGTDOMAINGROUP: <empty>
BROWSERSVCSTARTUPTYPE: Disabled
CONFIGURATIONFILE: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20110721_104721\ConfigurationFile.ini
CUSOURCE:
ENU: True
ERRORREPORTING: False
FAILOVERCLUSTERROLLOWNERSHIP: 2
FARMACCOUNT: <empty>
FARMADMINPORT: 0
FARMPASSWORD: *****
FTSVCACCOUNT: NT AUTHORITY\LOCAL SERVICE
FTSVCPASSWORD: *****
FTUPGRADEOPTION: Import
HELP: False
IACCEPTSQLSERVERLICENSETERMS: False
INDICATEPROGRESS: False
INSTANCEID: MSSQLSERVER
INSTANCENAME: MSSQLSERVER
ISSVCACCOUNT: NT AUTHORITY\NetworkService
ISSVCPASSWORD: *****
ISSVCSTARTUPTYPE: Automatic
PASSPHRASE: *****
PCUSOURCE:
PID: *****
QUIET: False
QUIETSIMPLE: False
RSCATALOGSERVERINSTANCENAME: ITMTRUESDELL2
RSUPGRADEDATABASEACCOUNT: sa
RSUPGRADEPASSWORD: *****
SQLDOMAINGROUP: <empty>
SQMREPORTING: True
UIMODE: Normal
X86: False
Configuration file: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20110721_104721\ConfigurationFile.ini
Detailed results:
Feature: Database Engine Services
Status: Failed: see logs for details
MSI status: Failed: see details below
MSI error code: 25012
MSI log file location: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20110721_104721\sql_engine_core_inst_Cpu64_1.log
MSI error description: There was an error attempting to remove the configuration of the product which prevents any other action from occuring. The current configuration of the product is being cancelled as a result.
Configuration status: Failed: see details below
Configuration error code: 0xD3BEBD98@1211@1
Configuration error description: Service 'SQLSERVERAGENT' start request failed.
Configuration log: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20110721_104721\Detail.txt
Feature: SQL Client Connectivity
Status: Passed
MSI status: Passed
Configuration status: Passed
Feature: SQL Client Connectivity SDK
Status: Passed
MSI status: Passed
Configuration status: Passed
Feature: SQL Writer
Status: Passed
MSI status: Passed
Configuration status: Passed
Feature: SQL Browser
Status: Passed
MSI status: Passed
Configuration status: Passed
Feature: SQL Server Replication
Status: Failed: see logs for details
MSI status: Failed: see details below
MSI error code: 25012
MSI log file location: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20110721_104721\sql_engine_core_inst_Cpu64_1.log
MSI error description: There was an error attempting to remove the configuration of the product which prevents any other action from occuring. The current configuration of the product is being cancelled as a result.
Configuration status: Failed: see details below
Configuration error code: 0xD3BEBD98@1211@1
Configuration error description: Service 'SQLSERVERAGENT' start request failed.
Configuration log: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20110721_104721\Detail.txt
Feature: Full-Text Search
Status: Failed: see logs for details
MSI status: Failed: see details below
MSI error code: 25012
MSI log file location: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20110721_104721\sql_engine_core_inst_Cpu64_1.log
MSI error description: There was an error attempting to remove the configuration of the product which prevents any other action from occuring. The current configuration of the product is being cancelled as a result.
Configuration status: Failed: see details below
Configuration error code: 0xD3BEBD98@1211@1
Configuration error description: Service 'SQLSERVERAGENT' start request failed.
Configuration log: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20110721_104721\Detail.txt
Feature: Analysis Services
Status: Failed: see logs for details
MSI status: Failed: see details below
MSI error code: 25012
MSI log file location: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20110721_104721\sql_engine_core_inst_Cpu64_1.log
MSI error description: There was an error attempting to remove the configuration of the product which prevents any other action from occuring. The current configuration of the product is being cancelled as a result.
Configuration status: Passed
Feature: Reporting Services
Status: Failed: see logs for details
MSI status: Failed: see details below
MSI error code: 25012
MSI log file location: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20110721_104721\sql_engine_core_inst_Cpu64_1.log
MSI error description: There was an error attempting to remove the configuration of the product which prevents any other action from occuring. The current configuration of the product is being cancelled as a result.
Configuration status: Failed: see details below
Configuration error code: 0xD3BEBD98@1211@1
Configuration error description: Service 'SQLSERVERAGENT' start request failed.
Configuration log: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20110721_104721\Detail.txt
Feature: Integration Services
Status: Passed
MSI status: Passed
Configuration status: Passed
Feature: SQL Compact Edition Tools
Status: Passed
MSI status: Passed
Configuration status: Passed
Feature: Client Tools Connectivity
Status: Passed
MSI status: Passed
Configuration status: Passed
Feature: Management Tools - Complete
Status: Passed
MSI status: Passed
Configuration status: Passed
Feature: Management Tools - Basic
Status: Passed
MSI status: Passed
Configuration status: Passed
Feature: Client Tools SDK
Status: Passed
MSI status: Passed
Configuration status: Passed
Feature: Client Tools Backwards Compatibility
Status: Passed
MSI status: Passed
Configuration status: Passed
Feature: Business Intelligence Development Studio
Status: Passed
MSI status: Passed
Configuration status: Passed
Feature: SQL Server Books Online
Status: Passed
MSI status: Passed
Configuration status: Passed
Rules with failures:
Global rules:
Scenario specific rules:
Rules report file: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20110721_104721\SystemConfigurationCheck_Report.htm
August 3, 2011 at 8:18 am
Ok, I tried this:
When prompted for a reboot (but given no option to do so) I aborted the installation and rebooted and then ran the install again.
After waiting with bated breath for 20 minutes, it finally errored out. Database Engine, Analysis Services, and a few other biggies all failed, but the smaller things like compatibility and connectivity features installed correctly. See attached screen shot for the summary screen I get at the end of the install.
Error during install
TITLE: Microsoft SQL Server 2008 R2 Setup
------------------------------
The following error has occurred:
There was an error attempting to remove the configuration of the product which prevents any other action from occuring. The current configuration of the product is being cancelled as a result.
------------------------------
Also at one point it said that it failed to start the SQL Server Agent Service.
Thoughts?
Mary Truesdell
Database Administrator
Cincinnati Christian University
August 3, 2011 at 12:32 pm
Mary Truesdell (8/3/2011)
Ok, I tried this:When prompted for a reboot (but given no option to do so) I aborted the installation and rebooted and then ran the install again.
After waiting with bated breath for 20 minutes, it finally errored out. Database Engine, Analysis Services, and a few other biggies all failed, but the smaller things like compatibility and connectivity features installed correctly. See attached screen shot for the summary screen I get at the end of the install.
Error during install
TITLE: Microsoft SQL Server 2008 R2 Setup
------------------------------
The following error has occurred:
There was an error attempting to remove the configuration of the product which prevents any other action from occuring. The current configuration of the product is being cancelled as a result.
------------------------------
Also at one point it said that it failed to start the SQL Server Agent Service.
Thoughts?
Mary Truesdell
Database Administrator
Cincinnati Christian University
I am sorry for not able to reply you on time. I am from a different time zone so things can go slow.From your logs, I believe that it is the SQL agent that is causing issues in your installation.
Forget the upgrade for a while, can you please check if the SQL agent in your current 2008 env. is running. You can find it in the configuration services. What is its current status? If it is stopped, what happens if you start it. Can you find all this information.
August 3, 2011 at 2:03 pm
Ok, I am going to have to uninstall and clean up the bad install before I can try again. Windows seems to have deleted my restore point. >.<
Viewing 15 posts - 1 through 15 (of 25 total)
You must be logged in to reply to this topic. Login to reply