Hi, 

I am working on a SQL Server 2008 instance where log shipping is configured for one of the databases. The secondary database is configured on the same instance for reporting purposes. 

The three log shipping jobs (LSBackup, LSCopy and LSRestore) are running every 10 mins, the LSCopy job generated this error every time; 

Error: The process cannot access the file '\\pwdsg1er \LogShipping\db_prod_20160415152002.trn' because it is being used by another process.(mscorlib) *** 

But it works on the second attempt. Do you think I should reconfigure the schedule and separate them with a little gap as the log shipping is configured on the same instance?

Please let me know your feedback. 

Thanks!

I have an instance of SQL Server 2012 Developer edition. I need to support the TLS 1.2 features available in SP2 or SP3.  I have reviewed the upgrade matrix at https://msdn.microsoft.com/en-us/library/ms143393(v=sql.110).aspx.  I am only seeing Developer editions upgrading to new Developer editions.  Ultimately I just need TLS 1.2 support, is there an upgrade available for SQL Server 2012 Developer edition?

Thanks.

Hi there,

Thanks for any link provided,

Installation of SQL Server 2014 fails on Windows 10.

The 64 bit version complains about files not found.

The 32 bit version complains about folders not found.

I’ve uninstalled and reinstalled the 64 bit version 3 times and it failed each time.

I tried the 32 bit version. Installation fails there also. I says: cannot find destination folder.

These are installation issues beyond my control. How do I solve this problem.

Thanks

I have task to implement sqlserver2008r2 sp1 with CU6, I installed succfully 2008r2 and SP1 but when i install cu6 my sql server won't come online, when i try to sqlserver from servicecs.msc i got the below said error i am getting similar error after rebuild also

Windows could not start the SQL Server (MSSQLSERVER) service on local computer
Error2: The system cannot find the file specified

Error: 17172, Severity: 16, State: 1.

SNIInitialize() failed with error 0x2.
SQL Server Audit failed to record the SERVER SHUTDOWN action.

Hello all,

I need one help. Recently one project came to my company.They are managing some sql servers.so i will access that sql servers vai RDP.

They are asking

what permission you need on the SQL servers to do you?

What passwords do you need to know?

SA’s?

Infodba?

and they are asking

Here is what we have to choose from?

 Please help any one.

thank you

we have a 2-node active-active sql 2012 cluster with 3 sql instances on one node and 2 on the other.   one specific role (instance) fails when we attempt to move it from one node to another.   after 4 retries it remains in a failed state with these two entries in the error log:

Error: 17172, Severity: 16, State: 1.
SNIInitialize() failed with error 0x2.

there is a workaround here:

https://social.msdn.microsoft.com/Forums/sqlserver/en-US/ffb71e7d-0d55-463f-98c6-f8efde1c157c/sql-server-2008r2-cu6-error?forum=sqlsetupandupgrade

...which does work for us but requires manual steps (delete the 'cluster' registry key) to be performed during failover which means there will be an outage while we perform those steps.

are there any details on the underlying cause?    and a possible fix that allows automated failover to be successful?

thanks

rob

Hi All ,

I am trying an automated install of SQL SERVER 2014 ENTERPRISE EDITION with below Features :

FEATURES=SQLENGINE,REPLICATION,FULLTEXT,DQ,AS,RS,RS_SHP,RS_SHPWFE,DQC,CONN,IS,BC,SDK,BOL,SSMS,ADV_SSMS,DREPLAY_CTLR,DREPLAY_CLT,MDS

OS detail : Windows Server 2008 R2

SQL Server : SQL SERVER 2014 ENTERPRISE EDITION 

Below are the contents of Summary.txt :

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:                    2016-04-19 04:34:35
  End time:                      2016-04-19 04:35:22
  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 SSMS:            SQL Server Setup was canceled before completing the operation. Try the setup process again.
  Next step for ComponentUpdate: 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 MDS:             SQL Server Setup was canceled before completing the operation. Try the setup process again.


Machine Properties:
  Machine name:                  DENCITS03
  Machine processor count:       1
  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  Configured
  SQL Server 2005      JDESSELOCAL          MSSQL.1                        Database Engine Services                 1033                 Express Edition      9.4.5000        No         Yes       
  SQL Server 2005      JDESSELOCAL          MSSQL.1                        SharedTools                             1033                 Express Edition      9.4.5000        No         Yes       
  SQL Server 2005                                                          Tools                                   1033                 Express Edition      9.1.2047        No         Yes       
  SQL Server 2005                                                          ToolsClient                             1033                 Express Edition      9.1.2047        No         Yes      

