Hi,

our setup: 2 node failover cluster instance using clustered shared volumes.

Long story short, trying to get SCCM to work in our environment. SCCM doesn't support SQL CSV! >.<

Is it possible to create a separate failover cluster instance just for SCCM using the traditional way of LUNs (1 for data (D:\), 1 for logs (E:\)) in our current environment already with CSV? If so, please provide some guidance as I've already tried and it always fail at this point:

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

TITLE: Microsoft SQL Server 2014 Setup
------------------------------

The following error has occurred:

The cluster resource 'SQL Server (instanceSQLSCCM)' could not be brought online due to an error bringing the dependency resource 'SQL Network Name (vcoSQLSCCM)' online.  Refer to the Cluster Events in the Failover Cluster Manager for more information.

Click 'Retry' to retry the failed action, or click 'Cancel' to cancel this action and continue setup.

For help, click: http://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft%20SQL%20Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.5579.0&EvtType=0xE8049925%25400x42B4DED7

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

I've also already tried pre-staging the VCO as described here:

https://blogs.msdn.microsoft.com/psssql/2013/09/30/error-during-installation-of-an-sql-server-failover-cluster-instance/

Also, permission is not an issue as I've already created several other VCOs, but within the CSV, without issues.

Hi,

I have to install SQL Server 2017 in high availability for BI purpose. please guide me what consideration and configuration should i keep so that SQL Server best for BI applications.

Thanks.

iffi

After installing SSMS on a fully updated Windows 10 64 bit laptop the UI is partially missing / invisible.

This is what happens when I choose to 'select top 1000 rows' from a table. It appears the rest of the interface is available as hovering over it displays tooltips (see 'new query' in the screenshot):

Any ideas on how to solve this issue? Thanks in advance!

Regards,

Martin

Hello everybody!

I'm needing a solution to integrate a database to a VS 2013 App in the final user machine.

Some background information:

I've built an app that has the clients, products, etc of a business, I used SQL Server 2014 Express which I installed manually on target computer, a common user woulnd't be able but since I work there, there really wasn't any problem.

But these months, an idea appeared, and it was to resell that App to other businesses, the problem is that installing SQL Server 2014 (or any version for that matter), is something that a common user will not know, and doesn't need to know, but also, I don't want to go to each business and install it manually.

I'm using InstallAware for building the installer, I need a database that can be added to the setup that InstallAware builds, or at least something easy to install for a common user.

I hope that what I wrote is clear.

Thank you!

We have upgraded our sql server 2012 instances to service pack 4 and the meltdown patch 7462.

All seems well except for some reporting services instances We get an issue with report builder. The issue is present with the patch 7462 but goes away when we uninstall the patch 7462 (running at sp4)

We are reluctant to uninstall the patch, but the facility is required on the live system. Any help is appreciated

ERROR SUMMARY
 Below is a summary of the errors, details of these errors are listed later in the log.
 * Activation of <url> resulted in exception. Following failure messages were detected:
  + File, interop.shdocvw.dll, has a different computed hash than specified in manifest.

