Hi guys, I'm trying to install an SQL Server 2008 Enterprise on Windows Server 2008 R2 Standard and I've got an network error:

TITLE: Microsoft SQL Server 2008 Setup
------------------------------

The following error has occurred:

A network error occurred while attempting to read from the file: C:\Publico\en_sql_server_2008_enterprise_x86_x64_ia64_dvd_x14-89207\x64\setup\x64\SQL93C3.tmp.msi

For help, click: http://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=10.0.1600.22&EvtType=0xDF039760%25401201%25401

------------------------------
BUTTONS:

OK
------------------------------

I don't know why a network error, because I'm intalling from an local .ISO file.

Thanks,
Luciano

I had an evaluation copy of SQL Server 2012 installed which expired yesterday. Even though a had subsequently installed a valid copy SQL 2012 Enterprise I could not open the management studio.

Based on advice in other articles I completely un-installed all additions of SQL Server on the machine followed by a fresh install of SQL 2012 Enterprise (64bit).

I now get the message "An error has occurred while trying to access the license validation file. Please reinstall SQL server to correct this file."

A previous post suggested the below, what should I do for a 2012 install to correct the issue?

"Hi Kevin,

It should be a known issue. It is caused by that the setup fail to create the checksun key in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\100\Tools\ClientSetup because of sqlboot.dll issue.

To fix the issue, please follow these steps:

1. Create a text file with the following content:

   Windows Registry Editor Version 5.00
   [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\100\Tools\ClientSetup]"checksum"=hex:38,39,33,66,66,66,30,65,62,38,32,62,30,34,37,62,31,30,35,31,36,\
    38,32,31,30,30,63,63,36,36,33,30,30,31,35,36,38,61,38,33,36,31,37,63,66,62,\
    31,61,38,61,36,63,32,66,36,35,32,31,39,65,66,34,30,30,39,32,62,37,61,39,32,\
    62,32,35,33,32,33,39,63,62,36,35,33,38,65,31,66,34,61,31,33,63,61,64,32,65,\
    33,34,37,66,37,64,30,64,33,32,32,64,36,36,62,31,62,66,33,66,63,34,34,65,65,\
    35,37,38,34,63,61,65,66,33,64,31,30,31,31,38,65,30,37,63,39,66,66,31,32,61,\
    66,66,63,35,32,32,31,64,61,34,34,32,34,64,37,34,66,63,37,30,39,35,32,32,39,\
    38,62,31,63,34,34,65,66,35,00"ProductID"="00001-296-0000007-05075""DigitalProductID"=hex:a4,00,00,00,03,00,00,00,30,30,30,30,31,2d,32,39,36,2d,\
    30,30,30,30,30,30,37,2d,30,35,30,37,35,00,0a,00,00,00,38,31,30,2d,30,37,34,\
    31,36,00,00,00,00,00,00,00,00,34,49,a3,e1,b4,0c,65,79,03,e0,fe,9e,92,01,00,\
    00,00,00,00,02,19,9f,4a,c3,75,c1,0a,00,00,00,00,00,00,00,00,00,00,00,00,00,\
    00,00,00,00,00,00,00,00,00,00,00,34,36,31,30,33,00,00,00,00,00,00,00,65,05,\
    00,00,77,b1,01,90,af,0f,00,00,17,0d,00,00,00,00,00,00,00,00,00,00,00,00,00,\
    00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,a7,a1,77,36

2. Change the file extension to be .reg
3. Double-click the file to create the keys
4. Uninstall the SQL Server Management Studio(SSMS)
5. Re-install the SSMS

Now, we should be able to open the SSMS and connect to SQL Server instances.

If you have any more questions, please feel free to ask.

Thanks,
Jin Chen

Hi everyone,

  I would like to repair my actual SQL Server 2008 R2 SP2 CU1 Express with Advanced Services setup.

  BTW, the "SELECT @@VERSION" statement actually gives me this result:

Microsoft SQL Server 2008 R2 (SP2) - 10.50.4000.0 (Intel X86)   Jun 28 2012 08:42:37   Copyright (c) Microsoft Corporation  Express Edition with Advanced Services on Windows NT 6.0 <X86> (Build 6002: Service Pack 2)

  When going through the "control panel/add-remove programs",  I then got a popup window:  "Browse for SQL Server 2008 R2 installation media".  Where should I find this setup file the repair process is asking for?

  Looking at my C: drive for any setup files like "SQLEXPRADV_*.exe", I could find the following:

• C:\ProgramData\Microsoft\SQL Server 2008 Express Install\Downloads\SqlExpressWithAdv\SQLEXPRADV_x86_FRA.exe:  version is 10.0.1601.1
• C:\Users\All Users\Microsoft\SQL Server 2008 Express Install\Downloads\SqlExpressWithAdv\SQLEXPRADV_x86_FRA.exe: version is also 10.0.1601.1
• The one I recently downloaded from the web - SQLEXPRADV_x86_ENU.exe:  version is10.50.4000.0

  I also found these ones:

• C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\SQLServer2008R2\x86\setup100.exe
  version: 10.50.4000.0   date: 2012-06-29
• C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Update Cache\KB2494086\QFE\x86\setup100.exe
  version: 10.50.1790.0   date: 2011-06-14
• C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Update Cache\KB2507770\QFE\x86\setup100.exe
  version: 10.50.1777.0   date: 2011-06-10
• C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Update Cache\KB2528583\ServicePack\x86\setup100.exe
  version: 10.50.2500.0  date: 2011-07-25
• C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Update Cache\KB2544793\QFE\x86\setup100.exe
  version:  10.50.2769.0 date: 2011-07-27
• C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Update Cache\KB2630458\ServicePack\x86\setup100.exe
  version:  10.50.4000.0 date: 2013-01-10

Which one would you suggest I choose for my repair?  I would myself choose the last one (KB2630458) but I'm not sure because of the SP2CU1 level I currently am. Or maybe I'm still not looking at the right place?

Thanks in advance for helping,

Stéphane

When i am trying to shift msdb database from it's default path(C:\Program Files\Microsoft SQL Server\MSSQL10.SQLEXPRESS\MSSQL\DATA) to another drive(E:\). After shifting the database i am getting error as shown below.(the error i am getting while expanding database node in SSMS an d now i am not able to access any database.)

Failed to retrieve data for this request. (Microsoft.SqlServer.Management.Sdk.Sfc)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&LinkId=20476

------------------------------
ADDITIONAL INFORMATION:

An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)

------------------------------

Database 'msdb' cannot be opened due to inaccessible files or insufficient memory or disk space.  See the SQL Server errorlog for details. (Microsoft SQL Server, Error: 945)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=10.00.2531&EvtSrc=MSSQLServer&EvtID=945&LinkId=20476

------------------------------


The procedure i followed to shift msdb database is as follows:

