I am seeing this error after the update:

Failed to verify the Authenticode signature of 'C:\Program Files\Microsoft SQL Server\MSSQL13.MSSQLSERVER\MSSQL\Binn\BatchParser.dll'. Signature verification of SQL Server DLLs will be skipped. Genuine copies of SQL Server are signed. Failure to verify the Authenticode signature might indicate that this is not an authentic release of SQL Server. Install a genuine copy of SQL Server or contact customer support.

Failed to verify the Authenticode signature of 'C:\Program Files\Microsoft SQL Server\MSSQL13.MSSQLSERVER\MSSQL\Binn\hkengine.dll'. Signature verification of SQL Server DLLs will be skipped. Genuine copies of SQL Server are signed. Failure to verify the Authenticode signature might indicate that this is not an authentic release of SQL Server. Install a genuine copy of SQL Server or contact customer support.

Hi,

I have a web app  server , this server is connected to DB using a single user . If that is the case how many USER CAL OR DEVICE CAL i need to purchase 

Thanks

I have a SQL Server estate with servers in various major versions, SPs, and CUs.  I want to get all of them up to SQL 2017 + latest CU.  I am aware of the minimum versions required for upgrade to 2017:

Most servers meet these requirements.  My question is: Would it be best to apply the latest SPs and CUs for the current major versions as a stepping stone to the upgrade to 2017?  OR to just move forward with ensuring that they have the minimal SPs and CUs and then upgrade them straight to 2017?

TIA,

-Peter

While installing SQLServer 2014, found the error; any explanation why I got this error? Never experienced the error message before.

Hello,

We are currently preparing for a new SQL Server 2017 Standard for our site (Internal Site).

We are buying a Server + CAL licensing model for the SQL Server to install on our server, but we found that one of our devices is using iPad to access the database through our application.

We are buying 5 devices CAL for the SQL Server, which we are wondering if this can be used/install on an iPad.

Since we are using express edition in the past, we would like to know if the CAL will work on an iPad or other android devices.

Thanks for your help.

Best Regards,

Foc3

Have installed SQL 2017 Standard from the ISO file but now for activation the keys are not displayed in the VLSC.

It says this "This product does not require a product key."

So how to activate the SQL 2017 License.

Nimish.

Hi

I am trying to change the edition of SQL from Enterprise Evaluation to Standard, which is supported according to this article: https://docs.microsoft.com/en-us/sql/database-engine/install-windows/supported-version-and-edition-upgrades?view=sql-server-2017 . This is a single instance, no clustering.

I have downloaded the SQL Server 2016 Standard SP2 ISO from my volume licensing portal and run the Edition Upgrade option.

After running through the wizard, it says it has completed successfully, however when I look at the properties of the instance it is still Enterprise Evaluation.

I tested this scenario on another computer and it worked fine, so I don't know why it isn't working on this other machine.

The version is 2016 SP2 running on Windows Server 2016.

I have noticed that the Database Engine is missing from the 'Ready to upgrade edition' window during the wizard. Perhaps this could be the issue?

Hope someone can help.

Thanks

I am trying to update my SQL server 2005 to 2012, using the upgrade feature on the DVD.  It passes it's pre tests and it doesn't see any updates for the installation. When i get to "select features" Both options are grayed out, and I am unable to select any of them. How can i fix this? Please help me. 

Hello, 

I am using Visual Studio 2019, SQL Server 2016.  but when i install SQL Server 2016 automatically install Visual studio 2010 shell isolation. i have already Visual studio so why need it. if its important, so which version i use to don't need shell isolation. 

thank you!

Thanks, Nithin

Hello, 

I'm seeing this on multiple Windows 2012R2 servers.  KB4505217 fails to install and the performance counters are gone.  This key is missing - HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Instance-Name-Here\Performance\

This in the System log "Installation Failure: Windows failed to install the following update with error 0x80070643: Security Update for SQL Server 2014 Service Pack 2 GDR (KB4505217)."

This is in the Application log.

***************************

****************

Yet when I open the error log, the first line is "Microsoft SQL Server 2014 (SP2-GDR) (KB4505217) - 12.0.5223.6 (X64)"

Any assistance would be appreciated.

hello,

I was trying to download sql server 2017 developer edition the download done successfully but the automatically setup that leads to download plan didn't start and it gave a blank error message an empty window. when I tried to start it manually from setup.exe file it returned the same blank error. I tried to uninstall it then reinstall also I tried to install it from the iso I tried the express edition and i checked for deleted old version files all these returned the same blank error message.