ERROR DETAILS
 Following errors were detected during this operation.
 * [02/02/2018 09:11:17] System.Deployment.Application.InvalidDeploymentException (HashValidation)
  - File, interop.shdocvw.dll, has a different computed hash than specified in manifest.
  - Source: System.Deployment
  - Stack trace:
   at System.Deployment.Application.ComponentVerifier.VerifyFileHash(String filePath, Hash hash)
   at System.Deployment.Application.ComponentVerifier.VerifyFileHash(String filePath, HashCollection hashCollection)
   at System.Deployment.Application.ComponentVerifier.FileComponent.Verify()
   at System.Deployment.Application.ComponentVerifier.VerifyComponents()
   at System.Deployment.Application.DownloadManager.DownloadDependencies(SubscriptionState subState, AssemblyManifest deployManifest, AssemblyManifest appManifest, Uri sourceUriBase, String targetDirectory, String group, IDownloadNotification notification, DownloadOptions options)
   at System.Deployment.Application.ApplicationActivator.DownloadApplication(SubscriptionState subState, ActivationDescription actDesc, Int64 transactionId, TempDirectory& downloadTemp)
   at System.Deployment.Application.ApplicationActivator.InstallApplication(SubscriptionState& subState, ActivationDescription actDesc)
   at System.Deployment.Application.ApplicationActivator.PerformDeploymentActivation(Uri activationUri, Boolean isShortcut, String textualSubId, String deploymentProviderUrlFromExtension, BrowserSettings browserSettings, String& errorPageUrl, Uri& deploymentUri)
   at System.Deployment.Application.ApplicationActivator.PerformDeploymentActivationWithRetry(Uri activationUri, Boolean isShortcut, String textualSubId, String deploymentProviderUrlFromExtension, BrowserSettings browserSettings, String& errorPageUrl)
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Deployment.Application.ApplicationActivator.PerformDeploymentActivationWithRetry(Uri activationUri, Boolean isShortcut, String textualSubId, String deploymentProviderUrlFromExtension, BrowserSettings browserSettings, String& errorPageUrl)
   at System.Deployment.Application.ApplicationActivator.ActivateDeploymentWorker(Object state)

COMPONENT STORE TRANSACTION DETAILS
 No transaction information is available

I cannot instalation SQL Server 2017 Express on Windows 10, and this summary log

Overall summary:
  Final result:                  Failed: see details below
  Exit code (Decimal):           -2068052377
  Start time:                    2018-07-03 12:26:37
  End time:                      2018-07-03 13:14:59
  Requested action:              Install

Setup completed with required actions for features.
Troubleshooting information for those features:
  Next step for SQLEngine:       Use the following information to resolve the error, and then try the setup process again.
  Next step for Replication:     Use the following information to resolve the error, and then try the setup process again.


Machine Properties:
  Machine name:                  DESKTOP-M4HSG00
  Machine processor count:       2
  OS version:                    Microsoft Windows 10 Pro (10.0.17134)
  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  Configured

Package properties:
  Description:                   Microsoft SQL Server 2017
  ProductName:                   SQL Server 2017
  Type:                          RTM
  Version:                       14
  SPLevel:                       0
  Installation location:         C:\Users\Fadel Muhammad Aslam\Documents\SQLEXPR_x64_ENU\x64\setup\
  Installation edition:          Express

Product Update Status:
  None discovered.

