Hello, 

I am trying to import SQL Server Cumulative Updates into WSUS on Windows Server 2012 R2. In WSUS, I have all of the SQL products selected, as well as all of the classifications (feature packs, updates, service packs, etc.) selected.

When I try to import the Cumulative Updates (Like KB3144517) into WSUS, the "Import" button is greyed out and I get the error "This update cannot be imported into Windows Server Update Services, because it does not have the required applicability information."

I was told on another forum that it is highly recommended to not deploy updates via WSUS, but I am tasked with deploying the updates that way unless there is another way to mass-deploy Cumulative Updates to SQL Server.

Is there anything I may have misconfigured on my end, or a solution to fix this problem?

Thank you,

Sal

Hi, all

I have a licensing question for you. We have a Select Agreement (actually, an Enterprise Agreement) which includes SQL Server (2000, 2005, 2008). Some of us also have MSDN licenses. The MSDN versions may have been installed onto production servers. Is it possible to change the license number from that of the MSDN to our SA? I want to check to make sure that all of our production servers have the SA license number and not the MSDN so that we're in compliance.

Perhaps the broader question is whether or not it even matters. Does the license number in the software make a difference if we are paid up and licensed through the SA or EA?

Also, is the media/installation any different? I expect that the MSDN and Volume Licensing versions would be the same. It would be awful if we would have to re-install.

Again, I want to make sure that we're in compliance and won't hurt ourselves down the road. Thanks a ton!

Brian

Sr. DBA

Dear Team,

I have 3 Application server where SQL 2012 R2 enterprise was installed locally but not in use.

1) 1 Application server was pointing to remote datbase instance on other server

2) Other 2 were not at all using local or remote SQL instance

Here during implementation we forgot to uninstall the unused SQL installation on application server.

Here licensing compliance will be considered on number of SQL installation on each server or based on active or passive SQL instance use?

Please  reply.

Kamlesh Ambre

kamlesh

I do not want to duplicate a forum thread.  One of Microsoft MVP guys suggested to ask a question at Windows 10 updates and SQL Server forum.  Therefore I just post a link to my original thread

https://social.microsoft.com/Forums/en-US/337b2a2f-0d86-40b5-8c2e-19464edbe7a8/sql-server-2014-developer-on-windows-10-pro

I do not know where to post it.  I apologize if I violate forum  rules

I am trying to set up the database mail in SQL 2016.  I have tried several times and looked at many articles online.

I can stop and start the mail service and check the status and it will briefly show as receives_occurring, then it goes back to inactive.  I seem to be missing something simple.  I am doing this within SSMS by running a set of commands.

If anyone can provide some help, that would be greatly appreciated.

All test emails fail and no logs are present.

The emails sit in the queue waiting to be sent.

I have made sure to follow the setup instructions carefully and still I can't get this to work.

Kind regards

Tim

I have tried cleaning, then installing 2008 SQL server Express on Vista Ultimate 3 times and spent hours on this. I have installed regular SQL server on 2003 server with no issues many times, but I have huge issues with 2008 SQL server Express. I keep getting the proceeding errors.

Any ideas?

Configuration file:            C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20081202_010008\ConfigurationFile.ini

Detailed results:
  Feature:                       Database Engine Services
  Status:                        Failed: see logs for details
  MSI status:                    Passed
  Configuration status:          Failed: see details below
  Configuration error code:      0x0A2FBD17@1211@1
  Configuration error description: A MOF syntax error occurred.
  Configuration log:             C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20081202_010008\Detail.txt

  Feature:                       SQL Client Connectivity SDK
  Status:                        Passed
  MSI status:                    Passed
  Configuration status:          Passed

  Feature:                       SQL Server Replication
  Status:                        Failed: see logs for details
  MSI status:                    Passed
  Configuration status:          Failed: see details below
  Configuration error code:      0x0A2FBD17@1211@1
  Configuration error description: A MOF syntax error occurred.
  Configuration log:             C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20081202_010008\Detail.txt

  Feature:                       Management Tools - Basic
  Status:                        Failed: see logs for details
  MSI status:                    Passed
  Configuration status:          Failed: see details below
  Configuration error code:      0x0A2FBD17@1211@1
  Configuration error description: A MOF syntax error occurred.
  Configuration log:             C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20081202_010008\Detail.txt

