Quantcast
Channel: SQL Server Setup & Upgrade forum

Azure VM SQL Offer: sql2019-ws2019-byol Not allowing to be installed.

$
0
0

I have tried creating a VM from the Azure Portal and from Powershell and both get the same error.

The following list of images referenced from the deployment template are not found: Publisher: microsoftsqlserver, Offer: sql2019-ws2019-byol, Sku: standard, Version: 15.0.200609.

If I change the offer": "sql2019-ws2019-byol", to "sql2019-ws2019"  All works fine. 

So I gave a new 2019 Server (Hybrid Benefit) and SQL 2019, but no BYOL. 

Can we fix the BYOL Image?  Can I convert the non-BYOL Image to a BYOL SQL Image?  I can blow it away once the other is fixed, but if it not fixed for a while I need to get going...

Output of commands below...

Thanks,

Scott<-

I believe the only part of the the template and parameters JSON files that is important is the Image Reference:

Command Line uses the following imageReference:

                   "imageReference": {
                        "publisher": "microsoftsqlserver",
                        "offer": "sql2019-ws2019-byol",
                        "sku": "standard",
                        "version": "15.0.200609"
                    },

Portal uses the following imageReferences: 

                   "imageReference": {
                        "publisher": "microsoftsqlserver",
                        "offer": "sql2019-ws2019-byol",
                        "sku": "standard",
                      "version": "latest" //Command line didn't like this
                    },

I can query the Image and it finds it:

PS /Users/scooter133/Downloads/template-2> Get-AzVMImage-Location"westus"-PublisherName"microsoftsqlserver"-offer sql2019-ws2019-byol-sku standard -version 15.0.200609

Id               : /Subscriptions/<subscription>/Providers/Microsoft.Compute/Locations/westus/Publishers/microsoftsqlserver/ArtifactTypes/VMImage/Offers/sql2019-ws2019-byol/Skus/standard/Versions/15.0.200609

Location         : westus

PublisherName    : microsoftsqlserver

Offer            : sql2019-ws2019-byol

Skus             : standard

Version          : 15.0.200609

FilterExpression : 

Name             : 15.0.200609

HyperVGeneration : V1

OSDiskImage      : {

                     "operatingSystem": "Windows"

                   }

PurchasePlan     : null

DataDiskImages   : []

Creating the new VM via Command Line. 

New-AzResourceGroupDeployment: 10:11:43 AM - Error: Code=InvalidTemplateDeployment; Message=The template deployment 'ASVR-SQL2019' is not valid according to the validation procedure. The tracking id is '4463012a-8e0d-40a3-ad07-881350632eb8'. See inner errors for details.

New-AzResourceGroupDeployment: 10:11:43 AM - Error: Code=InvalidParameter; Message=The following list of images referenced from the deployment template are not found: Publisher: microsoftsqlserver, Offer: sql2019-ws2019-byol, Sku: standard, Version: 15.0.200609. Please refer to https://docs.microsoft.com/en-us/azure/virtual-machines/windows/cli-ps-findimage for instructions on finding available images.

New-AzResourceGroupDeployment: The deployment validation failed





SQL SERVER AGENT DOESNT START 0x80070422

$
0
0
Hi, I have windows 7, 64bits. Today I download and install sql server 2008 express and everytime I try to start the sql agent and the browser i got an error message 0x80070422... the sp1 didn't fix it either... plz help

Microsoft® Data Migration Assistant results differs from SQL Server Profiler

$
0
0

Hi, we are going from SQL server 2012 to 2017.
Need to know if there are deprecated functions, so used  Microsoft® Data Migration Assistant.
A great tool and gave me a nice report. Also let SQL Server Profiler run a trace file for deprecated events. Less results of course..but a function (like SETUSER) that Migration Assistant did not mention in it's report. How come ? regards


SQL SERVER LICENSING

$
0
0

Hello guys, 

I have few question abt upgrade SQL Server Version. I have SQL Server 2008 R2 Enterprise running on Win Server 2008 R2 also. We have to upgrade Win Server maybe to 2016 version,  due to security reason. May i also upgrade the SQL to 2019 version and re-use the SQL Server 2008R2 license?

Thank you

Install SQL Server 2017 - CU21 on Distributed availibility group (DAG) environment

$
0
0
Hi All,

I have to install SQL Server 2017 - CU21 on Distributed availibility group (DAG) environment. Could you please share the steps to install CU21 on all 4 DB servers.

