After a silent installation of the MSSQL 2008 R2, I validate the installation based on the SqlSetup.log.
In the log, the last few lines shows the following
07/18/2012 15:45:25.182 Saved .Net security policy file
07/18/2012 15:45:25.184 Attempting to release setup mutex
07/18/2012 15:45:25.187 Setup mutex has been released
07/18/2012 15:45:25.350 SQM: 3 SQM data files are queued to be uploaded
07/18/2012 15:45:25.709 SQM: Uploading file C:\Users\Administrator\AppData\Local\Microsoft\Microsoft SQL Server\100\SQLSQLSETUP00.DAT completed with status: hr = -2147012889 Http Response = 0.
07/18/2012 15:45:25.720 SQM: Uploading file C:\Users\Administrator\AppData\Local\Microsoft\Microsoft SQL Server\100\SQLSQLSETUP01.DAT completed with status: hr = -2147483376 Http Response = 0.
07/18/2012 15:45:25.723 SQM: Uploading file C:\Users\Administrator\AppData\Local\Microsoft\Microsoft SQL Server\100\SQLSQLSETUP02.DAT completed with status: hr = -2147483376 Http Response = 0.
07/18/2012 15:45:25.725 SQM: SqmWaitForUploadComplete() returns with success
07/18/2012 15:45:25.728 Setup closed with exit code: 0x84C40013
07/18/2012 15:45:25.732 ======================================================================
We noticed that there is an exit code: 0x84C40013
However, it appears that the MSSQL services can be started. To ensure that the installation was successfully, we used the methods describe in the following article to validate the MS SQL installation.
The tool produced a webpage that shows that the installation was successful for "Database Engines Services", "SQL Server Replication" and "Full-Text Search".
So my concern is, what would have caused the error code during installation and if there is any feature that wasn't installed properly?