Package properties:
  Description:                   Microsoft SQL Server 2014 
  ProductName:                   SQL Server 2014
  Type:                          RTM
  Version:                       12
  SPLevel:                       0
  Installation location:         Z:\Downloads\en_sql_server_2014_enterprise_edition_x64_dvd_3932700\x64\setup\
  Installation edition:          Enterprise

Product Update Status:
  None discovered.

User Input Settings:
  ACTION:                        Install
  ADDCURRENTUSERASSQLADMIN:      false
  AGTSVCACCOUNT:                 NT Service\SQLSERVERAGENT
  AGTSVCPASSWORD:                <empty>
  AGTSVCSTARTUPTYPE:             Manual
  ASBACKUPDIR:                   C:\Program Files\Microsoft SQL Server\MSAS12.MSSQLSERVER\OLAP\Backup
  ASCOLLATION:                   Latin1_General_CI_AS
  ASCONFIGDIR:                   C:\Program Files\Microsoft SQL Server\MSAS12.MSSQLSERVER\OLAP\Config
  ASDATADIR:                     C:\Program Files\Microsoft SQL Server\MSAS12.MSSQLSERVER\OLAP\Data
  ASLOGDIR:                      C:\Program Files\Microsoft SQL Server\MSAS12.MSSQLSERVER\OLAP\Log
  ASPROVIDERMSOLAP:              1
  ASSERVERMODE:                  MULTIDIMENSIONAL
  ASSVCACCOUNT:                  NT Service\MSSQLServerOLAPService
  ASSVCPASSWORD:                 <empty>
  ASSVCSTARTUPTYPE:              Automatic
  ASSYSADMINACCOUNTS:            DENCITS03\ITS03
  ASTEMPDIR:                     C:\Program Files\Microsoft SQL Server\MSAS12.MSSQLSERVER\OLAP\Temp
  BROWSERSVCSTARTUPTYPE:         Automatic
  CLTCTLRNAME:                   SQL2014Controller
  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:             C:\ConfigurationFile.ini
  CTLRSTARTUPTYPE:               Manual
  CTLRSVCACCOUNT:                NT Service\SQL Server Distributed Replay Controller
  CTLRSVCPASSWORD:               <empty>
  CTLRUSERS:                     DENCITS03\ITS03
  ENABLERANU:                    false
  ENU:                           true
  ERRORREPORTING:                false
  FEATURES:                      SQLENGINE, REPLICATION, FULLTEXT, DQ, AS, RS, RS_SHP, RS_SHPWFE, DQC, CONN, IS, BC, SDK, BOL, SSMS, ADV_SSMS, DREPLAY_CTLR, DREPLAY_CLT, MDS
  FILESTREAMLEVEL:               3
  FILESTREAMSHARENAME:           MSSQLSERVER
  FTSVCACCOUNT:                  NT Service\MSSQLFDLauncher
  FTSVCPASSWORD:                 <empty>
  HELP:                          false
  IACCEPTSQLSERVERLICENSETERMS:  true
  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\MsDtsServer120
  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:              Automatic
  SAPWD:                         <empty>
  SECURITYMODE:                  SQL
  SQLBACKUPDIR:                  <empty>
  SQLCOLLATION:                  SQL_Latin1_General_CP1_CI_AS
  SQLSVCACCOUNT:                 NT Service\MSSQLSERVER
  SQLSVCPASSWORD:                <empty>
  SQLSVCSTARTUPTYPE:             Automatic
  SQLSYSADMINACCOUNTS:           DENCITS03\ITS03
  SQLTEMPDBDIR:                  <empty>
  SQLTEMPDBLOGDIR:               <empty>
  SQLUSERDBDIR:                  <empty>
  SQLUSERDBLOGDIR:               <empty>
  SQMREPORTING:                  false
  TCPENABLED:                    1
  UIMODE:                        Normal
  UpdateEnabled:                 true
  UpdateSource:                  MU
  USEMICROSOFTUPDATE:            false
  X86:                           false

  Configuration file:            C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20160419_043435\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:                       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:                       Setup Support Files
  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:                       Master Data 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.

Rules with failures:

Global rules:

Scenario specific rules:

Rules report file:               C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20160419_043435\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.<>c__DisplayClasse.<ExecuteActionWithRetryHelper>b__b()
        at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(ActionWorker workerDelegate)
    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

Below are the contents of ConfigurationFile.ini :

;SQL Server 2014 Configuration File
[OPTIONS]

; Required to acknowledge acceptance of the license terms.
IACCEPTSQLSERVERLICENSETERMS="True"