1. For each file to be moved, run the following statement.

 ALTER DATABASE msdb
 MODIFY FILE ( NAME = MSDBData , FILENAME = 'E:\MSDBData.mdf' )
 ALTER DATABASE msdb
 MODIFY FILE ( NAME = MSDBLog , FILENAME = 'E:\MSDBLog.ldf' )

2. Stop the instance of SQL Server to perform maintenance.
3. Move the file or files to the new location.
4. Restart the instance of SQL Server or the server.

This error happened while i did it for testing server. I want to do it for a production server. So please help me on this error. How exactly to shift msdb database?

I am attempting to install SQL Server 2008 Enterprise Trial and receive the follow error during installation.

"The SQL Server 2005 Express Tools are installed. To continue, remove the SQL Server 2005 Express Tools."

I have used Add or Remove programs to remove all components of SQL Server 2005 Express.  I have even reinstalled the Workstation Tools of SQL Server 2005 just so I could indiviually remove those tools, and then completly removed the SQL 2005 installation.

I have used regedit to search for any instance of SQL Server 2005, there is none.

There is still an entry for SQL Server Mangement Express in my all programs listing.  However trying to launch that program fails with errors, so it is partial still installed.

Can anyone tell me how to wipe out these last bits of SQL Server 2005 Express Tools?  I have tried everything I have found searching this forum to no avail.

Bill

Hi all,

I can't install the SQL Server 2012 Express version with tools downloaded from http://www.microsoft.com/en-us/sqlserver/editions/2012-editions/express.aspx

I'm getting the following error: 

Error installing SQL Server Database Engine Services Instance Features
Could not find the Database Engine startup handle.
Error code: 0x851A0019

I'm trying to install a new stand-alone version with a default instance but always getting this error. From the features I'm installing the database engine services (not the replication), all the tools, only the basic management toolds and the SQL Client connectivity SDK.

Further in the installation I'm choosing the Windows authentication and in the list of SQL administrators I've already tried to install as current user but also as System. Both with the same error result.

The Summary File can be found here: http://d.pr/f/didH

Note: Visual studio is not installed.

Thanks in advance

I have similar problem with "http://social.msdn.microsoft.com/Forums/en-US/sqlsetupandupgrade/thread/6491c614-56ee-4c31-ba12-8a766ef806d5/".

Since 1 week ago, I have tried  to uninstall and reinstall sqlserver 2008 r2 again in windows 7 professional x64.
I have check windows power shell
from this link "http://blogs.technet.com/b/josebda/archive/2009/11/25/download-for-powershell-v2-for-windows-7-no-need-it-s-already-there.aspx"..it is no problem.
I have check framework from HKLM\SOFTWARE\Microsoft\NET Framework Setup\NDP\v3.5\..I got the folder. it mean my laptop have framework .net 3.5 sp1

I have check windows installer from "http://stackoverflow.com/questions/1144888/how-can-i-detect-if-windows-installer-is-installed"
I got Windows ® Installer. V 5.0.7601.17514.

and I have use Run As Administrator to start the setup, and reformat this OS again but  I still get the similar error "sqlenginedbstartconfigaction_install_configrc_Cpu64" during installation process.


I have no idea to solve this problem, anyone can help ?
thanks ..

-----summary----

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):           -391544739
  Exit facility code:            169
  Exit error code:               32861
  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:                    2013-03-31 14:30:32
  End time:                      2013-03-31 15:40:01
  Requested action:              Install
  Log with failure:              c:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20130331_142758\Detail.txt
  Exception help link:           http%3a%2f%2fgo.microsoft.com%2ffwlink%3fLinkId%3d20476%26ProdName%3dMicrosoft%2bSQL%2bServer%26EvtSrc%3dsetup.rll%26EvtID%3d50000%26ProdVer%3d10.50.1600.1%26EvtType%3d0x987D2693%400xE8A9805D

Machine Properties:
  Machine name:                  PL-PC
  Machine processor count:       2
  OS version:                    Windows 7
  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

Package properties:
  Description:                   SQL Server Database Services 2008 R2
  ProductName:                   SQL Server 2008 R2
  Type:                          RTM
  Version:                       10
  SPLevel:                       0
  Installation location:         C:\Users\pl\Documents\MSSQL2008R2\MSSQL2008R2\x64\setup\
  Installation edition:          DEVELOPER

User Input Settings:
  ACTION:                        Install
  ADDCURRENTUSERASSQLADMIN:      False
  AGTSVCACCOUNT:                 NT AUTHORITY\NETWORK SERVICE
  AGTSVCPASSWORD:                *****
  AGTSVCSTARTUPTYPE:             Manual
  ASBACKUPDIR:                   c:\Program Files\Microsoft SQL Server\MSAS10_50.MSSQLSERVER\OLAP\Backup
  ASCOLLATION:                   Latin1_General_CI_AS
  ASCONFIGDIR:                   c:\Program Files\Microsoft SQL Server\MSAS10_50.MSSQLSERVER\OLAP\Config
  ASDATADIR:                     c:\Program Files\Microsoft SQL Server\MSAS10_50.MSSQLSERVER\OLAP\Data
  ASDOMAINGROUP:                 <empty>
  ASLOGDIR:                      c:\Program Files\Microsoft SQL Server\MSAS10_50.MSSQLSERVER\OLAP\Log
  ASPROVIDERMSOLAP:              1
  ASSVCACCOUNT:                  NT AUTHORITY\NETWORK SERVICE
  ASSVCPASSWORD:                 *****
  ASSVCSTARTUPTYPE:              Automatic
  ASSYSADMINACCOUNTS:            BUILTIN\Administrators
  ASTEMPDIR:                     c:\Program Files\Microsoft SQL Server\MSAS10_50.MSSQLSERVER\OLAP\Temp
  BROWSERSVCSTARTUPTYPE:         Disabled
  CONFIGURATIONFILE:             c:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20130331_142758\ConfigurationFile.ini
  CUSOURCE:                      
  ENABLERANU:                    False
  ENU:                           True
  ERRORREPORTING:                True
  FARMACCOUNT:                   <empty>
  FARMADMINPORT:                 0
  FARMPASSWORD:                  *****
  FEATURES:                      SQLENGINE,REPLICATION,FULLTEXT,AS,RS,BIDS,CONN,IS,BC,SDK,BOL,SSMS,ADV_SSMS,OCS
  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:                   c:\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:                 DefaultNativeMode
  RSSVCACCOUNT:                  NT AUTHORITY\NETWORK SERVICE
  RSSVCPASSWORD:                 *****
  RSSVCSTARTUPTYPE:              Automatic
  SAPWD:                         *****
  SECURITYMODE:                  SQL
  SQLBACKUPDIR:                  <empty>
  SQLCOLLATION:                  SQL_Latin1_General_CP1_CI_AS
  SQLSVCACCOUNT:                 NT AUTHORITY\NETWORK SERVICE
  SQLSVCPASSWORD:                *****
  SQLSVCSTARTUPTYPE:             Automatic
  SQLSYSADMINACCOUNTS:           pl-PC\pl
  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\20130331_142758\ConfigurationFile.ini

Detailed results:
  Feature:                       Database Engine Services
  Status:                        Failed: see logs for details
  MSI status:                    Passed
  Configuration status:          Failed: see details below
  Configuration error code:      0xE8A9805D
  Configuration error description: External component has thrown an exception.
  Configuration log:             c:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20130331_142758\Detail.txt

  Feature:                       SQL Server Replication
  Status:                        Failed: see logs for details
  MSI status:                    Passed
  Configuration status:          Failed: see details below
  Configuration error code:      0xE8A9805D
  Configuration error description: External component has thrown an exception.
  Configuration log:             c:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20130331_142758\Detail.txt

  Feature:                       Full-Text Search
  Status:                        Failed: see logs for details
  MSI status:                    Passed
  Configuration status:          Failed: see details below
  Configuration error code:      0xE8A9805D
  Configuration error description: External component has thrown an exception.
  Configuration log:             c:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20130331_142758\Detail.txt

  Feature:                       Analysis Services
  Status:                        Passed
  MSI status:                    Passed
  Configuration status:          Passed

  Feature:                       Reporting Services
  Status:                        Failed: see logs for details
  MSI status:                    Passed
  Configuration status:          Failed: see details below
  Configuration error code:      0xE8A9805D
  Configuration error description: External component has thrown an exception.
  Configuration log:             c:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20130331_142758\Detail.txt

  Feature:                       Integration Services
  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

  Feature:                       Microsoft Sync Framework
  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\20130331_142758\SystemConfigurationCheck_Report.htm

This is probably a simple question for the SQL Server veterans, but am a bit confused about directories.  I have searched all over, and there is very little information about optimizing this, unless you have an unlimited number of drives (I don't).  I read that it is best to split the log files and data files between two drives.

1)  Since I only have two 15K drives, where should Temp DB go for best performance, on the drive with the log files or data files?  I'm thinking probably the data drive.  I do have a third drive, but it only a 7200 rpm drive, versus 15K for the other two, so probably too slow.

2)  Should the Temp DB Log file go on the Log file drive?

3)  While I am splitting data and log files, is there a preference for drives for the System Database directory?  This is just used for access control, and is not very big, right?

4)  Any suggestions for directory naming conventions when splitting drives?  E:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQL_SERVER\MSSQL\Data seems a bit clumsy and long.

Thanks.

Michael

hi All,

Lat week we have upgraded sql server 2008 with sp3.but now user asking us to roll back to sp1.

Please let me know the step by step process for rollback to sp1.

Regards,

Maheshwar Reddy

while installing sql server 2008 r2 i'm getting Not applicable errors, 

The system is  I7 64bit, windows 7 pro.

Microsoft SQL Server 2008 R2 Setup - System Configuration Check Report

Computer Name(s): YONI 
Report Date/Time: 08/04/2013 13:17
Saved to Directory: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20130408_131615\SystemConfigurationCheck_Report.htm

Rule Name		Rule Description	Result	Message/Corrective Action
GlobalRules: SQL Server 2008 R2 Setup configuration checks for rules group 'GlobalRules'
	AclPermissionsFacet	Checks if the SQL Server registry keys are consistent.	Passed	SQL Server registry keys are consistent and can support SQL Server installation or upgrade.
	HasSecurityAndBackupPrivilegesCheck	Checks whether the account that is running SQL Server Setup has the right to back up files and directories, and the right to manage auditing and the security log.	Passed	The account that is running SQL Server Setup has the right to back up files and directories, and the right to manage auditing and security log.
	MediaPathLength	Checks whether the SQL Server installation media is too long.	Passed	The SQL Server installation media is not too long.
	OsVersionCheck	Checks whether the computer meets minimum operating system version requirements.	Passed	The operating system version meets the minimum requirements for this product.
	RebootRequiredCheck	Checks if a pending computer restart is required. A pending restart can cause Setup to fail.	Passed	The computer does not require a restart.
	SetupCompatibilityCheck	Checks whether the current version of SQL Server is compatible with a later installed version.	Passed	Setup has not detected any incompatibilities.
	ThreadHasAdminPrivilegeCheck	Checks whether the account running SQL Server Setup has administrator rights on the computer.	Passed	The account running SQL Server Setup has administator rights on the computer.
	WmiServiceStateCheck	Checks whether the WMI service is started and running on the computer.	Passed	The Windows Management Instrumentation (WMI) service is running.
InstallGlobalRules: SQL Server 2008 R2 Setup configuration checks for rules group 'InstallGlobalRules'
	AclPermissionsFacet	Checks if the SQL Server registry keys are consistent.	Passed	SQL Server registry keys are consistent and can support SQL Server installation or upgrade.
	Bids2008InstalledCheck	Checks if any of SQL Server 2008 Business Intelligence Development Studio installation exists.	Passed	SQL Server 2008 Business Intelligence Development Studio is not installed.
	BlockInstallSxS	Checks whether there is an existing SQL Server 2008 CTP installation.	Passed	There are no previous CTP installations of SQL Server 2008.
	FacetDomainControllerCheck	Checks whether the computer is a domain controller. Installing SQL Server 2008 R2 on a domain controller is not recommended.	Passed	This computer is not a domain controller.
	FacetPowerShellCheck	Checks whether Windows PowerShell is installed. Windows PowerShell is a pre-requisite of SQL Server 2008 R2 Express with Advanced Services.	Passed	Windows PowerShell is installed or not required.
	FacetWOW64PlatformCheck	Determines whether SQL Server Setup is supported on this operating system platform.	Passed	SQL Server Setup is supported on this operating system platform.
	FusionRebootCheck	Checks if a computer restart is required because of broken fusion ATL. A pending restart can cause SQL Server Setup to fail.	Passed	The computer does not require a restart.
	PerfMonCounterNotCorruptedCheck	Checks if existing performance counter registry hive is consistent.	Passed	The performance counter registry hive is consistent.
	SqlUnsupportedProductBlocker	Checks whether SQL Server 7.0 or SQL Server 7.0 OLAP Services is installed. SQL Server 2008 R2 is not supported with SQL Server 7.0.	Passed	SQL Server 7.0 or SQL Server 7.0 OLAP Services is not installed.
	SSMS_IsInternetConnected	Verifies that the computer is connected to the Internet. When a Microsoft .NET application like Microsoft Management Studio starts, there maybe be a slight delay while the .NET security check validates a certificate.	Passed	The computer is connected to the Internet and .NET security checks can be completed.
	IsFirewallEnabled	Checks whether the Windows Firewall is enabled.	Warning	The Windows Firewall is enabled. Make sure the appropriate ports are open to enable remote access. See the rules documentation at http://go.microsoft.com/fwlink/?LinkId=94001 for information about ports to open for each feature.
InstallFeatureSpecificRules: SQL Server 2008 R2 Setup configuration checks for rules group 'InstallFeatureSpecificRules'
	ASSPI64bitsMachineCheck	Checks whether the computer processor meets the 64-bit requirement for installing SQL Server PowerPivot for SharePoint.	Not applicable	This rule does not apply to your system configuration.
	ASSPIExistingFarmMustBeAvailableCheck	Checks to see that SharePoint Server 2010 farm is presently available.	Not applicable	This rule does not apply to your system configuration.
	ASSPIExistingFarmRequiresMoss14FarmCheck	Checks for membership in a SharePoint Server 2010 farm.	Not applicable	This rule does not apply to your system configuration.
	ASSPIExistingFarmRequiresUpgradeCheck	Checks existing farm for SharePoint Server 2010.	Not applicable	This rule does not apply to your system configuration.
	ASSPIIISVersionCheck	Checks for Internet Information Services 7.0 or later. IIS 7.0 or later is required for installing SQL Server PowerPivot for SharePoint.	Not applicable	This rule does not apply to your system configuration.
	ASSPIInstanceNameNotInUseCheck	Checks for the required instance name.	Not applicable	This rule does not apply to your system configuration.
	ASSPINewFarmNeedsUpgradeToO14MossEnterpriseCheck	Checks for an un-configured SharePoint Server 2010.	Not applicable	This rule does not apply to your system configuration.
	ASSPINewFarmRequiresMoss14BitsCheck	Checks whether SharePoint Server 2010 is installed.	Not applicable	This rule does not apply to your system configuration.
	ASSPINewFarmRequiresMossBitsCheck	Checks whether the SharePoint server can be configured.	Not applicable	This rule does not apply to your system configuration.
	ASSPINewFarmRequiresNewAdminSiteCheck	Checks whether the SharePoint Central Administration site name is available.	Not applicable	This rule does not apply to your system configuration.
	ASSPINewO14EnterpriseFarmUnconfiguredCheck	Checks whether Setup will be able to configure the local SharePoint server.	Not applicable	This rule does not apply to your system configuration.
	ASSPINo32BitsOrWowCheck	Checks whether Setup is running in a 64-bit process on a computer that is running a 64-bit operating system. This is required for installing SQL Server PowerPivot for SharePoint.	Not applicable	This rule does not apply to your system configuration.
	ASSPINoExistingIMBICheck	Checks for an existing instance of SQL Server PowerPivot for SharePoint. You can have only one instance of PowerPivot for SharePoint on a computer.	Not applicable	This rule does not apply to your system configuration.
	ASSPIOperationSystemCheck	Checks for the Windows Server 2008 or later operating system. This operating system is required for installing SQL Server PowerPivot for SharePoint.	Not applicable	This rule does not apply to your system configuration.
	ASSPIProvisionResultValidCheck	Checks whether all of the SQL Server PowerPivot for SharePoint instances in the farm are the same version.	Not applicable	This rule does not apply to your system configuration.
	ASSPIRequiresCompleteFarmCheck	Checks whether SharePoint Server 2010 was installed with the "Farm", "Complete" option.	Not applicable	This rule does not apply to your system configuration.
	ASSPISharePointPlatformSupportedCheck	Checks whether SharePoint supports current .Net Framework version.	Not applicable	This rule does not apply to your system configuration.
	ASSPIUserIsFarmAdminCheck	Checks whether the user running Setup is also a SharePoint farm administrator.	Not applicable	This rule does not apply to your system configuration.
	EditionRequirementCheck	Checks whether the SQL Server edition is supported on this operating system.	Passed	This SQL Server edition is supported on this operating system.
	RS_W2K3IA64InstallCheck	Checks whether the operating system is Window 2003 and the architecture is IA64.	Passed	The operating system is not Windows 2003 IA64.
	SharedComponentsUpgradeRule	Checks whether SQL Server 2008 shared components (such as IS, BIDS, Tools, SSMS, or BOL) are present on the machine, because installing SQL Server 2008 R2 shared components will automatically upgrade the existing shared components.	Passed	There are no shared components of SQL Server 2008 already on the machine.
	SlipstreamMediaInfoCheck	Checks whether the language of the original media is the same as the language of the service pack for updating the setup media.	Passed	The language of the original SQL Server 2008 R2 media and the service pack match.
	Sql2005SsmsExpressFacet	Checks whether SQL Server 2005 Express Tools are installed.	Passed	The SQL Server 2005 Express Tools are not installed.
	VSShellInstalledRule	Checks for previous releases of Microsoft Visual Studio 2008	Passed	Previous releases of Microsoft Visual Studio 2008 is not installed or already upgraded to SP1.

Rules Documentation: http://go.microsoft.com/fwlink/?LinkId=157129 
Community: http://go.microsoft.com/fwlink/?LinkId=157128 
Setup Help File: http://go.microsoft.com/fwlink/?LinkId=157127

I have moved the model database by using following method

1. For each file to be moved, run the following statement.

ALTER DATABASE model
 MODIFY FILE ( NAME = modeldev , FILENAME = 'G:\model\model.mdf' )
ALTER DATABASE model
 MODIFY FILE ( NAME = modellog , FILENAME = 'G:\model\modellog.ldf' )

2. Stop the instance of SQL Server to perform maintenance.
3. Move the file or files to the new location.
4. Restart the instance of SQL Server or the server.

While restarting instance of server i am getting following error.

How to solve this error?

I currently have sql 2008 R2 RTM running on Windows Server 2008r2 sp1.  I attempting to install sql 2008r2 sp2.  However, it failed.  I looked at error log.  This is the error that jumped out at me--The INSTALLSHAREDWOWDIR command line value is not valid. Please ensure the specified path is valid and different than the INSTALLSHAREDDIR path.

I have seen some other post about this error, but it seems to be related to installing SQL from the setup and installing a service pack. 

Has anyone run into this installing SP2?  Do you know how I can resolve it?  

Below is the summary log:

Overall summary:
  Final result:                  The patch installer has failed to update the following instance: MSSQLSERVER. To determine the reason for failure, review the log files.
  Exit code (Decimal):           -2068578304
  Exit facility code:            1204
  Exit error code:               0
  Exit message:                  The patch installer has failed to update the following instance: MSSQLSERVER. To determine the reason for failure, review the log files.
  Start time:                    2013-04-07 19:37:52
  End time:                      2013-04-07 19:41:11
  Requested action:              Patch

Instance MSSQLSERVER overall summary:
  Final result:                  The patch installer has failed to update the shared features. To determine the reason for failure, review the log files.
  Exit code (Decimal):           -2068578304
  Exit facility code:            1204
  Exit error code:               0
  Exit message:                  The INSTALLSHAREDWOWDIR command line value is not valid. Please ensure the specified path is valid and different than the INSTALLSHAREDDIR path.
  Start time:                    2013-04-07 19:40:43
  End time:                      2013-04-07 19:41:09
  Requested action:              Patch

