I'm trying to get the update which is Security Update for SQL Server 2016 SP2 (KB4293802) from Windows Update on my Windows 10. However it returns me Security Update for SQL Server 2016 SP2 (KB4293802) -Error 0x80070643 error.

Therefore I downloaded the update from microsoft.com download page to manual installing but I'm getting failure now. The following log file, which is shown after uncompleted setup, contains information as follows:

Overall summary:
  Final result:                  The patch installer has failed to update the following instance: MSSQLSERVER. To determine the reason for failure, review the log files.
  Exit code (Decimal):           -2068709375
  Start time:                    2019-06-05 01:27:52
  End time:                      2019-06-05 01:30:46
  Requested action:              Patch

Instance MSSQLSERVER overall summary:
  Final result:                  The patch installer has failed to update the shared features. To determine the reason for failure, review the log files.
  Exit code (Decimal):           -2068709375
  Exit facility code:            1202
  Exit error code:               1
  Exit message:                  The NT service 'SQLPBDMS' could not be stopped.
  Start time:                    2019-06-05 01:28:36
  End time:                      2019-06-05 01:30:44
  Requested action:              Patch
  Exception help link:           http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=13.0.5081.1&EvtType=0xAC454CB1%400xF762992B%401202%401&EvtType=0xAC454CB1%400xF762992B%401202%401

Machine Properties:
  Machine name:                  ****
  Machine processor count:       8
  OS version:                    Microsoft Windows 10 ****
  OS service pack:               
  OS region:                     ****
  OS language:                   English (****)
  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 2016      MSSQLSERVER          MSSQL13.MSSQLSERVER            Database Engine Services                 1033                 Express Edition      13.2.5026.0     No         Yes       
  SQL Server 2016      MSSQLSERVER          MSSQL13.MSSQLSERVER            SQL Server Replication                   1033                 Express Edition      13.2.5026.0     No         Yes       
  SQL Server 2016      MSSQLSERVER          MSSQL13.MSSQLSERVER            Full-Text and Semantic Extractions for Search 1033                 Express Edition      13.2.5026.0     No         Yes       
  SQL Server 2016      MSSQLSERVER          MSSQL13.MSSQLSERVER            PolyBase Query Service for External Data 1033                 Express Edition      13.2.5026.0     No         Yes       
  SQL Server 2016      MSSQLSERVER          MSSQL13.MSSQLSERVER            R Services (In-Database)                 1033                 Express Edition      13.2.5026.0     No         Yes       
  SQL Server 2016      MSSQLSERVER          MSSQL13.MSSQLSERVER            sql_inst_mr                              1033                 Express Edition      13.2.5026.0     No         Yes       
  SQL Server 2016      MSSQLSERVER          MSRS13.MSSQLSERVER             Reporting Services - Native              1033                 Express Edition      13.2.5081.1     No         Yes       
  SQL Server 2016                                                          SSMS                                     1033                                      13.0.16106.4    No         Yes       
  SQL Server 2016                                                          Client Tools Connectivity                1033                                      13.0.14500.10   No         Yes       
  SQL Server 2016                                                          Client Tools Backwards Compatibility     1033                                      13.0.14500.10   No         Yes       
  SQL Server 2016                                                          Client Tools SDK                         1033                                      13.0.14500.10   No         Yes       
  SQL Server 2016                                                          LocalDB                                  1033                 Express Edition      13.2.5081.1     No         Yes      

Package properties:
  Description:                   Microsoft SQL Server 2016 
  ProductName:                   SQL Server 2016
  Type:                          RTM
  Version:                       13
  SPLevel:                       2
  KBArticle:                     KB4293802
  KBArticleHyperlink:            http://support.microsoft.com/?kbid=4293802
  PatchType:                     GDR
  AssociatedHotfixBuild:         5158
  Platform:                      x64
  PatchLevel:                    13.2.5081.1
  ProductVersion:                13.2.5026.0
  GDRReservedRange:              13.0.1700.0:13.0.1899.0;13.0.4200.0:13.0.4299.0;13.0.5200.0:13.0.5399.0
  Installation location:         C:\cd2734868aa85d93cc33ba11c023\x64\setup\ 

Updated product edition:
  Instance             Edition             
  MSSQLSERVER          Express             

User Input Settings:
  ACTION:                        Patch
  ALLINSTANCES:                  false
  CLUSTERPASSIVE:                false
  CONFIGURATIONFILE:             
  ENU:                           false
  HELP:                          false
  IACCEPTROPENLICENSETERMS:      true
  IACCEPTSQLSERVERLICENSETERMS:  true
  INDICATEPROGRESS:              false
  INSTANCEID:                    <empty>
  INSTANCENAME:                  <empty>
  MRCACHEDIRECTORY:              
  QUIET:                         false
  QUIETSIMPLE:                   false
  SUPPRESSPRIVACYSTATEMENTNOTICE: false
  UIMODE:                        Normal
  X86:                           false

