We recently upgraded to SentryOne V19.0.1 and the performance monitoring tool shows several sections where there is no data available. 

Looking at the performance counters on an instance that does show all of the graphs as working and comparing it to my instances that do not I see that there are no SQL Server performance counters at all on my servers that are not working. 

I have found the sql-performance-counters-are-missing guide on this site but am getting stuck partway through the repair process.

But the issue I am having is I do not see the perf- MSSQL$InstanceNameqlctr.ini file anywhere in the BINN directory to rebuild the performance counters from.  Is there a way for me to get a generic version of this file I could use to rebuild all of my servers' performance counters or is it specific to each server where I need to do something to generate the file again? 

Is it possible the file is somewhere else I just don't know to look? I saw the first part of the post that says the best way to deal with this is to reinstall SQL Server but I guess I am hoping there is a way to not have to do that as all of our servers are live and in various environments being used daily.

Hello,

I am quite new to SQL SERVER. I have installed windows 10 Pro and I need to install SQLSERVER 2017. The first time I tried it out, I couldn't install correctly. Then, I installed Microsoft Visual C++ 2015 Redistributable and now on the Feature Selection window I get this message: Microsoft Visual Studio Tools for Application 2015 to be installed! I checked my programs and features and see this is installed already on my computer! What should I do to be able to get it recognized by SQLSERVER 2017?

Thank you very much

Hi,

I am having upgrade issues when attempting to perform an inplace upgrade from MS SQL Server 2012 SP3 (Running on Windows Server 2012 R2) to Windows Server 2017 (SW_DVD9_NTRL_SQL_Svr_Standard_Edtn_2017_64Bit_English_OEM_VL_X21-56945)

The Installation fails during the upgrade process:

Feature:                      Database Engine Services
Status:                        Failed
Reason for failure:        An error occurred during the setup process of the feature.
Next Step:                   The upgrade process for SQL Server failed. Use the following information to resolve the error, and                                            then repair your installation by using this command line: setup /action=repair                                                                        /instancename=MSSQLSERVER
Component name:                SQL Server Database Engine Services Instance Features
Component error code:          0x851A001A
Error description:             Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential                                             causes.

Error Log states:

2019-03-19 16:14:27.18 spid5s      ---------------------------------------------
2019-03-19 16:14:27.18 spid5s      Starting execution of ISServer_upgrade.SQL
2019-03-19 16:14:27.18 spid5s      ---------------------------------------------
2019-03-19 16:14:27.18 spid5s       
2019-03-19 16:14:27.18 spid5s      Taking SSISDB to single user mode
2019-03-19 16:14:27.18 spid5s      Setting database option SINGLE_USER to ON for database 'SSISDB'.
2019-03-19 16:14:27.70 spid5s      Error: 1712, Severity: 16, State: 1.
2019-03-19 16:14:27.70 spid5s      Online index operations can only be performed in Enterprise edition of SQL Server.
2019-03-19 16:14:27.70 spid5s      Error: 917, Severity: 15, State: 1.
2019-03-19 16:14:27.70 spid5s      An upgrade script batch failed to execute for database 'master' due to compilation error. Check the previous error message for the line which caused compilation to fail.
2019-03-19 16:14:27.70 spid5s      Error: 912, Severity: 21, State: 2.
2019-03-19 16:14:27.70 spid5s      Script level upgrade for database 'master' failed because upgrade step 'ISServer_upgrade.sql' encountered error 917, state 1, severity 15. This is a serious error condition which might interfere with regular operation and the database will be taken offline. If the error happened during upgrade of the 'master' database, it will prevent the entire SQL Server instance from starting. Examine the previous errorlog entries for errors, take the appropriate corrective actions and re-start the database so that the script upgrade steps run to completion.
2019-03-19 16:14:27.70 spid5s      Error: 3417, Severity: 21, State: 3.
2019-03-19 16:14:27.70 spid5s      Cannot recover the master database. SQL Server is unable to run. Restore master from a full backup, repair it, or rebuild it. For more information about how to rebuild the master database, see SQL Server Books Online.
2019-03-19 16:14:27.70 spid5s      SQL Server shutdown has been initiated
2019-03-19 16:14:27.70 spid5s      SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.
2019-03-19 16:14:28.73 spid5s      Error: 25725, Severity: 16, State: 1.
2019-03-19 16:14:28.73 spid5s      An error occurred while trying to flush all running Extended Event sessions.  Some events may be lost.

