Hello Team,

I get the following error while installing SQL server 2014 on Windows 2012R2.

I've uninstalled SQL and tried to reinstall as mentioned in the below article but still get the same error.

Warm regards MeVs

• SQL Server Standard 2017 allows high availability through the feature called AlwaysOn.
• AlwaysOn allows customers to have an active / passive instances meaning that SQL Server can have a secondary (cold installation), to recover data from in case of a disaster or hardware failure on the primary server.
• The licensing of AlwaysOn scenario requires a SQL Server license on the primary server and a Software Assurance coverage to be able to install a passive instance on the secondary server.
• AlwaysOn feature on SQL Server Standard is limited to 2 nodes (active/passive instances)
  
  
  However It seems tthat software assurance is not avaible for OEM licensing? So am I out of look?

Hello,

We recently upgraded our SQL Server 2012 Business Intelligence Edition installation to SQL Server 2014 Business Intelligence Edition. 

The following errors now occur in the SQL Server error log:

• Unsafe assembly 'microsoft.sqlserver.integrationservices.server, version=12.0.0.0, culture=neutral, publickeytoken=89845dcd8080cc91, processorarchitecture=msil' loaded into appdomain 3 (SSISDB.dbo[runtime].1).
• Unsafe assembly 'microsoft.ssdqs, version=11.0.0.0, culture=neutral, publickeytoken=89845dcd8080cc91, processorarchitecture=msil' loaded into appdomain 2 (DQS_MAIN.dbo[runtime].2).

Searching the web has yielded no results. Any advice would be appreciated.

Thanks.

Norm

I recently took a position as an Operations Manager of a database team focused on SQL Server.  We've got a large SQL presence (couple thousand servers) and I'm looking at setting standards for version usage and providing guidance to the business on planning for upgrades.  We've just kicked off a project begin migration away from SQL 2012.  That's better than starting next year but what are others doing in regards to lifecycle management?  Do you cutoff new installs for a version before mainstream support ends, on the day it ends or sometime during extended support?  When do you drop internal support for SQL versions and/or start your migration/upgrades to newer versions?

Looking forward to comments!

This SQL Server related Forum will be migrated to a new home on Microsoft Q&A!

We’ve listened to your feedback on how we can enhance the forum experience. Microsoft Q&A  allows us to add new functionality and enables easier access to all the technical resources most useful to you, like Microsoft Docs and Microsoft Learn. 

Now until Aug 23, 2020:

• You can post any new questions on Microsoft Q&A or here.

From Aug 24, 2020 until Sep 7, 2020:

• New posts – We invite you to post new questions in the “SQL Server” forum’s new home on Microsoft Q&A. The current forum will not allow any new questions.
• Existing posts – Interact here with existing content, answer questions, provide comments, etc.

Sep 7, 2020 onward:

• This forum will be closed to all new and existing posts and all interactions will be in Microsoft Q&A.

We are excited about moving to Microsoft Q&A and seeing you there.  

""SQL Server related"" forum will be migrated to a new home onMicrosoft Q&A SQL Server!
We invite you to post new questions in the "SQL Server related" forum’s new home on Microsoft Q&A SQL Server!
For more information, please refer to the sticky post.

Hello,

   We have Windows Server 2016 Standard as Hyper-v host and we would like to deploy SQL Server 2016 in the Guest OS and want to take the advantage of Hyperv Replicas. Has any one deployed this before ??

http://www.arabitpro.com

Trying to install SQL 2005 Std. During the installation I am specifying a regular windows domain account for the SQL Service and SQL Agent to run under. During the installation it tries to start the services, but fails. I was under the impression that setup will grant the necessary permissions to allow this account to run properly. If during the install I select to run the services under the Local System account  everything installs fine. I can then use the SQL Server Configuration Manager and change the services to run under a windows domain account and everything works.

Is there any permissions that need to be in place before I start the installation?

I have a fairly significant set of issues that I cannot figure out how to resolve that has brought down a bunch of systems. A windows update occurred and the SQL 2019 RC1 server rebooted itself (do not believe that this error is related just coincidental).

This error indicates that the SQL Server evaluation period has expired. Upon reviewing the startup logs this concurs with my belief:

I am confused about why I am running into this issue as I am running a developer version of SQL and not the evaluation version but none the less it currently appears to be a problem.

