I am attempting to learn more about the machine learning capabilities of SQL 2017.

However, when I attempt to run Python scripts, I keep getting the error highlighted in the subject.

I have reinstalled SQL Server several times, with no improvement.

At one point, I was looking through the EXTLAUNCHERLOG and noticed the R seemed to have started OK.

The log follows:

EXTLAUNCHERLOG

2018-03-26 15:17:11.926    Privilege SeAssignPrimaryTokenPrivilege is present in launchpad process token.

2018-03-26 15:17:11.926    Privilege SeChangeNotifyPrivilege is present in launchpad process token.

2018-03-26 15:17:11.926    Privilege SeIncreaseQuotaPrivilege is present in launchpad process token.

2018-03-26 15:17:11.926    Launchpad process is a part of Service Group. Launchpad does have SeServiceLogonRight.

2018-03-26 15:17:11.973    Negotiated Runtime Version for launcher RLauncher.dll is 2

2018-03-26 15:17:11.973    Got API for launcher RLauncher.dll with version 2

2018-03-26 15:17:11.973    Successfully loaded launcher RLauncher.dll and negotiated version

2018-03-26 15:17:12.004    Successfully initialized launcher RLauncher.dll

2018-03-26 15:17:12.004    Successfully found the launcher interfaces for launcher RLauncher.dll

2018-03-26 15:17:12.004    Successfully registered the launchcontext for launcher RLauncher.dll

2018-03-26 15:17:12.004    Successfully registered the launcher RLauncher.dll for the scriptType 1

2018-03-26 15:17:12.004    Negotiated Runtime Version for launcher Pythonlauncher.dll is 2

2018-03-26 15:17:12.004    Got API for launcher Pythonlauncher.dll with version 2

2018-03-26 15:17:12.004    Successfully loaded launcher Pythonlauncher.dll and negotiated version

2018-03-26 15:17:12.019    InitLauncher failed! Error: 0x80004005

2018-03-26 15:17:12.019    Failed to initialize the launcher Pythonlauncher.dll

2018-03-26 15:17:12.019    User Config data file: C:\Program Files\Microsoft SQL Server\MSSQL14.MS_SQL2017_DEV3\MSSQL\Binn\SQLRConfigData

2018-03-26 15:17:12.019    User Config key file: C:\Program Files\Microsoft SQL Server\MSSQL14.MS_SQL2017_DEV3\MSSQL\Binn\SQLRConfig

2018-03-26 15:17:12.644    Physical user pool has been initialized with 21 users.

2018-03-26 15:17:12.660    Security Context Manager is initialized successfully.

2018-03-26 15:17:12.660    Satellite Session Manager is initialized successfully.

2018-03-26 15:17:12.660    Server local connection provider is ready to accept connection on [ \\.\pipe\sqlsatellitelaunchMS_SQL2017_DEV3 ].

2018-03-26 15:17:12.660    Launchpad started to listen on named pipe \\.\pipe\sqlsatellitelaunchMS_SQL2017_DEV3.

2018-03-26 15:17:12.660    MSSQLLaunchpad$MS_SQL2017_DEV3 service successfully started.

 I then ran through the R tutorial scripts and they all seemed to run OK, or at the very least, they did not give errors.

So then I went back to trying Python.

When I run a Python script, as shown in the sample below,

'

EXEC sp_execute_external_script  @language =N'Python',

@script=N'

OutputDataSet = InputDataSet;

',

@input_data_1 =N'SELECT 1 AS hello'

WITH RESULT SETS (([hello] int not null));

GO

I get the error as shown here:

Msg 39021, Level 16, State 1, Line 1

Unable to launch runtime for 'Python' script. Please check the configuration of the 'Python' runtime.

Msg 39019, Level 16, State 2, Line 1

An external script error occurred:

Unable to launch the runtime. ErrorCode 0x80070490: 1168(Element not found.).

Please advise.

Many thanks.

Hi!

I'd like to upgrade my SSRS 2012 and 2016 instances to SSRS 2017. Upgrading from 2012 to 2016 was fine. However, when I run the stand-alone installer for SSRS 2017 I get no option to upgrade but only install and configure later. I've searched the documentation which is a mix of 2016 and 2017 references but have failed to find an answer.

Can I upgrade from SSRS 2016 to 2017 and if so, how?

The OS is W2K12 and the SSRS instance is named.

Thanks/U

Detail:

(01) 2017-10-19 02:14:41 Slp: Log provider 'Microsoft.SqlServer.Chainer.Infrastructure.LogProviderFile' has been registered
(01) 2017-10-19 02:14:41 Slp: Log provider 'Microsoft.SqlServer.Chainer.Infrastructure.LogProviderConsole' has been registered
(01) 2017-10-19 02:14:41 Slp: Log provider 'Microsoft.SqlServer.Chainer.Infrastructure.LogProviderStatus' has been registered
(01) 2017-10-19 02:14:41 Slp: Reading XML resource 'Microsoft.SQL.Chainer.PackageData.Package.xml'
(01) 2017-10-19 02:14:41 Slp: Reading schema resource 'Microsoft.SQL.Chainer.Package.Package.xsd'
(01) 2017-10-19 02:14:41 Slp: Document 'Microsoft.SQL.Chainer.PackageData.Package.xml' validated with schema 'Microsoft.SQL.Chainer.Package.Package.xsd' has been successfuly loaded into datastore path '/Datastore/Package'
(01) 2017-10-19 02:14:41 Slp: ----------------------------------------------------------------------
(01) 2017-10-19 02:14:41 Slp: Running Action: ReadProductXML
(01) 2017-10-19 02:14:41 Slp: Reading XML resource 'Microsoft.SQL.Chainer.Product.Product.xml'
(01) 2017-10-19 02:14:41 Slp: Document 'Microsoft.SQL.Chainer.Product.Product.xml' validated with schema 'Microsoft.SQL.Chainer.Product.Product.xsd' has been successfuly loaded into datastore path '/Datastore/Product'
(01) 2017-10-19 02:14:41 Slp: Completed Action: ReadProductXML, returned True
(01) 2017-10-19 02:14:41 Slp: ----------------------------------------------------------------------
(01) 2017-10-19 02:14:41 Slp: Running Action: LoadExtensions
(01) 2017-10-19 02:14:42 Slp: Loading extension 'MSI' from file 'C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\SQL2017\x64\.\Microsoft.SqlServer.Configuration.MsiExtension.dll'
(01) 2017-10-19 02:14:42 Slp: Extension 'MSI' version '14.0.1000.169' loaded
(01) 2017-10-19 02:14:42 Slp: Loading extension 'Config' from file 'C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\SQL2017\x64\.\Microsoft.SqlServer.Configuration.ConfigExtension.dll'
(01) 2017-10-19 02:14:42 Slp: Extension 'Config' version '14.0.1000.169' loaded
(01) 2017-10-19 02:14:42 Slp: Loading extension 'Common' from file 'C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\SQL2017\x64\.\Microsoft.SqlServer.Chainer.ExtensionCommon.dll'
(01) 2017-10-19 02:14:42 Slp: Extension 'Common' version '14.0.1000.169' loaded
(01) 2017-10-19 02:14:42 Slp: Loading extension 'SqlConfigBase' from file 'C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\SQL2017\x64\.\Microsoft.SqlServer.Configuration.SqlConfigBase.dll'
(01) 2017-10-19 02:14:42 Slp: Extension 'SqlConfigBase' version '14.0.1000.169' loaded
(01) 2017-10-19 02:14:42 Slp: Loading extension 'Slp' from file 'C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\SQL2017\x64\.\Microsoft.SqlServer.Configuration.SetupExtension.dll'
(01) 2017-10-19 02:14:42 Slp: Extension 'Slp' version '14.0.1000.169' loaded
(01) 2017-10-19 02:14:42 Slp: Loading extension 'RulesEngine' from file 'C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\SQL2017\x64\.\Microsoft.SqlServer.Configuration.RulesEngineExtension.dll'
(01) 2017-10-19 02:14:42 Slp: Extension 'RulesEngine' version '14.0.1000.169' loaded
(01) 2017-10-19 02:14:42 Slp: Loading extension 'WorkflowData' from file 'C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\SQL2017\x64\.\Microsoft.SqlServer.Chainer.WorkflowData.dll'
(01) 2017-10-19 02:14:42 Slp: Extension 'WorkflowData' version '14.0.1000.169' loaded
(01) 2017-10-19 02:14:42 Slp: Loading extension 'SlpConfig' from file 'C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\SQL2017\x64\.\Microsoft.SqlServer.Configuration.SlpExtension.dll'
(01) 2017-10-19 02:14:42 Slp: Extension 'SlpConfig' version '14.0.1000.169' loaded
(01) 2017-10-19 02:14:42 Slp: Loading extension 'Clst' from file 'C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\SQL2017\x64\.\Microsoft.SqlServer.Configuration.Cluster.dll'
(01) 2017-10-19 02:14:42 Slp: Extension 'Clst' version '14.0.1000.169' loaded
(01) 2017-10-19 02:14:42 Slp: Loading extension 'AgentConfig' from file 'C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\SQL2017\x64\.\Microsoft.SqlServer.Configuration.AgentExtension.dll'
(01) 2017-10-19 02:14:42 Slp: Extension 'AgentConfig' version '14.0.1000.169' loaded
(01) 2017-10-19 02:14:42 Slp: Loading extension 'SqlPowershellConfig' from file 'C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\SQL2017\x64\.\Microsoft.SqlServer.Configuration.PowershellExtension.dll'
(01) 2017-10-19 02:14:42 Slp: Extension 'SqlPowershellConfig' version '14.0.1000.169' loaded
(01) 2017-10-19 02:14:42 Slp: Loading extension 'SSISConfig' from file 'C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\SQL2017\x64\.\Microsoft.SqlServer.Configuration.SSISExtension.dll'
(01) 2017-10-19 02:14:42 Slp: Extension 'SSISConfig' version '14.0.1000.169' loaded
(01) 2017-10-19 02:14:42 Slp: Loading extension 'ISMasterConfig' from file 'C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\SQL2017\x64\.\Microsoft.SqlServer.Configuration.ISMasterExtension.dll'
(01) 2017-10-19 02:14:42 Slp: Extension 'ISMasterConfig' version '14.0.1000.169' loaded
(01) 2017-10-19 02:14:42 Slp: Loading extension 'ISWorkerConfig' from file 'C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\SQL2017\x64\.\Microsoft.SqlServer.Configuration.ISWorkerExtension.dll'
(01) 2017-10-19 02:14:42 Slp: Extension 'ISWorkerConfig' version '14.0.1000.169' loaded
(01) 2017-10-19 02:14:42 Slp: Loading extension 'DReplayConfig' from file 'C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\SQL2017\x64\.\Microsoft.SqlServer.Configuration.DistributedReplayExtension.dll'
(01) 2017-10-19 02:14:42 Slp: Extension 'DReplayConfig' version '14.0.1000.169' loaded
(01) 2017-10-19 02:14:42 Slp: Loading extension 'ASConfig' from file 'C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\SQL2017\x64\.\Microsoft.SqlServer.Configuration.ASExtension.dll'
(01) 2017-10-19 02:14:42 Slp: Extension 'ASConfig' version '14.0.1000.169' loaded
(01) 2017-10-19 02:14:42 Slp: Loading extension 'ReplConfig' from file 'C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\SQL2017\x64\.\Microsoft.SqlServer.Configuration.Repl_ConfigExtension.dll'
(01) 2017-10-19 02:14:42 Slp: Extension 'ReplConfig' version '14.0.1000.169' loaded
(01) 2017-10-19 02:14:42 Slp: Loading extension 'ManagementToolsConfig' from file 'C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\SQL2017\x64\.\Microsoft.SqlServer.Configuration.ManagementToolsExtension.dll'
(01) 2017-10-19 02:14:42 Slp: Extension 'ManagementToolsConfig' version '14.0.1000.169' loaded
(01) 2017-10-19 02:14:42 Slp: Loading extension 'ManagementToolsAdvancedConfig' from file 'C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\SQL2017\x64\.\Microsoft.SqlServer.Configuration.ManagementToolsExtension.dll'
(01) 2017-10-19 02:14:42 Slp: Extension 'ManagementToolsAdvancedConfig' version '14.0.1000.169' loaded