Rules with failures:

Global rules:

Scenario specific rules:

Rules report file:               C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20081202_010008\SystemConfigurationCheck_Report.htm

Hi,

Where can I get the SQL Server 2008 R2 Standard or Developer version (not sure if it exists)?

Does the SQL Server 2014 support database downgrade to SQL Server 2008 R2?

Trying to restore a Db backed up on ver. 11.009120.
My SQL Server 2012 is ver. 11.00.2218

Any suggestions for remedies?

Thanks!

RICHARDG

Microsoft SQL Server 2014 SP1 Cumulative Update (CU) 7 KB3162659 - Error 0x80070643 can't pass this error.

Please help

Hi All.  Hoping someone might be able to point me in the right direction:

Scenario:

2 Node Cluster:
Identical HPE DL360 Servers (Server A, Server B)
Server 2012 R2 (Windows Update installs current)
Clustered with WSFC

iSCSI SAN Storage:
7 LUNs configured:
0 - Quorum Witness
1,4 - Data for ServerA, ServerB
2,5 - Logs for ServerA, ServerB
3,6 - TempDB for ServerA, ServerB

Cluster:
All disks are added to the cluster and Cluster Storage Volumes. LUN0 is successfully the Quorum Disk Witness

Network:
192.168.x - Domain Network (priority)
10.x - SAN Network
Active Directory (each machine is a member, Cluster is in DNS and AD)

Situation:

I'm not receiving any errors in Windows Event Viewer or WSFC for disk, network or clustering.

I run the SQL Server 2014 Failover Cluster Installation (Not Advanced Installation). For Data Directories, I use the ServerA Data, Logs and Temp_DB CSVs.  (Will use ServerB volumes when installing the second Node on ServerB). The installation begins successfully, then I get this error.

  Error description:             Could not add cluster access for SID 'S-1-5-80-3880718306-3832830129-1677859214-2598158968-1052248003'. Error: There was a failure to call cluster code from a provider. Exception message: The cluster resource could not be found.  .
  Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.4100.1&EvtType=0xD760FD9B%400x0ECC8CBC&EvtType=0xD760FD9B%400x0ECC8CBC
I get this for the Database Engine Services, Data Quality services, Full-Text and Semantic Extractions for Search, and SQL Server Replication. Clicking the link takes me to the Microsoft homepage/store. Many links I look at are for VMs or older versions of SQL. Nothing seems to describe why this failed.  Thoughts?

Detailed Summary File:

Overall summary:
  Final result:                  Failed: see details below
  Exit code (Decimal):           -2032664555
  Start time:                    2016-07-25 13:29:24
  End time:                      2016-07-25 15:07:48
  Requested action:              InstallFailoverCluster

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

Cluster properties:
  Machine name: SERVERA
  Product              Instance             Instance ID                    Feature                                  Language             Edition              Version         Clustered  Configured

  Machine name: SERVERB
  Product              Instance             Instance ID                    Feature                                  Language             Edition              Version         Clustered  Configured

Machine Properties:
  Machine name:                  HPDL360-160504F
  Machine processor count:       28
  OS version:                    Windows Server 2012
  OS service pack:              
  OS region:                     United States
  OS language:                   English (United States)
  OS architecture:               x64
  Process architecture:          64 Bit
  OS clustered:                  Yes

Product features discovered:
  Product              Instance             Instance ID                    Feature                                  Language             Edition              Version         Clustered  Configured

Package properties:
  Description:                   Microsoft SQL Server 2014
  ProductName:                   SQL Server 2014
  Type:                          RTM
  Version:                       12
  Installation location:         D:\SQLSvrEnt_2014SP1_ENU_X64\x64\setup\
  Installation edition:          Standard

  Slipstream:                    True
  SP Level                       1

Product Update Status:
  Success: KB 3058865