; Specifies a Setup work flow, like INSTALL, UNINSTALL, or UPGRADE. This is a required parameter. 

ACTION="Install"

; Use the /ENU parameter to install the English version of SQL Server on your localized Windows operating system. 

ENU="True"

; Setup will not display any user interface. 

QUIET="True"

; Setup will display progress only, without any user interaction. 

QUIETSIMPLE="False"

; Specify whether SQL Server Setup should discover and include product updates. The valid values are True and False or 1 and 0. By default SQL Server Setup will include updates that are found. 

UpdateEnabled="True"

; Specify if errors can be reported to Microsoft to improve future SQL Server releases. Specify 1 or True to enable and 0 or False to disable this feature. 

ERRORREPORTING="False"

; If this parameter is provided, then this computer will use Microsoft Update to check for updates. 

USEMICROSOFTUPDATE="False"

; Specifies features to install, uninstall, or upgrade. The list of top-level features include SQL, AS, RS, IS, MDS, and Tools. The SQL feature will install the Database Engine, Replication, Full-Text, and Data Quality Services (DQS) server. The Tools feature will install Management Tools, Books online components, SQL Server Data Tools, and other shared components. 

FEATURES=SQLENGINE,REPLICATION,FULLTEXT,DQ,AS,RS,RS_SHP,RS_SHPWFE,DQC,CONN,IS,BC,SDK,BOL,SSMS,ADV_SSMS,DREPLAY_CTLR,DREPLAY_CLT,MDS

; Specify the location where SQL Server Setup will obtain product updates. The valid values are "MU" to search Microsoft Update, a valid folder path, a relative path such as .\MyUpdates or a UNC share. By default SQL Server Setup will search Microsoft Update or a Windows Update service through the Window Server Update Services. 

UpdateSource="MU"

; Displays the command line parameters usage 

HELP="False"

; Specifies that the detailed Setup log should be piped to the console. 

INDICATEPROGRESS="False"

; Specifies that Setup should install into WOW64. This command line argument is not supported on an IA64 or a 32-bit system. 

X86="False"

; Specify the root installation directory for shared components.  This directory remains unchanged after shared components are already installed. 

INSTALLSHAREDDIR="C:\Program Files\Microsoft SQL Server"

; Specify the root installation directory for the WOW64 shared components.  This directory remains unchanged after WOW64 shared components are already installed. 

INSTALLSHAREDWOWDIR="C:\Program Files (x86)\Microsoft SQL Server"

; Specify a default or named instance. MSSQLSERVER is the default instance for non-Express editions and SQLExpress for Express editions. This parameter is required when installing the SQL Server Database Engine (SQL), Analysis Services (AS), or Reporting Services (RS). 

INSTANCENAME="MSSQLSERVER"

; Specify that SQL Server feature usage data can be collected and sent to Microsoft. Specify 1 or True to enable and 0 or False to disable this feature. 

SQMREPORTING="False"

; Specify the Instance ID for the SQL Server features you have specified. SQL Server directory structure, registry structure, and service names will incorporate the instance ID of the SQL Server instance. 

INSTANCEID="MSSQLSERVER"

; The computer name that the client communicates with for the Distributed Replay Controller service. 

CLTCTLRNAME="SQL2014Controller"

; The Windows account(s) used to grant permission to the Distributed Replay Controller service. 

CTLRUSERS="Domain\user"

; The account used by the Distributed Replay Controller service. 

CTLRSVCACCOUNT="NT Service\SQL Server Distributed Replay Controller"

; The startup type for the Distributed Replay Controller service. 

CTLRSTARTUPTYPE="Manual"

; The account used by the Distributed Replay Client service. 

CLTSVCACCOUNT="NT Service\SQL Server Distributed Replay Client"

; The startup type for the Distributed Replay Client service. 

CLTSTARTUPTYPE="Manual"

; The result directory for the Distributed Replay Client service. 

CLTRESULTDIR="C:\Program Files (x86)\Microsoft SQL Server\DReplayClient\ResultDir"

; The working directory for the Distributed Replay Client service. 

CLTWORKINGDIR="C:\Program Files (x86)\Microsoft SQL Server\DReplayClient\WorkingDir"

; RSInputSettings_RSInstallMode_Description 

RSINSTALLMODE="DefaultNativeMode"

; RSInputSettings_RSInstallMode_Description 

RSSHPINSTALLMODE="SharePointFilesOnlyMode"

; Specify the installation directory. 

INSTANCEDIR="C:\Program Files\Microsoft SQL Server"

