I was told in the Windows Server 2008 R2 Hyper-V forum they no longer wished to attempt to assist me with my issue. http://social.technet.microsoft.com/Forums/en-US/windowsserver2008r2virtualization/thread/8be91c1f-e293-45bf-9734-5d9fc1d60f3f/  And so was referred here.

I have attempted to clone a SQL Server 2008 R2 virtual machine in Hyper V. The cloning worked and the VM started just fine. However, the SQL Server will not start.  I ran Sysprep on the machine with the shutdown action.

Then in Hyper V performed an export of the VM to an alternate HD location. Followed this with an import in Hyper V. Gave the system a different name during the initial system startup. The new VM booted fine and everything on it worked except SQL Server.

The server was joined to a domain and I have reentered credentials for the domain account used as a service account for all SQL Services.

The error in the System event log is Event 7000, "The SQL Server (MSSQLSERVER) service failed to start due to the following error: The system cannot find the path specified."

I have verified that all the SQL folder/file structure is in place and at the same location/drives present in the server template VM. I attempted to drop the SQL server name using SQLCMD and the sp_dropserver stored procedure (the intent to then use sp_addserver %computername% in order to add it back withe new computer name) but was told SQLCMD was not a supported command.

Also attempted, as suggested in the Windows forum, to perform the following:

SET SQL=C:\install\SQL.sql
ECHO DECLARE @SRVNAME SYSNAME >%SQL%
ECHO SELECT @SRVNAME = @@SERVERNAME >>%SQL%
ECHO EXEC SP_DROPSERVER @SRVNAME >>%SQL%
ECHO EXEC SP_ADDSERVER '%COMPUTERNAME%' >>%SQL%
OSQL -E -n -w 20 -s -h-1 -i "%SQL%"
::DEL /F "%SQL%"

But, this also had no effect as the MSSQLSERVER service could not be started (I assume).

I attempted to run a repair on the installation, and this produced multiple errors regarding lack of all the system databases and multiple files. All of which (including the system DBs) I verified were actually present.

I am used to using VMWare to make this a practically seemless process using VM Templates (Have created multiple fully functional SQL Server 2008 templates and clones in VMWare), but Hyper V has no such basic capabilities. But, it is what have to work with at this time.

So...how do I get this process to work in Hyper V?

I have installed the evaluation version of SQL Server. When i click on the Intelligence Development Studio link it starts looking for the file devenv.exe. The file is not on the pc. Repeated installation twice making sure that all components are selected. What is causing this file not to be available?

Haris

I am facing the below error while upgrading from SQL 2008 to SQL 2008 r2

OS:Windows 2008 Enterprise r2--64 Bit

There was an error looking up common property"Restatrt Action" for resource 'SQL FileSTREAM Share(PROD)". Error: the private properties for resource'SQL Server Filestream share(PROD)' could not be saved. Error: The network path was not found.

Hi All,

While working on data compression I came across a statement mentioned in Books On Line (which is below)

When a heap is configured for page-level compression, pages receive page-level compression only in the following ways:

• Data is inserted by using the BULK INSERT syntax.
• Data is inserted using INSERT INTO...WITH (TABLOCK) syntax.
• A table is rebuilt by executing the ALTER TABLE..REBUILD statement with the PAGE compression option.

New pages allocated in a heap as part of DML operations will not use PAGE compession utill the heap is rebuilt. Rebuild the heap by removing and reapplying compression, or by creating and removing a clustered index.

Now the question..?

By reading the last 2 lines "New pages allocated...clustered index" what I am understanding is that once we enable data compression - page level compression on  a heap then what all data which is available (till the point when we enable compression) will be compressed but after that if any new page which is allocated needs to be compressed again (by methods mentioned in above statement).

However... in actual that is not the case. I created one table with Page Compression and later inserted 20K records and when I see the page using DBCC PAGE i am able to see that all pages are compressed properly.

Is this a BOL BUG or I am interprating it wrongly...?

Regards Gursethi Blog: http://gursethi.blogspot.com/ ++++ Please mark "Propose As Answer" if my answer helped ++++

Hi,

We are designing a commercial application, which uses SQL Server 2008 R2 Express as backend. Here is how we install it:

• We have a msi installer using Visual Studio installer, which packages the SQL Server Express setup file "SQLEXPRWT_x86_EN.exe" inside. 
• We wrote a small program using C# called "Database Installer", which uses System.Diagnostics.Process to extract SQLEXPRWT_x86_EN.exe (by passing "/x" as command-line parameter), then launch the setup.exe passing all the parameters such as "/QS" etc. to do a silent install.
• We used a manifest file in the Database Installer to declare that it needs admin right.
• We then launch this small program from within the msi installer as a "custom action".

Problem:

When the SQL Express goes to the "Setup Support Files" page, and when the progress bar go to 60%, and showing "ExecuteStandardTimingsWorkflow" stage, it got stuck there - it repeatedly pop up the "Please wait while SQL Server 2008 R2 Setup processes the current operation" window - again and again,  infinitely.

What I already know:

• It is not the Database Installer - for if I launch it separately it installs the database and sets up everything beautifully;
• It is not how I added the custom action to the install project, for I did it in other projects and it works fine.

It must be the msi not calling the database installer correctly. Can someone shed some light please?

We are on SQL SERVER 2008 R2 CU5 and we are planning to upgrade it to SQL SERVER 2008 R2 SP2.
I appreciate if you could put me in right direction how to go about.Can I do an in-place upgrade

I have 2 node windows 2008 cluster that has two sql instance running. SQL1 and SQL2 instance (SQL Server 2008 Ent).

I need to upgrade SQL1 instance to SQL Server 2008 R2 and leave the SQL2 to SQL Server 2008.  what is best to do this.

After reading document this steps I will take.

NODE1

SQL1 & SQL2 - running

NODE2

Steps:

run SQL Server 2008 R2 setup  on node2

after upgrade is completed on NODE2, failover instance SQL2 to NODE2

run SQL Server 2008 R2 setup on node1 & reboot if required

test the upgrade

Let me know if this are correct steps, if not please provide your suggestions.

Thanks in advance

Hi,

This is the first time I am encountering this issue. This is on a Windows 7 64 bit domain workstation and I am trying to install SQL Server developer edition for 2012.

I get the following error message at the end of Setup:

 Feature:                       Reporting Services - Native
  Status:                        Failed: see logs for details
  Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
  Next Step:                     Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
  Component name:                SQL Server Database Engine Services Instance Features
  Component error code:          0x851A0019
  Error description:             Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
  Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.2100.60&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025

  Feature:                       Database Engine Services
  Status:                        Failed: see logs for details
  Reason for failure:            An error occurred during the setup process of the feature.
  Next Step:                     Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
  Component name:                SQL Server Database Engine Services Instance Features
  Component error code:          0x851A0019
  Error description:             Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
  Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.2100.60&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025

  Feature:                       Data Quality Services
  Status:                        Failed: see logs for details
  Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
  Next Step:                     Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
  Component name:                SQL Server Database Engine Services Instance Features
  Component error code:          0x851A0019
  Error description:             Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
  Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.2100.60&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025

  Feature:                       Full-Text and Semantic Extractions for Search
  Status:                        Failed: see logs for details
  Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
  Next Step:                     Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
  Component name:                SQL Server Database Engine Services Instance Features
  Component error code:          0x851A0019
  Error description:             Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
  Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.2100.60&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025

  Feature:                       SQL Server Replication
  Status:                        Failed: see logs for details
  Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
  Next Step:                     Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
  Component name:                SQL Server Database Engine Services Instance Features
  Component error code:          0x851A0019
  Error description:             Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
  Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.2100.60&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025

I checked the SQL Server Log file and see this:

2012-08-03 12:42:24.40 Server      SQL Server detected 1 sockets with 4 cores per socket and 8 logical processors per socket, 8 total logical processors; using 8 logical processors based on SQL Server licensing. This is an informational message; no user action is required.
2012-08-03 12:42:24.40 Server      SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2012-08-03 12:42:24.40 Server      Detected 8150 MB of RAM. This is an informational message; no user action is required.
2012-08-03 12:42:24.40 Server      Using conventional memory in the memory manager.
2012-08-03 12:42:24.93 Server      Perfmon counters for resource governor pools and groups failed to initialize and are disabled.
2012-08-03 12:42:25.00 Server      Node configuration: node 0: CPU mask: 0x00000000000000ff:0 Active CPU mask: 0x00000000000000ff:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2012-08-03 12:42:25.02 Server      Using dynamic lock allocation.  Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node.  This is an informational message only.  No user action is required.
2012-08-03 12:42:25.05 Server      Database Mirroring Transport is disabled in the endpoint configuration.
2012-08-03 12:42:25.07 Server      Software Usage Metrics is disabled.
2012-08-03 12:42:25.12 spid5s      Warning ******************
2012-08-03 12:42:25.12 spid5s      SQL Server started in single-user mode. This an informational message only. No user action is required.
2012-08-03 12:42:25.42 spid5s      Starting up database 'master'.
2012-08-03 12:42:25.45 Server      CLR version v4.0.30319 loaded.
2012-08-03 12:42:26.40 Server      Common language runtime (CLR) functionality initialized using CLR version v4.0.30319 from C:\Windows\Microsoft.NET\Framework64\v4.0.30319\.
2012-08-03 12:42:26.63 spid5s      SQL Server Audit is starting the audits. This is an informational message. No user action is required.
2012-08-03 12:42:26.63 spid5s      SQL Server Audit has started the audits. This is an informational message. No user action is required.
2012-08-03 12:42:26.76 spid5s      SQL Trace ID 1 was started by login "sa".
2012-08-03 12:42:26.76 spid5s      Server name is 'ITS-094111D'. This is an informational message only. No user action is required.
2012-08-03 12:42:26.80 spid12s     Password policy update was successful.
2012-08-03 12:42:26.81 spid12s     Error: 17190, Severity: 16, State: 1.
2012-08-03 12:42:26.81 spid12s     Initializing the FallBack certificate failed with error code: 1, state: 20, error number: 0.
2012-08-03 12:42:26.81 spid12s     Unable to initialize SSL encryption because a valid certificate could not be found, and it is not possible to create a self-signed certificate.
2012-08-03 12:42:26.83 spid12s     Error: 17182, Severity: 16, State: 1.
2012-08-03 12:42:26.83 spid12s     TDSSNIClient initialization failed with error 0x80092004, status code 0x80. Reason: Unable to initialize SSL support. Cannot find object or property.
2012-08-03 12:42:26.83 spid12s     Error: 17182, Severity: 16, State: 1.
2012-08-03 12:42:26.83 spid12s     TDSSNIClient initialization failed with error 0x80092004, status code 0x1. Reason: Initialization failed with an infrastructure error. Check for previous errors. Cannot find object or property.
2012-08-03 12:42:26.83 spid12s     Error: 17826, Severity: 18, State: 3.
2012-08-03 12:42:26.83 spid12s     Could not start the network library because of an internal error in the network library. To determine the cause, review the errors immediately preceding this one in the error log.
2012-08-03 12:42:26.83 spid12s     Error: 17120, Severity: 16, State: 1.
2012-08-03 12:42:26.83 spid12s     SQL Server could not spawn FRunCommunicationsManager thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.

I tried the workaround given in here : http://blogs.msdn.com/b/sqljourney/archive/2012/03/16/sql-2008-r2-setup-fails-with-quot-wait-on-the-database-engine-recovery-handle-failed-quot.aspx

I tried changing the service accounts for the Database Engine Service from <NT Service\MSSQLServer>, to Built-in Accounts <Local System> and <Local Service> and also a specially built local administrative user account. None of them get past the issue.

I checked under protocols for MSSQLServer and under properties, certificates, there is nothing. I was going to figure out a way to generate a local certificate and import it into the Configuration Manager but wanted to reach out to you all first.

Madan Gopal

Prezados, boa noite!

Há um tempo atrás eu tive um problema com meu SQL Server 2008 R2, para ser mais específico eu havia desligado todos os serviços do servidor há muito tempo atrás, para não consumir minha máquina, porém quando precisei, tentei inicializar os serviços e em alguns deles não obtive sucesso.

Bom, isto é só o começo, o problema real está no seguinte: devido a este fato, eu tentei desinstalar o SQL Server 2008 R2 e reinstalá-lo, pois precisava urgente utilizá-lo, para término de minha monografia. Como a desinstalação deste servidor é impossível, pelo menos até aonde eu entendo, eu fui desinstalando item por item no Painel de Controle (bem iniciante...).

Até então, tudo bem, porém quando eu tentei instalar novamente, a instalação para quando acontece a instalação dos recursos de instalação, pede para eu aguardar e some, não fala mais nada... Já tentei várias vezes, limpei registros, exclui diretórios, fiz de tudo que eu sabia e não consegui.

Será que alguém pode me ajudar?

Grato!

Atenciosamente,

Guilherme Alves Rodrigues

I cannot install SQL Server 2008 on Windows 7 64 bit.  I get a failure during the checks for "Performance counter registry hive consistency".  I have tried various solutions on these forums to no avail.  The help points to http://support.microsoft.com/kb/300956, but that does not apply to Windows 7.

Can anyone help?

I have a Win 7 machine with a fresh Win 7 build.  I had run VS2010 for a few months, then uninstalled it when VS2012 shipped.  I now am trying to install SQL Server 2012, but it is saying that I need VS2010 SP1.  Do I really need to REinstall VS2010SP1 just to install  the Client Tools of SQL Server 2012?  