User Input Settings:
  ACTION:                        Install
  ADDCURRENTUSERASSQLADMIN:      true
  AGTSVCACCOUNT:                 NT AUTHORITY\NETWORK SERVICE
  AGTSVCPASSWORD:                *****
  AGTSVCSTARTUPTYPE:             Disabled
  ASBACKUPDIR:                   Backup
  ASCOLLATION:                   Latin1_General_CI_AS
  ASCONFIGDIR:                   Config
  ASDATADIR:                     Data
  ASLOGDIR:                      Log
  ASPROVIDERMSOLAP:              1
  ASSERVERMODE:                  TABULAR
  ASSVCACCOUNT:                  <empty>
  ASSVCPASSWORD:                 <empty>
  ASSVCSTARTUPTYPE:              Automatic
  ASSYSADMINACCOUNTS:            <empty>
  ASTELSVCACCT:                  <empty>
  ASTELSVCPASSWORD:              <empty>
  ASTELSVCSTARTUPTYPE:           0
  ASTEMPDIR:                     Temp
  BROWSERSVCSTARTUPTYPE:         Disabled
  CLTCTLRNAME:                   <empty>
  CLTRESULTDIR:                  <empty>
  CLTSTARTUPTYPE:                0
  CLTSVCACCOUNT:                 <empty>
  CLTSVCPASSWORD:                <empty>
  CLTWORKINGDIR:                 <empty>
  COMMFABRICENCRYPTION:          0
  COMMFABRICNETWORKLEVEL:        0
  COMMFABRICPORT:                0
  CONFIGURATIONFILE:             
  CTLRSTARTUPTYPE:               0
  CTLRSVCACCOUNT:                <empty>
  CTLRSVCPASSWORD:               <empty>
  CTLRUSERS:                     <empty>
  ENABLERANU:                    true
  ENU:                           true
  EXTSVCACCOUNT:                 <empty>
  EXTSVCPASSWORD:                <empty>
  FEATURES:                      SQLENGINE, REPLICATION
  FILESTREAMLEVEL:               0
  FILESTREAMSHARENAME:           <empty>
  FTSVCACCOUNT:                  <empty>
  FTSVCPASSWORD:                 <empty>
  HELP:                          false
  IACCEPTPYTHONLICENSETERMS:     false
  IACCEPTROPENLICENSETERMS:      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:                    SQLEXPRESS
  INSTANCENAME:                  SQLEXPRESS
  ISMASTERSVCACCOUNT:            NT AUTHORITY\Network Service
  ISMASTERSVCPASSWORD:           <empty>
  ISMASTERSVCPORT:               8391
  ISMASTERSVCSSLCERTCN:          <empty>
  ISMASTERSVCSTARTUPTYPE:        Automatic
  ISMASTERSVCTHUMBPRINT:         <empty>
  ISSVCACCOUNT:                  NT AUTHORITY\Network Service
  ISSVCPASSWORD:                 <empty>
  ISSVCSTARTUPTYPE:              Automatic
  ISTELSVCACCT:                  <empty>
  ISTELSVCPASSWORD:              <empty>
  ISTELSVCSTARTUPTYPE:           0
  ISWORKERSVCACCOUNT:            NT AUTHORITY\Network Service
  ISWORKERSVCCERT:               <empty>
  ISWORKERSVCMASTER:             <empty>
  ISWORKERSVCPASSWORD:           <empty>
  ISWORKERSVCSTARTUPTYPE:        Automatic
  MATRIXCMBRICKCOMMPORT:         0
  MATRIXCMSERVERNAME:            <empty>
  MATRIXNAME:                    <empty>
  MRCACHEDIRECTORY:              
  NPENABLED:                     0
  PBDMSSVCACCOUNT:               <empty>
  PBDMSSVCPASSWORD:              <empty>
  PBDMSSVCSTARTUPTYPE:           0
  PBENGSVCACCOUNT:               <empty>
  PBENGSVCPASSWORD:              <empty>
  PBENGSVCSTARTUPTYPE:           0
  PBPORTRANGE:                   <empty>
  PBSCALEOUT:                    false
  PID:                           *****
  QUIET:                         false
  QUIETSIMPLE:                   false
  ROLE:                          AllFeatures_WithDefaults
  RSINSTALLMODE:                 DefaultNativeMode
  RSSVCACCOUNT:                  <empty>
  RSSVCPASSWORD:                 <empty>
  RSSVCSTARTUPTYPE:              Automatic
  SAPWD:                         <empty>
  SECURITYMODE:                  <empty>
  SQLBACKUPDIR:                  <empty>
  SQLCOLLATION:                  Latin1_General_CI_AS
  SQLSVCACCOUNT:                 NT Service\MSSQL$SQLEXPRESS
  SQLSVCINSTANTFILEINIT:         true
  SQLSVCPASSWORD:                <empty>
  SQLSVCSTARTUPTYPE:             Automatic
  SQLSYSADMINACCOUNTS:           DESKTOP-M4HSG00\Fadel Muhammad Aslam
  SQLTELSVCACCT:                 NT Service\SQLTELEMETRY$SQLEXPRESS
  SQLTELSVCPASSWORD:             <empty>
  SQLTELSVCSTARTUPTYPE:          Automatic
  SQLTEMPDBDIR:                  <empty>
  SQLTEMPDBFILECOUNT:            1
  SQLTEMPDBFILEGROWTH:           64
  SQLTEMPDBFILESIZE:             8
  SQLTEMPDBLOGDIR:               <empty>
  SQLTEMPDBLOGFILEGROWTH:        64
  SQLTEMPDBLOGFILESIZE:          8
  SQLUSERDBDIR:                  <empty>
  SQLUSERDBLOGDIR:               <empty>
  SUPPRESSPRIVACYSTATEMENTNOTICE: false
  TCPENABLED:                    0
  UIMODE:                        AutoAdvance
  UpdateEnabled:                 true
  UpdateSource:                  MU
  USEMICROSOFTUPDATE:            false
  X86:                           false

  Configuration file:            C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\Log\20180703_122635\ConfigurationFile.ini