Hi All,

If we are on SQL 2012 SP4(11.0.7001.0) and install KB4091266 directly. Does this mean we have missed fixes included in KB4057116 ?

Hello,

We are getting the following errors in our SQL Server 2016 servers. These messages are filled in error log. 

2018-07-25 14:21:48.070 spid124s     SSBDT: Dialog timer delete during registration (did: CB9C71C8-93CB-4AE6-B92E-B237A7AE4C67:Initiator, OpType: CloseDialog OpResult: Null)
2018-07-25 14:21:48.080 spid124s     SSBDT: Dialog timer delete during registration (did: 9EDAD00A-90EE-4C0E-925B-DD3258580CE1:Initiator, OpType: CloseDialog OpResult: Null)
2018-07-25 14:22:07.160 spid124s     SSBDT: Dialog timer delete during registration (did: B59E1EB3-D8B7-45EB-82C4-D6145838414F:Initiator, OpType: CloseDialog OpResult: Null)
2018-07-25 14:22:15.730 spid124s     SSBDT: Dialog timer delete during dispatch (did: 039E621C-B0DB-48FE-8B3E-0B09ECE8104B:Target, OpType: DialogCleanupDispatch OpResult: Null)
2018-07-25 14:22:15.760 spid124s     SSBDT: Dialog timer delete during dispatch (did: 7CD4A466-4F9C-404A-9210-A3B4CE2F520D:Target, OpType: DialogCleanupDispatch OpResult: Null)