Details Log

(01) 2019-03-19 16:20:14 Slp: Error result: -2061893606
(01) 2019-03-19 16:20:14 Slp: Result facility code: 1306
(01) 2019-03-19 16:20:14 Slp: Result error code: 26
(01) 2019-03-19 16:20:14 Slp: WER: Application level consent value 'True' was mapped to consent status 'WerConsentApproved'
(01) 2019-03-19 16:20:17 Slp: WER: Result of the submission:: 'WerReportUploaded'
(01) 2019-03-19 16:20:17 Slp: WER: Submitted 1 of 1 failures to the Watson data repository
(01) 2019-03-19 16:20:17 Slp: SetupTelemetry: Closing Telemetry Session
(01) 2019-03-19 16:20:17 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine 
(01) 2019-03-19 16:20:17 Slp: Sco: Attempting to open registry subkey SOFTWARE\Microsoft\SQMClient
(01) 2019-03-19 16:20:17 Slp: Sco: Attempting to get registry value MachineId
(01) 2019-03-19 16:20:17 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine 
(01) 2019-03-19 16:20:17 Slp: Sco: Attempting to open registry subkey Software\Microsoft\Microsoft SQL Server\140
(01) 2019-03-19 16:20:17 Slp: SetupTelemetry: Not creating telemetry audit log. Value 'UserRequestedLocalAuditDirectory' doesn't exist in 'HKLM\Software\Microsoft\Microsoft SQL Server\140'
(01) 2019-03-19 16:20:17 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine 
(01) 2019-03-19 16:20:17 Slp: Sco: Attempting to open registry subkey Software\Microsoft\Microsoft SQL Server\140
(01) 2019-03-19 16:20:17 Slp: Sco: Attempting to get registry value CustomerFeedback
(01) 2019-03-19 16:20:17 Slp: Sco: Attempting to get registry value EnableErrorReporting
(01) 2019-03-19 16:20:17 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine 
(01) 2019-03-19 16:20:17 Slp: Sco: Attempting to open registry subkey Software\Microsoft\Microsoft SQL Server\Instance Names
(01) 2019-03-19 16:20:17 Slp: Sco: Attempting to open registry subkey SQL
(01) 2019-03-19 16:20:17 Slp: Sco: Attempting to get registry value MSSQLSERVER
(01) 2019-03-19 16:20:17 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine 
(01) 2019-03-19 16:20:17 Slp: Sco: Attempting to open registry subkey Software\Microsoft\Microsoft SQL Server\MSSQL14.MSSQLSERVER\CPE
(01) 2019-03-19 16:20:17 Slp: Sco: Attempting to get registry value CustomerFeedback
(01) 2019-03-19 16:20:17 Slp: Sco: Attempting to get registry value EnableErrorReporting
(01) 2019-03-19 16:20:17 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine 
(01) 2019-03-19 16:20:17 Slp: Sco: Attempting to open registry subkey Software\Microsoft\Microsoft SQL Server\Instance Names
(01) 2019-03-19 16:20:17 Slp: Sco: Attempting to open registry subkey OLAP
(01) 2019-03-19 16:20:17 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine 
(01) 2019-03-19 16:20:17 Slp: Sco: Attempting to open registry subkey Software\Microsoft\Microsoft SQL Server\Instance Names
(01) 2019-03-19 16:20:17 Slp: Sco: Attempting to open registry subkey RS
(01) 2019-03-19 16:20:17 Slp: SetupTelemetry: Telemetry has an active session with 157 events.