Product Updates Selected for Installation:
  Title:                         Microsoft SQL Server 2014  with SP1
  Knowledge Based Article:       KB 3058865
  Version:                       12.1.4100.0
  Architecture:                  x64
  Language:                      1033

  Update Source:                 Slipstream

User Input Settings:
  ACTION:                        InstallFailoverCluster
  AGTDOMAINGROUP:                <empty>
  AGTSVCACCOUNT:                 domain\sqlagent
  AGTSVCPASSWORD:                *****
  ASBACKUPDIR:                   Backup
  ASCOLLATION:                   Latin1_General_CI_AS
  ASCONFIGDIR:                   Config
  ASDATADIR:                     Data
  ASLOGDIR:                      Log
  ASPROVIDERMSOLAP:              1
  ASSERVERMODE:                  MULTIDIMENSIONAL
  ASSVCACCOUNT:                  <empty>
  ASSVCPASSWORD:                 <empty>
  ASSVCSTARTUPTYPE:              Automatic
  ASSYSADMINACCOUNTS:            <empty>
  ASTEMPDIR:                     Temp
  COMMFABRICENCRYPTION:          0
  COMMFABRICNETWORKLEVEL:        0
  COMMFABRICPORT:                0
  CONFIGURATIONFILE:             C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20160725_132924\ConfigurationFile.ini
  ENU:                           true
  ERRORREPORTING:                false
  FAILOVERCLUSTERDISKS:          SQLA_Data, SQLA_Logs, SQLA_TempDB
  FAILOVERCLUSTERGROUP:          SQL Server (GreatPlains)
  FAILOVERCLUSTERIPADDRESSES:    IPv4;192.168.0.23;Domain Network;255.255.255.0
  FAILOVERCLUSTERNETWORKNAME:    SQLClusterGP
  FEATURES:                      SQLENGINE, REPLICATION, FULLTEXT, DQ, SSMS, ADV_SSMS
  FILESTREAMLEVEL:               0
  FILESTREAMSHARENAME:           <empty>
  FTSVCACCOUNT:                  NT Service\MSSQLFDLauncher
  FTSVCPASSWORD:                 <empty>
  HELP:                          false
  IACCEPTSQLSERVERLICENSETERMS:  true
  INDICATEPROGRESS:              false
  INSTALLSHAREDDIR:              D:\Program Files\Microsoft SQL Server\
  INSTALLSHAREDWOWDIR:           D:\Program Files (x86)\Microsoft SQL Server\
  INSTALLSQLDATADIR:             C:\ClusterStorage\SQLA_Data
  INSTANCEDIR:                   D:\Program Files\Microsoft SQL Server\
  INSTANCEID:                    MSSQLSERVER
  INSTANCENAME:                  MSSQLSERVER
  ISSVCACCOUNT:                  NT AUTHORITY\Network Service
  ISSVCPASSWORD:                 <empty>
  ISSVCSTARTUPTYPE:              Automatic
  MATRIXCMBRICKCOMMPORT:         0
  MATRIXCMSERVERNAME:            <empty>
  MATRIXNAME:                    <empty>
  PID:                           *****
  QUIET:                         false
  QUIETSIMPLE:                   false
  RSINSTALLMODE:                 DefaultNativeMode
  RSSHPINSTALLMODE:              DefaultSharePointMode
  RSSVCACCOUNT:                  <empty>
  RSSVCPASSWORD:                 <empty>
  RSSVCSTARTUPTYPE:              Automatic
  SAPWD:                         *****
  SECURITYMODE:                  SQL
  SQLBACKUPDIR:                  C:\ClusterStorage\SQLA_TempDB\MSSQL12.MSSQLSERVER\MSSQL\Data
  SQLCOLLATION:                  SQL_Latin1_General_CP1_CI_AS
  SQLSVCACCOUNT:                 domain\sqldb
  SQLSVCPASSWORD:                *****
  SQLSYSADMINACCOUNTS:           DOMAIN\administrator
  SQLTEMPDBDIR:                  C:\ClusterStorage\SQLA_TempDB\MSSQL12.MSSQLSERVER\MSSQL\Data
  SQLTEMPDBLOGDIR:               C:\ClusterStorage\SQLA_Logs\MSSQL12.MSSQLSERVER\MSSQL\Data
  SQLUSERDBDIR:                  <empty>
  SQLUSERDBLOGDIR:               C:\ClusterStorage\SQLA_Logs\MSSQL12.MSSQLSERVER\MSSQL\Data
  SQMREPORTING:                  false
  UIMODE:                        Normal
  UpdateEnabled:                 true
  UpdateSource:                  Slipstream
  USEMICROSOFTUPDATE:            false
  X86:                           false

  Configuration file:            C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20160725_132924\ConfigurationFile.ini