SQL Server Service
(2014) is set to "Automatic" and should therefore be automatically started when I boot up my computer. As viewed from Services it is in a "Stopped" state after reboot. I believe this is due to a recent service pack or cumulative update(?)

From the command prompt I am able to start the SQL Server Service by bypassing the Cumulative Update or Service Pack option with the option switch "/T902" :

NET START MSSQL$MSSQLSERVER2014 /T902 after which everything behaves normally.

The Service "Logon" is currently set to "LocalSystem" and I have changed this to both "NT Authority\System" and "NT
AUTHORITY\NETWORKSERVICE" in an attempt to resolve the problem.

Each time the Windows Event log records :

"The SQL Server (MSSQLSERVER2014) service terminated with the following service-specific error:

WARNING: You have until SQL Server (MSSQLSERVER2014) to logoff. If you have not logged off at this time, your session will be disconnected, and any open files or devices you have open may lose data."

By itself the message is pretty useless but I get similar messages when I attempt to change the service logon. Thus, my suspicion is that this is a "permission" type issue such that some script has insufficient "rights" in order to carry out what it is attempting to do.

If I knew where these scripts were located I might try running the scripts manually to identify which one(s) are causing the problem. Running the script manually might be more informative and pinpoint exactly what is causing this. Unfortunately, the next step in resolving this eludes me.  

Can you help?

Kev

Hi,

I do have installed the English Version of SQL Server 2016 and SQL Server Management Studio 17.1.  


How can I change the language to English?  As you can see, the DB menu in Object Explorer is in English, but the user interface still is in German.

When I use the link to install other languages. I get a link to http://go.microsoft.com/fwlink/?LinkId=558810&clcid=0x407 

This is completely  wrong, because it redirects me to install a "Microsoft Visual Studio 2015 Sprachpaket" = Language Pack for VS2015.  Why I need to install a Language pack if I installed the English version: "SSMS-Setup-ENU.exe"

I do have Visual Studio 2017 English installed.  

It's very strange.

Regards,

Arash

Hi,

I was installing one identity service with MS SQL server 2016 and received error:

Line 1: FOR UPDATE clause allowed only for DECLARE CURSOR

I saw below fix which is in SQL server 2012.

2740957: fix-for-update-clause-allowed-only-for-declare-cursor-error-when-you-e

Now I have question since I am using MS MSQL server 2016, do I need to apply this package? I believe 2016 should have this fix since it's cumulative build. Please help me here to identify proper fix.

Thanks in advance.

Hello,

Have a new server with SQL 2008 and an old server with SQL 2005 sp1.  I need to move my data over to new server but the SQL's are not compatible.  When trying to upgrade my old server to SQL 2008 its unsuccessful.  Cant even upgrade on old server to SQL 2005 sp4

we have a sql server 2016 which is running on windows server and is part of Active directory domain.

I have provided db_owner permission on an active directory group account(Domain\accountname) and user id(Domain\userid) is member of that group. When user tried with id (Domain\userid) using active directory password authentication via SSMS getting below error:

ERROR:18456 -  could not find  a login matching the name provided.

Sql server is running in AD domain, user had AD credentials and is part of active directory group account but getting the error.

Kindly help!

I encountered this error and I cannot fix it.

I tried to give full permissions to everyone,I tried some stackoverflow.com's tips(I'm not allowed to post here links yet)  and I aalso tried to setup my tmp folder as I have seen on some links,but my folder was already  like there. And many others things I don't remember right now...

Also the summary of log file is(if it helps):

Overall summary:

  Final result:                  Failed: see details below

  Exit code (Decimal):           -2068051813
  Start time:                    2019-10-11 13:27:16
  End time:                      2019-10-11 13:29:40
  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.
  Next step for Browser:         Use the following information to resolve the error, and then try the setup process again.
  Next step for Writer:          Use the following information to resolve the error, and then try the setup process again.
  Next step for SNAC:            Use the following information to resolve the error, and then try the setup process again.
  Next step for SNAC_SDK:        Use the following information to resolve the error, and then try the setup process again.
  Next step for ComponentUpdate: Use the following information to resolve the error, and then try the setup process again.