Detailed results:
  Feature:                       Database Engine Services
  Status:                        Failed
  Reason for failure:            An error occurred during the setup process of the feature.
  Next Step:                     Use the following information to resolve the error, and then try the setup process again.
  Component name:                SQL Server Database Engine Services Instance Features
  Component error code:          1639
  Component log file:            C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\Log\20180703_122635\sql_engine_core_inst_Cpu64_1.log
  Error description:             Invalid command line argument. Consult the Windows Installer SDK for detailed command line help.
  Error help link:               https://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=14.0.1000.169&EvtType=sql_engine_core_inst.msi%400x162A16FE%400x1639

  Feature:                       SQL Server Replication
  Status:                        Failed
  Reason for failure:            An error occurred during the setup process of the feature.
  Next Step:                     Use the following information to resolve the error, and then try the setup process again.
  Component name:                SQL Server Database Engine Services Instance Features
  Component error code:          1639
  Component log file:            C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\Log\20180703_122635\sql_engine_core_inst_Cpu64_1.log
  Error description:             Invalid command line argument. Consult the Windows Installer SDK for detailed command line help.
  Error help link:               https://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=14.0.1000.169&EvtType=sql_engine_core_inst.msi%400x162A16FE%400x1639

  Feature:                       SQL Writer
  Status:                        Passed

Rules with failures:

Global rules:

Scenario specific rules:

Rules report file:               C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\Log\20180703_122635\SystemConfigurationCheck_Report.html

My question can sound crazy but it does reflect a real Customer issue.

A Customer migrated their DBs to a new SQL 2016 server hosted by a Windows Server 2016 server but discovered that an old legacy application is still attempting to establish an ODBC connection from a Windows 2000 (!) Server.

The Customer realizes that they MUST migrate the application to a less ancient box but in the meantime they need to allow the legacy application work.

When they try to establish a connection they get an error that sounds like:

Connection Failed:

SQLState: '01000'

SQL Server Error: 772 Connection failed:

SQLState: '08001'

SQL Error: 18

The same ODBC connection can be successfully created from a Windows 10 client, so the connections settings and authentication are ok.

Based on what I read in forums and blogs it looks like an SSL or TLS issue.

What can they implement as a TEMPORARY workaround to let the legacy application work waiting to be migrated to a newer server?

Regards

Mario

I have been receiving this error for too long and too often.  I have done everything that has been suggested in blogs, in documentation, and in every imagining.

HELP!

This is not a new problem.  The majority of corrective advice are for previous versions of SSMS and few if any for version 17.

If the installation routine knows a component is missing, can't the routine notify the user and offer to fix the issue?

Resolving this is vital now to my small business and it's success as a startup.

Thank you for your assistance and advice.

Kevin

OG IT Systems

Hello all,

I have a sQL 2000, because the version is too old.,Need to upgrade now, I want to upgrade to the 2014 version, can you upgrade directly? Do you need to upgrade to an intermediate version? Please describe the upgrade process, thank you.

Hi there

Ok, migrating all databases over time from 2014 to 2016.

Previous upgrades just used detach/attach, all worked ok.

On both servers the dbs and logs are stored on different drives.

I detach from 2014...all fine.  Copy mdf and ldf files to correct default locations.

On SQL 2016 SSMS, when I attach and add the mdf file, it does not populate the ldf in the lower window, the mdf does appear ok.  The default settings are correct.  Indeed if I ok the process, it comes back with an error basically saying it can't create the ldf file because it exists, which indeed it does.

However, if I put both the mdf and ldf files in same location, the attach process works fine even though not the default location.

If I use TSQL, it does work ok.  However, I'm used to using the GUI and in the past this has been the easiest option.

Any ideas how to get this working properly, have I missed something obvious?

Regards

Ian

Hi!

I'd like to upgrade my SSRS 2012 and 2016 instances to SSRS 2017. Upgrading from 2012 to 2016 was fine. However, when I run the stand-alone installer for SSRS 2017 I get no option to upgrade but only install and configure later. I've searched the documentation which is a mix of 2016 and 2017 references but have failed to find an answer.

Can I upgrade from SSRS 2016 to 2017 and if so, how?

The OS is W2K12 and the SSRS instance is named.

Thanks/U

Hi,

I set up a new cluster the other day, after doing two others successfully. This particular cluster on windows 2012 R2 is a SQL 2014 installation that has been patched to SP2 CU10. The cluster also hosts 9 other instances and a file share we use for backups for all the instances. 

It will not come online and has the error - "Could not find any IP address that this SQL Server instance depends upon. Make sure that the cluster service is running, that the dependency relationship between SQL Server and Network Name resources is correct, and that the IP addresses on which this SQL Server instance depends are available."

I verified that dependencies were set up like the other clustered instance on this cluster, took the IP & Network name offline and then tried to ping it - no response. I put the IP/NetName online and was able to ping it. I changed the IP to a new IP provided by my network team and also known to be available. I have read through several similar threads here that mention validating registry entries and looked at those entries. I've tried bringing it up on both nodes.  The same error has occurred after all these steps.

System Log:

The SQL Server (INST10) service terminated with the following service-specific error: 
Access is denied.

SQL Log:

2018-07-05 11:41:11.59 spid16s     Could not find any IP address that this SQL Server instance depends upon.  Make sure that the cluster service is running, that the dependency relationship between SQL Server and Network Name resources is correct, and that the IP addresses on which this SQL Server instance depends are available.  Error code: 0x5.
2018-07-05 11:41:11.59 spid16s     Error: 17182, Severity: 16, State: 1.
2018-07-05 11:41:11.59 spid16s     TDSSNIClient initialization failed with error 0x5, status code 0xa. Reason: Unable to initialize the TCP/IP listener. Access is denied. 
2018-07-05 11:41:11.59 spid16s     Error: 17182, Severity: 16, State: 1.
2018-07-05 11:41:11.59 spid16s     TDSSNIClient initialization failed with error 0x5, status code 0x1. Reason: Initialization failed with an infrastructure error. Check for previous errors. Access is denied. 
2018-07-05 11:41:11.59 spid16s     Error: 17826, Severity: 18, State: 3.
2018-07-05 11:41:11.59 spid16s     Could not start the network library because of an internal error in the network library. To determine the cause, review the errors immediately preceding this one in the error log.
2018-07-05 11:41:11.59 spid16s     Error: 17120, Severity: 16, State: 1.
2018-07-05 11:41:11.59 spid16s     SQL Server could not spawn FRunCommunicationsManager thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.

Thanks for your review and suggestions.

Sam

Hi,

How to identify more reasons in Log file, to below problems?

Many Thanks & Best Regards, Hua Min

Hello,

After recent updates for Windows 7 x64 we have encountered a problem with SQL Server Management Studio 2012. While trying to make a new query, the following error appears:

https://imgur.com/ecDwhWA

We have tried to reset fonts in Windows and reinstall Management Studio. Restoring system had helped for a while, but after a few days the problem reappeared when updates were installed again. If you know the solution, please help.

Best regards,

Emil

We have a 3 node SQL failover cluster with SQL2014 SP1 and CU13. Because CU13 is out of support we are going to upgrade to SP2. SP2 is older than CU13 (for SP1). I was wondering if someone encountered an issue, because some componentes of SP2 are older then components from CU13. I expected to find some information about this, but could not find anything about it.

I think the approach should be install the SP2, reboot, and install the latest CU for SP2 (reboot). Of course start with node where the SQL cluster role is not running on. Fail over to the upgraded server and do the others.

Regards, Jeroen

Detail:

(01) 2017-10-19 02:14:41 Slp: Log provider 'Microsoft.SqlServer.Chainer.Infrastructure.LogProviderFile' has been registered
(01) 2017-10-19 02:14:41 Slp: Log provider 'Microsoft.SqlServer.Chainer.Infrastructure.LogProviderConsole' has been registered
(01) 2017-10-19 02:14:41 Slp: Log provider 'Microsoft.SqlServer.Chainer.Infrastructure.LogProviderStatus' has been registered
(01) 2017-10-19 02:14:41 Slp: Reading XML resource 'Microsoft.SQL.Chainer.PackageData.Package.xml'
(01) 2017-10-19 02:14:41 Slp: Reading schema resource 'Microsoft.SQL.Chainer.Package.Package.xsd'
(01) 2017-10-19 02:14:41 Slp: Document 'Microsoft.SQL.Chainer.PackageData.Package.xml' validated with schema 'Microsoft.SQL.Chainer.Package.Package.xsd' has been successfuly loaded into datastore path '/Datastore/Package'
(01) 2017-10-19 02:14:41 Slp: ----------------------------------------------------------------------
(01) 2017-10-19 02:14:41 Slp: Running Action: ReadProductXML
(01) 2017-10-19 02:14:41 Slp: Reading XML resource 'Microsoft.SQL.Chainer.Product.Product.xml'
(01) 2017-10-19 02:14:41 Slp: Document 'Microsoft.SQL.Chainer.Product.Product.xml' validated with schema 'Microsoft.SQL.Chainer.Product.Product.xsd' has been successfuly loaded into datastore path '/Datastore/Product'
(01) 2017-10-19 02:14:41 Slp: Completed Action: ReadProductXML, returned True
(01) 2017-10-19 02:14:41 Slp: ----------------------------------------------------------------------
(01) 2017-10-19 02:14:41 Slp: Running Action: LoadExtensions
(01) 2017-10-19 02:14:42 Slp: Loading extension 'MSI' from file 'C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\SQL2017\x64\.\Microsoft.SqlServer.Configuration.MsiExtension.dll'
(01) 2017-10-19 02:14:42 Slp: Extension 'MSI' version '14.0.1000.169' loaded
(01) 2017-10-19 02:14:42 Slp: Loading extension 'Config' from file 'C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\SQL2017\x64\.\Microsoft.SqlServer.Configuration.ConfigExtension.dll'
(01) 2017-10-19 02:14:42 Slp: Extension 'Config' version '14.0.1000.169' loaded
(01) 2017-10-19 02:14:42 Slp: Loading extension 'Common' from file 'C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\SQL2017\x64\.\Microsoft.SqlServer.Chainer.ExtensionCommon.dll'
(01) 2017-10-19 02:14:42 Slp: Extension 'Common' version '14.0.1000.169' loaded
(01) 2017-10-19 02:14:42 Slp: Loading extension 'SqlConfigBase' from file 'C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\SQL2017\x64\.\Microsoft.SqlServer.Configuration.SqlConfigBase.dll'
(01) 2017-10-19 02:14:42 Slp: Extension 'SqlConfigBase' version '14.0.1000.169' loaded
(01) 2017-10-19 02:14:42 Slp: Loading extension 'Slp' from file 'C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\SQL2017\x64\.\Microsoft.SqlServer.Configuration.SetupExtension.dll'
(01) 2017-10-19 02:14:42 Slp: Extension 'Slp' version '14.0.1000.169' loaded
(01) 2017-10-19 02:14:42 Slp: Loading extension 'RulesEngine' from file 'C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\SQL2017\x64\.\Microsoft.SqlServer.Configuration.RulesEngineExtension.dll'
(01) 2017-10-19 02:14:42 Slp: Extension 'RulesEngine' version '14.0.1000.169' loaded
(01) 2017-10-19 02:14:42 Slp: Loading extension 'WorkflowData' from file 'C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\SQL2017\x64\.\Microsoft.SqlServer.Chainer.WorkflowData.dll'
(01) 2017-10-19 02:14:42 Slp: Extension 'WorkflowData' version '14.0.1000.169' loaded
(01) 2017-10-19 02:14:42 Slp: Loading extension 'SlpConfig' from file 'C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\SQL2017\x64\.\Microsoft.SqlServer.Configuration.SlpExtension.dll'
(01) 2017-10-19 02:14:42 Slp: Extension 'SlpConfig' version '14.0.1000.169' loaded
(01) 2017-10-19 02:14:42 Slp: Loading extension 'Clst' from file 'C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\SQL2017\x64\.\Microsoft.SqlServer.Configuration.Cluster.dll'
(01) 2017-10-19 02:14:42 Slp: Extension 'Clst' version '14.0.1000.169' loaded
(01) 2017-10-19 02:14:42 Slp: Loading extension 'AgentConfig' from file 'C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\SQL2017\x64\.\Microsoft.SqlServer.Configuration.AgentExtension.dll'
(01) 2017-10-19 02:14:42 Slp: Extension 'AgentConfig' version '14.0.1000.169' loaded
(01) 2017-10-19 02:14:42 Slp: Loading extension 'SqlPowershellConfig' from file 'C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\SQL2017\x64\.\Microsoft.SqlServer.Configuration.PowershellExtension.dll'
(01) 2017-10-19 02:14:42 Slp: Extension 'SqlPowershellConfig' version '14.0.1000.169' loaded
(01) 2017-10-19 02:14:42 Slp: Loading extension 'SSISConfig' from file 'C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\SQL2017\x64\.\Microsoft.SqlServer.Configuration.SSISExtension.dll'
(01) 2017-10-19 02:14:42 Slp: Extension 'SSISConfig' version '14.0.1000.169' loaded
(01) 2017-10-19 02:14:42 Slp: Loading extension 'ISMasterConfig' from file 'C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\SQL2017\x64\.\Microsoft.SqlServer.Configuration.ISMasterExtension.dll'
(01) 2017-10-19 02:14:42 Slp: Extension 'ISMasterConfig' version '14.0.1000.169' loaded
(01) 2017-10-19 02:14:42 Slp: Loading extension 'ISWorkerConfig' from file 'C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\SQL2017\x64\.\Microsoft.SqlServer.Configuration.ISWorkerExtension.dll'
(01) 2017-10-19 02:14:42 Slp: Extension 'ISWorkerConfig' version '14.0.1000.169' loaded
(01) 2017-10-19 02:14:42 Slp: Loading extension 'DReplayConfig' from file 'C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\SQL2017\x64\.\Microsoft.SqlServer.Configuration.DistributedReplayExtension.dll'
(01) 2017-10-19 02:14:42 Slp: Extension 'DReplayConfig' version '14.0.1000.169' loaded
(01) 2017-10-19 02:14:42 Slp: Loading extension 'ASConfig' from file 'C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\SQL2017\x64\.\Microsoft.SqlServer.Configuration.ASExtension.dll'
(01) 2017-10-19 02:14:42 Slp: Extension 'ASConfig' version '14.0.1000.169' loaded
(01) 2017-10-19 02:14:42 Slp: Loading extension 'ReplConfig' from file 'C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\SQL2017\x64\.\Microsoft.SqlServer.Configuration.Repl_ConfigExtension.dll'
(01) 2017-10-19 02:14:42 Slp: Extension 'ReplConfig' version '14.0.1000.169' loaded
(01) 2017-10-19 02:14:42 Slp: Loading extension 'ManagementToolsConfig' from file 'C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\SQL2017\x64\.\Microsoft.SqlServer.Configuration.ManagementToolsExtension.dll'
(01) 2017-10-19 02:14:42 Slp: Extension 'ManagementToolsConfig' version '14.0.1000.169' loaded
(01) 2017-10-19 02:14:42 Slp: Loading extension 'ManagementToolsAdvancedConfig' from file 'C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\SQL2017\x64\.\Microsoft.SqlServer.Configuration.ManagementToolsExtension.dll'
(01) 2017-10-19 02:14:42 Slp: Extension 'ManagementToolsAdvancedConfig' version '14.0.1000.169' loaded

TITLE: Microsoft SQL Server Management Studio
------------------------------

Cannot create a task from XML for task "", type "" due to error 0x80070057 "The parameter is incorrect.".
 (OnPreExecute)

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

Cannot create a task from XML for task "", type "" due to error 0x80070057 "The parameter is incorrect.".
 (OnPreExecute)

more on the error :