Rules with failures:

Global rules:

There are no scenario-specific rules.

Rules report file:               C:\Program Files\Microsoft SQL Server\130\Setup Bootstrap\Log\20190605_012732\SystemConfigurationCheck_Report.htm
I found similar questions about this but couldn't reach a conclusion with them. How can I fix this issue?

Hi, our current SQL server was installed at sp2 CU1.  I see we are now up to CU7.

Think this is a relative straightforward question.  is it ok to apply the upgrade whilst the server is in use?  If not, what's the recommended method(s) for ensuring no access whilst we run the CU?  We currently have about 7 instances on this SQL server.

Regards

Ian

Fellow SQLers,

I am a SQL DBA

We are flipping a collation. We have done this before and understand the use of the Setup /QUIET /ACTION=REBUILDDATABASE  command. Have used it before just fine.

For some reason on a test clustered instance we are getting errors. I and my fellow dbas have treid as well. Tried from the install disc folder and also tried from Bootstrap setup. we are all admins. All attemps are failing with below errors.

The active node has sql instance offline and we also tried enabling Named Pipes - no success.

After the failure, the sa password is blank (which we supplied in the command). When we fix the security, the db DID get the new collation but of course we do not trust the instance.

What are we missing?

Feature:                       Data Quality Services
  Status:                        Failed: see logs for details
  Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
  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:          0x84BB0001
  Error description:             A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
  Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=13.0.4001.0&EvtType=0x6BB41ECB%400xDC80C325&EvtType=0x6BB41ECB%400xDC80C325

  Feature:                       Full-Text and Semantic Extractions for Search
  Status:                        Failed: see logs for details
  Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
  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:          0x84BB0001
  Error description:             A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
  Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=13.0.4001.0&EvtType=0x6BB41ECB%400xDC80C325&EvtType=0x6BB41ECB%400xDC80C325

  Feature:                       SQL Server Replication
  Status:                        Failed: see logs for details
  Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
  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:          0x84BB0001
  Error description:             A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
  Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=13.0.4001.0&EvtType=0x6BB41ECB%400xDC80C325&EvtType=0x6BB41ECB%400xDC80C325

  Feature:                       Database Engine Services
  Status:                        Failed: see logs for details
  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:          0x84BB0001
  Error description:             A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
  Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=13.0.4001.0&EvtType=0x6BB41ECB%400xDC80C325&EvtType=0x6BB41ECB%400xDC80C325

Thanks MG

We have a production machine which runs SQL Server 2016 Standard.  A SQL Server 2017 evaluation edition was installed on the machine.  During this installation, Upgrade Shared Components was selected.  We haven't been able to fully uninstall 2017 and we can no longer use SSIS because it's been upgraded to 2017 and outside the evaluation period.

Is there something that can be done to get the shared components back to 2016?  I was going to try installing SSDT for 2016 but it seems there isn't an installer for it any more?

As a last-ditch effort, if when SQL Server 2019 Standard becomes available, we would be able to install that on the server and it should bring everything up to current and functional, correct?

Thank You In Advance.

Hey all,

I'm having some trouble re-installing SQL Server 2017 after doing a system restore on my Windows 10 machine. The install summary shows the following failures;

There's over 150 gigs of free space on the C drive where I'm trying to install this but I continue to get these errors. I'm also installing this under an administrator account. Here's a Pastebin link to the full install summary https://pastebin.com/te6bsb0V. Any help would be appreciated. Thanks!

try to install sql server on centos server, following by this tutorial: docs.microsoft.com/en-us/sql/linux/quickstart-install-connect-red-hat?view=sql-server-2017

in step 3 "/opt/mssql/bin/mssql-conf setup", after setting password for system administrator, it shows:

Configuring SQL Server...

/opt/mssql/bin/sqlservr: Can't find package [system]; searched in the following locations:
 /opt/mssql/bin /opt/mssql/bin/../lib /var/opt/mssql
Initial setup of Microsoft SQL Server failed. Please consult the ERRORLOG
in /var/opt/mssql/log for more information.

when i try to check the ERRORLOG in /var/opt/mssql/log, i found its empty.

however, i did the same on another centos server, the sql server was successfully installed without any errors.

any suggestions to solve the problem above? thanks in advance!

Hi,

Two machines on the same network

Machine A ( IP : XXX.XXX.XXX.XXX)

Machine B ( IP : YYY.YYY.YYY.YYY)

1. I install the sql server instance ( default instance - machine name B ) in machine B

2. Migrate the database from A to B

3. now shutdown A

4. Change the Machine name and IP address of B with Machine name IP address of A ) so B become A.