Detailed results:
  Feature:                       Management Tools - Complete
  Status:                        Passed

  Feature:                       Management Tools - Basic
  Status:                        Passed

  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, uninstall this feature, and then run the setup process again.
  Component name:                SQL Server Database Engine Services Instance Features
  Component error code:          0x86D80015
  Error description:             Could not add cluster access for SID 'S-1-5-80-3880718306-3832830129-1677859214-2598158968-1052248003'. Error: There was a failure to call cluster code from a provider. Exception message: The cluster resource could not be found.  .
  Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.4100.1&EvtType=0xD760FD9B%400x0ECC8CBC&EvtType=0xD760FD9B%400x0ECC8CBC

  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, uninstall this feature, and then run the setup process again.
  Component name:                SQL Server Database Engine Services Instance Features
  Component error code:          0x86D80015
  Error description:             Could not add cluster access for SID 'S-1-5-80-3880718306-3832830129-1677859214-2598158968-1052248003'. Error: There was a failure to call cluster code from a provider. Exception message: The cluster resource could not be found.  .
  Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.4100.1&EvtType=0xD760FD9B%400x0ECC8CBC&EvtType=0xD760FD9B%400x0ECC8CBC

  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, uninstall this feature, and then run the setup process again.
  Component name:                SQL Server Database Engine Services Instance Features
  Component error code:          0x86D80015
  Error description:             Could not add cluster access for SID 'S-1-5-80-3880718306-3832830129-1677859214-2598158968-1052248003'. Error: There was a failure to call cluster code from a provider. Exception message: The cluster resource could not be found.  .
  Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.4100.1&EvtType=0xD760FD9B%400x0ECC8CBC&EvtType=0xD760FD9B%400x0ECC8CBC

  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, uninstall this feature, and then run the setup process again.
  Component name:                SQL Server Database Engine Services Instance Features
  Component error code:          0x86D80015
  Error description:             Could not add cluster access for SID 'S-1-5-80-3880718306-3832830129-1677859214-2598158968-1052248003'. Error: There was a failure to call cluster code from a provider. Exception message: The cluster resource could not be found.  .
  Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.4100.1&EvtType=0xD760FD9B%400x0ECC8CBC&EvtType=0xD760FD9B%400x0ECC8CBC

  Feature:                       SQL Browser
  Status:                        Passed

  Feature:                       SQL Writer
  Status:                        Passed

  Feature:                       SQL Client Connectivity
  Status:                        Passed

  Feature:                       SQL Client Connectivity SDK
  Status:                        Passed

  Feature:                       Setup Support Files
  Status:                        Passed

Rules with failures:

Global rules:

There are no scenario-specific rules.

Rules report file:               C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20160725_132924\SystemConfigurationCheck_Report.htm

Have an interesting situation.

I have a NeverFail cluster on which I loaded SQL Server 2005 and SP1.

All was great. Both nodes had no issues with the initial setup or the SP1 update.

When I forced a failover to the inactive node, MOST of the services like SSIS, Full-Text and SQL Browser came up like a champ.

BUT ... the SQL Server service and the SQL Agent did not come up (or shall I say not fully).

I am now looking at the SQL Server Configuration Manager and I see the following for the SQL Server service:

"Name"      shows the RED block icon for the SQL Server

"State"       shows "Change pending ..."

"Start Mode" is set to Manual

"Log on as"   has my domain account listed

"Process ID"   has the number 2956 (so it has started somewhat).