To attempt to resolve this issue I have done the following:

1. Attempted to do an edition upgrade and set everything back to developer and the process ran and completed successfully but the service will still not start.
2. Attempted to upgrade editions to a licensed version of SQL (which I do also own) and I cannot complete the upgrade because the SQL server is not running.
3. I attempted to follow instructions to turn back the computer time and set common files registry entry to "3" in an attempt to trick it into being active so that I could upgrade. My system automatically reverts the time back to the standard time almost immediately.
   1. Attempted to turn off network connection to disable time sync
   2. Defaulted the time settings for windows
   3. Unjoined the server from the domain thinking GPO might be interfering

This system MUST be restored. Any ideas you have on how to get it back up and running again would be seriously appreciated!

Overall summary:
  Final result:                  Failed: see details below
  Exit code (Decimal):           -2061893607
  Start time:                    2017-08-12 18:48:38
  End time:                      2017-08-12 18:58:32
  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:                  
  Machine processor count:       4
  OS version:                    Microsoft Windows 10 Enterprise (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

Package properties:
  Description:                   Microsoft SQL Server 2016 
  ProductName:                   SQL Server 2016
  Type:                          RTM
  Version:                       13
  Installation location:         C:\SQLServer2016Media\Developer\x64\setup\
  Installation edition:          Developer

  Slipstream:                    True
  SP Level                       1

Product Update Status:
  User selected not to include product updates.

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:         Disabled
  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\20170812_184832\ConfigurationFile.ini
  CTLRSTARTUPTYPE:               0
  CTLRSVCACCOUNT:                <empty>
  CTLRSVCPASSWORD:               <empty>
  CTLRUSERS:                     <empty>
  ENABLERANU:                    false
  ENU:                           true
  EXTSVCACCOUNT:                 <empty>
  EXTSVCPASSWORD:                <empty>
  FEATURES:                      SQLENGINE
  FILESTREAMLEVEL:               0
  FILESTREAMSHARENAME:           <empty>
  FTSVCACCOUNT:                  <empty>
  FTSVCPASSWORD:                 <empty>
  HELP:                          false
  IACCEPTROPENLICENSETERMS:      false
  IACCEPTSQLSERVERLICENSETERMS:  true
  INDICATEPROGRESS:              true
  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:                         true
  QUIETSIMPLE:                   false
  ROLE:                          
  RSINSTALLMODE:                 DefaultNativeMode
  RSSHPINSTALLMODE:              DefaultSharePointMode
  RSSVCACCOUNT:                  <empty>
  RSSVCPASSWORD:                 <empty>
  RSSVCSTARTUPTYPE:              Automatic
  SAPWD:                         <empty>
  SECURITYMODE:                  <empty>
  SQLBACKUPDIR:                  <empty>
  SQLCOLLATION:                  SQL_Latin1_General_CP1_CI_AS
  SQLSVCACCOUNT:                 NT Service\MSSQLSERVER
  SQLSVCINSTANTFILEINIT:         true
  SQLSVCPASSWORD:                <empty>
  SQLSVCSTARTUPTYPE:             Automatic
  SQLSYSADMINACCOUNTS:           GLOBAL\I316655
  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:                 false
  UpdateSource:                  Slipstream
  USEMICROSOFTUPDATE:            false
  X86:                           false

  Configuration file:            C:\Program Files\Microsoft SQL Server\130\Setup Bootstrap\Log\20170812_184832\ConfigurationFile.ini

Detailed results:
  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:          0x851A0019
  Error description:             Could not find the Database Engine startup handle.
  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=0xD15B4EB2%400x4BDAF9BA%401306%4025&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025

  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:

Scenario specific rules:

Rules report file:               C:\Program Files\Microsoft SQL Server\130\Setup Bootstrap\Log\20170812_184832\SystemConfigurationCheck_Report.htm

Unable to start the Service also. Same Error Code: 2061893607 pop up show in the dialog box. As shown below.

I tried uninstall and install again several times same. Facing same issue.

Any help mostly appreciated. 

I would like some help please. I have taken a back up on SQL Server 2008 version 10.0.5538. I need to restore this on a new server. What version of SQL server are compatible with this backup? 

Thanks in advance.

I've just installed "R Services (In-Database)" onto an existing, updated SQL instance but I can't get the launchpad service to start. Looking online, this seems to be related to the issue:

    8. Launchpad services fails to start if the version is different from the R version

https://docs.microsoft.com/en-us/sql/machine-learning/troubleshooting/known-issues-for-sql-server-machine-learning-services?view=sql-server-2016

Checking the details, I can see that the version of "Launchpad.exe" (13.0.1601.5 - RTM) is different from "sqldk.dll" (13.0.5820.21 - SP2/CU13) but when I run the SP2/CU13 executable, all options for upgrade are greyed-out and clicking on the "R Services (In-Database)" entry it reports "Installed".

How can I update the R Services components which need it?

Pls confirm that the below is AE or commercial

SQLSvrStdCore
ALNG LicSAPk MVL 2Lic CoreLic

Part No. 7NQ-00302

Regards

Anshul Goyal

Hello.

I would like to check if the hardware on which the SQL server is installed is efficient enough.

I have installed Red Gate Monitoring.

This is how the logs for two days look like (large images on: RegGate Logs ):

Do I understand correctly that the hardware is sufficient?

Regards,

Tomasz

I have SQL 2014 Standard installed on Server 2012 R2.

SQL is latest service pack & CU.

Install media is for for SQL 2016 Standard RTM (Microsoft Open Business [Open License]).

Existing SQL is installed to L: partition.

This includes the actual instance & executable paths as shown in services.msc

Upon launching the SQL 2016 installer and selecting Installation > Upgrade from a Previous Version of SQL Server

the prior SQL instance is displayed correctly. We can select it to be upgraded.

However the paths shown for the instance & other components are C:, and one is actual on I: (Shared feature directory)

The server does not have an I:. I do not know where this is coming from.

I cannot find a way to change these paths during the upgrade process. I proceed all the way through the upgrade Wizard until the "Upgrade" button appears as the next step.

I have chosen not to click Upgrade, because I don't want it to put the components on the C: (or the non-existent I:)

Does anyone here have insight into why these paths would change from their existing drive letters during the upgrade to SQL 2016?

I would really appreciate some guidance here. Hoping to avoid making any mistakes. I know it is better to get this right upfront then try to change it later.

Thanks in advance for any help!

Regards,

-

Doug Mortensen

CCNA, MCSA, MCP, Security+, Linux+, Server+, Net+, A+, MSSBS

I am trying to install Microsoft SQL Server 2012 in Windows 10 Operating System.

When I try to open SSDT, I get this error:

The requested operation cannot be completed.The computer must be trusted for delegation and the current user account must be configured to allow delegation.

I have a separate built-in administrator account from where I installed SQL Server.  I am able to open SSDT from that account without any issues.  From my ownuser account, by running SSDT as an administrator, I have the above error.

Can you let me know on how I can overcome this delegation issue? I have installed SQL Server Service 2012 Pack 3.

On a brand new (fresh) Windows 10 Pro 1909 system, I have run into problems installing theLocalDB component of SQL Server 2019 Express Edition. 

I first acquired the MSI install file by running the GUI for the SQL Server 2019 Express Edition installer and selecting the "Download Media" option:

Then I chose the LocalDB option:

The above downloaded a 53 MB file: sqllocaldb.msi.

I ran the file from an elevated CMD window.  The install failed with the error message:"Service 'SQL Server VSS Writer' (SQLWriter) failed to start. Verify that you have sufficient priviliges to start system services."

The indication about lack of privilige is misleading, as I used an admin account to do the install, as mentioned. 

Per online suggestions, I also tried modifying the "Log On" tab for the service in question and set "Local System account -> Allow service to interact with the desktop" box, which did not help.

The only way I was able to proceed with the install was to use the Custom option in the GUI and check both Instance Features -> Database Engine Services and Shared Features -> LocalDB in the Feature Selection pane.

However, this results in the installation of two instances, as follows:

This kind of defeats my purpose: I want the compact LocalDB version only, not accompanied by the full Express edition.

In any case, I don't understand why, during the install, LocalDB shows a dependence on the VSS Writer service?

I would appreciate learning more about the whole thing.  Maybe my understanding of LocalDB, that it's a simple, SQLite-like db, is incorrect. 

Thanks.