Hi,
One guy had ordered a server with OS and SQL. Due to some process failure, he lacked SQL server license, so he installed evaluate version of SQL 2016 upon project deployment. Then -as a delivery correction- he received the OEM license for SQL but it has a different license key than required for Eval activation. Can we expect kind of product/key exchange from Microsoft?
If not, does he have to perform kind of Clean Reinstallation, or simple reinstallation could solve his issue?
I'm trying to install Microsoft SQL Server 2016 Developer edition on my home computer for educational purposes. At first, the Database Engine Services would not install. Five days later, I've tried much to no avail, including the instructions found in:
http://social.technet.microsoft.com/wiki/contents/articles/24364.sql-server-troubleshooting-could-not-find-database-engine-startup-handle-error-during-installation.aspx
Following multiple installs/uninstalls, and now a registry key deletion, I've gotten various errors including (1) "Wait on the Database Engine recovery handle failed", and (2) "Object reference not set to an instance of an object."
How much more of this before I must go onto suicide watch? Any help is appreciated.
Overall summary: Final result: Failed: see details below Exit code (Decimal): -2147467261 Start time: 2016-11-23 04:30:07 End time: 2016-11-23 04:41:17 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, uninstall this feature, and then run the setup process again. Machine Properties: Machine name: XPS Machine processor count: 4 OS version: Microsoft Windows 10 Home (10.0.14393) 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 SQL Server 2016 SSMS 1033 13.0.16000.28 No Yes SQL Server 2016 Adv_SSMS 1033 13.0.16000.28 No Yes Package properties: Description: Microsoft SQL Server 2016 ProductName: SQL Server 2016 Type: RTM Version: 13 Installation location: E:\x64\setup\ Installation edition: Developer Slipstream: True SP Level 1 Product Update Status: Success: KB 3182545 Product Updates Selected for Installation: Title: Microsoft SQL Server 2016 with SP1 Knowledge Based Article: KB 3182545 Version: 13.1.4001.0 Architecture: x64 Language: 1033 Update Source: Slipstream User Input Settings: ACTION: Install ADDCURRENTUSERASSQLADMIN: false AGTSVCACCOUNT: NT Service\SQLSERVERAGENT AGTSVCPASSWORD: ***** AGTSVCSTARTUPTYPE: Manual 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> 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: C:\Program Files\Microsoft SQL Server\130\Setup Bootstrap\Log\20161123_042941\ConfigurationFile.ini CTLRSTARTUPTYPE: 0 CTLRSVCACCOUNT: <empty> CTLRSVCPASSWORD: <empty> CTLRUSERS: <empty> ENABLERANU: false ENU: true EXTSVCACCOUNT: <empty> EXTSVCPASSWORD: <empty> FEATURES: SQLENGINE, CONN FILESTREAMLEVEL: 0 FILESTREAMSHARENAME: <empty> FTSVCACCOUNT: <empty> FTSVCPASSWORD: <empty> HELP: 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: MSSQLSERVER INSTANCENAME: MSSQLSERVER ISSVCACCOUNT: NT AUTHORITY\Network Service ISSVCPASSWORD: <empty> ISSVCSTARTUPTYPE: Automatic ISTELSVCACCT: <empty> ISTELSVCPASSWORD: <empty> ISTELSVCSTARTUPTYPE: 0 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: RSINSTALLMODE: DefaultNativeMode RSSHPINSTALLMODE: DefaultSharePointMode RSSVCACCOUNT: <empty> RSSVCPASSWORD: <empty> RSSVCSTARTUPTYPE: Automatic SAPWD: ***** SECURITYMODE: SQL SQLBACKUPDIR: <empty> SQLCOLLATION: SQL_Latin1_General_CP1_CI_AS SQLSVCACCOUNT: NT AUTHORITY\SYSTEM SQLSVCINSTANTFILEINIT: false SQLSVCPASSWORD: ***** SQLSVCSTARTUPTYPE: Automatic SQLSYSADMINACCOUNTS: XPS\Joseph SQLTELSVCACCT: NT Service\SQLTELEMETRY SQLTELSVCPASSWORD: <empty> SQLTELSVCSTARTUPTYPE: Automatic SQLTEMPDBDIR: <empty> SQLTEMPDBFILECOUNT: 4 SQLTEMPDBFILEGROWTH: 64 SQLTEMPDBFILESIZE: 8 SQLTEMPDBLOGDIR: <empty> SQLTEMPDBLOGFILEGROWTH: 64 SQLTEMPDBLOGFILESIZE: 8 SQLUSERDBDIR: <empty> SQLUSERDBLOGDIR: <empty> SUPPRESSPRIVACYSTATEMENTNOTICE: false TCPENABLED: 0 UIMODE: Normal UpdateEnabled: true UpdateSource: Slipstream USEMICROSOFTUPDATE: false X86: false Configuration file: C:\Program Files\Microsoft SQL Server\130\Setup Bootstrap\Log\20161123_042941\ConfigurationFile.ini Detailed results: Feature: Client Tools Connectivity 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: -2147467261 Error description: Object reference not set to an instance of an object. 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=0x9C8C9C81%400x44A889F9&EvtType=0x9C8C9C81%400x44A889F9 Feature: SQL Browser Status: Passed Feature: SQL Writer Status: Passed Feature: SQL Client Connectivity Status: Passed Feature: SQL Client Connectivity SDK Status: Passed Rules with failures: Global rules: Scenario specific rules: Rules report file: C:\Program Files\Microsoft SQL Server\130\Setup Bootstrap\Log\20161123_042941\SystemConfigurationCheck_Report.htm
Cannot install SQL 2016 correctly.
When the installation is almost done it will have a dialog box saying "Object references not set to an instance of an object".
Then when the installation finished, it says some feature failed, one of which is Database Service Engine.
And once I tried connecting to the database engine I could not login with my windows authentication or the SQL server authentication for SA user, But I can connect to the analysis server.
Then Configuration manages doe not show the SQL services, it says "MMC could not create the snap-in. The snap-in might not have been installed correctly."
My machine is a Windows 10.
Apologies as I still can't upload images or URLs as my account is still to be verified,
Please help.
I'm running windows 8.1, SSMS 17 and Visual Studio 2017 CE. When I open SSMS and either connect to a server or click cancel in the opening dialog box I get an error that my license for Visual Studio has expired. When I click close on the error dialog, SSMS exits. Visual Studio runs fine on it's own. Anyone have an idea how to fix this?
I tried installing sql server 2017 but I gpt some errors ....by the way I am using visual stdio 2017..
this is the error message :
PerfLib 2.0 counter removal failed with exit code 2. Command line: C:\WINDOWS\system32\unlodctr.exe /m:hkengperfctr.xml from directory C:\Program Files\Microsoft SQL Server\140\Shared\.
this is the log summary :
Please clarify.
I now support SQL Servers installed in USA, UK and Poland. I'm in the US. All SQLs are "English" language installs. For SERVICE PACK / CUs / etc., are there COUNTRY SPECIFIC downloads (UK, Poland) or do I just stick to "English" language?
Hi,
I have SQL Server Cluster running with two sql intances. SQL server 2008 r2 and Sql server 2012 r2 and current version is
SQL SERVER 2012 r2
Microsoft SQL Server Management Studio11.0.5058.0
Microsoft Analysis Services Client Tools11.0.5058.0
SQL SERVER 2008 r2
Microsoft SQL Server Management Studio10.50.6000.34What is the best practice to upgrade the Cluster SQL CU?
Regards,
Mohammed
Please remember to mark the replies as answers if they helped. Br, Farhan
Please help,
We downloaded SQL 2014 Enterprise edition evaluation version.
We now want to officially license the product.
My server has 10 cores.
We ordered license packs to meet the per core licensing requirement.
We found a Product ID code off a forum which converted the evaluation version to licensed version.
Question: How do we apply the additional (per core) licenses to the product?
Or do I not apply them and just retain for auditing purposes ?
After the KB4462923 was applied on the System (install & reboot) the Windows Server 2008 R2 the SQL 2008R2 SP2 Server Express wasn't able to start anymore.
The only thing what helped was to uninstall the KB OR upgrade the SQL Server 2008R2 SP2 to SP3 + specture patch be able to Start the service again.
The Security only package is showing the same behavior.
This doesn't happen with 09-2018 KB (rollup & security only).
Does somebody know what the problem could be?
2018-10-10 15:49:42.83 Server Error: 26011, Severity: 16, State: 1. 2018-10-10 15:49:42.83 Server 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. 2018-10-10 15:49:42.83 Server Error: 17182, Severity: 16, State: 1. 2018-10-10 15:49:42.83 Server 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. 2018-10-10 15:49:42.83 Server Error: 17182, Severity: 16, State: 1. 2018-10-10 15:49:42.83 Server 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. 2018-10-10 15:49:42.83 Server Error: 17826, Severity: 18, State: 3. 2018-10-10 15:49:42.83 Server 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-10-10 15:49:42.83 Server Error: 17120, Severity: 16, State: 1. 2018-10-10 15:49:42.83 Server SQL Server could not spawn FRunCM thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.
I recently had to setup two SQL servers with Always on availability as this is recommended for Skype for Business.
After setting this up (mostly similar to how we setup all our other SQL Servers) to include backups I found that backups were failing on the secondary server and seemingly can only run when it is the active server.
I therefore removed backups from the fail over server hoping that when it fails over to the secondary server, I will receive an error message from the backup job that will remind me to set it back to primary as I think I can live with missing one backup.
Then later noticed that for some reason I was not receiving emails from the server to warn that backups are failing (another separate problem I need to deal with)
So now I have written a separate powershell script to run and check daily and warn me when server one is not primary.
Just wondering how others are dealing with this?
(PS we not subscribe to using any 3rd party solutions, only Enterprise OOTB)
no se puede encontrar la clave de registro Software\Microsoft\Servidor Microsoft SQL\ 140\ configurationstate
Hello,
I am trying to install SQL Server 2016 on windows server 2016 box. I have setup two domain accounts which I am using during the installation. I am planning to use one of the domain account for running SQL Server Database Engine and the other to run SQL Server Reporting Service.
However during the installation on the Server Configuration page I am getting the following error for both the domain accounts
Error Log
(13) 2018-10-19 20:43:17 SQLEngine: --InputValidator: Engine : Validating Service Account
(13) 2018-10-19 20:43:17 SQLEngine: --InputValidator: SQLEngine : Validating Engine Service Account
(13) 2018-10-19 20:43:17 Slp: Sco: Attempting to determine if the account 'SQLEngineUser@domain' is Virtual Account
(13) 2018-10-19 20:43:17 Slp: Sco: Attempting to determine if the account 'SQLEngineUser@domain' is Managed Service Account
(13) 2018-10-19 20:43:17 SQLEngine: --InputValidator: Engine : Attempting to get account sid for account SQLEngineUser@domain
(13) 2018-10-19 20:43:17 Slp: Sco: Attempting to get account sid for user account SQLEngineUser@domain
(13) 2018-10-19 20:43:17 Slp: Sco: Attempting to get sid for user account SQLEngineUser@domain
(13) 2018-10-19 20:43:17 Slp: Sco: Attempting to get account from sid S-1-5-21-1497914556-3009341001-223396943-2672
(13) 2018-10-19 20:43:17 Slp: Sco: Attempting to initialize user group SQLEngineUser@domain
(13) 2018-10-19 20:43:17 Slp: Sco: Attempting to check if user group SQLEngineUser@domain exists
(13) 2018-10-19 20:43:17 Slp: Sco: Attempting to open root DirectoryEntry object for local computer
(13) 2018-10-19 20:43:17 Slp: Sco: Attempting to check if container 'WinNT://domainSQLEngine,computer' of group exists
(13) 2018-10-19 20:43:17 Slp: Sco: User group SQLEngineUser@domain doesn't exist
(13) 2018-10-19 20:43:17 Slp: Sco: Attempting to get account sid for user account SQLEngineUser@domain
(13) 2018-10-19 20:43:17 Slp: Sco: Attempting to get sid for user account SQLEngineUser@domain
(13) 2018-10-19 20:43:17 Slp: Sco: Attempting to get account sid for user account SQLEngineUser@domain
(13) 2018-10-19 20:43:17 Slp: Sco: Attempting to get sid for user account SQLEngineUser@domain
(13) 2018-10-19 20:43:17 SQLEngine: --InputValidator: Engine : Service Acccount Specified, Validating Password
(13) 2018-10-19 20:43:17 Slp: Sco: Attempting to validate credentials for user account 'SQLEngineUser@domain' and service name 'MSSQLSERVER'
(13) 2018-10-19 20:43:17 Slp: Sco: Attempting to determine if the account 'SQLEngineUser@domain' is Virtual Account
(13) 2018-10-19 20:43:17 Slp: Sco: Attempting to get account sid for user account SQLEngineUser@domain
(13) 2018-10-19 20:43:17 Slp: Sco: Attempting to get sid for user account SQLEngineUser@domain
(13) 2018-10-19 20:43:17 Slp: Sco: Attempting to see if user SQLEngineUser@domain exists
(13) 2018-10-19 20:43:17 Slp: Sco.User.OpenRoot - root DirectoryEntry object already opened for this computer for this object
(13) 2018-10-19 20:43:17 Slp: Sco: Attempting to check if user account SQLEngineUser@domain exists
(13) 2018-10-19 20:43:17 Slp: Sco: Attempting to look up AD entry for user SQLEngineUser@domain
(13) 2018-10-19 20:43:17 Slp: Sco.User.OpenRoot - root DirectoryEntry object already opened for this computer for this object
(13) 2018-10-19 20:43:17 Slp: Sco.User.LookupADEntry - Attempting to find user account SQLEngineUser@domain
(13) 2018-10-19 20:43:17 Slp: Sco: Attempting to check if container 'WinNT://domainSQLEngine,computer' of user account exists
(13) 2018-10-19 20:43:17 Slp: Sco: User SQLEngineUser@domain wasn't located
(13) 2018-10-19 20:43:17 Slp: Sco: User SQLEngineUser@domain doesn't exist
(13) 2018-10-19 20:43:17 SQLEngine: --InputValidator: Engine: Validation for account SQLEngineUser@domain failed. Account 'SQLEngineUser@domain' provided for service 'MSSQLSERVER' does not exist. Provide an existing account name for the service.
(13) 2018-10-19 20:43:17 SQLEngine: --InputValidator: Action Scenario: Install, Feature Scenario: Install, Resolved Scenario Install
I would much appreciate if any one can help me on this.
Thanks
Dev
-Devashish
http://thecrmworld.wordpress.com
http://ebizartisans.com
Como se resuelve este error:
no se puede encontrar la clave de registro Software\ Microsoft\Servidor Microsoft SQL\ 140\ configurationstate
Hi,
For MS-SQL Database server on a Windows Server 2012 R2 running on a virtual machine in Vmware, Disk should be thin provision or thick provision. Please share link of Microsoft or vmware product documentation and not blog
Thanks in advance,
Nikhil P Desai
buenas tardes muchachos
La verdad estuve observando la solucion para este error , pero tengo el problem de que me aparece el cuadro sin poderlo modificar asi:
Servicio NOMBRE DE CUENTA CONTRASEÑA TIPO DE INICIO
Motor de base de datos de sql Nt Service/MSSQLSERVER... AUTOMATICO
SQL SERVER BROSER NT AUTHORIRY / LOCAL AUTOMATICO
ME APARECE SOMBREADO LA SECUNDA CUENTA Y NO ME DEJA CAMBIAR NADA.
ME PODRIAN AYUDAR POR FAVOR GRACIAS
I have a two node Windows Server 2016 cluster built. Windows Cluster validation passes, but when I go to install SQL Server 2016 on the second node, it fails after clicking on "Add node to a SQL Server Failover Cluster".
I have copied a part of the log file created when the failure occurred.
When I remove node from Windows Cluster, SQL Server install starts just fine.
(01) 2018-10-19 16:37:09 Slp: Running Action: ExecuteOuterSetupStartUII tired to Update SQL Server 2014 Enterprise to SQL Server 2016 Enterprise today. All components succeeded except Client Tools SDK and Client Tools Backwards Compatibility. I then UNINSTALLED the 2 components successfully. I ran Sql Server 2016 setup to ADD the 2 components but a I got the same error. SEE DETAILS BELOW:
Overall summary: