Reporting Services install on SQL 2012 SP1 instance blank

Sorry for the duplicate . . . didn't think the first on posted due to VDI locking up.
I have looked at all the links and tried the suggestions and I am still having the problem:
SCCM 2012 R2 SQL 2012 SP1 SSRS installed and configured (separate boxes)
When I try to add the reporting services role, it finds the SCCM database and verifies connectivity to it, the SSRS instance drop down is blank.
Using a domain service accout with local admin rights on both machines and sa rights in SQL.
There is a firewall between the Primary Server and the SQL Server and ports 80, 135, 443, 445, 1433 and the high RPC range.
Does anyone know how it is determining the instance? I have read it is via WMI but I am not sure if it is a query or executing a method. I have verified the svc acct has the correct DCOM privs.

Hi,
How are things going? Please let us know if there is any progress.
Regards.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Similar Messages

SCOM 2012 R2 Report Server component install to SQL 2012 Sp1 error?

Hi All
Im having issues installing SCOM 2012 R2 Report Server component to a SQL 2012 Sp1 Server (which is a Windows 2012 R2 Standard server). Im trying to install to the SQL Default server instance, note that the server also has a named instance
which hosts the SCOM databases. SQL Reporting Services is up and running fine (can access the web urls etc). Im also using the SCOM install account wich has full SQL and SCOM Server admin rights for the install. Ive checked that the Firewall
is off locally on the SQL Server, Ive also checked that the existing SCOM components are all in a Healthy state in the SCOM console.
The installed version of SQL Server could not be verified or is not supported. Verify that the computer and the installed version of SQL Server meet the minimum requirements for installation, and that the firewall settings are correct. See the Supported
Configurations document for further information.
Ive attempted the install on a standalone SQL Server away from the SQL Server hosting the SCOM databases, but encounter the same error. The full SCOM MSI Installer log details are below, line that appears most relevant is below but unsure why
this would be the case (same account that I used for SQL install etc). Any help much appreciated! : )
Error: :getSQLInstanceVersion: Unable to find the SRS Instance Key: MSSQLSERVER
[11:51:46]: Debug: :CheckPrerequisites: IsComputerNameValidTitle: Passed
[11:51:46]: Debug: :
[11:51:46]: Debug: :**************************************************
[11:51:46]: Debug: :**************************************************
[11:51:46]: Debug: :<![CDATA[CheckPrerequisites:   Logic Type:and AvicodeAgentInstalled-x86: 0CheckPrerequisites:   Logic Type:and AvicodeAgentInstalled-x64: 0]]>
[11:51:46]: Debug: :
[11:51:46]: Debug: :CheckPrerequisites: AVIcodeAgentCheck: Passed
[11:51:46]: Debug: :
[11:51:46]: Debug: :**************************************************
[11:51:46]: Always: :CheckPrerequisites: Return Value 0
[11:51:46]: Always: :Entering Page: AdditionalPrerequisitesPage
[11:51:48]: Always: :Entering Page: ShortEulaPage
[11:51:48]: Always: :Displaying localized EULA for localization: en
[11:51:48]: Always: :Displaying Eula: C:\Users\opsmgr\AppData\Local\SCOM\Setup\en\eula_en_notice.rtf
[11:51:49]: Info: :Info:User has agreed to EULA.
[11:51:50]: Always: :Entering Page: SelectManagementServerForReporting
[11:52:08]: Info: :Info:Management Server matches the current version of setup.
[11:52:08]: Always: :Entering Page: SelectReportingInstance
[11:52:08]: Always: :SQL Server SRS Instance (escaped name) RS_MSSQLSERVER
[11:52:08]: Info: :Attempting to get the SSRS version from:
\\WDC-SYSSQL01\Root\Microsoft\SqlServer\ReportServer\RS_MSSQLSERVER:__NAMESPACE
[11:52:08]: Debug: :Path is
\\WDC-SYSSQL01\Root\Microsoft\SqlServer\ReportServer\RS_MSSQLSERVER\V11:MSReportServer_Instance
[11:52:08]: Always: :SRS instance on WDC-SYSSQL01. Version 11.0.3000.0.
[11:52:08]: Always: :No SRS instances on WDC-SYSSQL01.
[11:52:08]: Error: :getSQLInstanceVersion: Unable to find the SRS Instance Key: MSSQLSERVER
[11:52:08]: Info: :Info: WDC-SYSSQL01 SRS version =
[11:52:08]: Error: :Couldn't check SRS version: Threw Exception.Type: System.ArgumentException, Exception Error Code: 0x80070057, Exception.Message: Version string portion was too short or too long.
[11:52:08]: Error: :StackTrace:   at System.Version.TryParseVersion(String version, VersionResult& result)
   at System.Version.Parse(String input)
   at Microsoft.EnterpriseManagement.OperationsManager.Setup.ReportingComponent.CheckSRSVersion(String srsInstance, String requiredSRSVersion)
[11:52:11]: Info: :Attempting to check SRS version
[11:52:11]: Error: :getSQLInstanceVersion: Unable to find the SRS Instance Key: MSSQLSERVER
[11:52:11]: Info: :Info: WDC-SYSSQL01 SRS version =
[11:52:11]: Error: :Couldn't check SRS version: Threw Exception.Type: System.ArgumentException, Exception Error Code: 0x80070057, Exception.Message: Version string portion was too short or too long.
[11:52:11]: Error: :StackTrace:   at System.Version.TryParseVersion(String version, VersionResult& result)
   at System.Version.Parse(String input)
   at Microsoft.EnterpriseManagement.OperationsManager.Setup.ReportingComponent.CheckSRSVersion(String srsInstance, String requiredSRSVersion)
[11:52:28]: Info: :The user canceled setup
[11:52:28]: Always: :Begin: Property bag dump.
[11:52:28]: Always: :SetupStartTime = 26/03/2014 11:51:38
[11:52:28]: Always: :Collection ProtectedProperties (System.Collections.ArrayList):
[11:52:28]: Always: : [0] = ActionAccountPassword
[11:52:28]: Always: : [1] = DASAccountPassword
[11:52:28]: Always: :DefaultLogName = C:\Users\opsmgr\AppData\Local\SCOM\Logs\OpsMgrSetupWizard.log
[11:52:28]: Always: :DefaultLogPath = C:\Users\opsmgr\AppData\Local\SCOM\Logs
[11:52:28]: Always: :path = F:\Setup\AMD64\
[11:52:28]: Always: :setupexepath = C:\Users\opsmgr\AppData\Local\SCOM\Setup
[11:52:28]: Always: :ArchitectureIs64Check = True
[11:52:28]: Always: :OperationManagerAgentInstalled = 1
[11:52:28]: Always: :Collection ListOfSupportedComponents (System.Collections.ArrayList):
[11:52:28]: Always: : [0] = OMCONSOLE
[11:52:28]: Always: : [1] = OMSERVER
[11:52:28]: Always: : [2] = OMWEBCONSOLE
[11:52:28]: Always: : [3] = OMREPORTING
[11:52:28]: Always: :install = 1
[11:52:28]: Always: :installpath = C:\Program Files\Microsoft System Center 2012 R2\Operations Manager
[11:52:28]: Always: :EulaFilesPath = C:\Users\opsmgr\AppData\Local\SCOM\Setup
[11:52:28]: Always: :HealthServiceTypeId = AB4C891F-3359-3FB6-0704-075FBFE36710
[11:52:28]: Always: :hsPort = C51B7833-DA54-1653-D8FD-1A738EF8DED5
[11:52:28]: Always: :ServerBlockReason = A Operations Manager agent was found on this computer. Please remove the agent and then run Setup again.
[11:52:28]: Always: :ScreensLoaded = 1
[11:52:28]: Always: :Collection ListOfSelectedComponents (System.Collections.ArrayList):
[11:52:28]: Always: : [0] = OMREPORTING
[11:52:28]: Always: :OMREPORTING = 1
[11:52:28]: Always: :SelectDatabaseInstanceReloadScreenInformation = 1
[11:52:28]: Always: :ReloadPrerequisitesPageChoice = PrerequisitesProgressPage
[11:52:28]: Always: :LoadedPrerequisiteXmlFile = True
[11:52:28]: Always: :PrerequisitesCheckXMLLoaded = True
[11:52:28]: Always: :CountFilteredPrerequisites_Failed = 0
[11:52:28]: Always: :CountFilteredPrerequisites_Warning = 0
[11:52:28]: Always: :CountFilteredPrerequisites_PassedWithChoices = 0
[11:52:28]: Always: :CountFilteredPrerequisites_Passed = 10
[11:52:28]: Always: :PrerequisiteState = Passed
[11:52:28]: Always: :XmlFilteredPrerequisites_Passed : Begin XML property
[11:52:28]: Always: :<?xml version="1.0" encoding="utf-8"?><Root><Title TitleText="OMREPORTING"><Detail state="Passed" image="pack://application:,,,/SetupChainerUI;component/GreenCheck.png"
name="memoryCheckTitle" descriptionBody="" descriptionTitle="ReportingMemCheckPassed" resolution="ReportingMemCheckResolution" /><Detail state="Passed" image="pack://application:,,,/SetupChainerUI;component/GreenCheck.png"
name="ntfsCheckTitle" descriptionBody="" descriptionTitle="ntfsCheckPassed" resolution="ntfsCheckResolution" /><Detail state="Passed" image="pack://application:,,,/SetupChainerUI;component/GreenCheck.png"
name="DriveSpaceCheckTitle" descriptionBody="" descriptionTitle="ServerDriveSpaceCheckPassed" resolution="ServerDriveSpaceCheckResolution" /><Detail state="Passed" image="pack://application:,,,/SetupChainerUI;component/GreenCheck.png"
name="OSVersionCheckTitle" descriptionBody="" descriptionTitle="OSVersionCheckPassed" resolution="OSVersionCheckResolution" /><Detail state="Passed" image="pack://application:,,,/SetupChainerUI;component/GreenCheck.png"
name="WindowsInstallerCheckTitle" descriptionBody="" descriptionTitle="WindowsInstallerCheckPassed" resolution="WindowsInstallerCheckResolution" /><Detail state="Passed" image="pack://application:,,,/SetupChainerUI;component/GreenCheck.png"
name="RemoteRegistryCheckTitle" descriptionBody="" descriptionTitle="RemoteRegistryCheckPassed" resolution="RemoteRegistryCheckResolution" /><Detail state="Passed" image="pack://application:,,,/SetupChainerUI;component/GreenCheck.png"
name="PendingRebootCheckTitle" descriptionBody="" descriptionTitle="PendingRebootCheckPassed" resolution="PendingRebootCheckResolution" /><Detail state="Passed" image="pack://application:,,,/SetupChainerUI;component/GreenCheck.png"
name="ActiveDirectoryCheckTitle" descriptionBody="" descriptionTitle="ActiveDirectoryCheckPassed" resolution="ActiveDirectoryCheckResolution" /><Detail state="Passed" image="pack://application:,,,/SetupChainerUI;component/GreenCheck.png"
name="IsComputerNameValidTitle" descriptionBody="" descriptionTitle="IsComputerNameValidPassed" resolution="IsComputerNameValidResolution" /><Detail state="Passed" image="pack://application:,,,/SetupChainerUI;component/GreenCheck.png"
name="AVIcodeAgentCheck" descriptionBody="" descriptionTitle="AVICodeAgentCheckPassed" resolution="AVICodeAgentCheckResolution" /></Title></Root>
[11:52:28]: Always: :End XML property
[11:52:28]: Always: :ManagementServer = WDC-SYSOPS01.landmarc.local
[11:52:28]: Always: :DefaultSDKMachine = WDC-SYSOPS01.landmarc.local
[11:52:28]: Always: :UserCanceledInstall = 1
[11:52:28]: Always: :InstallSuccess = 1
[11:52:28]: Always: :End: Property bag dump.
[11:52:28]: Debug: :CEIP disabled. CEIP data will NOT be sent.
[11:52:28]: Always: :Application Ended: Successful
[11:52:28]: Always: :
[2014-03-26T11:52:28.4724357+00:00]: Always: Trace Session Ended

Hi,
According to the error message:
[11:52:11]: Error: :getSQLInstanceVersion: Unable to find the SRS Instance Key: MSSQLSERVER
[11:52:11]: Info: :Info: WDC-SYSSQL01 SRS version =
[11:52:11]: Error: :Couldn't check SRS version: Threw Exception.Type: System.ArgumentException, Exception Error Code: 0x80070057, Exception.Message: Version string portion was too short or too long.
The issue is SQL report server database related, I would like to suggest you create a new report database for SCOM and then check the reuslt. Please refer to the below links and follow it to set up SCOM 2012 R2:
http://blogs.technet.com/b/kevinholman/archive/2013/01/16/opsmgr-2012-sp1-quickstart-deployment-guide.aspx
In addition, here is thread for your reference also:
http://social.technet.microsoft.com/Forums/en-US/3f883b7f-5a33-49f0-a40d-f3311e68609d/unable-to-connect-to-the-data-access-service-installing-report-server?forum=operationsmanagerreporting
Regards,
Yan Li
Regards, Yan Li

SCOM 2012 R2 installing on SQL 2012 SP1 - Error Code: 0x80131904, Exception.Message: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.

Hi,
I am getting an issue during a SCOM 2012 R2 installation while creating the SCOM DataWarehouse database. Setup seems to timeout during creating the datawarehouse database. I can see all database files created in windows explorer on the SQL server before
setup rolls the SCOM install back.
Has anyone seen this issue before or know how to help resolve it?
Appreciate your help, below is the SCOM installation log:
Thanks
Marc
[13:27:27]: Always: :Creating Database: OperationsManagerDW
[13:35:28]: Warn: :Warning:Retry on SQL error -2: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
[13:43:28]: Warn: :Warning:Retry on SQL error -2: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
[13:51:29]: Warn: :Warning:Retry on SQL error -2: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
[13:59:30]: Warn: :Warning:Retry on SQL error -2: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
[14:07:30]: Warn: :Warning:Retry on SQL error -2: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
[14:15:31]: Warn: :Warning:Retry on SQL error -2: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
[14:23:31]: Warn: :Warning:Retry on SQL error -2: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
[14:31:32]: Warn: :Warning:Retry on SQL error -2: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
[14:39:32]: Warn: :Warning:Retry on SQL error -2: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
[14:47:33]: Warn: :Warning:Retry on SQL error -2: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
[14:55:33]: Error: :DB operations failed with SQL error -2: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
: Threw Exception.Type: System.Data.SqlClient.SqlException, Exception Error Code: 0x80131904, Exception.Message: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
[14:55:33]: Error: :StackTrace:   at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
   at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)
   at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
   at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async, Int32 timeout, Task& task, Boolean asyncWrite, SqlDataReader ds)
   at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, TaskCompletionSource`1 completion, Int32 timeout, Task& task, Boolean asyncWrite)
   at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(TaskCompletionSource`1 completion, String methodName, Boolean sendToPipe, Int32 timeout, Boolean asyncWrite)
   at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
   at Microsoft.EnterpriseManagement.OperationsManager.Setup.Common.SqlRetryHandler.ExecuteNonQuery(SqlCommand sqlCommand, Int32& result)
   at Microsoft.EnterpriseManagement.OperationsManager.Setup.Common.SqlRetryHandler.Execute[T](SqlCommand sqlCommand, SqlRetryPolicy retryPolicy, GenericExecute`1 genericExecute)
[14:55:33]: Error: :Inner Exception.Type: System.ComponentModel.Win32Exception, Exception Error Code: 0x80131904, Exception.Message: The wait operation timed out
[14:55:33]: Error: :InnerException.StackTrace:
[14:55:33]: Error: :Error:Failed to execute sql command. Setup has reached maximum retry limit.
[14:55:33]: Warn: :Sql error: 11. Error: -2. Error Message: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
[14:55:33]: Error: :Exception running sql string
DECLARE @sql NVARCHAR(MAX);
SET @sql = 'CREATE DATABASE ' + QUOTENAME(@DatabaseName) + '
    ON PRIMARY(NAME=MOM_DATA,FILENAME=''' + REPLACE(@Filename, '''', '''''') + ''',SIZE=' + CAST(@Size AS VARCHAR) + 'MB,MAXSIZE=UNLIMITED,FILEGROWTH=' + CAST(@FileGrowth AS VARCHAR) + 'MB)
    LOG ON(NAME=MOM_LOG, FILENAME=''' + REPLACE(@LogFilename, '''', '''''') + ''',SIZE=' + CAST(@LogSize AS VARCHAR) + 'MB,MAXSIZE=UNLIMITED,FILEGROWTH=' + CAST(@LogFileGrowth AS VARCHAR) + 'MB)';
EXEC(@sql);: Threw Exception.Type: System.Data.SqlClient.SqlException, Exception Error Code: 0x80131904, Exception.Message: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
[14:55:33]: Error: :StackTrace:   at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
   at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)
   at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
   at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async, Int32 timeout, Task& task, Boolean asyncWrite, SqlDataReader ds)
   at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, TaskCompletionSource`1 completion, Int32 timeout, Task& task, Boolean asyncWrite)
   at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(TaskCompletionSource`1 completion, String methodName, Boolean sendToPipe, Int32 timeout, Boolean asyncWrite)
   at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
   at Microsoft.EnterpriseManagement.OperationsManager.Setup.Common.SqlRetryHandler.ExecuteNonQuery(SqlCommand sqlCommand, Int32& result)
   at Microsoft.EnterpriseManagement.OperationsManager.Setup.Common.SqlRetryHandler.Execute[T](SqlCommand sqlCommand, SqlRetryPolicy retryPolicy, GenericExecute`1 genericExecute)
   at Microsoft.EnterpriseManagement.OperationsManager.Setup.DBConfigurationHelper.DBConfiguration.RunSqlCommandsList(IEnumerable`1 sqlCommands)
[14:55:33]: Error: :Inner Exception.Type: System.ComponentModel.Win32Exception, Exception Error Code: 0x80131904, Exception.Message: The wait operation timed out
[14:55:33]: Error: :InnerException.StackTrace:
[14:55:33]: Always: :Failed to create and configure the DB with exception.: Threw Exception.Type: System.Data.SqlClient.SqlException, Exception Error Code: 0x80131904, Exception.Message: Timeout expired. The timeout period elapsed prior to completion
of the operation or the server is not responding.
[14:55:33]: Always: :StackTrace:   at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
   at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)
   at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
   at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async, Int32 timeout, Task& task, Boolean asyncWrite, SqlDataReader ds)
   at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, TaskCompletionSource`1 completion, Int32 timeout, Task& task, Boolean asyncWrite)
   at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(TaskCompletionSource`1 completion, String methodName, Boolean sendToPipe, Int32 timeout, Boolean asyncWrite)
   at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
   at Microsoft.EnterpriseManagement.OperationsManager.Setup.Common.SqlRetryHandler.ExecuteNonQuery(SqlCommand sqlCommand, Int32& result)
   at Microsoft.EnterpriseManagement.OperationsManager.Setup.Common.SqlRetryHandler.Execute[T](SqlCommand sqlCommand, SqlRetryPolicy retryPolicy, GenericExecute`1 genericExecute)
   at Microsoft.EnterpriseManagement.OperationsManager.Setup.DBConfigurationHelper.DBConfiguration.RunSqlCommandsList(IEnumerable`1 sqlCommands)
   at Microsoft.EnterpriseManagement.OperationsManager.Setup.DWConfigurationHelper.DWConfigurationProcessor.RunAdminScripts(String sqlServerInstance, Nullable`1 port, String databaseName, Int64 dbSize, Int64 logSize, String dbPath, String logPath)
   at Microsoft.EnterpriseManagement.OperationsManager.Setup.DWConfigurationHelper.DWConfigurationProcessor.ConfigureDataWarehouseDatabase(String sqlServerInstance, Nullable`1 port, String databaseName, Int64 dbSize, Int64 logSize, String dbPath,
String logPath)
[14:55:33]: Always: :Inner Exception.Type: System.ComponentModel.Win32Exception, Exception Error Code: 0x80131904, Exception.Message: The wait operation timed out
[14:55:33]: Always: :InnerException.StackTrace:
[14:55:33]: Error: :CreateDataWarehouse failed: Threw Exception.Type: System.Data.SqlClient.SqlException, Exception Error Code: 0x80131904, Exception.Message: Timeout expired. The timeout period elapsed prior to completion of the operation or
the server is not responding.
[14:55:33]: Error: :StackTrace:   at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
   at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)
   at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
   at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async, Int32 timeout, Task& task, Boolean asyncWrite, SqlDataReader ds)
   at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, TaskCompletionSource`1 completion, Int32 timeout, Task& task, Boolean asyncWrite)
   at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(TaskCompletionSource`1 completion, String methodName, Boolean sendToPipe, Int32 timeout, Boolean asyncWrite)
   at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
   at Microsoft.EnterpriseManagement.OperationsManager.Setup.Common.SqlRetryHandler.ExecuteNonQuery(SqlCommand sqlCommand, Int32& result)
   at Microsoft.EnterpriseManagement.OperationsManager.Setup.Common.SqlRetryHandler.Execute[T](SqlCommand sqlCommand, SqlRetryPolicy retryPolicy, GenericExecute`1 genericExecute)
   at Microsoft.EnterpriseManagement.OperationsManager.Setup.DBConfigurationHelper.DBConfiguration.RunSqlCommandsList(IEnumerable`1 sqlCommands)
   at Microsoft.EnterpriseManagement.OperationsManager.Setup.DWConfigurationHelper.DWConfigurationProcessor.RunAdminScripts(String sqlServerInstance, Nullable`1 port, String databaseName, Int64 dbSize, Int64 logSize, String dbPath, String logPath)
   at Microsoft.EnterpriseManagement.OperationsManager.Setup.DWConfigurationHelper.DWConfigurationProcessor.ConfigureDataWarehouseDatabase(String sqlServerInstance, Nullable`1 port, String databaseName, Int64 dbSize, Int64 logSize, String dbPath,
String logPath)
   at Microsoft.SystemCenter.Essentials.SetupFramework.InstallItemsDelegates.OMDataWarehouseProcessor.CreateDataWarehouse()
[14:55:33]: Error: :Inner Exception.Type: System.ComponentModel.Win32Exception, Exception Error Code: 0x80131904, Exception.Message: The wait operation timed out
[14:55:33]: Error: :InnerException.StackTrace:
[14:55:33]: Error: :FATAL ACTION: CreateDataWarehouse
[14:55:33]: Error: :FATAL ACTION: DWInstallActionsPostProcessor
[14:55:33]: Error: :ProcessInstalls: Running the PostProcessDelegate returned false.
[14:55:33]: Always: :SetErrorType: Setting VitalFailure. currentInstallItem: Data Warehouse Configuration
[14:55:33]: Error: :ProcessInstalls: Running the PostProcessDelegate for OMDATAWAREHOUSE failed.... This is a fatal item. Setting rollback.
marc nalder

Hi,
Based on the log, I recommend you use the following way to test SQL connectivity.
You can use a UDL file to test various connectivity scenarios, create a simple text file, rename the extension from TXT to UDL, fill out the necessary information on the connection tab then test the connection, and troubleshoot as necessary
if it fails to connect.
For more information, please review the link below:
The easy way to test SQL connectivity
http://blogs.technet.com/b/michaelgriswold/archive/2014/01/06/the-easy-way-to-test-sql-connectivity.aspx
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Report Services Install - SQL Server 2012 instance blank

I have looked at all the links and tried the suggestions and I am still having the problem:
SCCM 2012 R2 SQL 2012 SP1 SSRS installed and configured (separate boxes)
When I try to add the reporting services role, it finds the SCCM database and verifies connectivity to it, the SSRS instance drop down is blank.
Using a domain service accout with local admin rights on both machines and sa rights in SQL.
There is a firewall between the Primary Server and the SQL Server and ports 80, 135, 443, 445, 1433 and the high RPC range.
Does anyone know how it is determining the instance? I have read it is via WMI but I am not sure if it is a query or executing a method. I have verified the svc acct has the correct DCOM privs.

Hi Jo75,
According to my understanding, you get the error message “Unable to connect to the database: Network error IOException: Connection refused: connect” when you connect to the SQL Server database
during installation of Trend Micro's DSM.
Based on my test, I was able to connect to the SQL Server database with the user name “sa” during the installation of Deep Security Manager and no error message appeared. Besides, I created
a new SQL Server login and it also worked fine.
Make sure you can connect to the SQL Server instance successfully, you can follow these steps:
1. Open SQL Server Management Studio and click Database Engine from pull-down menu of Connect in Object Explorer.
2. In the Server name box, you should type hostname\instance name. And you should choose SQL Server Authentication in Authentication box and type “sa” in Login box, then type your password
and click Connect.
If you can’t connect to SQL Server, you can try to create a new login and give it full permission. Please follow these steps:
1. Open SQL Server Management Studio and connect to SQL Server with administrator account.
2. Click Security and right click Logins then choose New Login.
3. In General page, type your new Login name and choose SQL Server Authentication, then set your password.
4. Click Server Roles
at
the
top-left
corner
and check the dbcreator box.
5. Click Status at the top-left corner and check enabled under the login, then click ok.
6. Click the database you want to connect during the installation of Deep Security Manager, expand the security and right click the users, then choose New User.
7. Type your user name and login name in General page. Click Owned Schemas page and check db_owner. Also check db_owner in Membership page then click ok.
8. Retry install Deep Security Manager.
Please follow these steps and how it works.
Best regards,
Qiuyun Yu

SQL 2012 SP1 Enterprise (SSRS in SharePoint mode): Reporting Services scale-out deployment is not supported in this edition of Reporting Services

Hello,
SSRS in SharePoint mode is driving me insane.
We are recreating a SharePoint 2013 (SP1) farm in a test environment with the following set-up:
2 SP Web FrontEnds
2 SP Application Servers
1 SQL Server
At both SP APP Servers, we installed SSRS (SQL 2012 Enterprise w/ SP1) in SP integrated mode.
We managed to start the SSRS SP service at the first SP APP Server. However when we try to start it on the second APP Server, we get the following error:
"Reporting Services scale-out deployment is not supported in this edition of Reporting Services. This edition only supports one instance of the SQL Server Reporting Services Service in the farm. The SQL Server Reporting Services service cannot
be started on this server unless it is stopped on all other servers in the farm. "
Now I can't stress this enough: This is a SQL Server 2012 SP1 Enterprise. This is the image we got from our MSDN subscription. There is no mistake here.
Could someone please advise why SP might think this version of SSRS is not the correct one?
Thanks in advance for your help.
Regards,
P.

Hello,
I'm afraid that is not it.
After a long, frustrating and strenuous investigation and troubleshooting, we found the problem.
The problem is the current ISO for SQL Server 2012 Enterprise SP1 (x64) found at MSDN. Bear in mind that we downloaded this ISO from MSDN about a month ago.
As soon as we recreated the environment using the ISO for SQL Server 2012 Enterprise SP2 (x64) found at MSDN, everything worked as expected -- and that includes running more than one SSRS in SharePoint mode.
Also bear in mind that we tried updating the SQL SP1 install with SP2 and subsequent cumulative updates but that never fixed the problem.
There is something fundamentally wrong with that ISO with SP1 slipstreamed in it that no matter the subsequent updates installed, SSRS in SharePoint mode fails to work properly on a multi-server environment. We went as far as SP2 with CU3 and nothing seemed
to fix the problem. And yes, we also performed manual updates to the SSRS and PowerPivot SharePoint MSI add-ins.
I am shocked and distraught to find out that I lost hours of work due to a dodgy ISO image.
Regards,
P.

Reporting Service Error Code 7403, on SCCM 2012 R2 with SQL 2012 SP1 CU6

Dear All,
I am facing issue to install Reporting Services Point on SCCM 2012 R2 with SQL 2012 SP1 CU6. getting error messages id 7403. please let me know if SQL 2012 SP1 CU6 is supported with SCCM 2012 R2 or not & if you have any solution on it.
Error Message: The report server service is not running on Reporting Service Point server "SCCM2012"; start the service to enable reporting.

I am getting below error msg when trying to browse both sites
1) For Reports
The report server cannot decrypt the
symmetric key that is used to access sensitive or encrypted data in a report
server database. You must either restore a backup key or delete all encrypted
content. (rsReportServerDisabled)
Get Online Help
Keyset does not exist (Exception from
HRESULT:
0x80090016)
2) For Reportserver
Reporting Services Error
The report server cannot decrypt the symmetric key that is used to access
sensitive or encrypted data in a report server database. You must either restore
a backup key or delete all encrypted content. (rsReportServerDisabled)
Get Online Help
Keyset does not exist (Exception from HRESULT: 0x80090016)
SQL Server Reporting Services

Reports not Generated after moving SCCM 2012 SP1 DB on SQL 2012 SP1 cluster

Hi all,
i have moved my SCCM 2012 SP1 DB on SQL 2012 SP1 Failover Cluster,this cluster is a two node cluster.the DB was moved fine and the DB configuration in SCCM Site maintenance was also done successfully.After the migration process,SCCM was working fine created
few collections & packages, then checked the DB on cluster & they were updated successfully.
but when i tried to install report server on my SCCM machine,again there was no instance displayed after entering the cluster name.
I searched this & come across this post :-
http://social.technet.microsoft.com/Forums/en-US/configmanagergeneral/thread/4479e73e-8a19-4c7e-9418-b36770656b9b/
which says to install report server on the cluster node machine which is currently running the Reporting Service.I tried to install the report server & the instance was detected this time.it was installed successfully.
But when i tried to generate reports I got this error :-
Permissions are fine as i have added SCCMadmin & sccm machine in the local admin of both the nodes.
Please Help.
Thanks,
Pranay.

Yes, I know this is an old post, but I’m trying to clean them up. Did you solve this problem, if so what was the solution?
If you look at your second screenshot the Remote errors is not enabled. Use this blog to enable them.
http://www.enhansoft.com/blog/enabling-remote-errors-in-sql
If changing the data source on the report fixed it for a single report. It means that your shared Datasource is having problems. Reset the username and password within CM12 console and this should fix it for every report.
Garth Jones | My blogs: Enhansoft and
Old Blog site | Twitter:
@GarthMJ

Sharepoint 2013 SSRS Interaction with Sql Server 2012 Reporting Services connecting to Sql Server 2008 R2 database

Hi
I'm working on upgrading sharepoint 2010 to sharepoint 2013 with sql server 2008 r2. I've ran into some problems but have been able to get a test farm upgraded. However to run SSRS 2013 it seems Sql Server 2012 Reporting Services are required. Upgrading
to a full sql server 2012 database isn't an option. I know that sql server 2012 reporting services can use sql server 2008 r2 as a catalog and content database so I was wondering could this be a workaround? Importantly would I need a separate machine/virtual
machine to host sql server 2012 reporting services? or could it live on the sql server 2008 r2 machine? Any pointers appreciated. Thanks Dan

Remember that SSRS must be deployed on the SharePoint server. Having said that, yes you can install SSRS 2012 SP1 on a server running SQL 2008 R2. And yes, you can use 2008 R2 as your Database Engine server while SSRS 2012 SP1 runs on the SharePoint server.
Trevor Seward
Follow or contact me at...
&nbsp&nbsp
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

Non supported version of SQL with new install of SCOM 2012 SP1

I have SQL 2012 SP1 running on Server 2012. I have tried the SCOM installation with and without CU2 (to fix the 1618 installation error)
SC VMM installed cleanly and appears to work.
The install for SCOM produces an error that says, "The installed version of SQL Server is not supported". I have not been able to find any log from the install that has that error in it.
Also, I have not been able to determine the true requirements of the SQL server for SCOM. (I found dock SCOM 2012 RTM and SQL 2008 R2, but noting for 2012 SP1.
Can someone point me to the correct place for the install log with (hopefully more information) and/or the requrements for the SQL installation?
Roy

The log is not created yet because it has not started the install.
The firewall is the most common issue indeed. Temporarily Disable the firewall and see whether you can continue.
Are you using a developers edition? The only 2 editions supported are standard and Enterprise.
The true requirements for SCOM 2012 sp1:
We recommend that you check for updates and hotfixes for SQL Server. Note the following database considerations for Operations Manager:
SQL Server 2008 R2 and SQL Server 2012 are available in both Standard and Enterprise editions. Operations Manager will function with both editions.
Operations Manager does not support hosting its databases or SQL Server Reporting Services on a 32-bit edition of SQL Server.
Using a different version of SQL Server for different Operations Manager features is not supported. The same version should be used for all features.
SQL Server collation settings for all databases must be one of the following: SQL_Latin1_General_CP1_CI_AS, French_CI_AS, Cyrillic_General_CI_AS, Chinese_PRC_CI_AS, Japanese_CI_AS, Traditional_Spanish_CI_AS, or Latin1_General_CI_AS. No other collation
settings are supported.
The SQL Server Agent service must be started, and the startup type must be set to automatic.
Side-by-side installation of System Center Operations Manager 2007 R2 reporting and System Center 2012 Service Pack 1 (SP1), Operations Manager reporting on the same server is not supported.
The db_owner role for the operational database must be a domain account. If you set the SQL Server Authentication to Mixed mode, and then try to add a local SQL Server login on the operational database, the Data Access service will not be able to start.
For information about how to resolve the issue, see System Center Data Access Service Start Up Failure Due to SQL Configuration Change
If you plan to use the Network Monitoring features of System Center 2012 – Operations Manager, you should move the tempdb database to a separate disk that has multiple spindles. For more information, see
tempdb Database.
Found here:
http://technet.microsoft.com/en-us/library/jj656654.aspx#BKMK_RBF_OperationsDatabase
It's doing common things uncommonly well that brings succes.

SQL Reporting Services install

I've installed 2 SCOM 2012 management servers. I now need to install SQL reporting services. Can I install this on a seperate server (not the management server or the SQL server where the database will be)?
I asked the SQL team if i could install SQL reporting services on the SQL servers where all the databases are held and they don't want this done so need to install on a seperate box but can't find any notes what says this is possible

Hi,
SCOM reporting server role should be installed on a SQL server where SQL reporting services is installed.
Please also refer to the article below:
How to Install the Operations Manager Reporting Server
https://technet.microsoft.com/en-us/library/hh298611.aspx
Regards,
Yan Li
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]

SQL 2012 sp1 EE setup disappears when installing Setup Support files ( Error: sqm does not have active session)

HI Folks,
WIndows : 2008 R2
SQL : 2012 sp1 EE
Setup disappears when installing setup support files On passiive node ( 2 node cluster), sql is runing on active node without any issue
Error : SQM does not active session ( In summary detail txt file)
blog is suggesting . Save the following in a .reg file and merge to populate the registry: (
here i am confusing how to save and where to save , how to merge and how to populate)
http://blogs.msdn.com/b/sqljourney/archive/2012/05/07/sql-2008-2008-r2-setup-disappears-fails-when-installing-setup-support-files.aspx
Can you share your views, if you need any information for clarification. pls let us know for resolution.
Thanks in Advance.

Sorry but there is already released SP2 for SQL Server 2012. Start installation on the passive node first
Best Regards,Uri Dimant SQL Server MVP,
http://sqlblog.com/blogs/uri_dimant/
MS SQL optimization: MS SQL Development and Optimization
MS SQL Consulting:
Large scale of database and data cleansing
Remote DBA Services:
Improves MS SQL Database Performance
SQL Server Integration Services:
Business Intelligence

SQL Server Reporting Services installed on a production database server used to support JD Edwards EnterpriseOne. What performance isses can arise

SQL Server Reporting Services installed on a production database server used to support JD Edwards EnterpriseOne. What performance isses can arise. Is it recommended. What are the pros and cons

Hi hazelannc,
I am trying to involve someone more familiar with this topic for a further look at this issue. Sometime delay might be expected from the job transferring. Your patience is greatly appreciated. Thank you for your understanding and support.
Regards,
Katherine Xiong
Katherine Xiong
TechNet Community Support

Moving Service Manager Database From SQL 2008 R2 SP2 to SQL 2012 SP1

Hi Guys,
Just looking for some clarification about moving our Service Manager 2012 R2 database to a new SQL Server.
Our Service Manager database is currently on a remote SQL server, shared with other databases, running SQL 2008 R2 SP2. It was originally setup this way as we only deployed Change Management but we are now wanting to deploy everything, fully
utilising SCSM/Orchestrator and Cireson's suite. Due to the limited resources available on that SQL server we are seeing performance issues before even getting it all up and running.
I want to move the Service Manager database to a new dedicated SQL server running SQL 2012 SP1. I am aware of the official DB move procedure but it does not specifically mention moving up SQL versions. I have seen some comments around here that
it is fine to do but some feedback would be good, it is not something I have done before.
All servers in this are fully patched Windows 2008 R2. Also, we do not currently have a Data Warehouse so do not need to worry about that. It was dropped and uninstalled before upgrading to Service Manager 2012 R2 and will be reinstalled after this DB move
using a separate dedicated SQL server.
Thanks, Chris.

As long as your collations and permissions are the same as before it
should not be a problem. That sad i could not find any other documentation saying it's not supported.
I have moved SCSM databases between different SQL-versions before and it has worked fine if the collations etc are correct.
Cheers,
Thomas Strömberg
System Center Specialist
Blog:
Twitter: LinkedIn:
Please remember to 'Propose as answer' if you find a reply helpful

Silent install parameters for Mgmt Studio (from SQL 2012 SP1 Express)

Hi All,
I'm looking to incorporate the installation of SQL Management studio ONLY from the SQL 2012 Sp1 Express bundle, into System Centre Configuration Manager. I need the silent installation options to install all features for it.
File used - SQLManagementStudio_x64_ENU.exe
From URL - http://www.microsoft.com/en-ca/download/details.aspx?id=35579
I'm looking for something like this:
"SQLManagementStudio_x64_ENU.exe /ACTION=INSTALL /QUIET /IAcceptSQLServerLicenseTerms="True"
/FEATURES= etc.....
Can anyone point me in the right direction? I just want to run the command and have it install SQL 2012
Management Studio (this one is the full version) without having to run through the whole setup.exe process and it's silent installation..
Thanks in advance

Hello,
First you need to extract the content of the .EXE file to a local folder, as shown below:
SQLManagementStudio_x64_ENU.exe /x
Then you can try to run the following command:
"c:\folder_containing_installation_files\setup.exe" /ACTION=INSTALL /QUIET /FEATURES=SSMS /HIDECONSOLE
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

Error during unattended install of SQL 2012 (..setting 'CLTRESULTDIR' does not exist.)

Hi ALl,
I'm trying an automated install of SQL 2012 on WIndows 2012, but I keep running into this error (using a configuration.ini file generated by running through setup and grabbing it just before I clicked 'OK')
Contents of summary log:
Overall summary:
   Final result:                  Failed: see details below
   Exit code (Decimal):           -2068578304
   Exit facility code:            1204
   Exit error code:               0
   Exit message:                  The specified directory 'C:\Program Files (x86)\Microsoft SQL Server\DReplayClient\ResultDir' for setting 'CLTRESULTDIR' does not
exist.
   Start time:                    2015-01-09 10:19:12
   End time:                      2015-01-09 10:20:07
   Requested action:              Install
Setup completed with required actions for features.
Troubleshooting information for those features:
   Next step for SQLEngine:       SQL Server Setup was canceled before completing the operation. Try the setup process again.
   Next step for Replication:     SQL Server Setup was canceled before completing the operation. Try the setup process again.
   Next step for FullText:        SQL Server Setup was canceled before completing the operation. Try the setup process again.
   Next step for DQ:              SQL Server Setup was canceled before completing the operation. Try the setup process again.
   Next step for AS:              SQL Server Setup was canceled before completing the operation. Try the setup process again.
   Next step for RS:              SQL Server Setup was canceled before completing the operation. Try the setup process again.
   Next step for RS_SHP:          SQL Server Setup was canceled before completing the operation. Try the setup process again.
   Next step for RS_SHPWFE:       SQL Server Setup was canceled before completing the operation. Try the setup process again.
   Next step for DQC:             SQL Server Setup was canceled before completing the operation. Try the setup process again.
   Next step for IS:              SQL Server Setup was canceled before completing the operation. Try the setup process again.
   Next step for Conn:            SQL Server Setup was canceled before completing the operation. Try the setup process again.
   Next step for Adv_SSMS:        SQL Server Setup was canceled before completing the operation. Try the setup process again.
   Next step for SDK:             SQL Server Setup was canceled before completing the operation. Try the setup process again.
   Next step for BC:              SQL Server Setup was canceled before completing the operation. Try the setup process again.
   Next step for DREPLAY_CTLR:    SQL Server Setup was canceled before completing the operation. Try the setup process again.
   Next step for DREPLAY_CLT:     SQL Server Setup was canceled before completing the operation. Try the setup process again.
   Next step for BIDS:            SQL Server Setup was canceled before completing the operation. Try the setup process again.
   Next step for SSMS:            SQL Server Setup was canceled before completing the operation. Try the setup process again.
   Next step for SNAC:            SQL Server Setup was canceled before completing the operation. Try the setup process again.
   Next step for SNAC_SDK:        SQL Server Setup was canceled before completing the operation. Try the setup process again.
   Next step for Writer:          SQL Server Setup was canceled before completing the operation. Try the setup process again.
   Next step for BOL:             SQL Server Setup was canceled before completing the operation. Try the setup process again.
   Next step for Browser:         SQL Server Setup was canceled before completing the operation. Try the setup process again.
Machine Properties:
   Machine name:                  IDCSQLTST11
   Machine processor count:       2
   OS version:                    Future Windows Version
   OS service pack:
   OS region:                     United States
   OS language:                   English (United States)
   OS architecture:               x64
   Process architecture:          64 Bit
   OS clustered:                  No
Product features discovered:
   Product              Instance             Instance ID
Feature                                  Language
Edition              Version         Clustered
Package properties:
   Description:                   Microsoft SQL Server 2012
   ProductName:                   SQL Server 2012
   Type:                          RTM
   Version:                       11
   SPLevel:                       0
   Installation location:         E:\SQL_Server_2012_StandardEdition\x64\setup\
   Installation edition:          Standard
Product Update Status:
   None discovered.
User Input Settings:
   ACTION:                        Install
   ADDCURRENTUSERASSQLADMIN:      false
   AGTSVCACCOUNT:                 NT Service\SQLSERVERAGENT
   AGTSVCPASSWORD:                <empty>
   AGTSVCSTARTUPTYPE:             Automatic
   ASBACKUPDIR:                   C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Backup
   ASCOLLATION:                   Latin1_General_CI_AS
   ASCONFIGDIR:                   C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Config
   ASDATADIR:                     C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Data
   ASLOGDIR:                      C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Log
   ASPROVIDERMSOLAP:              1
   ASSERVERMODE:                  MULTIDIMENSIONAL
   ASSVCACCOUNT:                  NT Service\MSSQLServerOLAPService
   ASSVCPASSWORD:                 <empty>
   ASSVCSTARTUPTYPE:              Manual
   ASSYSADMINACCOUNTS:            DOMAINAA\SQLADMINS
   ASTEMPDIR:                     C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Temp
   BROWSERSVCSTARTUPTYPE:         Disabled
   CLTCTLRNAME:
   CLTRESULTDIR:                  C:\Program Files (x86)\Microsoft SQL Server\DReplayClient\ResultDir
   CLTSTARTUPTYPE:                Manual
   CLTSVCACCOUNT:                 NT Service\SQL Server Distributed Replay Client
   CLTSVCPASSWORD:                <empty>
   CLTWORKINGDIR:                 C:\Program Files (x86)\Microsoft SQL Server\DReplayClient\WorkingDir
   COMMFABRICENCRYPTION:          0
   COMMFABRICNETWORKLEVEL:        0
   COMMFABRICPORT:                0
   CONFIGURATIONFILE:             E:\SQL_Server_2012_StandardEdition\ConfigurationFile.ini
   CTLRSTARTUPTYPE:               Manual
   CTLRSVCACCOUNT:                NT Service\SQL Server Distributed Replay Controller
   CTLRSVCPASSWORD:               <empty>
   CTLRUSERS:                     DOMAINAA\user12345
   ENABLERANU:                    false
   ENU:                           true
   ERRORREPORTING:                false
   FEATURES:                      SQLENGINE, REPLICATION, FULLTEXT, DQ, AS, RS, RS_SHP, RS_SHPWFE, DQC, BIDS, CONN, IS, BC, SDK, BOL, SSMS, ADV_SSMS,
DREPLAY_CTLR, DREPLAY_CLT, SNAC_SDK
   FILESTREAMLEVEL:               0
   FILESTREAMSHARENAME:           <empty>
   FTSVCACCOUNT:                  NT Service\MSSQLFDLauncher
   FTSVCPASSWORD:                 <empty>
   HELP:                          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 Service\MsDtsServer110
   ISSVCPASSWORD:                 <empty>
   ISSVCSTARTUPTYPE:              Automatic
   MATRIXCMBRICKCOMMPORT:         0
   MATRIXCMSERVERNAME:            <empty>
   MATRIXNAME:                    <empty>
   NPENABLED:                     0
   PID:                           *****
   QUIET:                         true
   QUIETSIMPLE:                   false
   ROLE:
   RSINSTALLMODE:                 DefaultNativeMode
   RSSHPINSTALLMODE:              SharePointFilesOnlyMode
   RSSVCACCOUNT:                  NT Service\ReportServer
   RSSVCPASSWORD:                 <empty>
   RSSVCSTARTUPTYPE:              Manual
   SAPWD:                         <empty>
   SECURITYMODE:                  SQL
   SQLBACKUPDIR:                  <empty>
   SQLCOLLATION:                  Latin1_General_CI_AS
   SQLSVCACCOUNT:                 NT Service\MSSQLSERVER
   SQLSVCPASSWORD:                <empty>
   SQLSVCSTARTUPTYPE:             Automatic
   SQLSYSADMINACCOUNTS:           DOMAINAA\SQLADMINS
   SQLTEMPDBDIR:                  F:\TempDB
   SQLTEMPDBLOGDIR:               <empty>
   SQLUSERDBDIR:                  E:\SQLData
   SQLUSERDBLOGDIR:               D:\SQLLog
   SQMREPORTING:                  false
   TCPENABLED:                    1
   UIMODE:                        Normal
   UpdateEnabled:                 true
   UpdateSource:                  MU
   X86:                           false
Configuration file:            C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20150109_101753\ConfigurationFile.ini
Detailed results:
   Feature:                       Database Engine Services
   Status:                        Failed: see logs for details
   Reason for failure:            Setup was canceled for the feature.
   Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature:                       SQL Server Replication
   Status:                        Failed: see logs for details
   Reason for failure:            Setup was canceled for the feature.
   Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature:                       Full-Text and Semantic Extractions for Search
   Status:                        Failed: see logs for details
   Reason for failure:            Setup was canceled for the feature.
   Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature:                       Data Quality Services
   Status:                        Failed: see logs for details
   Reason for failure:            Setup was canceled for the feature.
   Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature:                       Analysis Services
   Status:                        Failed: see logs for details
   Reason for failure:            Setup was canceled for the feature.
   Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature:                       Reporting Services - Native
   Status:                        Failed: see logs for details
   Reason for failure:            Setup was canceled for the feature.
   Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature:                       Reporting Services - SharePoint
   Status:                        Failed: see logs for details
   Reason for failure:            Setup was canceled for the feature.
   Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature:                       Reporting Services Add-in for SharePoint Products
   Status:                        Failed: see logs for details
   Reason for failure:            Setup was canceled for the feature.
   Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature:                       Data Quality Client
   Status:                        Failed: see logs for details
   Reason for failure:            Setup was canceled for the feature.
   Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature:                       Integration Services
   Status:                        Failed: see logs for details
   Reason for failure:            Setup was canceled for the feature.
   Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature:                       Client Tools Connectivity
   Status:                        Failed: see logs for details
   Reason for failure:            Setup was canceled for the feature.
   Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature:                       Management Tools - Complete
   Status:                        Failed: see logs for details
   Reason for failure:            Setup was canceled for the feature.
   Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature:                       Client Tools SDK
   Status:                        Failed: see logs for details
   Reason for failure:            Setup was canceled for the feature.
   Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature:                       Client Tools Backwards Compatibility
   Status:                        Failed: see logs for details
   Reason for failure:            Setup was canceled for the feature.
   Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature:                       Distributed Replay Controller
   Status:                        Failed: see logs for details
   Reason for failure:            Setup was canceled for the feature.
   Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature:                       Distributed Replay Client
   Status:                        Failed: see logs for details
   Reason for failure:            Setup was canceled for the feature.
   Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature:                       SQL Server Data Tools
   Status:                        Failed: see logs for details
   Reason for failure:            Setup was canceled for the feature.
   Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature:                       Management Tools - Basic
   Status:                        Failed: see logs for details
   Reason for failure:            Setup was canceled for the feature.
   Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature:                       SQL Client Connectivity
   Status:                        Failed: see logs for details
   Reason for failure:            Setup was canceled for the feature.
   Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature:                       SQL Client Connectivity SDK
   Status:                        Failed: see logs for details
   Reason for failure:            Setup was canceled for the feature.
   Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature:                       SQL Writer
   Status:                        Failed: see logs for details
   Reason for failure:            Setup was canceled for the feature.
   Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature:                       Documentation Components
   Status:                        Failed: see logs for details
   Reason for failure:            Setup was canceled for the feature.
   Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature:                       SQL Browser
   Status:                        Failed: see logs for details
   Reason for failure:            Setup was canceled for the feature.
   Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
Rules with failures:
Global rules:
Scenario specific rules:
Rules report file:               C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20150109_101753\SystemConfigurationCheck_Report.htm
Exception summary:
The following is an exception stack listing the exceptions in outermost to innermost order
Inner exceptions are being indented
Exception type: Microsoft.SqlServer.Chainer.Infrastructure.InputSettingValidationException
     Message:
         The specified directory 'C:\Program Files (x86)\Microsoft SQL Server\DReplayClient\ResultDir' for setting 'CLTRESULTDIR' does not exist.
     HResult : 0x84b40000
         FacilityCode : 1204 (4b4)
         ErrorCode : 0 (0000)
     Data:
       SQL.Setup.FailureCategory = InputSettingValidationFailure
       DisableWatson = true
     Stack:
         at Microsoft.SqlServer.Chainer.Infrastructure.InputSettingService.LogAllValidationErrorsAndThrowFirstOne(ValidationState vs)
         at Microsoft.SqlServer.Configuration.SetupExtension.ValidateFeatureSettingsAction.ExecuteAction(String actionId)
         at Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)
         at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(TextWriter statusStream, ISequencedAction actionToRun, ServiceContainer context)
     Inner exception type: Microsoft.SqlServer.Configuration.DistributedReplayExtension.DirectoryNotExistException
         Message:
                 The specified directory 'C:\Program Files (x86)\Microsoft SQL Server\DReplayClient\ResultDir' for setting 'CLTRESULTDIR' does not exist.
         HResult : 0x87d00006
                 FacilityCode : 2000 (7d0)
                 ErrorCode : 6 (0006)
         Data:
           DirectoryPath = C:\Program Files (x86)\Microsoft SQL Server\DReplayClient\ResultDir
           SettingName = CLTRESULTDIR
           WatsonData =
Microsoft.SqlServer.Configuration.DistributedReplayExtension.DirectoryNotExistException@6

Hello,
Open the configuration file with notepad, then go to the “features” variable. On the following article you will find what
means each parameter:
http://msdn.microsoft.com/en-us/library/ms144259(v=sql.110).aspx#Feature
You will also find the list of features supported by each edition on the following article:
http://msdn.microsoft.com/en-us/library/Cc645993(v=sql.110).aspx
For example, it seems you have DQ and DQC on that configuration file, please remove them with their corresponding commas.
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com
Thanks Albert that worked when I just selected the main features and excluded ones like DQ and DRC. Thing is why would the standard media allow you to install enterprise features, create a configuration file with these enterprise features and then fail?? Why
would Microsoft tease you like that? Frustrating since I spent hours on this ..

Reporting Services install on SQL 2012 SP1 instance blank

Similar Messages

Maybe you are looking for