Here is where it gets to installing this (PS - how silly is it that there is not a simple Tools Only installation instead of having to ALMOST install SQL Server 2012 just to get SQL Server Management Studio.)

Hi, I installed the Evaluation Version of SQL 2008 R2 (Standard) got it set up and working just the way we wanted it. We then decided to purchase the full copy of SQL 2008 R2 (Standard) through our normal reseller channel. According to the Evaluation Version to upgrade to a 'Full' version we nneded to enter a license key however, When we got the license from our Volume License Reseller there was no License Key. We called Microsoft License Support who states that there is no key required for SQL Server 2008 R2 (Standard). My call was then redirected to Customer Service who came to the same conclusion....

They are telling me that my only option is to uninstall and reinstall. Unfortunately we have invested so much time and effort configuring this we would have to have to do it all over...

Can anyone assist me with this issue? We are running the 64-Bit Version of SQL Server 2008 R2 (Standard). We are installing it on a Windows Server 2008 Standard 64-Bit.

Here is my situation.

• Upgrade the current SQL 2000 db to new hardware. Same SQL server, Same Server Name. 
• 16 Dbs with 640 GB data in total
• The server is working with replication as publication, distribution & subscriber.

Migration Plan A:

1. Backup system table (master, msdb, distribution) in old server and restore them in new server
2. Restore userdb one by one and restore them one by one.
3. Re-create publication, distribution & subscriber that pre-script

Since the old server will take around 6 hrs to backup all DBs. I'm thinking plan B to shorten the time.

Migration Plan B:

1. Shutdown SQL agent in old server. 
2. Backup system table (master, msdb, distribution) in old server and restore them in new server
3. Shutdown SQL server in old server.
4. Copy all data & log files of userdb to new server through network.
5. Attach the userid one by one
6. Re-create publication, distribution & subscriber that pre-script

I think this plan since I have try to copy a 100GB db at around 30 mins. It may shorten the backup & restore time. 

Please feel free to share if which plan is more securer. Also, the feasibility of the plan. Thanks

Hello.. I just received my copy of 2008r2 Developer Edition, and I am unable to start the install. I haven't been able to locate any installation instructions, so I inserted the cd. After running for a very long time, just one file shows in windows explorer on the cd, "Track09.cda" That's all that's visible.

Can anyone point me in the right direction? I kind of expected this, rather frustrating..

Thanks in advance..

Kevin Rice

The following exception occurs as i starts my installation. Please help

madeeha

I have an SQL sysprepped image I use for SQL templates, and I want to them to have SP1, apart from rebuilding all the templated machines with SP1 does anyone have any ideas?

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: )

I intalled SQL Server 2008 R2 (with Management Studio) on my virtual machine that has Windows Server 2008 R2 installed . I installed SQL Server from the following website using my local Admin account.

http://www.microsoft.com/en-us/download/details.aspx?id=7593

I am getting this errror when I try to log into SQL Server,

An error has occurred while establishing a connection to the server. When connecting to SQL Server, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (.Net SqlClient Data Provider)

TCP/IP, named pipes are all enabled. Not sure what is going on. Any clues. Thanks a lot.

Mayank

I am trying to now install the Full-Text search capability to a working 2008 R2 server but it keeps failing:

Here is what the summary.txt shows.

Any ideas on how to correct this.  thanks!

Overall summary:
  Final result:                  SQL Server installation failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then rerun SQL Server Setup.
  Exit code (Decimal):           -2068052371
  Exit facility code:            1212
  Exit error code:               1645
  Exit message:                  SQL Server installation failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then rerun SQL Server Setup.
  Start time:                    2012-08-21 13:41:39
  End time:                      2012-08-21 13:44:11
  Requested action:              Install
  Log with failure:              C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120821_134056\sql_engine_core_shared_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:                  THEHUB1
  Machine processor count:       16
  OS version:                    Windows Server 2008 R2
  OS service pack:               Service Pack 1
  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 R2   MSSQLSERVER          MSSQL10_50.MSSQLSERVER         Database Engine Services                 1033                 Standard Edition     10.50.1600.1    No       
  Sql Server 2008 R2   MSSQLSERVER          MSSQL10_50.MSSQLSERVER         SQL Server Replication                   1033                 Standard Edition     10.50.1600.1    No       
  Sql Server 2008 R2                                                       Management Tools - Basic                 1033                 Standard Edition     10.50.1600.1    No       
  Sql Server 2008 R2                                                       Management Tools - Complete              1033                 Standard Edition     10.50.1600.1    No       
  Sql Server 2008 R2                                                       Client Tools Connectivity                1033                 Standard Edition     10.50.1600.1    No       
  Sql Server 2008 R2                                                       Client Tools SDK                         1033                 Standard Edition     10.50.1600.1    No       
  Sql Server 2008 R2                                                       Integration Services                     1033                 Standard Edition     10.50.1600.1    No       