DC1:
SQLDB1 (Primary)
SQLDB2 (Secondary)
DC2:
SQLDB3 (Forwarder)
SQLDB4 (Secondary)

SQL Server Memory

$
0
0

Hi Team,

What is the recommended Min & Max SQL server memory, if DB and Web Server is on same box?

SQL Server 2019 on Windows CORE mode.

$
0
0

Hello team!

  Does the SQL Server 2019 version allows the engine installation on Windows CORE mode? Or not yet?

Thanks.


Doria


Installing SQL Server on a PC

$
0
0
I know that SQL Server requires local admin permission to be installed on a PC but does SQL Server need local admin permission to run on a PC.  If not how do you set it up to not use local admin rights?

Fred


Unable to Enlist Target to MSX after Collation Change.

$
0
0

Hi folks,

After changing the Collation of SQL Server to Latin1_General_CI_AI from QL_Latin1_General_CP1_CI_AS  I'm trying to add the server to MSX as target in CMS but Enlisting is failing. One thing I forgot to do before SQL Collation change was defecting the server. Now I'm not sure if it is because of not defecting the server or changing collation that has caused this? Regardless, now I need to enlist the server in MSX and push monitoring jobs. This same server was enlisted before the change. 

I'm able to connect to the target server from CMS and vice versa using SSMS.

Target SQL Server Version: 2017

CMS SQL Server Version: 2017

Error when trying to enlist from CMS:

===================================

MSX enlist failed for JobServer 'myserver.domain.sa'.  (Microsoft.SqlServer.Smo)

------------------------------
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=14.0.17285.0+((SSMS_Rel_17_4).180821-0238)&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.FailedOperationExceptionText&EvtID=MSX+enlist+JobServer&LinkId=20476

------------------------------
Program Location:

   at Microsoft.SqlServer.Management.Smo.Agent.JobServer.MsxEnlist(String masterServer, String location)
   at Microsoft.SqlServer.Management.SqlManagerUI.EnlistTsxActions.DoAction(ProgressItemCollection actions, Int32 index)
   at Microsoft.SqlServer.Management.SqlStudio.Controls.ProgressItemCollection.DoWorkOnThread()

===================================

An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)

------------------------------
Program Location:

   at Microsoft.SqlServer.Management.Common.ServerConnection.ExecuteNonQuery(String sqlCommand, ExecutionTypes executionType, Boolean retry)
   at Microsoft.SqlServer.Management.Common.ServerConnection.ExecuteNonQuery(StringCollection sqlCommands, ExecutionTypes executionType, Boolean retry)
   at Microsoft.SqlServer.Management.Smo.ExecutionManager.ExecuteNonQuery(StringCollection queries, Boolean retry)
   at Microsoft.SqlServer.Management.Smo.Agent.JobServer.MsxEnlist(String masterServer, String location)

===================================

The enlist operation failed (reason: The time-out was exceeded while the server waited for a response from SQL Server Agent. Make sure that the SQL Server Agent service is running) (.Net SqlClient Data Provider)

------------------------------
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%20SQL%20Server&ProdVer=14.00.3281&EvtSrc=MSSQLServer&EvtID=22026&LinkId=20476

------------------------------
Server Name: myserver.domain.sa
Error Number: 22026
Severity: 16
State: 1


------------------------------
Program Location:

   at Microsoft.SqlServer.Management.Common.ConnectionManager.ExecuteTSql(ExecuteTSqlAction action, Object execObject, DataSet fillDataSet, Boolean catchException)
   at Microsoft.SqlServer.Management.Common.ServerConnection.ExecuteNonQuery(String sqlCommand, ExecutionTypes executionType, Boolean retry)

Error when trying to Add this as target from target server:

===================================

MSX enlist failed for JobServer 'myserver.domain.sa'.  (Microsoft.SqlServer.Smo)

------------------------------
For help, click: https://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=15.0.18206.0+((SSMS_Rel).191029-2112)&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.FailedOperationExceptionText&EvtID=MSX+enlist+JobServer&LinkId=20476

------------------------------
Program Location:

   at Microsoft.SqlServer.Management.Smo.Agent.JobServer.MsxEnlist(String masterServer, String location)
   at Microsoft.SqlServer.Management.SqlManagerUI.EnlistTsxActions.DoAction(ProgressItemCollection actions, Int32 index)
   at Microsoft.SqlServer.Management.SqlStudio.Controls.ProgressItemCollection.DoWorkOnThread()

===================================

An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)