My question is after i change the machine name from B to A, Do i still need to update the sql server instance name from B to A to access the sql server with instance name from other machines?

So, what i want to do is related with sql patching (This pertains to normal sql patching - CU's/SP's in the same sql version)

Can patching be done say on prod AG nodes on one weekend , apps test on it on the next week, if all is fine , update the BCP AG nodes on next weekend - The reason i want to do this is if there is a issue reported by apps after the initial prod patching we have a env (bcp) where we can failover till the issue is resolved in Prod. 

My question is - Is it possible to failover sql from a patched prod to unpatched bcp if needed, is that possible in AG?

And secondly, how are people going about patching their AG env's , please don't answer about rolling upgrades ,this is not about minimizing downtime(https://docs.microsoft.com/en-us/sql/database-engine/availability-groups/windows/upgrading-always-on-availability-group-replica-instances?view=sql-server-2017) , I am only interested in knowing if people are looking into patching only 1 env first and waiting for some time & then patching other.

Maybe i am going about it a wrong way, do people uninstall the CU's , SP's if issues and just do the complete prod-bcp patching together - is that the best way?

Thanks

D

Hi,

My name is Hari Gopi. I was trying to install SQL server 2017 developer edition on my Windows 8.1 machine. After the setup is run i am getting  some path not found error at the finish and Database engine services installation is failed. Below is the error description.

Unable to install SQL Server(setup.exe)

Exit code (Decimal): -2147467259 Error Description: The system  cannot find the specified path

Below is the Summary file content.

Can someone help me out on this please. Thanks in Advance.

Hi 

Please let me know how to : SQL Server 2016 Standard to Enterprise edition upgrade step by step using SSMS or T-SQL too.

Question : 

1. How much time it will take & what are the pre-requisite steps to be taken?

2. Is there any fallback plan to revert if in case activity failed?

3. SQL Server type : [1] Standalone  & [2] Failover cluster - 2 Nodes

4. Any impact on System & App DBs. [User DB Size : 3 TB.]

5. Any down-time required.

Thanks.

MRVSFLY

MRVSFLY

I've seen an article on this but need more detailed info. Once I go into SQL Server Configuration Manager and click on New Alias what do I enter in the 4 fields. I tried putting the IP address of the computer into Alias Name, 1433 into port number, TCP/IP as protocol and localhost as server. What have I done incorrectly?

update: I have also tried put the named instance name instead of localhost. Still won't connect.

Examples of this on the internet are non-existing. How can that be?

i want to setup sql server 2016 express. but its showing an error message . 

SQL Server Setup has encountered the following error:

Value cannot be null.

Parameter name : doc.

How can i solve this problem ? Please help me . 

We have an autosys server which has sqlcmd.exe and bcp.exe installed on it so we can run SQL queries through our console apps.  On the server we have SQL 2016 and two other components: SQL Server 2008 Setup Support Files and SQL Server 2014 Management Objects.  Since 2008 is reaching end of life, we are being required to remove it from our server.  When we try to do this we are getting a message that indicates that SQL Sever 2016 Management Studio depends on this product and might not function properly if we remove it.  When we did this in the DEV environment we ended up losing sqlcmd.exe and bcp.exe, but I believe this happened when we removed the 2014 component.  So my question is simple: can we remove SQL Server 2008 Setup Support Files from the server and not have to worry about sqlcmd.exe and bcp.exe being removed as well?

Thanks for any information you can provide on this.

Mark Stone

We are planning to upgrade from SQL 2012 to SQL 2017.

What type of tests and other preparations should I do\check in advance to be sure it is going to work?

We are planning a migration of our SQL 2012 from Windows 2k8R2 to Windows 2016.

I was told I should notice flag 9481 Cardinality Estimation.

Is there anything else I should be aware of or check\test before doing the migration?

(For sure we will first do the migration on our Test environment, but as we don't have automation on it, it doesn't really check the whole system)

SQL Server setup failed with exit code 2068119551

I could not find any thing on this exit code.

The only indication i manage to find is in the log itself : uninstall and install again. That does not work.

Anyone with insight on this ?

We're currently running the RTM version and I'm looking to install SP2. Couple of questions that I couldn't find definitive answers for:

1. Can I install SP2 directly, or do I need to first install SP1?
2. Where are the instructions to install the service pack on a cluster to avoid unnecessary downtime? I found directions for SQL Server 2008 and 2012, but nothing newer. The procedure for 2008 requires removing owned services from passive nodes before installation, whereas the 2012 appears to be just install the SP on passive node, restart, then fail over and install on other node, then restart that node. Is the latter procedure correct for 2016?

Thanks!

Hi Experts,

Please suggest : How to enable Backup Compression for TDE-enabled Databases ?

Thanks

MRVS

MRVSFLY