These may may informational message but not sure these messages are related to which object or process. Error log getting filled. How to stop these message ?

Thanks

Selva

Hi Team,

Could any one provide SSMS 2016 download path?. I tried but no luck. it is still going to 17.x.

We need SSMS 2016 for some testing.

when I have used the administrator account to install SQL 2014 it worked fine from a chef, but when I am using local user part of administrator group and also domain user part of administrator group it failed with below error.

 execute[install_sql] action run
      ================================================================================[0m
 Error executing action `run` on resource 'execute[install_sql]'
    ================================================================================[0m

Mixlib::ShellOut::ShellCommandFailed
    -----------------------------------
    Expected process to exit with [0, 3010], but received '-2146233079'
---- Begin output of C:\temp\rds\expand_area\sql2014_win\SETUP.EXE /ConfigurationFile=C:\temp\rds\expand_area\sql2014_win\config_base.ini /Q /INDICATEPROGRESS

/IACCEPTSQLSERVERLICENSETERMS

We have upgraded our sql server 2012 instances to service pack 4 and the meltdown patch 7462.

All seems well except for some reporting services instances We get an issue with report builder. The issue is present with the patch 7462 but goes away when we uninstall the patch 7462 (running at sp4)

We are reluctant to uninstall the patch, but the facility is required on the live system. Any help is appreciated

ERROR SUMMARY
 Below is a summary of the errors, details of these errors are listed later in the log.
 * Activation of <url> resulted in exception. Following failure messages were detected:
  + File, interop.shdocvw.dll, has a different computed hash than specified in manifest.

ERROR DETAILS
 Following errors were detected during this operation.
 * [02/02/2018 09:11:17] System.Deployment.Application.InvalidDeploymentException (HashValidation)
  - File, interop.shdocvw.dll, has a different computed hash than specified in manifest.
  - Source: System.Deployment
  - Stack trace:
   at System.Deployment.Application.ComponentVerifier.VerifyFileHash(String filePath, Hash hash)
   at System.Deployment.Application.ComponentVerifier.VerifyFileHash(String filePath, HashCollection hashCollection)
   at System.Deployment.Application.ComponentVerifier.FileComponent.Verify()
   at System.Deployment.Application.ComponentVerifier.VerifyComponents()
   at System.Deployment.Application.DownloadManager.DownloadDependencies(SubscriptionState subState, AssemblyManifest deployManifest, AssemblyManifest appManifest, Uri sourceUriBase, String targetDirectory, String group, IDownloadNotification notification, DownloadOptions options)
   at System.Deployment.Application.ApplicationActivator.DownloadApplication(SubscriptionState subState, ActivationDescription actDesc, Int64 transactionId, TempDirectory& downloadTemp)
   at System.Deployment.Application.ApplicationActivator.InstallApplication(SubscriptionState& subState, ActivationDescription actDesc)
   at System.Deployment.Application.ApplicationActivator.PerformDeploymentActivation(Uri activationUri, Boolean isShortcut, String textualSubId, String deploymentProviderUrlFromExtension, BrowserSettings browserSettings, String& errorPageUrl, Uri& deploymentUri)
   at System.Deployment.Application.ApplicationActivator.PerformDeploymentActivationWithRetry(Uri activationUri, Boolean isShortcut, String textualSubId, String deploymentProviderUrlFromExtension, BrowserSettings browserSettings, String& errorPageUrl)
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Deployment.Application.ApplicationActivator.PerformDeploymentActivationWithRetry(Uri activationUri, Boolean isShortcut, String textualSubId, String deploymentProviderUrlFromExtension, BrowserSettings browserSettings, String& errorPageUrl)
   at System.Deployment.Application.ApplicationActivator.ActivateDeploymentWorker(Object state)

COMPONENT STORE TRANSACTION DETAILS
 No transaction information is available

Hi,

I am trying to upgrade an instance of 200R2 Express to 2012 Evaluation.

At the "Upgrade Rules" section I receive an error message stating:

"SQL Server 2012 Feature Upgrade Failed"

"The specified edition upgrade is not supported. For information about supported upgrade paths, see the SQL Server 2012 version and edition upgrade in Books Online."

The link below states it should be possible to upgrade from 2008R2 Express to 2012:

https://docs.microsoft.com/en-us/previous-versions/sql/sql-server-2012/ms143393(v=sql.110)

hi 

shall i disable below services from production server  (Customer Experience Improvement Programme ?  is there any depends?

pros / cons ? 

SQL Analysis Services CEIP
SQL Server CEIP service
SQL Server Integration Services CEIP service

Good morning,

I'm trying to install SQL Server 2008 R2 on a Windows 2012 R2 cluster, but have hit a bit of a barrier.

Everything has gone swimmingly, up until the "Cluster Security Policy" page.  I am EXPECTING to see the following:

But am, in fact, seeing this:

Where has the "Use Service SIDs" default option gone?  I'm certain its the same install media that I've used a hundred times, but now this option has vanished?

What would the recommendation be to do in its absence?  Just create 2 AD groups with appropriate names and carry on?

Any help here would be massively appreciated!

Andy

When setting up a 2nd instance of SQL 2012 Express, I need to change the service accounts from the default to NT Authority\System.

Any reason for this?

Ok to do this?

Thanks!

We want to migrate our SQL on premise(sql 2008, sql 2012, and 2014) to the Azure cloud (sql 2016).

A backup of the database will be done for the on premise databases then this will be restored on a sql 2016 located in Azure.

Do we need to take any special steps?  Does the database get upgraded when it moves to a newer version of sql?,... and what do we need to do for this upgrade?

dsk

Server is running 2012 r2, domain controller.

1st instance is running production software so I don't want to have to rebuild that instance so a complete uninstall isn't an option.

Changed service accounts on 2nd instance from default to NT AUTHORITY\SYSTEM.

The following error has occurred:

SQL Server Browser service group does not exist. Check for earlier failures in the setup.

Error installing SQL Server Database Engine Services Instance Features
SQL Server Browser service group does not exist. Check for earlier failures in the setup.
Error code: 0x84C5C74B

An error occurred for a dependency of the feature causing the setup process for the feature to fail.

Some have said creating security groups can fix this.  Can anyone confirm this or provide other solutions?

SQLServer2012SQLBrowserUser${ServerName}
SQLServer2008SQLBrowserUser${ServerName}

SQLServer2005SQLBrowserUser${ServerName}

Thanks!

Setting: test lab with Windows Server 2012 R2, Sql 2016 Enter (w Sp1), "Update for Visual C++ 2013 and Visual C++ Redistributable Package", SSMS v17.4, no Internet access.

Issue: before installing SSMS I can successfully open the Sql Server 2016 Config Manager (from the Sql 2016 install).  After installing SSMS v 17.4 the Sql 2016 Config Manager still opens properly but trying to open the "Sql Server 2017 Configuration Manager" ("run as administrator") gives this error

"Cannot connect to WMI provider. You do not have permission or the server is unreachable. Note that you can only manage SQL Server 2005 and later servers with SQL Server Configuration Manager. Invalid namespace (0x8004100e)

From an Internet search this URL looks promising: "https://sqlserver-help.com/tag/invalid-namespace-0x8004100e/"

Haven't tried it yet.

Question:  What is the source of this repeatable error? Did I miss an install step or do something in the wrong order?

TIA,

edm2

Hi,

We will deploy a SQL 2017 standard clustered instance on two Windows 2016 servers using our licensed media till our customer license is available as they sent us the PO and it will require around two weeks to secure the license.

My question if it is possible to change the installed product key for both SQL servers with the new product key once it is available; we know that it is possible for stand-alone servers using edition upgrade option under maintenance; but for clustered instances we do not know how to do it.

I am working on a Delph DB application, and trying to convert it to use MS SQL Server with “LocalDB”.  I’m running into some installation problems, and also have other questions.  I am using the 2016 version of MS SQL Server Express – LocalDB.

I can’t seem to make LocalDB work without first installing the full MS SQL Server Express, and installing LocaldB.  If I then, uninstall MS SQL Server Express it will work.  Something is just not being setup in just the lone LocalDB installation, and there is something lingering from the full MS SQL Server Express installation that is making it work.  The error message that I usually get is that it can’t find the server, but I’ve gotten different ones as well.  I’ve seen other solutions on the web, but they either don’t work, or apply to older versions.  This application must install easily.

The second question is:  Will MS SQL Server work with older Operating System (Windows 7 and prior).  I’ve seen some discussions that that might be the case.  Also is there a 32-bit version of MS SQL Server 2016?  I’ve been unable to find them.  In that case, I may be forced to go to an earlier version of MS SQL Server.  I’ve seen some discussions that there might be work around, at lease for working in Windows 7 – 64 bit, but not sure about the 32-bit?