Machine Properties:
  Machine name:                  SYSDB
  Machine processor count:       2
  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   MSSQLSERVER          MSSQL10_50.MSSQLSERVER         Full-Text Search                         1033                 Standard Edition     10.50.1600.1    No       
  Sql Server 2008 R2   MSSQLSERVER          MSAS10_50.MSSQLSERVER          Analysis Services                        1033                 Standard Edition     10.50.1600.1    No       
  Sql Server 2008 R2   MSSQLSERVER          MSRS10_50.MSSQLSERVER          Reporting Services                       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 Backwards Compatibility     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:                   SQL2008
  Type:                          RTM
  Version:                       10
  SPLevel:                       2
  KBArticle:                     KB2630458
  KBArticleHyperlink:           http://support.microsoft.com/?kbid=2630458
  PatchType:                     SP
  AssociatedHotfixBuild:         0
  Platform:                      x64
  PatchLevel:                    10.52.4000.0
  ProductVersion:                10.50.1600.1
  GDRReservedRange:              10.0.1000.0:10.0.1099.0;10.0.3000.0:10.0.3099.0
  PackageName:                   SQLServer2008R2-KB2630458-x64.exe
  Installation location:         e:\8b0813e6770181867286c924\x64\setup\

Updated product edition:
  Instance             Edition            
  MSSQLSERVER          STANDARD           

User Input Settings:
  ACTION:                        Patch
  ALLINSTANCES:                  False
  CLUSTERPASSIVE:                False
  CONFIGURATIONFILE:            
  ENU:                           True
  FARMACCOUNT:                   <empty>
  FARMADMINPORT:                 0
  FARMPASSWORD:                  *****
  HELP:                          False
  INDICATEPROGRESS:              False
  INSTANCEID:                    <empty>
  INSTANCENAME:                  <empty>
  PASSPHRASE:                    *****
  QUIET:                         False
  QUIETSIMPLE:                   False
  UIMODE:                        Normal
  X86:                           False

Rules with failures:

Global rules:

There are no scenario-specific rules.

RODD

newbie:

We need to move a user db from an old server (Win2003 Standard 32bit) to a new one  (Win2008R2 64bit) and I'm asking for suggestions, tips, hints on how to do this with the least amount of problems.

The old server has the entire volume set up as drive C. And it's running SQL Server 2008 Standard unpatched.

The new server has multiple volumes setup, C for the o/s, D for the apps, E for the data, F for the log files, G for the backups.  We've installed SQL Server 2008 Standard, and patched it with SP3 and cumulative update 10.  Pointed the destination folders to the respective drives - App and shared apps on drive D, Data dirs to drive E, log files to drive F, backup to drive G.

So what's the best way to go about doing this with the least amount of problems?  Backup and Restore, Copy, or Copy Wizard, Move, SSIS Import and Export Wizard etc.

I've read these doc's, and they describe different methods for different scenarios which makes me wonder which way is best for what we need to do.

kb189624 Copying Databases to Other Servers. kb190436 Copying Databases with Backup and Restore, kb190923 Copying Data Between Servers, kb 274188 Troubleshooting Orphaned Users".

I'm trying to Install SQL Server 2012.  I have reached Installation Configuration rules and recieved two failures:

"Reporting Services Catalog Database Existence" Failed (A Reporting Services Catalog database exists.  Select a Reporting Services files-only mode installation)

"Reporting Services Catalog Temporary Database File Exists" Failed (The Reporting Services catalog database file exists.  Select a Reporting Services files-only mode installation)

These correspond to:

I'm unsure of what the error reports mean.  Do I run through the installation process again and search out these options?

I'm trying to install a SQL test version.  When doing so I encounter the following error:

TITLE: SQL Server Setup failure.
------------------------------

SQL Server Setup has encountered the following error:

Data error (cyclic redundancy check).

A link is inclued from MS which indicates that they have no information.  Does anyone have any ideas?

Thank you...

Hi,

I need to organise to patch an SQL 2008 R2 environment up to SP2 level. It is a 4 node active/active/active/active configuration, with 4 named instances. One of the named instances is a distributor, the rest are both publishers and subscriber

I understand that the 'method' of patching replicated servers is distributor -> publisher -> subscriber - however my main question in this scenario is around timeframes and affects on replication.

If I was to patch the distributor first, how long could I leave the distributor at a different version from the publisher and subscriber? I'm assuming for patching the distributor like a normal cluster patch installation I will need to patch and failover to each node in order to ensure they are all patched which I can do - can the distributor be 'left' for potentially a few days to a week on a different SP than the publishers/subscribers?

More than 1 of the named instances are a publisher and a subscriber as well, so would I need to patch all the publishers first, then the subscribers - or should I patch the whole lot (publishers and subscribers) at once?  What is the risk of the publishers/subscribers being on different SP levels - is it only changes to the publication that could affect the replicated environment?

I'm pretty much after a solution with least downtime, and potentially a solution where the 'downtime' can be 'staged', as well as potentially the work so I am not patching for 24 hours straight!

Thanks!
Melissa

Hi,

I got a 2-node sql server 2008 R2 failover cluster (64 bit) to patch SP2. One of the node failed with error during sp2 installation as below. Please check and help.

Overall summary:
  Final result:                  The patch installer has failed to update the following instance: MSSQLSERVER. To determine the reason for failure, review the log files.
  Exit code (Decimal):           -2068709375
  Exit facility code:            1202
  Exit error code:               1
  Exit message:                  Cannot execute a program. The command being executed was "C:\Windows\Microsoft.NET\Framework64\v2.0.50727\csc.exe" /noconfig /fullpaths @"C:\Users\cwsmain\AppData\Local\Temp\ebms87n0.cmdline".
  Start time:                    2013-03-07 20:09:53
  End time:                      2013-03-07 20:19:46
  Requested action:              Patch

Instance MSSQLSERVER overall summary:
  Final result:                  The patch installer has failed to update the shared features. To determine the reason for failure, review the log files.
  Exit code (Decimal):           -2068709375
  Exit facility code:            1202
  Exit error code:               1
  Exit message:                  The directory 'f:\275f14ca3bc4000435db3d388419a854\' doesn't exist.
  Start time:                    2013-03-07 20:16:40
  End time:                      2013-03-07 20:18:48
  Requested action:              Patch

Detail:

2013-03-07 20:16:00 Slp: Sco: Attempting to get service start mode for service ReportServer
2013-03-07 20:16:00 Slp: Invoking QueryServiceConfig Win32 API for buffer size
2013-03-07 20:16:00 Slp: Invoking QueryServiceConfig Win32 API with AllocHGlobal buffer
2013-03-07 20:16:00 Slp: Sco: Returning service start mode Automatic
2013-03-07 20:16:00 Slp: Sco: Returning service status Running
2013-03-07 20:16:00 Slp: The following NT service was in a running state prior to patch action: ReportServer
2013-03-07 20:16:00 Slp: Attempting to run patch request for instance: MSSQLSERVER
2013-03-07 20:18:48 Slp: Error: Failed to run patch request for instance: MSSQLSERVER (exit code: -2068709375)
2013-03-07 20:18:48 Slp: Sco: Attempting to get service start mode for service SQLBrowser
2013-03-07 20:18:48 Slp: Invoking QueryServiceConfig Win32 API for buffer size
2013-03-07 20:18:48 Slp: Invoking QueryServiceConfig Win32 API with AllocHGlobal buffer
2013-03-07 20:18:48 Slp: Sco: Returning service start mode Automatic
2013-03-07 20:18:48 Slp: Sco: Attempting to get service start mode for service SQLBrowser
2013-03-07 20:18:48 Slp: Invoking QueryServiceConfig Win32 API for buffer size
2013-03-07 20:18:48 Slp: Invoking QueryServiceConfig Win32 API with AllocHGlobal buffer
2013-03-07 20:18:48 Slp: Sco: Returning service start mode Automatic
2013-03-07 20:18:48 Slp: Restoring the following NT service to a running state after patch action: SQLBrowser
2013-03-07 20:18:48 Slp: Sco: Attempting to start service SQLBrowser
2013-03-07 20:18:48 Slp: Sco: Attempting to start service SQLBrowser, start parameters
2013-03-07 20:18:48 Slp: Sco: Attempting to start service SQLBrowser
2013-03-07 20:18:48 Slp: Sco: Service SQLBrowser started
2013-03-07 20:18:48 Slp: Sco: Attempting to get service start mode for service SQLWriter
2013-03-07 20:18:48 Slp: Invoking QueryServiceConfig Win32 API for buffer size
2013-03-07 20:18:48 Slp: Invoking QueryServiceConfig Win32 API with AllocHGlobal buffer
2013-03-07 20:18:48 Slp: Sco: Returning service start mode Automatic
2013-03-07 20:18:48 Slp: Sco: Attempting to get service start mode for service SQLWriter
2013-03-07 20:18:48 Slp: Invoking QueryServiceConfig Win32 API for buffer size
2013-03-07 20:18:48 Slp: Invoking QueryServiceConfig Win32 API with AllocHGlobal buffer
2013-03-07 20:18:48 Slp: Sco: Returning service start mode Automatic
2013-03-07 20:18:48 Slp: Restoring the following NT service to a running state after patch action: SQLWriter
2013-03-07 20:18:48 Slp: Sco: Attempting to start service SQLWriter
2013-03-07 20:18:48 Slp: Sco: Attempting to start service SQLWriter, start parameters
2013-03-07 20:18:48 Slp: Sco: Attempting to start service SQLWriter
2013-03-07 20:18:49 Slp: Sco: Service SQLWriter started
2013-03-07 20:18:49 Slp: Sco: Attempting to get service start mode for service ReportServer
2013-03-07 20:18:49 Slp: Invoking QueryServiceConfig Win32 API for buffer size
2013-03-07 20:18:49 Slp: Invoking QueryServiceConfig Win32 API with AllocHGlobal buffer
2013-03-07 20:18:49 Slp: Sco: Returning service start mode Automatic
2013-03-07 20:18:49 Slp: Sco: Attempting to get service start mode for service ReportServer
2013-03-07 20:18:49 Slp: Invoking QueryServiceConfig Win32 API for buffer size
2013-03-07 20:18:49 Slp: Invoking QueryServiceConfig Win32 API with AllocHGlobal buffer
2013-03-07 20:18:49 Slp: Sco: Returning service start mode Automatic
2013-03-07 20:18:49 Slp: Restoring the following NT service to a running state after patch action: ReportServer
2013-03-07 20:18:49 Slp: Sco: Attempting to start service ReportServer
2013-03-07 20:18:49 Slp: Sco: Attempting to start service ReportServer, start parameters
2013-03-07 20:18:49 Slp: Sco: Attempting to start service ReportServer
2013-03-07 20:18:59 Slp: Sco: Service ReportServer started
2013-03-07 20:18:59 Slp: Completed Action: RunPatchAllInstanceAction, returned True
2013-03-07 20:18:59 Slp: ----------------------------------------------------------------------
2013-03-07 20:18:59 Slp: Skipping Action: ValidatePatchInstanceName due to user cancel request
2013-03-07 20:18:59 Slp: ----------------------------------------------------------------------
2013-03-07 20:18:59 Slp: Skipping Action: ExecutePatchCalculateWorkflow due to user cancel request
2013-03-07 20:18:59 Slp: ----------------------------------------------------------------------
2013-03-07 20:18:59 Slp: Skipping Action: FinalCalculateSettings due to user cancel request
2013-03-07 20:18:59 Slp: ----------------------------------------------------------------------
2013-03-07 20:18:59 Slp: Skipping Action: ValidateFeatureSettings due to user cancel request
2013-03-07 20:18:59 Slp: ----------------------------------------------------------------------
2013-03-07 20:18:59 Slp: Skipping Action: AddPackageInstallerEnginesAction due to user cancel request
2013-03-07 20:18:59 Slp: ----------------------------------------------------------------------
2013-03-07 20:18:59 Slp: Skipping Action: SchedulePackageInstallActionsAction due to user cancel request
2013-03-07 20:18:59 Slp: ----------------------------------------------------------------------
2013-03-07 20:18:59 Slp: Skipping Action: ScheduleUpgradePackageInstallActionsAction due to user cancel request
2013-03-07 20:18:59 Slp: ----------------------------------------------------------------------
2013-03-07 20:18:59 Slp: Skipping Action: NotifyProgressCountDisplay due to user cancel request
2013-03-07 20:18:59 Slp: ----------------------------------------------------------------------
2013-03-07 20:18:59 Slp: Skipping Action: ScheduleConfigAction due to user cancel request
2013-03-07 20:18:59 Slp: ----------------------------------------------------------------------
2013-03-07 20:18:59 Slp: Skipping Action: ValidationTimingConfigAction due to user cancel request
2013-03-07 20:18:59 Slp: ----------------------------------------------------------------------
2013-03-07 20:18:59 Slp: Skipping Action: PreMsiTimingConfigAction due to user cancel request
2013-03-07 20:18:59 Slp: ----------------------------------------------------------------------
2013-03-07 20:18:59 Slp: Skipping Action: StopPatchedServices due to user cancel request
2013-03-07 20:18:59 Slp: ----------------------------------------------------------------------
2013-03-07 20:18:59 Slp: Skipping Action: CachePatchPage due to user cancel request
2013-03-07 20:18:59 Slp: ----------------------------------------------------------------------
2013-03-07 20:18:59 Slp: Skipping Action: InitializeMsiAction due to user cancel request
2013-03-07 20:18:59 Slp: ----------------------------------------------------------------------
2013-03-07 20:18:59 Slp: Skipping Action: MsiTimingAction due to user cancel request
2013-03-07 20:18:59 Slp: ----------------------------------------------------------------------
2013-03-07 20:18:59 Slp: Skipping Action: FinalizeMsiAction due to user cancel request
2013-03-07 20:18:59 Slp: ----------------------------------------------------------------------
2013-03-07 20:18:59 Slp: Skipping Action: PostMsiTimingConfigAction due to user cancel request
2013-03-07 20:18:59 Slp: ----------------------------------------------------------------------
2013-03-07 20:18:59 Slp: Skipping Action: DowntimeTimingConfigAction due to user cancel request
2013-03-07 20:18:59 Slp: ----------------------------------------------------------------------
2013-03-07 20:18:59 Slp: Skipping Action: StartPatchedServices due to user cancel request
2013-03-07 20:18:59 Slp: ----------------------------------------------------------------------
2013-03-07 20:18:59 Slp: Skipping Action: StartupTimingConfigAction due to user cancel request
2013-03-07 20:18:59 Slp: ----------------------------------------------------------------------
2013-03-07 20:18:59 Slp: Skipping Action: PreUninstallTimingConfigAction due to user cancel request
2013-03-07 20:18:59 Slp: ----------------------------------------------------------------------
2013-03-07 20:18:59 Slp: Skipping Action: UninstallTimingConfigAction due to user cancel request
2013-03-07 20:18:59 Slp: ----------------------------------------------------------------------
2013-03-07 20:18:59 Slp: Skipping Action: UpgradeMsiTimingAction due to user cancel request
2013-03-07 20:18:59 Slp: ----------------------------------------------------------------------
2013-03-07 20:18:59 Slp: Skipping Action: FinalizeTimingConfigAction due to user cancel request
2013-03-07 20:18:59 Slp: ----------------------------------------------------------------------
2013-03-07 20:18:59 Slp: Skipping Action: CreateARPRegKeyAction due to user cancel request
2013-03-07 20:18:59 Slp: ----------------------------------------------------------------------
2013-03-07 20:18:59 Slp: Skipping Action: NotifyProgressComplete due to user cancel request
2013-03-07 20:18:59 Slp: ----------------------------------------------------------------------
2013-03-07 20:18:59 Slp: Running Action: FinalizeProgressStatus
2013-03-07 20:18:59 Slp: Completed Action: FinalizeProgressStatus, returned True
2013-03-07 20:18:59 Slp: ----------------------------------------------------------------------
2013-03-07 20:18:59 Slp: Running Action: CloseUI
2013-03-07 20:18:59 Slp: Stop action skipped in UI Mode Full
2013-03-07 20:18:59 Slp: Completed Action: CloseUI, returned True
2013-03-07 20:19:00 Slp: Received request to add the following file to Watson reporting: C:\Users\cwsmain\AppData\Local\Temp\tmp29B5.tmp
2013-03-07 20:19:00 Slp: The following is an exception stack listing the exceptions in outermost to innermost order
2013-03-07 20:19:00 Slp: Inner exceptions are being indented
2013-03-07 20:19:00 Slp:
2013-03-07 20:19:00 Slp: Exception type: Microsoft.SqlServer.Chainer.Infrastructure.ChainerInfrastructureException
2013-03-07 20:19:00 Slp:     Message:
2013-03-07 20:19:00 Slp:         Cannot execute a program. The command being executed was "C:\Windows\Microsoft.NET\Framework64\v2.0.50727\csc.exe" /noconfig /fullpaths @"C:\Users\cwsmain\AppData\Local\Temp\ebms87n0.cmdline".
2013-03-07 20:19:00 Slp:     Stack:
2013-03-07 20:19:00 Slp:         at Microsoft.SqlServer.Chainer.Infrastructure.DataStoreService.DeserializeObject(String rootPath, Type type, String elementXPath)
2013-03-07 20:19:00 Slp:         at Microsoft.SqlServer.Chainer.Infrastructure.DataStoreService.DeserializeObject(String rootPath, Type type)
2013-03-07 20:19:00 Slp:         at Microsoft.SqlServer.Chainer.Infrastructure.InputSettingService.GetInputSettingValue(String settingName)
2013-03-07 20:19:00 Slp:         at Microsoft.SqlServer.Chainer.Infrastructure.StatusLogs.WriteInputSettings(LogProviderSummaryFile summaryLog)
2013-03-07 20:19:00 Slp:         at Microsoft.SqlServer.Chainer.Infrastructure.StatusLogs.WritePatchSummaryLog(Int32 resultCode, Exception exception)
2013-03-07 20:19:00 Slp:         at Microsoft.SqlServer.Chainer.Infrastructure.StatusLogs.WriteSummaryLog(Int32 resultCode, Boolean finalResult, Exception exception)
2013-03-07 20:19:00 Slp:         at Microsoft.SqlServer.Chainer.Setup.Setup.WriteStatusLogs(Int32 resultCode, Exception e)
2013-03-07 20:19:00 Slp:         at Microsoft.SqlServer.Chainer.Setup.Setup.Start()
2013-03-07 20:19:00 Slp:         at Microsoft.SqlServer.Chainer.Setup.Setup.Main()
2013-03-07 20:19:00 Slp:     Inner exception type: System.Runtime.InteropServices.ExternalException
2013-03-07 20:19:00 Slp:         Message:
2013-03-07 20:19:00 Slp:                 Cannot execute a program. The command being executed was "C:\Windows\Microsoft.NET\Framework64\v2.0.50727\csc.exe" /noconfig /fullpaths @"C:\Users\cwsmain\AppData\Local\Temp\ebms87n0.cmdline".
2013-03-07 20:19:00 Slp:         Stack:
2013-03-07 20:19:00 Slp:                 at System.CodeDom.Compiler.Executor.ExecWaitWithCaptureUnimpersonated(SafeUserTokenHandle userToken, String cmd, String currentDir, TempFileCollection tempFiles, String& outputName, String& errorName, String trueCmdLine)
2013-03-07 20:19:00 Slp:                 at System.CodeDom.Compiler.Executor.ExecWaitWithCapture(SafeUserTokenHandle userToken, String cmd, String currentDir, TempFileCollection tempFiles, String& outputName, String& errorName, String trueCmdLine)
2013-03-07 20:19:00 Slp:                 at Microsoft.CSharp.CSharpCodeGenerator.Compile(CompilerParameters options, String compilerDirectory, String compilerExe, String arguments, String& outputFile, Int32& nativeReturnValue, String trueArgs)
2013-03-07 20:19:00 Slp:                 at Microsoft.CSharp.CSharpCodeGenerator.FromFileBatch(CompilerParameters options, String[] fileNames)
2013-03-07 20:19:00 Slp:                 at Microsoft.CSharp.CSharpCodeGenerator.FromSourceBatch(CompilerParameters options, String[] sources)
2013-03-07 20:19:00 Slp:                 at Microsoft.CSharp.CSharpCodeGenerator.System.CodeDom.Compiler.ICodeCompiler.CompileAssemblyFromSourceBatch(CompilerParameters options, String[] sources)
2013-03-07 20:19:00 Slp:                 at System.CodeDom.Compiler.CodeDomProvider.CompileAssemblyFromSource(CompilerParameters options, String[] sources)
2013-03-07 20:19:00 Slp:                 at System.Xml.Serialization.Compiler.Compile(Assembly parent, String ns, XmlSerializerCompilerParameters xmlParameters, Evidence evidence)
2013-03-07 20:19:00 Slp:                 at System.Xml.Serialization.TempAssembly.GenerateAssembly(XmlMapping[] xmlMappings, Type[] types, String defaultNamespace, Evidence evidence, XmlSerializerCompilerParameters parameters, Assembly assembly, Hashtable assemblies)
2013-03-07 20:19:00 Slp:                 at System.Xml.Serialization.TempAssembly..ctor(XmlMapping[] xmlMappings, Type[] types, String defaultNamespace, String location, Evidence evidence)
2013-03-07 20:19:00 Slp:                 at System.Xml.Serialization.XmlSerializer.GenerateTempAssembly(XmlMapping xmlMapping, Type type, String defaultNamespace)
2013-03-07 20:19:00 Slp:                 at System.Xml.Serialization.XmlSerializer..ctor(Type type, String defaultNamespace)
2013-03-07 20:19:00 Slp:                 at Microsoft.SqlServer.Chainer.Infrastructure.DataStoreService.DeserializeObject(String rootPath, Type type, String elementXPath)
2013-03-07 20:19:45 Slp: Watson Bucket 1
 Original Parameter Values

