Search

SQL 2008 R2 with Slipstreamed SP2 fails when install includes Reporting Services by Nicholas Cain

Closed
as Not Reproducible Help for as Not Reproducible

5
0
Sign in
to vote
Type: Bug
ID: 771260
Opened: 11/15/2012 8:54:10 AM
Access Restriction: Public
0
Workaround(s)
3
User(s) can reproduce this bug
I have the base SQL 2008 R2 media and have downloaded and slipstreamed Service Pack 2 by the same method described at http://blogs.msdn.com/b/petersad/archive/2011/07/13/how-to-slipstream-sql-server-2008-r2-and-a-sql-server-2008-r2-service-pack-1-sp1.aspx

When installing SQL Server using this slipstream there are no issues, however when attempting to also include Reporting Services I get a Watson error when it attempts to start the SSRS service. Reporting Services will not start and it also cannot be patched by rerunning SP2 against the install.
Details (expand)

Product Language

English

Version

SQL Server 2008 R2 SP2 CTP

Category

Setup

Operating System

Windows Server 2008 R2 Enterprise (SP1)

Operating System Language

US English

Steps to Reproduce

Start with basic SQL 2008 R2 media, then download and extract the Service Pack 2 files.

Slipstream Service Pack 2 following the method at http://blogs.msdn.com/b/petersad/archive/2011/07/13/how-to-slipstream-sql-server-2008-r2-and-a-sql-server-2008-r2-service-pack-1-sp1.aspx

Perform an install of SQL Server being sure to include the Reporting Services piece.

Actual Results

----------------------------------------------------------------------
Running Action: SqlRSConfigAction_install_Startup_Cpu64
Action Data:
Feature = RS_Server_Adv_sql_rs_Cpu64
Scenario = install
Timing = Startup
ConfigObjectType = Microsoft.SqlServer.Configuration.RSExtension.SQLRSConfigurationPrivate
FeatureName = RS_Server_Adv
FeatureCpuType = Cpu64
FeaturePackageId = sql_rs
SlipstreamInstall = 1
STATUS: Install_Startup started
Entering StartRSService()
Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine
Sco: Attempting to open registry subkey SOFTWARE\Microsoft\Microsoft SQL Server\MSRS10_50.MSSQLSERVER\Setup
Sco: Attempting to get registry value SQLPath
Sco: Returning service status Stopped
Current status of the RS service before starting the service is 'Stopped'.
Sco: Attempting to start service ReportServer
Sco: Attempting to start service ReportServer, start parameters
Sco: Attempting to start service ReportServer
Watson Bucket 1
Original Parameter Values

Parameter 0 : SQL Server 2008 R2@RTM@

Parameter 2 : Microsoft.SqlServer.Configuration.Sco.Service.StartService

Parameter 3 : Microsoft.SqlServer.Configuration.Sco.ScoException@1211@1

Parameter 4 : System.ComponentModel.Win32Exception@-2147467259

Parameter 5 : SqlRSConfigAction_install_Startup

Parameter 7 : ReportServer

Parameter 8 : ReportServer


Final Parameter Values

Parameter 0 : SQL Server 2008 R2@RTM@

Parameter 2 : 0xDC112D1C

Parameter 3 : 0xD3BEBD98@1211@1

Parameter 4 : 0xDC80C325

Parameter 5 : SqlRSConfigAction_install_Startup

Parameter 7 : 0x22C8A7B3

Parameter 8 : 0x22C8A7B3

Expected Results

Successful installation of all components.

Platform

X64

Virtualization

 
File Attachments
File Name Submitted By Submitted On File Size  
LogFiles.cab 11/15/2012 4.97 MB
Sign in to post a comment.
Posted by Microsoft on 1/15/2013 at 4:01 PM
Thank you for reporting this issue. We tried this scenario on a clean machine and could not reproduce the errors.

The following scenarios succeeded on Windows Server 2008 R2 SP1:

1. Created SP2 slipstream install medium as described at [1].

2.1 GUI-based install of SQLENGINE and RS -> Installation successful

2.2 Customer seems to have tried installing combination SQLENGINE,REPLICATION,FULLTEXT,RS,BIDS,CONN,IS,BC,BOL,SSMS,ADV_SSMS as quiet command line installation. Did exact same thing -> Installation successful



Slipstream installation of SQL Server 2008 with SP2 + RS alone does not seem to cause the issue.
Posted by Microsoft on 11/15/2012 at 12:08 PM
Hi Nicholas, thanks for taking the time to report this issue & include logfiles. We will take a look at this issue.

thanks,
[SQL Server Team]
Posted by Nicholas Cain on 11/15/2012 at 8:55 AM
Logfiles from the install have been attached.
Note: the same issue does not apply to Service Pack 1.
Sign in to post a workaround.