------------------------------
Program Location:

   at Microsoft.SqlServer.Management.Common.ServerConnection.ExecuteNonQuery(String sqlCommand, ExecutionTypes executionType, Boolean retry)
   at Microsoft.SqlServer.Management.Common.ServerConnection.ExecuteNonQuery(StringCollection sqlCommands, ExecutionTypes executionType, Boolean retry)
   at Microsoft.SqlServer.Management.Smo.ExecutionManager.ExecuteNonQuery(StringCollection queries, Boolean retry)
   at Microsoft.SqlServer.Management.Smo.Agent.JobServer.MsxEnlist(String masterServer, String location)

===================================

The enlist operation failed (reason: The time-out was exceeded while the server waited for a response from SQL Server Agent. Make sure that the SQL Server Agent service is running) (.Net SqlClient Data Provider)

------------------------------
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%20SQL%20Server&ProdVer=14.00.3281&EvtSrc=MSSQLServer&EvtID=22026&LinkId=20476

I can't seem to find much information online on this issue. Any help would be appreciated. 

Migrating Database to new Server, Can i take my SQL Standard License with me?

$
0
0

Hi

We want to migrate from our current SQL Server that sits on a computer in our office to an Azure Virtual machine, we run this SQL:

Microsoft SQL Server 2014 (SP3-GDR) (KB4532095) - 12.0.6118.4 (X64) 
Dec 12 2019 21:46:15 
Copyright (c) Microsoft Corporation
Standard Edition (64-bit) on Windows NT 6.3 <X64> (Build 18363: )

Can we install this on our new server in Azure?

About SQL Server - Server + CAL license

$
0
0

If i purchase sql server 2016 Standard edition - server + cal license

server license for the vm/server (say serverA) on which database engine will be installed.

CAL license for each user/device accessing serverA remotely. Say there are 3 users > user1, user2, user3 who will be accessing serverA.

Question1: Can I install multiple sql engines on serverA since i already have server license? I know that multiple sql server engines can be installed in case of core based licensing. 

Question2: If answer of question 1 is 'No' means i have to buy another server license. Suppose i buy another server license and i install named instance of sql on same server 'serverA'. Now 'serverA' has two database engines. But the users who are going to use named instance are same as of default instance i.e user1, user2, user3 for which i already have 3 cal license. So do i need to buy 3 more cal license for the 3 users in order to them access named instance?

Thanks in Advance

Chirag

WindowsUpdate_84B20001 failed

$
0
0

Hello,

I am trying to apply a Security Update to SQL:

Security Update for SQL Server 2012 RTM (KB2716442)
Download size: 425.5 MB
You may need to restart your computer for this update to take effect.
Update type: Important
A security issue has been identified in the SQL Server 2012 RTM that could allow an attacker to compromise your system and gain control over it. You can help protect your computer by installing this update from Microsoft. After you install this item, you may have to restart your computer.
More information: 
http://support.microsoft.com/kb/2716442
Help and Support: 
http://support.microsoft.com

But it failed with

Any idea? and this failure is reoccurring on a months basis for months!!!

The machines have been restarted several times ...

Thanks,
Dom


Security / System Center Configuration Manager Current Branch / SQL




Quiet Install SQL 2016 using configuration file with passwords for service accounts encrypted

$
0
0

Hello

Im trying to make an automated MDT task for installing SQL Server 2016 using a configuration file and i dont want to enter my service accounts password in plain text

Example of command line to install

Setup.exe /SQLSVCPASSWORD="my pass" /ConfigurationFile=MyConfigurationFile.INI

there its any way i can encrypt this password ?

Thank you in advance for your help

Best Regards


SQL Server 2014 Upgrade - Unsafe assembly errors

$
0
0

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


Run as Domain User

$
0
0

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?


SQL Server 2014 installation error code - 2068119551

$
0
0

Hello Team,

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

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:          0x84BB0001
  Error description:             A connection was successfully established with the server, but then an error occurred during the pre-login handshake. (provider: Named Pipes Provider, error: 0 - No process is on the other end of the pipe.)
  Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.5000.0&EvtType=0xBA6E21AA%400x9A41B222&EvtType=0xBA6E21AA%400x9A41B222

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

SQL 2019 Fails to Start - Error 17051

$
0
0

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:

undefined

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!

How can I patch "R Services (In-Database")?

$
0
0

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?

SSDT 2019 standalone install

$
0
0
folks, i am looking to update lots of servers with SSDT2019. Is there any standalone installation available?

LocalDB will not install by itself unless installed as part of SQL Server Express

$
0
0

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.



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>