Package properties:
  Description:                   SQL Server Database Services 2008 R2
  ProductName:                   SQL Server 2008 R2
  Type:                          RTM
  Version:                       10
  SPLevel:                       0
  Installation location:         \\tsclient\E\x64\setup\
  Installation edition:          STANDARD

User Input Settings:
  ACTION:                        Install
  ADDCURRENTUSERASSQLADMIN:      False
  AGTSVCACCOUNT:                 <empty>
  AGTSVCPASSWORD:                *****
  AGTSVCSTARTUPTYPE:             Manual
  ASBACKUPDIR:                   Backup
  ASCOLLATION:                   Latin1_General_CI_AS
  ASCONFIGDIR:                   Config
  ASDATADIR:                     Data
  ASDOMAINGROUP:                 <empty>
  ASLOGDIR:                      Log
  ASPROVIDERMSOLAP:              1
  ASSVCACCOUNT:                  <empty>
  ASSVCPASSWORD:                 *****
  ASSVCSTARTUPTYPE:              Automatic
  ASSYSADMINACCOUNTS:            <empty>
  ASTEMPDIR:                     Temp
  BROWSERSVCSTARTUPTYPE:         Disabled
  CONFIGURATIONFILE:             C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120821_134056\ConfigurationFile.ini
  CUSOURCE:                     
  ENABLERANU:                    False
  ENU:                           True
  ERRORREPORTING:                False
  FARMACCOUNT:                   <empty>
  FARMADMINPORT:                 0
  FARMPASSWORD:                  *****
  FEATURES:                      FULLTEXT
  FILESTREAMLEVEL:               0
  FILESTREAMSHARENAME:           <empty>
  FTSVCACCOUNT:                  NT AUTHORITY\LOCAL SERVICE
  FTSVCPASSWORD:                 *****
  HELP:                          False
  IACCEPTSQLSERVERLICENSETERMS:  False
  INDICATEPROGRESS:              False
  INSTALLSHAREDDIR:              C:\Program Files\Microsoft SQL Server\
  INSTALLSHAREDWOWDIR:           C:\Program Files (x86)\Microsoft SQL Server\
  INSTALLSQLDATADIR:             <empty>
  INSTANCEDIR:                   D:\Program Files\Microsoft SQL Server
  INSTANCEID:                    MSSQLSERVER
  INSTANCENAME:                  MSSQLSERVER
  ISSVCACCOUNT:                  NT AUTHORITY\NetworkService
  ISSVCPASSWORD:                 *****
  ISSVCSTARTUPTYPE:              Automatic
  NPENABLED:                     0
  PASSPHRASE:                    *****
  PCUSOURCE:                    
  PID:                           *****
  QUIET:                         False
  QUIETSIMPLE:                   False
  ROLE:                          <empty>
  RSINSTALLMODE:                 FilesOnlyMode
  RSSVCACCOUNT:                  <empty>
  RSSVCPASSWORD:                 *****
  RSSVCSTARTUPTYPE:              Automatic
  SAPWD:                         *****
  SECURITYMODE:                  <empty>
  SQLBACKUPDIR:                  <empty>
  SQLCOLLATION:                  SQL_Latin1_General_CP1_CI_AS
  SQLSVCACCOUNT:                 <empty>
  SQLSVCPASSWORD:                *****
  SQLSVCSTARTUPTYPE:             Automatic
  SQLSYSADMINACCOUNTS:           <empty>
  SQLTEMPDBDIR:                  <empty>
  SQLTEMPDBLOGDIR:               <empty>
  SQLUSERDBDIR:                  <empty>
  SQLUSERDBLOGDIR:               <empty>
  SQMREPORTING:                  False
  TCPENABLED:                    0
  UIMODE:                        Normal
  X86:                           False

  Configuration file:            C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120821_134056\ConfigurationFile.ini

Detailed results:
  Feature:                       Full-Text Search
  Status:                        Failed: see logs for details
  MSI status:                    Failed: see details below
  MSI error code:                0x1645
  MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120821_134056\sql_engine_core_shared_Cpu64_1.log
  MSI error description:        
  Configuration status:          Passed

Rules with failures:

Global rules:

Scenario specific rules:

Rules report file:               C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120821_134056\SystemConfigurationCheck_Report.htm