I then click open the SQL Service item and it shows that it is stopped.

I am given the option to START the service. When I try to start it, the meter bar comes up and moves slowly to the end and then an error returns of ...

"The request failed or the service did not respond in a timely manner. Consult the event log or other applicable errors logs for details"

If I look under windows Services in the Admin Tools section... I see the services for SSIS, FT and Browser listed and started BUT I see SQL Server says its "starting".

If I click open the service from here, once again it show "starting" and all of the option buttons to Stop-Start-Pause-Resume are grayed out and I am not able to use them.

I have looked in the Windows Event Logs for any events but none are present. 

Now I know why the SQL Agent is not running, and of course that is due to is dependency on SQL Server being up and running.

First off WHAT does the "Change pending" message mean?

Then what other logs can I look at for some help or is there someone who has the answers to this dilemma.

Thanks and have a great evening

I have Signed up for SQL sever on Linux evaluation.

On March 16th, I received a download link from SQL server community for release candidate of SQL Server 2016.

But the link takes me to regular SQL server download page.

Was anyone able to successfully install SQL server on linux using the link provided in community newsletter?

Hi All,

I'm getting that error while trying to install SQL Server 2012 from removable media and I have a requirement to install the SQL Server from Removable Media.

All of our customers use DVDs to install SQL Server as per their requirement.

So please guide me the way to overcome this error, I cannot ask my customers to copy the setup folder to the hard drive.

Please help me in resolving the issue.

Best Regards

Shamsheer 

Hi,

I have a couple of databases on Sql 2005 (w 2003 server). 

I want to have them (start with one) on a different SQL server (sql 2008R2 on w 2008R2).

I saw a few kBs but still not sure what is the simplest way to go about that. Would appreciate if anyone can give some suggestions or steps. 

Not sure it matters, but both these servers are on different domains. People access these databases via ODBC connection using SQL server authentication (not windows), which will be same on the new server as well.

Thanks,

Ashok

hi there,i am trying to install sql server 2014 developer edition in windows 8.1.Byt I am getting the error.The program can't start because the sqlsetupbootstrapper.dll is missing in your computer and I also found that this dll is available in the .iso file of the server downloaded from Microsoft.

Sumit Bhargav

The database 'C:\Database.mdf' cannot be opened because it is version 852. This server supports version 851 and earlier. A downgrade path is not supported.
Could not open new database 'C:\Database.mdf'. CREATE DATABASE is aborted.
An attempt to attach an auto-named database for file C:\Database.mdf failed. A database with the same name exists, or specified file cannot be opened, or it is located on UNC share.

I'm receiving this error on another computer. How can i upgrade to version 852?

Dear colleagues at the community:

I went to https://myprodscussu1.app.vssubscriptions.visualstudio.com/Downloads?PId=2057 and downloaded the installer for SQL Server 2016 Developer Edition.

I opted to do a full install (all checkboxes selected), but during the installation process, at the "Ready to Install" step, my installation breaks, returning the message that this MSI package is necessary: sql_tools_extensions.msi

I opened the ISO I downloaded and also went to the directort where I uncompressed the installation files and found no occurrence ofsql_tools_extensions.msi. So, I downloaded the ISO again, but it looks like there is no sql_tools_extensions.msi in the package.

I understand that, as a case of a new release, things may be missing.

So I would like to know:

1. In practice, what is that sql_tools_extensions.msi file necessary for?
2. What options should I uncheck in the installation process so I can have my SQL Server working at least with basic functionality and SSRS?
3. Will that affect any SSRS experience I will make?
4. Is there any way I can get the sql_tools_extensions.msi file so I may go on with my full install?

Thank you in advance.

All the best,

- Pedro.

When R service(in-database) installed in SQL 2016 Enterprise Edition, The launchpad service worked fine. After two days, the service was stoped and it can't be re-started again. The popup message is "Error 1053: The service did not respond to the start or control request in a timely fashion". In the log file EXTLaunchErrorLog, the message is "SetNecessaryPrivileges failed. ErrorCode: 0x80040004".

I would appreciate any help!

Thanks,

Andrew66sql