2013-03-07 20:19:45 Slp: Parameter 0 : SQL2008@RTM@KB2630458

2013-03-07 20:19:45 Slp: Parameter 1 : Microsoft.SqlServer.Chainer.Infrastructure.DataStoreService.DeserializeObject

2013-03-07 20:19:45 Slp: Parameter 2 : System.CodeDom.Compiler.Executor.ExecWaitWithCaptureUnimpersonated

2013-03-07 20:19:45 Slp: Parameter 3 : Microsoft.SqlServer.Chainer.Infrastructure.ChainerInfrastructureException@1201@1

2013-03-07 20:19:45 Slp: Parameter 4 : System.Runtime.InteropServices.ExternalException@267

2013-03-07 20:19:45 Slp:
 Final Parameter Values

2013-03-07 20:19:45 Slp: Parameter 0 : SQL2008@RTM@KB2630458

2013-03-07 20:19:45 Slp: Parameter 1 : 0x055C02AC

2013-03-07 20:19:45 Slp: Parameter 2 : 0x86203738

2013-03-07 20:19:45 Slp: Parameter 3 : 0xDF039760@1201@1

2013-03-07 20:19:45 Slp: Parameter 4 : 0xD95CEA3F

2013-03-07 20:19:45 Slp: The following exception occurred while preparing status logs during Watson failure processing: Cannot execute a program. The command being executed was "C:\Windows\Microsoft.NET\Framework64\v2.0.50727\csc.exe" /noconfig /fullpaths @"C:\Users\cwsmain\AppData\Local\Temp\edxytlec.cmdline".
2013-03-07 20:19:45 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Microsoft\Microsoft SQL Server to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20130307_200912\Registry_SOFTWARE_Microsoft_Microsoft SQL Server.reg_
2013-03-07 20:19:45 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20130307_200912\Registry_SOFTWARE_Microsoft_Windows_CurrentVersion_Uninstall.reg_
2013-03-07 20:19:45 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Microsoft\MSSQLServer to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20130307_200912\Registry_SOFTWARE_Microsoft_MSSQLServer.reg_
2013-03-07 20:19:45 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Wow6432Node\Microsoft\Microsoft SQL Server to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20130307_200912\Registry_SOFTWARE_Wow6432Node_Microsoft_Microsoft SQL Server.reg_
2013-03-07 20:19:45 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20130307_200912\Registry_SOFTWARE_Wow6432Node_Microsoft_Windows_CurrentVersion_Uninstall.reg_
2013-03-07 20:19:45 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Wow6432Node\Microsoft\MSSQLServer to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20130307_200912\Registry_SOFTWARE_Wow6432Node_Microsoft_MSSQLServer.reg_
2013-03-07 20:19:46 Slp: The following exception occurred during Watson failure processing: The directory is not empty.