Any help would be appreciated.

Regards

Lost

Hi

We have an internal development environment with SQL Server 2014 - It is used to develop and test new data features and is not used or view able to any one outside the development/QA team. Once the data has been approved by the QA team it gets backed up and then the backup file is restored in to a totally separate production environment. 

It seems we have to have full SQL Server licences for both environments - consequently we are not able to upgrade to the latest SQL server versions because of the costs of licensing the two environments. 

Is this approach correct or is it an over zealous approach to the licencing requirements? 

If this is the right licensing approach then it is very frustrating that we can not able to move forward and upgrade to the latest & greatest versions (because of the cost of licensing 2 separate environments) and regrettably we will almost certainly have to look to ditch SQL Server and use an alternative database. 

Many thanks

Chris

I added a new node to a SQL Server failover cluster. When i was trying to update the SQL server 2008  r2 with SP2 on the New node I got an error . All the existing nodes already have  SQL Server service SP2, so the new node also needs to be SP2. I am getting the missing msi file error when applying SP2 to the new node.

SQL Server Setup has encountered the following error:

The cached MSI file 'C:\Windows\Installer\df540d0.msi' is missing.
Its original file is 'sql_engine_core_inst_loc.msi' and it was installed for product 'SQL Server 2008 R2 Database Engine Services'
from 'E:\en_sqlserver2008r2ent_x86_x64\1033_ENU_LP\x64\setup\sql_engine_core_inst_loc_msi\',
 version '10.50.1600.1', language 'ENU'.
To resolve this problem, recover the missing file from the installation media and start setup again.
For more information about how to resolve this problem, see 'Steps to restore the missing Windows Installer cache files' (http://go.microsoft.com/fwlink/?LinkId=144387)  in the Microsoft Knowledge Base.

Error code 0x84B20002.

My questions are:

1) how do the msi files become missing? Are they deleted automatically or do they get deleted manually?

2) I have read articles online about how to resolve the problem. But what i need to know is how and why do the files get missing?

Hi...got couple of questions, your help is really appreciable

1. If i install SQL Server 2017 Developer/Standard/Enterprise Edition using msdn subscriptions and can it be converted to licensed Standard Edition?

Do i need to uninstall the existing msdn subscription and re-install a licensed standard edition?

2. If i download the developer edition and can it be later upgraded to Standard Edition?

  Do i need to uninstall the instance completely and reinstall the licensed standard version of SQL 2017?

Please let me know, if my question is not clear.

Hi, could you please advice?

Error code: -2068119551

This might be simple, but I have missed something.

Got SQL Server 2016 installed on Win Core Server OS, as requested by my Windows Admin Team, BUT how do I run the SP1 & SP2 upgrades?  The standard SP1 package extracts as expected then nothing happens.  Is there a flag I need to use to tell it to run without the GUI or a separate package I need to download … OR even something simpler that I am missing?

Any info would be greatly appreciated.

Thanks,

DeWayne

  i am installing sql 2012 and getting error wait on database engine handle recovery failed. i  changed the credentials to "NT Authority\NETWORK SERVICE" but getting same error.

logs attached below :

     -T 8015
     -d "C:\Program Files\Microsoft SQL Server\MSSQL11.UBL\MSSQL\Template Data\master.mdf"
     -l "C:\Program Files\Microsoft SQL Server\MSSQL11.UBL\MSSQL\Template Data\mastlog.ldf"