; Agent account name 

AGTSVCACCOUNT="NT Service\SQLSERVERAGENT"

; Auto-start service after installation.  

AGTSVCSTARTUPTYPE="Manual"

; Startup type for Integration Services. 

ISSVCSTARTUPTYPE="Automatic"

; Account for Integration Services: Domain\User or system account. 

ISSVCACCOUNT="NT Service\MsDtsServer120"

; The name of the account that the Analysis Services service runs under. 

ASSVCACCOUNT="NT Service\MSSQLServerOLAPService"

; Controls the service startup type setting after the service has been created. 

ASSVCSTARTUPTYPE="Automatic"

; The collation to be used by Analysis Services. 

ASCOLLATION="Latin1_General_CI_AS"

; The location for the Analysis Services data files. 

ASDATADIR="C:\Program Files\Microsoft SQL Server\MSAS12.MSSQLSERVER\OLAP\Data"

; The location for the Analysis Services log files. 

ASLOGDIR="C:\Program Files\Microsoft SQL Server\MSAS12.MSSQLSERVER\OLAP\Log"

; The location for the Analysis Services backup files. 

ASBACKUPDIR="C:\Program Files\Microsoft SQL Server\MSAS12.MSSQLSERVER\OLAP\Backup"

; The location for the Analysis Services temporary files. 

ASTEMPDIR="C:\Program Files\Microsoft SQL Server\MSAS12.MSSQLSERVER\OLAP\Temp"

; The location for the Analysis Services configuration files. 

ASCONFIGDIR="C:\Program Files\Microsoft SQL Server\MSAS12.MSSQLSERVER\OLAP\Config"

; Specifies whether or not the MSOLAP provider is allowed to run in process. 

ASPROVIDERMSOLAP="1"

; Specifies the list of administrator accounts that need to be provisioned. 

ASSYSADMINACCOUNTS="Domain\user"

; Specifies the server mode of the Analysis Services instance. Valid values are MULTIDIMENSIONAL and TABULAR. The default value is MULTIDIMENSIONAL. 

ASSERVERMODE="MULTIDIMENSIONAL"

; CM brick TCP communication port 

COMMFABRICPORT="0"

; How matrix will use private networks 

COMMFABRICNETWORKLEVEL="0"

; How inter brick communication will be protected 

COMMFABRICENCRYPTION="0"

; TCP port used by the CM brick 

MATRIXCMBRICKCOMMPORT="0"

; Startup type for the SQL Server service. 

SQLSVCSTARTUPTYPE="Automatic"

; Level to enable FILESTREAM feature at (0, 1, 2 or 3). 

FILESTREAMLEVEL="3"

; Name of Windows share to be created for FILESTREAM File I/O. 

FILESTREAMSHARENAME="MSSQLSERVER"

; Set to "1" to enable RANU for SQL Server Express. 

ENABLERANU="False"

; Specifies a Windows collation or an SQL collation to use for the Database Engine. 

SQLCOLLATION="SQL_Latin1_General_CP1_CI_AS"

; Account for SQL Server service: Domain\User or system account. 

SQLSVCACCOUNT="NT Service\MSSQLSERVER"

; Windows account(s) to provision as SQL Server system administrators. 

SQLSYSADMINACCOUNTS="Domain\User"

; The default is Windows Authentication. Use "SQL" for Mixed Mode Authentication. 

SECURITYMODE="SQL"

; Specify 0 to disable or 1 to enable the TCP/IP protocol. 

TCPENABLED="1"

; Specify 0 to disable or 1 to enable the Named Pipes protocol. 

NPENABLED="0"

; Startup type for Browser Service. 

BROWSERSVCSTARTUPTYPE="Automatic"

; Specifies which account the report server NT service should execute under.  When omitted or when the value is empty string, the default built-in account for the current operating system.
; The username part of RSSVCACCOUNT is a maximum of 20 characters long and
; The domain part of RSSVCACCOUNT is a maximum of 254 characters long. 

RSSVCACCOUNT="NT Service\ReportServer"

; Specifies how the startup mode of the report server NT service.  When 
; Manual - Service startup is manual mode (default).
; Automatic - Service startup is automatic mode.
; Disabled - Service is disabled 

RSSVCSTARTUPTYPE="Automatic"

; Add description of input argument FTSVCACCOUNT 

FTSVCACCOUNT="NT Service\MSSQLFDLauncher"

Please guide me where i am going wrong in this whole process.

Thanks...

chandarekha

This may be a dumb question, but I'm no SQL guy and I did a fair amount of searching without an answer to this.