2013-03-07 20:19:46 Slp:
2013-03-07 20:19:46 Slp: ----------------------------------------------------------------------
2013-03-07 20:19:46 Slp:
2013-03-07 20:19:46 Slp: Error result: -2068774911
2013-03-07 20:19:46 Slp: Result facility code: 1201
2013-03-07 20:19:46 Slp: Result error code: 1
2013-03-07 20:19:46 Slp:
2013-03-07 20:19:46 Slp: ----------------------------------------------------------------------
2013-03-07 20:19:46 Slp:
2013-03-07 20:19:46 Slp: Error result: -2068774911
2013-03-07 20:19:46 Slp: Result facility code: 1201
2013-03-07 20:19:46 Slp: Result error code: 1

Good day!

I've ran into a serious discussion on SQL server licensing. Even from Microsoft I'm getting controversal answers.

In our organization, we have ISA server 2004 installation acting as a proxy server at our corporate network. Also, we have SQL server 2000 standard installation on the same server; it is used for storing access logs (approx. 15Gb/monthly). An important point is that no user content is stored in the SQL database, no web-cache, only access logs generated by the ISA server.

Now I have two controversal opinions on the licensing. Some people say that the log entries are generated by the users; so, ISA server acts as a "multiplexing device" and therefore we need SQL user CALs for all of our employees who are accessing internet via that ISA server. Others say that as far as the logs are generated by the ISA server itself, it is not "user data", and so far we need only 1 device CAL for the SQL server connection.

At least, they all agree that if SQL server stores turnstile entries, you don't need a license for everyone who passes it.

Would you please help to find out the apropriate licensing scheme?

Hi All,

while installing reporting services to the existing sql server 2008R2 i got the below options.

1>Install the native mode default configuration

2>Install the SharePoint integrated mode default configuration

3>Install,but don't configure Report Server

The above two options are disabled 1>Install the native mode default confirguration2>Install the Sharepoint intergrated mode default confirguration.so i selected the last optionInstall,but don't configure Report Server.Then the installation is completed successfully.

My question is that when am trying to connect to reporting services through the management studio.Am getting below error and not able to see the Reportserver and Report servertemp databases in database engine.

Error:The report services Instance could not be found(Microsoft.Sqlserver.Management.UI.RSClient).

But from Reporting server configuration Manger am able to connect to the report server.

Maheshwar Reddy