2019-03-22 16:23:29.98 Server      SQL Server detected 1 sockets with 2 cores per socket and 2 logical processors per socket, 2 total logical processors; using 2 logical processors based on SQL Server licensing. This is an informational message; no user action is required.
2019-03-22 16:23:29.98 Server      SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2019-03-22 16:23:29.98 Server      Detected 16383 MB of RAM. This is an informational message; no user action is required.
2019-03-22 16:23:29.98 Server      Using conventional memory in the memory manager.
2019-03-22 16:23:30.28 Server      Perfmon counters for resource governor pools and groups failed to initialize and are disabled.
2019-03-22 16:23:30.40 Server      Node configuration: node 0: CPU mask: 0x0000000000000003:0 Active CPU mask: 0x0000000000000003:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2019-03-22 16:23:30.56 Server      Using dynamic lock allocation.  Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node.  This is an informational message only.  No user action is required.
2019-03-22 16:23:30.58 Server      Database Mirroring Transport is disabled in the endpoint configuration.
2019-03-22 16:23:30.58 Server      Software Usage Metrics is disabled.
2019-03-22 16:23:30.59 spid7s      Warning ******************
2019-03-22 16:23:30.61 spid7s      SQL Server started in single-user mode. This an informational message only. No user action is required.
2019-03-22 16:23:30.62 spid7s      Starting up database 'master'.
2019-03-22 16:23:30.65 Server      CLR version v4.0.30319 loaded.
2019-03-22 16:23:31.04 spid7s      SQL Server Audit is starting the audits. This is an informational message. No user action is required.
2019-03-22 16:23:31.05 spid7s      SQL Server Audit has started the audits. This is an informational message. No user action is required.
2019-03-22 16:23:31.12 spid7s      SQL Trace ID 1 was started by login "sa".
2019-03-22 16:23:31.14 spid7s      Server name is 'TDL-EQ-SYSTEM\UBL'. This is an informational message only. No user action is required.
2019-03-22 16:23:31.18 spid11s     Password policy update was successful.
2019-03-22 16:23:31.18 spid7s      Failed to verify Authenticode signature on DLL 'C:\Program Files\Microsoft SQL Server\MSSQL11.UBL\MSSQL\Binn\ftimport.dll'.
2019-03-22 16:23:31.18 spid11s     Error: 26011, Severity: 16, State: 1.
2019-03-22 16:23:31.18 spid11s     The server was unable to initialize encryption because of a problem with a security library. The security library may be missing. Verify that security.dll exists on the system.
2019-03-22 16:23:31.19 spid7s      Starting up database 'msdb'.
2019-03-22 16:23:31.19 spid9s      Starting up database 'mssqlsystemresource'.
2019-03-22 16:23:31.22 spid11s     Error: 17182, Severity: 16, State: 1.
2019-03-22 16:23:31.22 spid11s     TDSSNIClient initialization failed with error 0x139f, status code 0x80. Reason: Unable to initialize SSL support. The group or resource is not in the correct state to perform the requested operation.
2019-03-22 16:23:31.22 spid11s     Error: 17182, Severity: 16, State: 1.
2019-03-22 16:23:31.22 spid11s     TDSSNIClient initialization failed with error 0x139f, status code 0x1. Reason: Initialization failed with an infrastructure error. Check for previous errors. The group or resource is not in the correct state to perform the requested operation.
2019-03-22 16:23:31.23 spid11s     Error: 17826, Severity: 18, State: 3.
2019-03-22 16:23:31.23 spid11s     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.
2019-03-22 16:23:31.23 spid11s     Error: 17120, Severity: 16, State: 1.
2019-03-22 16:23:31.23 spid11s     SQL Server could not spawn FRunCommunicationsManager thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.

Hi ,

There are many store procedure start with dt_ like dbo.dt_addtosourcecontrol,dt_addseroobject etc..

On same database they are t listed in System Stored Procedure. and same instance other database they are not innot listed in System Stored  Procedure but outside.

When i am running Generate Script wizards than they become part of user store procedure .

What exactly they are and why at diffreent loaction ( i mean inside or otside of System Stored Procedure) .

Regards,

Deepak