Got a client who is running SQL 2008 Standard for use with GoldMine, and I'm installing a replacement server. I could just load 2008 on the new server, but it would be nice to at least jump up to 2012. My client doesn't want to drop the RIDICULOUS amount of money for SQL 2012 Standard.

So, can I "upgrade" SQL 2008 Standard database to SQL 2012 Express? (put upgrade in quotes cause downgrading from standard to express, but upgrading from 2008 to 2012)

Hi,

I have a Odd Problem.My customer want to update/Patch on Windows internal database for Windows server 2012

But I am not getting any Patches Or Kb related to that.

Can any one help me Out How can I Update/patch Internals Database for Windows server 2012?

Is there any separate Kb is available for that?

What ever patch I am getting is all related for 2005 version SP4.

https://www.microsoft.com/en-in/download/details.aspx?id=16954

Please Help me to find out Something for Windows server 2012.

Thanks 

Suman

Hello, my name is Rosyid. I have a problem during installation of SQL Server on my Server. The SQL Server can't install because the SQL Server Browser service can't start. I tried to install following this article https://blogs.technet.microsoft.com/mdegre/2010/02/22/setup-sql-server-2008-service-sqlbrowser-start-request-failed/

I got error "SQL Server Setup has encountered the following error: Object reference not set to an instance of an object.."

Any help would be gratefully accepted.

Regards,

Rosyid

I have SQL Server 2008 R2 SP3, I was trying to apply 3045316 MS15-058: Description of the security update for SQL Server 2008 R2 Service Pack 3 GDR: July 14, 2015 build 10.53.6220.0. It fails with the error message.

<<The patch installer has failed to update the shared features. To determine the reason for failure, review the log files.>>

Overall summary:

Faran

Hello,
The present architecture is that there is one sql server 2008 R2 (ServerA ) which has the DEV database as well as the Prod database.
There are SSIS packages that run every 30 minutes or so...

1-
Do you think it is a good idea to have one server i.e. ServerD for Dev, another one i.e. ServerU for UAT and leave the current one (ServerA) as is but remove the Dev database.

2-
Should the SSIS/ETL be done on the same server as the production i.e. ServerA or should that be a separate server too? i.e. ServerS?

3-
There is also SSAS. should they be on another server?

Thanks

Hello,

I uninstalled and reinstalled everything but get the same error message, the MSDN Version has a prepared key and I installed not a free version, there is KB 971268.  After complete reinstall the SQL Server is running, but the management Studio shows up the error. It is possible to connect to the new installed instance by using Visual Studio SQL Server-Object Explorer.

Hi All,

I am installing Sql Server 2014 Developer edition by powershell dsc and getting below log file with error. I have given path of the sql setup.exe and ConfigurationFile.ini file in my code.

=            

$sqlInstances=gwmiwin32_service-computerNameNodeName| ? { $_.Name-match"mssqlserver*"-and$_.PathName-match"sqlservr.exe"} | %{$_.Caption }               

$res=$sqlInstances-ne$null-and$sqlInstances-gt0               

$vals=@{Installed=$res; InstanceCount =$sqlInstances.count}               

$vals           

=            

Write-Verbose"Drive letter for iso is: $setupDriveLetter"                                

# run the installer using the ini file               

$cmd="C:\Installs\SQL2014Developer64bit\setup.exe /ConfigurationFile=C:\Installs\SQL2014Developer64bit\ConfigurationFile.ini /SQLSVCPASSWORD=syntel@123 /AGTSVCPASSWORD=syntel@123 /SAPWD=syntel@123"

Write-Verbose"Running SQL Install - check %programfiles%\Microsoft SQL Server\120\Setup Bootstrap\Log\ for logs..."               

Invoke-Expression$cmd|Write-Verbose

=           

$sqlInstances=gwmiwin32_service-computerNameNodeName| ? {$_.Name-match"mssqlserver*"-and$_.PathName-match"sqlservr.exe"} | %{$_.Caption }               

$res=$sqlInstances-ne$null-and$sqlInstances-gt0               

if($res)

Write-Verbose"SQL Server is already installed"               

else

Write-Verbose"SQL Server is not installed"               

$res           

Error part of the log is given below.

Please suggest, how can I fix it.