Machine Properties:
  Machine name:                  DESKTOP-7A3NATV
  Machine processor count:       8
  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:\SQLServer2017Media\Express_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:         Automatic
  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, SNAC_SDK
  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:                         *****
  SECURITYMODE:                  SQL
  SQLBACKUPDIR:                  <empty>
  SQLCOLLATION:                  SQL_Latin1_General_CP1_CI_AS
  SQLSVCACCOUNT:                 NT Service\MSSQL$SQLEXPRESS
  SQLSVCINSTANTFILEINIT:         false
  SQLSVCPASSWORD:                <empty>
  SQLSVCSTARTUPTYPE:             Automatic
  SQLSYSADMINACCOUNTS:           DESKTOP-7A3NATV\Miriam
  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\20191011_132715\ConfigurationFile.ini

Detailed results:
  Feature:                       Database Engine Services
  Status:                        Failed
  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 Setup Support Files
  Component error code:          2203
  Component log file:            C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\Log\20191011_132715\SqlSupport_Cpu64_1.log
  Error description:             The installer has encountered an unexpected error. The error code is 2203. Database: C:\WINDOWS\Installer\inprogressinstallinfo.ipi. Cannot open database file. System error -2147286788.
  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=SqlSupport.msi%40InstallInitialize%402203

  Feature:                       SQL Server Replication
  Status:                        Failed
  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 Setup Support Files
  Component error code:          2203
  Component log file:            C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\Log\20191011_132715\SqlSupport_Cpu64_1.log
  Error description:             The installer has encountered an unexpected error. The error code is 2203. Database: C:\WINDOWS\Installer\inprogressinstallinfo.ipi. Cannot open database file. System error -2147286788.
  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=SqlSupport.msi%40InstallInitialize%402203

  Feature:                       SQL Browser
  Status:                        Failed
  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 Setup Support Files
  Component error code:          2203
  Component log file:            C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\Log\20191011_132715\SqlSupport_Cpu64_1.log
  Error description:             The installer has encountered an unexpected error. The error code is 2203. Database: C:\WINDOWS\Installer\inprogressinstallinfo.ipi. Cannot open database file. System error -2147286788.
  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=SqlSupport.msi%40InstallInitialize%402203

  Feature:                       SQL Writer
  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 Writer Component
  Component error code:          2203
  Component log file:            C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\Log\20191011_132715\SqlWriter_Cpu64_1.log
  Error description:             The installer has encountered an unexpected error. The error code is 2203. Database: C:\WINDOWS\Installer\inprogressinstallinfo.ipi. Cannot open database file. System error -2147286788.
  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=SqlWriter.msi%40InstallInitialize%402203

  Feature:                       SQL Client Connectivity
  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 Native Client Access Component
  Component error code:          2203
  Component log file:            C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\Log\20191011_132715\sqlncli_Cpu64_1.log
  Error description:             The installer has encountered an unexpected error. The error code is 2203. Database: C:\WINDOWS\Installer\inprogressinstallinfo.ipi. Cannot open database file. System error -2147286788.
  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=sqlncli.msi%40InstallInitialize%402203

  Feature:                       SQL Client Connectivity SDK
  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 Native Client Access Component
  Component error code:          2203
  Component log file:            C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\Log\20191011_132715\sqlncli_Cpu64_1.log
  Error description:             The installer has encountered an unexpected error. The error code is 2203. Database: C:\WINDOWS\Installer\inprogressinstallinfo.ipi. Cannot open database file. System error -2147286788.
  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=sqlncli.msi%40InstallInitialize%402203

  Feature:                       Setup Support Files
  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 Setup Support Files
  Component error code:          2203
  Component log file:            C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\Log\20191011_132715\SqlSupport_Cpu64_1.log
  Error description:             The installer has encountered an unexpected error. The error code is 2203. Database: C:\WINDOWS\Installer\inprogressinstallinfo.ipi. Cannot open database file. System error -2147286788.
  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=SqlSupport.msi%40InstallInitialize%402203

Rules with failures:

Global rules:

Scenario specific rules:

Rules report file:               C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\Log\20191011_132715\SystemConfigurationCheck_Report.htm

Thanks in advance!

Hi,

we are going to migrate SQL 2016 Enterprises to SQL 2017 Standard edition.

 what are the things to take care for this?

•   Compatibility?
•   can we upgrade SQL 2016 Ent to SQL 2017 Stand directly ( In-place upgrade)
•   we are using Rebuild with online /Table partition features in Enterprises. (what are the features differentiate with         standard)
•   Is there any difference in  Performance compare with SQL 2016 Ent vs SQL 2017Std.
• we configured Transnational Replication.