I'm trying to install SQL Server 2012 with SP1 on a laptop with Windows 7, but I'm getting an error immediately upon clicking setup.exe. Unfortunately, it's not a very helpful error message:

I've checked the prerequisites - I have .NET Framework v4 and v3.5, and Windows Powershell v2 installed. I currently have SQL 2008 R2. I've tried stopping all of the SQL services, but that didn't make any difference. Any ideas what I should look at next?

Hi

I have to install SSIS in the server on which Database engine & SSRS  is already installed in that machine 

what is the best practice of installing SSIS on top of DB engine

do we need to stop the DB engine service , SSRS services  and continue SSIS installation . 

is there any other points i need to focous while installing please do share me 

hemadri

Dear fellows,

kindly advise what are the drawbacks on installing sql serer 2014 on windows server 2008.

Regards

Has anyone had issues with SQL Server 2017 on server 2019? So far two servers have imploded!!

https://social.technet.microsoft.com/Forums/windowsserver/en-US/79c5b44a-7b5f-46ed-b3be-5d4969e9a3e0/bex64-ucrtbasedll-explorerexe-crash?forum=ws2019&prof=required

Thanks

I have a customer in need of a new server.  They are a local public library so funds are an issue.

The software that they use is based off of SQL 2014 at this point. (Not sure if they need to upgrade that also)

I am attempting to find out if SQL will install and run on the Windows Essential Server 2019 platform.  (Obviously Essentials is more reasonable so that would be the preferred platform otherwise, 2019 standard is next in line)

At this point the information that I have been able to access has done nothing but muddy the waters (some say yes while others say no)

Any assistance is appreciated.

John Huber

Hello all,

I am going to perform a rolling upgrade to my physical Hosts from 2012 R2 to Server 2016 Hyper-V to gain access to VHD Sets.  I have a 2 node Hyper-V 2012 R2 Guest Cluster running SQL Clustering in active/passive on this physical cluster.  I need to accomplish getting these 2 guest cluster nodes upgraded to Server 2016 after the physical hosts are done.

How do I perform the SQL portion in terms of the rolling upgrade?  Do I first run SQL Server setup and remove one node from the SQL Cluster and then evict it from the Windows cluster, upgrade it, bring it back into the Windows cluster and then run SQL Setup again and add it back into the SQL Cluster?

I am very comfortable doing these rolling upgrades in Windows Clusters/Hyper-v etc. but I have never tried to do one running a SQL Cluster.

Would someone please let me know what the steps would be to accomplish this?

Thanks!

I am trying to install SQL 2019 Preview on RHEL 7.6 .  When configuring mssql , it failed with following errors:

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

2019-01-25 11:44:06.39 spid23s     Server failed to listen on 'any' <ipv6> 1433. Error: 0x2742. To proceed, notify your system administrator.

2019-01-25 11:44:06.39 spid23s     Error: 17182, Severity: 16, State: 1.

2019-01-25 11:44:06.39 spid23s     TDSSNIClient initialization failed with error 0x2742, status code 0xa. Reason: Unable to initialize the TCP/IP listener. A socket operation encountered a dead network.

2019-01-25 11:44:06.39 spid23s     Error: 17182, Severity: 16, State: 1.

2019-01-25 11:44:06.39 spid23s     TDSSNIClient initialization failed with error 0x2742, status code 0x1. Reason: Initialization failed with an infrastructure error. Check for previous errors. A socket operation encountered a dead network.

2019-01-25 11:44:06.40 spid23s     Error: 17826, Severity: 18, State: 3.

2019-01-25 11:44:06.40 spid23s     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.

2019-01-25 11:44:06.40 spid23s     Error: 17120, Severity: 16, State: 1.

2019-01-25 11:44:06.40 spid23s     SQL Server could not spawn FRunCommunicationsManager thread. Check the SQL Server error log and the operating system error log for information about possible related problems.

S.Prema