(01) 2016-04-25 02:24:15 Slp: Error: Action "Microsoft.SqlServer.Configuration.UIExtension.StartAction" threw an exception during execution.
(01) 2016-04-25 02:24:25 Slp: Microsoft.SqlServer.Setup.Chainer.Workflow.ActionExecutionException: Thread was being aborted. ---> System.Threading.ThreadAbortException: Thread was being aborted.
(01) 2016-04-25 02:24:25 Slp:    at System.Threading.WaitHandle.WaitOneNative(SafeWaitHandle waitHandle, UInt32 millisecondsTimeout, Boolean hasThreadAffinity, Boolean exitContext)
(01) 2016-04-25 02:24:25 Slp:    at System.Threading.WaitHandle.WaitOne(Int64 timeout, Boolean exitContext)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Configuration.UIExtension.ShowActiveObjectTemplate.Show(String moniker)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Configuration.UIExtension.UserInterfaceService.Start(String moniker, Predicate`1 pageFilter)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Configuration.UIExtension.StartAction.ExecuteAction(String actionId)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.<>c__DisplayClasse.<ExecuteActionWithRetryHelper>b__b()
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(ActionWorker workerDelegate)
(01) 2016-04-25 02:24:25 Slp:    --- End of inner exception stack trace ---
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(ActionWorker workerDelegate)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionWithRetryHelper(WorkflowObject metaDb, ActionKey action, ActionMetadata actionMetadata, TextWriter statusStream)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.InvokeAction(WorkflowObject metabase, TextWriter statusStream)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.PendingActions.InvokeActions(WorkflowObject metaDb, TextWriter loggingStream)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionEngine.RunActionQueue()
(01) 2016-04-25 02:24:25 Slp: Error: Action "Microsoft.SqlServer.Configuration.BootstrapExtension.ExecuteWorkflowAction" threw an exception during execution.
(01) 2016-04-25 02:24:25 Slp: Microsoft.SqlServer.Setup.Chainer.Workflow.ActionExecutionException: Thread was being aborted. ---> System.Threading.ThreadAbortException: Thread was being aborted.
(01) 2016-04-25 02:24:25 Slp:    at System.Threading.WaitHandle.WaitOneNative(SafeWaitHandle waitHandle, UInt32 millisecondsTimeout, Boolean hasThreadAffinity, Boolean exitContext)
(01) 2016-04-25 02:24:25 Slp:    at System.Threading.WaitHandle.WaitOne(Int64 timeout, Boolean exitContext)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Configuration.UIExtension.ShowActiveObjectTemplate.Show(String moniker)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Configuration.UIExtension.UserInterfaceService.Start(String moniker, Predicate`1 pageFilter)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Configuration.UIExtension.StartAction.ExecuteAction(String actionId)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.<>c__DisplayClasse.<ExecuteActionWithRetryHelper>b__b()
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(ActionWorker workerDelegate)
(01) 2016-04-25 02:24:25 Slp:    --- End of inner exception stack trace ---
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(ActionWorker workerDelegate)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionWithRetryHelper(WorkflowObject metaDb, ActionKey action, ActionMetadata actionMetadata, TextWriter statusStream)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.InvokeAction(WorkflowObject metabase, TextWriter statusStream)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.PendingActions.InvokeActions(WorkflowObject metaDb, TextWriter loggingStream)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionEngine.RunActionQueue()
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.Workflow.RunWorkflow(WorkflowObject workflowObject, HandleInternalException exceptionHandler)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Configuration.BootstrapExtension.ExecuteWorkflowAction.ExecuteAction(String actionId)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.<>c__DisplayClasse.<ExecuteActionWithRetryHelper>b__b()
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(ActionWorker workerDelegate)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionWithRetryHelper(WorkflowObject metaDb, ActionKey action, ActionMetadata actionMetadata, TextWriter statusStream)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.InvokeAction(WorkflowObject metabase, TextWriter statusStream)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.PendingActions.InvokeActions(WorkflowObject metaDb, TextWriter loggingStream)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionEngine.RunActionQueue()
(01) 2016-04-25 02:24:25 Slp: Error: Action "Microsoft.SqlServer.Configuration.BootstrapExtension.ExecuteWorkflowAction" threw an exception during execution.
(01) 2016-04-25 02:24:25 Slp: Microsoft.SqlServer.Setup.Chainer.Workflow.ActionExecutionException: Thread was being aborted. ---> System.Threading.ThreadAbortException: Thread was being aborted.
(01) 2016-04-25 02:24:25 Slp:    at System.Threading.WaitHandle.WaitOneNative(SafeWaitHandle waitHandle, UInt32 millisecondsTimeout, Boolean hasThreadAffinity, Boolean exitContext)
(01) 2016-04-25 02:24:25 Slp:    at System.Threading.WaitHandle.WaitOne(Int64 timeout, Boolean exitContext)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Configuration.UIExtension.ShowActiveObjectTemplate.Show(String moniker)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Configuration.UIExtension.UserInterfaceService.Start(String moniker, Predicate`1 pageFilter)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Configuration.UIExtension.StartAction.ExecuteAction(String actionId)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.<>c__DisplayClasse.<ExecuteActionWithRetryHelper>b__b()
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(ActionWorker workerDelegate)
(01) 2016-04-25 02:24:25 Slp:    --- End of inner exception stack trace ---
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(ActionWorker workerDelegate)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionWithRetryHelper(WorkflowObject metaDb, ActionKey action, ActionMetadata actionMetadata, TextWriter statusStream)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.InvokeAction(WorkflowObject metabase, TextWriter statusStream)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.PendingActions.InvokeActions(WorkflowObject metaDb, TextWriter loggingStream)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionEngine.RunActionQueue()
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.Workflow.RunWorkflow(WorkflowObject workflowObject, HandleInternalException exceptionHandler)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Configuration.BootstrapExtension.ExecuteWorkflowAction.ExecuteAction(String actionId)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.<>c__DisplayClasse.<ExecuteActionWithRetryHelper>b__b()
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(ActionWorker workerDelegate)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionWithRetryHelper(WorkflowObject metaDb, ActionKey action, ActionMetadata actionMetadata, TextWriter statusStream)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.InvokeAction(WorkflowObject metabase, TextWriter statusStream)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.PendingActions.InvokeActions(WorkflowObject metaDb, TextWriter loggingStream)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionEngine.RunActionQueue()
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.Workflow.RunWorkflow(WorkflowObject workflowObject, HandleInternalException exceptionHandler)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Configuration.BootstrapExtension.ExecuteWorkflowAction.ExecuteAction(String actionId)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.<>c__DisplayClasse.<ExecuteActionWithRetryHelper>b__b()
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(ActionWorker workerDelegate)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionWithRetryHelper(WorkflowObject metaDb, ActionKey action, ActionMetadata actionMetadata, TextWriter statusStream)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.InvokeAction(WorkflowObject metabase, TextWriter statusStream)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.PendingActions.InvokeActions(WorkflowObject metaDb, TextWriter loggingStream)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionEngine.RunActionQueue()
(01) 2016-04-25 02:24:25 Slp: Error: Action "Microsoft.SqlServer.Configuration.BootstrapExtension.ExecuteWorkflowAction" threw an exception during execution.
(01) 2016-04-25 02:24:25 Slp: Microsoft.SqlServer.Setup.Chainer.Workflow.ActionExecutionException: Thread was being aborted. ---> System.Threading.ThreadAbortException: Thread was being aborted.
(01) 2016-04-25 02:24:25 Slp:    at System.Threading.WaitHandle.WaitOneNative(SafeWaitHandle waitHandle, UInt32 millisecondsTimeout, Boolean hasThreadAffinity, Boolean exitContext)
(01) 2016-04-25 02:24:25 Slp:    at System.Threading.WaitHandle.WaitOne(Int64 timeout, Boolean exitContext)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Configuration.UIExtension.ShowActiveObjectTemplate.Show(String moniker)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Configuration.UIExtension.UserInterfaceService.Start(String moniker, Predicate`1 pageFilter)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Configuration.UIExtension.StartAction.ExecuteAction(String actionId)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.<>c__DisplayClasse.<ExecuteActionWithRetryHelper>b__b()
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(ActionWorker workerDelegate)
(01) 2016-04-25 02:24:25 Slp:    --- End of inner exception stack trace ---
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(ActionWorker workerDelegate)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionWithRetryHelper(WorkflowObject metaDb, ActionKey action, ActionMetadata actionMetadata, TextWriter statusStream)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.InvokeAction(WorkflowObject metabase, TextWriter statusStream)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.PendingActions.InvokeActions(WorkflowObject metaDb, TextWriter loggingStream)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionEngine.RunActionQueue()
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.Workflow.RunWorkflow(WorkflowObject workflowObject, HandleInternalException exceptionHandler)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Configuration.BootstrapExtension.ExecuteWorkflowAction.ExecuteAction(String actionId)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.<>c__DisplayClasse.<ExecuteActionWithRetryHelper>b__b()
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(ActionWorker workerDelegate)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionWithRetryHelper(WorkflowObject metaDb, ActionKey action, ActionMetadata actionMetadata, TextWriter statusStream)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.InvokeAction(WorkflowObject metabase, TextWriter statusStream)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.PendingActions.InvokeActions(WorkflowObject metaDb, TextWriter loggingStream)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionEngine.RunActionQueue()
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.Workflow.RunWorkflow(WorkflowObject workflowObject, HandleInternalException exceptionHandler)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Configuration.BootstrapExtension.ExecuteWorkflowAction.ExecuteAction(String actionId)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.<>c__DisplayClasse.<ExecuteActionWithRetryHelper>b__b()
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(ActionWorker workerDelegate)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionWithRetryHelper(WorkflowObject metaDb, ActionKey action, ActionMetadata actionMetadata, TextWriter statusStream)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.InvokeAction(WorkflowObject metabase, TextWriter statusStream)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.PendingActions.InvokeActions(WorkflowObject metaDb, TextWriter loggingStream)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionEngine.RunActionQueue()
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.Workflow.RunWorkflow(WorkflowObject workflowObject, HandleInternalException exceptionHandler)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Configuration.BootstrapExtension.ExecuteWorkflowAction.ExecuteAction(String actionId)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.<>c__DisplayClasse.<ExecuteActionWithRetryHelper>b__b()
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(ActionWorker workerDelegate)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionWithRetryHelper(WorkflowObject metaDb, ActionKey action, ActionMetadata actionMetadata, TextWriter statusStream)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.InvokeAction(WorkflowObject metabase, TextWriter statusStream)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.PendingActions.InvokeActions(WorkflowObject metaDb, TextWriter loggingStream)
(01) 2016-04-25 02:25:11 Slp: Received request to add the following file to Watson reporting: C:\windows\TEMP\tmp72C9.tmp
(07) 2016-04-25 02:25:11 Slp: Search for updates completed as 'Succeeded', number of updates found: 0
(01) 2016-04-25 02:25:11 Slp: The following is an exception stack listing the exceptions in outermost to innermost order
(01) 2016-04-25 02:25:11 Slp: Inner exceptions are being indented
(01) 2016-04-25 02:25:11 Slp:
(01) 2016-04-25 02:25:11 Slp: Exception type: System.InvalidOperationException
(01) 2016-04-25 02:25:11 Slp:     Message:
(01) 2016-04-25 02:25:11 Slp:         Showing a modal dialog box or form when the application is not running in UserInteractive mode is not a valid operation. Specify the ServiceNotification or DefaultDesktopOnly style to display a notification from a service application.
(06) 2016-04-25 02:25:11 Slp:
(06) 2016-04-25 02:25:11 Slp: Microsoft Update Details:
(06) 2016-04-25 02:25:11 Slp:   Category ID searched on Microsoft Update:          892C0584-8B03-428f-9A74-224FCD6887C0
(06) 2016-04-25 02:25:11 Slp:   Major version of the Windows Update Agent:         8
(06) 2016-04-25 02:25:11 Slp:   Minor version of the Windows Update Agent:         0
(06) 2016-04-25 02:25:11 Slp:   Version of Wuapi.dll:                              7.9.9600.18235
(06) 2016-04-25 02:25:11 Slp:
(06) 2016-04-25 02:25:11 Slp: Completed Action: SearchUpdatesAction, returned True
(01) 2016-04-25 02:25:11 Slp:     HResult : 0x80131509
(01) 2016-04-25 02:25:12 Slp:     Stack:
(01) 2016-04-25 02:25:12 Slp:         at System.Windows.Forms.Form.ShowDialog(IWin32Window owner)
(01) 2016-04-25 02:25:12 Slp:         at Microsoft.SqlServer.Configuration.UIExtension.ShowWizard.ShowUserInterface()
(01) 2016-04-25 02:25:12 Slp:         at Microsoft.SqlServer.Configuration.UIExtension.ShowActiveObjectTemplate.ThreadStart(Object obj)
(01) 2016-04-25 02:25:27 Slp: SQM Service: Sqm does not have active session.

Thanks

Uttam

Thanks UK

I am new to Sql Server. I have downloaded Sql server 2014 Sp1 & Cumulative Update Package 6 for SQL Server 2014 SP1(KB3144524). Just want to understand how to patch CU6. I did not initiate the sql server 2014 Sp1 installation.

Thanks & regards

Anurag Jain

Hello.
The company uses sql server 2008 R2 with several databases, ssis packages, etc. We are in the process of setting up a Dev server which we do not have yet...
Question:
Should we set-up the Dev box with sql server 2008 R2 first and then test the Dev environment i.e. point applications to Dev for testing, etc. or should we install sql server 2014 on the Dev server first or upgrade prod to sql server 2014 first?

What do you suggest please?

Thanks