Hi,

I am getting below error while installing SQL server, when selected domain account for SQL server engine startup account and press next.

(11) 2020-02-16 14:58:48 Slp: Sco: Attempting to check if container 'WinNT://DOMAIN' of user account exists
(11) 2020-02-16 14:58:48 Slp: Prompting user if they want to retry this action due to the following failure:
(11) 2020-02-16 14:58:48 Slp: ----------------------------------------
(11) 2020-02-16 14:58:48 Slp: The following is an exception stack listing the exceptions in outermost to innermost order
(11) 2020-02-16 14:58:48 Slp: Inner exceptions are being indented
(11) 2020-02-16 14:58:48 Slp: 
(11) 2020-02-16 14:58:48 Slp: Exception type: Microsoft.SqlServer.Configuration.Sco.ScoException
(11) 2020-02-16 14:58:48 Slp:     Message: 
(11) 2020-02-16 14:58:48 Slp:         Access is denied.
(11) 2020-02-16 14:58:48 Slp:         
(11) 2020-02-16 14:58:48 Slp:     HResult : 0x84bb0001
(11) 2020-02-16 14:58:48 Slp:         FacilityCode : 1211 (4bb)
(11) 2020-02-16 14:58:48 Slp:         ErrorCode : 1 (0001)
(11) 2020-02-16 14:58:48 Slp:     Data: 
(11) 2020-02-16 14:58:48 Slp:       WatsonData = Domain
(11) 2020-02-16 14:58:48 Slp:       DisableRetry = true
(11) 2020-02-16 14:58:48 Slp:     Inner exception type: System.UnauthorizedAccessException
(11) 2020-02-16 14:58:48 Slp:         Message: 
(11) 2020-02-16 14:58:48 Slp:                 Access is denied.
(11) 2020-02-16 14:58:48 Slp:                 
(11) 2020-02-16 14:58:48 Slp:         HResult : 0x80070005
(11) 2020-02-16 14:58:48 Slp:         Stack: 
(11) 2020-02-16 14:58:48 Slp:                 at System.DirectoryServices.Interop.UnsafeNativeMethods.IAdsContainer.GetObject(String className, String relativeName)
(11) 2020-02-16 14:58:48 Slp:                 at System.DirectoryServices.DirectoryEntries.Find(String name, String schemaClassName)
(11) 2020-02-16 14:58:48 Slp:                 at Microsoft.SqlServer.Configuration.Sco.User.LookupADEntry()

I am installing SQL server 2016 STD version on Windows 2016 OS which joined to Domain controller.

Note:  I can install by selecting Local System as startup account. later can change through configuration manager.  I can't do this workaround for Cluster installation.

Any body faced this issue?

Hi All,

Currently I've install SQLSERVER Express on my laptop and now I am trying to install SQLSERVER 2019 CTP3.1 Developer Edition into the same Laptop.
Current version :

I have this issue in installing the sqlserver with logs as below :

Microsoft SQL Server 2019 Community Technology Preview 3.1 - System Configuration Check Report

Computer Name(s): LAPTOP-36GH24FB
Report Date/Time: 2020-02-26 16:46
Saved to Directory: C:\Program Files\Microsoft SQL Server\150\Setup Bootstrap\Log\20200226_164454\SystemConfigurationCheck_Report.htm

Rule NameRule DescriptionResultMessage/Corrective Action
GlobalRules: SQL Server 2019 CTP3.1 Setup configuration checks for rules group 'GlobalRules'
ServerCore64BitCheckChecks if this version of SQL Server is 64bit.Not applicableThis rule does not apply to your system configuration.
AclPermissionsFacetChecks if the SQL Server registry keys are consistent.PassedSQL Server registry keys are consistent and can support SQL Server installation or upgrade.
FacetWOW64PlatformCheckDetermines whether SQL Server Setup is supported on this operating system platform.PassedSQL Server Setup is supported on this operating system platform.
HasSecurityBackupAndDebugPrivilegesCheckChecks whether the account that is running SQL Server Setup has the right to back up files and directories, the right to manage auditing and the security log and the right to debug programs.PassedThe account that is running SQL Server Setup has the right to back up files and directories, the right to manage auditing and security log and the right to debug programs.
MediaPathLengthChecks whether the SQL Server installation media is too long.PassedThe SQL Server installation media is not too long.
RebootRequiredCheckChecks if a pending computer restart is required. A pending restart can cause Setup to fail.PassedThe computer does not require a restart.
SetupCompatibilityCheckChecks whether the current version of SQL Server is compatible with a later installed version.PassedSetup has not detected any incompatibilities.
ThreadHasAdminPrivilegeCheckChecks whether the account running SQL Server Setup has administrator rights on the computer.PassedThe account running SQL Server Setup has administrator rights on the computer.
WmiServiceStateCheckChecks whether the WMI service is started and running on the computer.PassedThe Windows Management Instrumentation (WMI) service is running.
InstallGlobalRules: SQL Server 2019 CTP3.1 Setup configuration checks for rules group 'InstallGlobalRules'
ServerCoreBlockUnsupportedSxSCheckChecks if an earlier version of SQL Server is currently installed.Not applicableThis rule does not apply to your system configuration.
AclPermissionsFacetChecks if the SQL Server registry keys are consistent.PassedSQL Server registry keys are consistent and can support SQL Server installation or upgrade.
BlockUnsupportedSxSCheckChecks for the existance of any SQL 2019 CTP instances prior than CTP 3.0.PassedNo SQL 2019 pre-CTP3.0 instances were discovered.
FacetDomainControllerCheckChecks whether the computer is a domain controller. Installing SQL Server 2019 CTP3.1 on a domain controller is not recommended.PassedThis computer is not a domain controller.
IsFirewallEnabledChecks whether the Windows Firewall is enabled.PassedThe Windows Firewall is not enabled. Remote access will not be blocked by Windows. Third party firewalls could still result in access failures.
InstallFeatureSpecificConfigRules: SQL Server 2019 CTP3.1 Setup configuration checks for rules group 'InstallFeatureSpecificConfigRules'
ASIsValidEditionForDeploymentModeCheckChecks whether the SQL Server edition supports the currently selected Analysis Services server mode.Not applicableThis rule does not apply to your system configuration.
InstanceClashRuleChecks whether the specified instance name is already used by an existing SQL Server instance.Not applicableThis rule does not apply to your system configuration.
BlockCrossLanguageInstallChecks whether the Setup language is the same as the language of existing SQL Server features.PassedThere are no existing SQL Server features, or the Setup language is as same as the language of existing SQL Server features.
BlockMixedArchitectureInstallChecks whether the installing feature(s) are the same CPU architecture as the specified instance.PassedThe CPU architecture of the installing feature(s) matches the specified instance.
FAT32FileSystemCheckChecks whether the specified drive is FAT32 file system volume. Installing on a FAT32 file system is supported but not recommended as it is less secure than the NTFS file system.PassedThe specified drive is not the FAT32 file system.
StandaloneInstall_HasClusteredOrPreparedInstanceCheckChecks if the selected instance name is already used by an existing cluster-prepared or clustered instance on any cluster node.PassedNo clustered or cluster-prepared instance with the selected instance name is installed on any cluster node.

Summary :

Sorry i can't upload image / links since my account is not verified yet.

We are starting to look for a physical server for SQL Server for our ERP. We will be utilizing Enterprise Edition licenses.

There is a bit of a debate on what the ideal way to provision the physical servers with regards to CPU clock speed versus CPU core count.

For instance, is a Intel Gold 6254, 4 x 18 cores, 3.1 Ghz more preferential to a Platinum 8260, 4 x 24 cores, 2,4 Ghz?

Has anyone come across a white paper that further delves into this type of topic?

NJPA

Hi,

SQL Server 2019 does not support seamless upgrade for SSRS - from following post it was concluded that report server configuration like setting web service url and web portal url, etc has to be done manually although report Server database can be re-used to save time and efforts. Pls correct me if my understanding is incorrect.

https://social.msdn.microsoft.com/Forums/sqlserver/en-US/74713627-8571-4086-8968-86de3c246286/no-seamless-upgrade-for-ssrs-in-sql-server-2019?forum=sqlsetupandupgrade

As configuration requires manual steps, there is a real danger that SQL Server 2014 upgrade could be delayed, even though Microsoft support would end soon. Is there a way to automate these steps somehow ? 

Appreciate your valuable insights !!

We have issues when try to run Setip.exe SQL Server 2012, this simply not show anything so we aplied reset policies with Caspol.exe but without any success. 

BR's 

Dears,

I´m trying to install SQL Server 2008 Express Edition or SQL Server 2016 Developer Edition on Windows 10 Pro, there's no Database Engine to select using GUI Setup.

Any Tip ?

Thanks,

Emerson Muniz

Brazil

Because I did see only an empty ssis toolboxI tried to reinstall SSIS Version 3.4 and I got an error and following protokol:

[0A70:1AA8][2020-03-04T18:45:56]i001: Burn v3.7.1224.0, Windows v6.2 (Build 9200: Service Pack 0), path: .\Downloads\Microsoft.DataTools.IntegrationServices.exe, cmdline: ''
[0A70:1AA8][2020-03-04T18:45:56]i000: Initializing string variable 'ProductVersionVar' to value '15.0.2000.71'
[0A70:1AA8][2020-03-04T18:45:56]i000: Initializing string variable 'ReleaseVersion' to value '3.4'
[0A70:1AA8][2020-03-04T18:45:56]i000: Initializing string variable 'LicenseTermsUrl' to value 'https://go.microsoft.com/fwlink/?LinkID=853828&clcid='
[0A70:1AA8][2020-03-04T18:45:56]i000: Initializing string variable 'PreviewStatementUrl' to value

../ some lines I had to delete because of size / ..

[27A0:0C4C][2020-03-04T18:47:31]i301: Applying execute package: SSAS_AMO2016, action: Repair, path: C:\ProgramData\Package Cache\{97A881AD-5134-4CD2-A6A8-371C83E5622B}v13.1.4561.14\payload\SQL_AS_AMO2016.msi, arguments: ' ARPSYSTEMCOMPONENT="1" MSIFASTINSTALL="7"'
[0A70:1AA8][2020-03-04T18:47:31]i000: MainViewModel.OnPackageActionProgress: Percent completed: 15, Overall progress: 47
[0A70:1AA8][2020-03-04T18:47:31]i000: MainViewModel.OnPackageActionProgress: Percent completed: 24, Overall progress: 48
[0A70:1AA8][2020-03-04T18:47:31]i000: MainViewModel.OnPackageActionProgress: Percent completed: 37, Overall progress: 49
[0A70:1AA8][2020-03-04T18:47:31]i000: MainViewModel.OnPackageActionProgress: Percent completed: 50, Overall progress: 50
[0A70:1AA8][2020-03-04T18:47:31]i000: MainViewModel.OnPackageActionProgress: Percent completed: 63, Overall progress: 51
[0A70:1AA8][2020-03-04T18:47:31]i000: MainViewModel.OnPackageActionProgress: Percent completed: 76, Overall progress: 52
[0A70:1AA8][2020-03-04T18:47:32]i000: MainViewModel.OnPackageActionProgress: Percent completed: 89, Overall progress: 53
[0A70:1AA8][2020-03-04T18:47:40]i000: MainViewModel.OnPackageAction: Repair Completed for package Microsoft SQL Server 2016 Analysis Management Objects (id: SSAS_AMO2016)
[0A70:1AA8][2020-03-04T18:47:40]i319: Applied execute package: SSAS_AMO2016, result: 0x0, restart: None
[27A0:0C4C][2020-03-04T18:47:40]i325: Registering dependency: {a20f3707-a180-41c0-b1b0-ae2feb783bfd} on package provider: {97A881AD-5134-4CD2-A6A8-371C83E5622B}, package: SSAS_AMO2016
[27A0:0C4C][2020-03-04T18:47:40]i323: Registering package dependency provider: {C49E181B-C19F-4A1F-BE76-D463E7E3B2B5}, version: 13.1.4561.14, package: SSAS_OLEDB2016
[0A70:1AA8][2020-03-04T18:47:40]i000: MainViewModel.OnPackageAction: Repair Started for package Microsoft AS OLE DB Provider for SQL Server 2016 (id: SSAS_OLEDB2016)
[27A0:0C4C][2020-03-04T18:47:40]i301: Applying execute package: SSAS_OLEDB2016, action: Repair, path: C:\ProgramData\Package Cache\{C49E181B-C19F-4A1F-BE76-D463E7E3B2B5}v13.1.4561.14\payload\SQL_AS_OLEDB2016.msi, arguments: ' ARPSYSTEMCOMPONENT="1" MSIFASTINSTALL="7"'
[0A70:1AA8][2020-03-04T18:47:41]i000: MainViewModel.OnPackageActionProgress: Percent completed: 15, Overall progress: 55
[0A70:1AA8][2020-03-04T18:47:41]i000: MainViewModel.OnPackageActionProgress: Percent completed: 28, Overall progress: 56
[0A70:1AA8][2020-03-04T18:47:41]i000: MainViewModel.OnPackageActionProgress: Percent completed: 41, Overall progress: 57
[0A70:1AA8][2020-03-04T18:47:41]i000: MainViewModel.OnPackageActionProgress: Percent completed: 54, Overall progress: 58
[0A70:1AA8][2020-03-04T18:47:41]i000: MainViewModel.OnPackageActionProgress: Percent completed: 67, Overall progress: 59
[0A70:1AA8][2020-03-04T18:47:41]i000: MainViewModel.OnPackageActionProgress: Percent completed: 80, Overall progress: 60
[0A70:1AA8][2020-03-04T18:47:42]i000: MainViewModel.OnPackageActionProgress: Percent completed: 95, Overall progress: 61
[0A70:1AA8][2020-03-04T18:47:45]i000: MainViewModel.OnPackageAction: Repair Completed for package Microsoft AS OLE DB Provider for SQL Server 2016 (id: SSAS_OLEDB2016)
[0A70:1AA8][2020-03-04T18:47:45]i319: Applied execute package: SSAS_OLEDB2016, result: 0x0, restart: None
[27A0:0C4C][2020-03-04T18:47:45]i325: Registering dependency: {a20f3707-a180-41c0-b1b0-ae2feb783bfd} on package provider: {C49E181B-C19F-4A1F-BE76-D463E7E3B2B5}, package: SSAS_OLEDB2016
[27A0:0C4C][2020-03-04T18:47:45]i323: Registering package dependency provider: {A1EF85A7-37B3-459F-B9E8-2A235BD5E98F}, version: 14.0.3002.563, package: SSDTISSingleton140
[0A70:1AA8][2020-03-04T18:47:45]i000: MainViewModel.OnPackageAction: Repair Started for package Microsoft SQL Server Integration Services Singleton (id: SSDTISSingleton140)
[27A0:0C4C][2020-03-04T18:47:45]i301: Applying execute package: SSDTISSingleton140, action: Repair, path: C:\ProgramData\Package Cache\{A1EF85A7-37B3-459F-B9E8-2A235BD5E98F}v14.0.3002.563\payload\SSDTISSingleton140.msi, arguments: ' MSIFASTINSTALL="7"'
[0A70:1AA8][2020-03-04T18:47:45]i000: MainViewModel.OnPackageActionProgress: Percent completed: 15, Overall progress: 62
[0A70:1AA8][2020-03-04T18:47:45]i000: MainViewModel.OnPackageActionProgress: Percent completed: 23, Overall progress: 63
[0A70:1AA8][2020-03-04T18:47:45]i000: MainViewModel.OnPackageActionProgress: Percent completed: 39, Overall progress: 64
[0A70:1AA8][2020-03-04T18:47:45]i000: MainViewModel.OnPackageActionProgress: Percent completed: 48, Overall progress: 65
[0A70:1AA8][2020-03-04T18:47:45]i000: MainViewModel.OnPackageActionProgress: Percent completed: 64, Overall progress: 66
[0A70:1AA8][2020-03-04T18:47:45]i000: MainViewModel.OnPackageActionProgress: Percent completed: 73, Overall progress: 67
[0A70:1AA8][2020-03-04T18:47:45]i000: MainViewModel.OnPackageActionProgress: Percent completed: 84, Overall progress: 68
[0A70:1AA8][2020-03-04T18:47:46]i000: MainViewModel.OnPackageActionProgress: Percent completed: 98, Overall progress: 69
[0A70:1AA8][2020-03-04T18:47:46]i000: MainViewModel.OnPackageAction: Repair Completed for package Microsoft SQL Server Integration Services Singleton (id: SSDTISSingleton140)
[0A70:1AA8][2020-03-04T18:47:46]i319: Applied execute package: SSDTISSingleton140, result: 0x0, restart: None
[27A0:0C4C][2020-03-04T18:47:46]i325: Registering dependency: {a20f3707-a180-41c0-b1b0-ae2feb783bfd} on package provider: {A1EF85A7-37B3-459F-B9E8-2A235BD5E98F}, package: SSDTISSingleton140
[27A0:0C4C][2020-03-04T18:47:46]i323: Registering package dependency provider: {13132923-6F86-4B22-8D23-11DCE88FC7F4}, version: 15.0.2000.71, package: SSDTISSingleton
[0A70:1AA8][2020-03-04T18:47:46]i000: MainViewModel.OnPackageAction: Repair Started for package Microsoft SQL Server Integration Services Singleton (id: SSDTISSingleton)
[27A0:0C4C][2020-03-04T18:47:46]i301: Applying execute package: SSDTISSingleton, action: Repair, path: C:\ProgramData\Package Cache\{13132923-6F86-4B22-8D23-11DCE88FC7F4}v15.0.2000.71\payload\SSDTISSingleton.msi, arguments: ' MSIFASTINSTALL="7"'
[0A70:1AA8][2020-03-04T18:47:47]i000: MainViewModel.OnPackageActionProgress: Percent completed: 15, Overall progress: 70
[0A70:1AA8][2020-03-04T18:47:47]i000: MainViewModel.OnPackageActionProgress: Percent completed: 23, Overall progress: 71
[0A70:1AA8][2020-03-04T18:47:47]i000: MainViewModel.OnPackageActionProgress: Percent completed: 39, Overall progress: 72
[0A70:1AA8][2020-03-04T18:47:47]i000: MainViewModel.OnPackageActionProgress: Percent completed: 56, Overall progress: 73
[0A70:1AA8][2020-03-04T18:47:47]i000: MainViewModel.OnPackageActionProgress: Percent completed: 64, Overall progress: 74
[0A70:1AA8][2020-03-04T18:47:47]i000: MainViewModel.OnPackageActionProgress: Percent completed: 75, Overall progress: 75
[0A70:1AA8][2020-03-04T18:47:47]i000: MainViewModel.OnPackageActionProgress: Percent completed: 88, Overall progress: 76
[0A70:1AA8][2020-03-04T18:47:51]i000: BootstrapperEngineDataModel.OnExecutePackageComplete: Package requires a restart but it has not been initiated yet.
[0A70:1AA8][2020-03-04T18:47:51]i000: MainViewModel.OnPackageAction: Repair Completed for package Microsoft SQL Server Integration Services Singleton (id: SSDTISSingleton)
[0A70:1AA8][2020-03-04T18:47:51]i319: Applied execute package: SSDTISSingleton, result: 0x0, restart: Required
[27A0:0C4C][2020-03-04T18:47:51]i325: Registering dependency: {a20f3707-a180-41c0-b1b0-ae2feb783bfd} on package provider: {13132923-6F86-4B22-8D23-11DCE88FC7F4}, package: SSDTISSingleton
[27A0:0C4C][2020-03-04T18:47:51]i323: Registering package dependency provider: ISVsixPreInstall, version: 1.0.0.0, package: ISVsixPreInstall
[0A70:1AA8][2020-03-04T18:47:51]i000: MainViewModel.OnPackageAction: Repair Started for package Microsoft SQL Server Integration Services Projects Pre Install (id: ISVsixPreInstall)
[27A0:0C4C][2020-03-04T18:47:51]i301: Applying execute package: ISVsixPreInstall, action: Install, path: C:\ProgramData\Package Cache\2FC1517AABA51C6B742AD49998003E7910042F0E\ISVsixPreInstall.exe, arguments: '"C:\ProgramData\Package Cache\2FC1517AABA51C6B742AD49998003E7910042F0E\ISVsixPreInstall.exe" /instanceIds:"33f63265" /log:".\AppData\Local\Temp\SsdtisSetup\Microsoft.DataTools.IntegrationServices_20200304184556_10_ISVsixPreInstall.log"'
[0A70:1AA8][2020-03-04T18:47:51]i000: MainViewModel.OnPackageActionProgress: Percent completed: 50, Overall progress: 80
[0A70:1AA8][2020-03-04T18:47:51]i000: MainViewModel.OnPackageActionProgress: Percent completed: 100, Overall progress: 84
[0A70:1AA8][2020-03-04T18:47:51]i000: MainViewModel.OnPackageAction: Repair Completed for package Microsoft SQL Server Integration Services Projects Pre Install (id: ISVsixPreInstall)
[0A70:1AA8][2020-03-04T18:47:51]i319: Applied execute package: ISVsixPreInstall, result: 0x0, restart: None
[27A0:0C4C][2020-03-04T18:47:51]i325: Registering dependency: {a20f3707-a180-41c0-b1b0-ae2feb783bfd} on package provider: ISVsixPreInstall, package: ISVsixPreInstall
[27A0:0C4C][2020-03-04T18:47:51]i323: Registering package dependency provider: ISVsix, version: 1.0.0.0, package: ISVsix
[0A70:1AA8][2020-03-04T18:47:51]i000: MainViewModel.OnPackageAction: Repair Started for package Microsoft SQL Server Integration Services Projects (id: ISVsix)
[27A0:0C4C][2020-03-04T18:47:51]i301: Applying execute package: ISVsix, action: Install, path: C:\ProgramData\Package Cache\15160B731819F56D87A626F9A2777550340022D7\VSIXBootstrapper.exe, arguments: '"C:\ProgramData\Package Cache\15160B731819F56D87A626F9A2777550340022D7\VSIXBootstrapper.exe" /q /admin /instanceIds:"33f63265" /logFile:".\AppData\Local\Temp\SsdtisSetup\Microsoft.DataTools.IntegrationServices_20200304184556_11_ISVsix.log" "payload\Microsoft.DataTools.IntegrationServices.vsix"'
[0A70:1AA8][2020-03-04T18:47:51]i000: MainViewModel.OnPackageActionProgress: Percent completed: 50, Overall progress: 88
[27A0:0C4C][2020-03-04T18:48:10]e000: Error 0x80131500: Process returned error: 0x80131500
[27A0:0C4C][2020-03-04T18:48:10]e000: Error 0x80131500: Failed to execute EXE package.
[0A70:1AA8][2020-03-04T18:48:10]e000: Error 0x80131500: Failed to configure per-machine EXE package.
[0A70:1AA8][2020-03-04T18:48:10]i000: MainViewModel.OnPackageAction: Repair Completed for package Microsoft SQL Server Integration Services Projects (id: ISVsix)
[0A70:1AA8][2020-03-04T18:48:10]i319: Applied execute package: ISVsix, result: 0x80131500, restart: None
[0A70:1AA8][2020-03-04T18:48:10]e000: Error 0x80131500: Failed to execute EXE package.
[27A0:0C4C][2020-03-04T18:48:10]i329: Removed package dependency provider: ISVsix, package: ISVsix
[27A0:0C4C][2020-03-04T18:48:10]i351: Removing cached package: ISVsix, from path: C:\ProgramData\Package Cache\15160B731819F56D87A626F9A2777550340022D7\
[27A0:0C4C][2020-03-04T18:48:10]i326: Removed dependency: {a20f3707-a180-41c0-b1b0-ae2feb783bfd} on package provider: ISVsixPreInstall, package ISVsixPreInstall
[0A70:1AA8][2020-03-04T18:48:10]i000: MainViewModel.OnPackageAction: Repair Started for package Microsoft SQL Server Integration Services Projects Pre Install (id: ISVsixPreInstall)
[0A70:1AA8][2020-03-04T18:48:10]i000: MainViewModel.OnPackageActionProgress: Percent completed: 100, Overall progress: 92
[27A0:0C4C][2020-03-04T18:48:10]i301: Applying rollback package: ISVsixPreInstall, action: Uninstall, path: C:\ProgramData\Package Cache\2FC1517AABA51C6B742AD49998003E7910042F0E\ISVsixPreInstall.exe, arguments: '"C:\ProgramData\Package Cache\2FC1517AABA51C6B742AD49998003E7910042F0E\ISVsixPreInstall.exe" /instanceIds:"33f63265" /log:".\AppData\Local\Temp\SsdtisSetup\Microsoft.DataTools.IntegrationServices_20200304184556_10_ISVsixPreInstall.log" /u'
[0A70:1AA8][2020-03-04T18:48:10]i000: MainViewModel.OnPackageAction: Repair Completed for package Microsoft SQL Server Integration Services Projects Pre Install (id: ISVsixPreInstall)
[0A70:1AA8][2020-03-04T18:48:10]i319: Applied rollback package: ISVsixPreInstall, result: 0x0, restart: None
[27A0:0C4C][2020-03-04T18:48:10]i329: Removed package dependency provider: ISVsixPreInstall, package: ISVsixPreInstall
[27A0:0C4C][2020-03-04T18:48:10]i351: Removing cached package: ISVsixPreInstall, from path: C:\ProgramData\Package Cache\2FC1517AABA51C6B742AD49998003E7910042F0E\
[27A0:0C4C][2020-03-04T18:48:10]i351: Removing cached package: SSDTISSingleton, from path: C:\ProgramData\Package Cache\{13132923-6F86-4B22-8D23-11DCE88FC7F4}v15.0.2000.71\
[27A0:0C4C][2020-03-04T18:48:10]i351: Removing cached package: SSDTISSingleton140, from path: C:\ProgramData\Package Cache\{A1EF85A7-37B3-459F-B9E8-2A235BD5E98F}v14.0.3002.563\
[27A0:0C4C][2020-03-04T18:48:10]i351: Removing cached package: SSAS_OLEDB2016, from path: C:\ProgramData\Package Cache\{C49E181B-C19F-4A1F-BE76-D463E7E3B2B5}v13.1.4561.14\
[27A0:0C4C][2020-03-04T18:48:10]i351: Removing cached package: SSAS_AMO2016, from path: C:\ProgramData\Package Cache\{97A881AD-5134-4CD2-A6A8-371C83E5622B}v13.1.4561.14\
[27A0:0C4C][2020-03-04T18:48:10]i351: Removing cached package: SSAS_AMO2014, from path: C:\ProgramData\Package Cache\{76CBDC35-0752-4B5A-83E8-49A741BD42BC}v12.2.5626.31\
[27A0:0C4C][2020-03-04T18:48:10]i351: Removing cached package: SSAS_AMO2012, from path: C:\ProgramData\Package Cache\{53086A62-13F3-4FC5-AA41-211FD74340B3}v11.4.7001.0\
[27A0:0C4C][2020-03-04T18:48:10]i351: Removing cached package: SSISOneDesigner2016, from path: C:\ProgramData\Package Cache\{1F86F7A6-BCC6-49C4-8033-785993FA6331}v13.1.4561.14\
[27A0:0C4C][2020-03-04T18:48:10]i351: Removing cached package: SSISOneDesigner2014, from path: C:\ProgramData\Package Cache\{07001141-C74D-47ED-B03D-892C7EF00E3D}v12.2.5626.31\
[27A0:0C4C][2020-03-04T18:48:10]i351: Removing cached package: SSISOneDesigner2012, from path: C:\ProgramData\Package Cache\{DB97C76B-9116-42C5-8814-0041856EB9E6}v11.4.7001.0\
[27A0:0C4C][2020-03-04T18:48:10]i351: Removing cached package: VCRedist2010, from path: C:\ProgramData\Package Cache\28C54491BE70C38C97849C3D8CFBFDD0D3C515CB\
[0A70:1AA8][2020-03-04T18:48:10]i000: MainViewModel.OnPackageActionProgress: Percent completed: 100, Overall progress: 100
[0A70:1AA8][2020-03-04T18:48:10]i000: BootstrapperEngineDataModel.OnApplyComplete: Bundle requires a restart but it has not been initiated yet.
[0A70:1AA8][2020-03-04T18:48:10]i000: TryCheckAndCopyVsixInstallerLog: Processing C:\Users\obresl01\AppData\Local\Temp\dd_VSIXInstaller_20200303165453_2594.log ...
[0A70:1AA8][2020-03-04T18:48:10]i000: TryCheckAndCopyVsixInstallerLog:   last modified at 03.03.2020 15:54:53, which is too old. Skip processing.
[0A70:1AA8][2020-03-04T18:48:10]i000: TryCheckAndCopyVsixInstallerLog: Processing C:\Users\obresl01\AppData\Local\Temp\dd_VSIXInstaller_20200303165453_2f54.log ...
[0A70:1AA8][2020-03-04T18:48:10]i000: TryCheckAndCopyVsixInstallerLog:   last modified at 03.03.2020 15:57:04, which is too old. Skip processing.
[0A70:1AA8][2020-03-04T18:48:10]e000: MainViewModel.OnBundleAction: Bundle action failed: Unknown error (0x80131500) (0x80131500)
[0A70:1AA8][2020-03-04T18:48:10]i399: Apply complete, result: 0x80131500, restart: Required, ba requested restart:  No
[0A70:0C04][2020-03-04T18:48:17]i000: MainViewModel.OpenUrl: Opening url: .\AppData\Local\Temp\SsdtisSetup\Microsoft.DataTools.IntegrationServices_20200304184556.log

Somebody can help?

regards

Olaf

olaf870

Hi,

As our company are planning to upgrade the application version and it require new SQL version, the version what that application recommended is SQL 2017 or SQL 2019, is there any chance that we can migrate the SQL server license from existing 2017 SP1 standard to 2017 standard or 2019 standard?

Thanks.

I am trying to install SQL Server Management Studio ver 18.3 on a server running Windows Server 2012, but the installation aborts with the following error message - "Fatal error during installation (0x80070643)", with the follow up instruction of "Microsoft ODBC Driver 2017 for SQL Server: Please install the Visual C++ 2017 Redistributable from https://aka.ms/vs/15/release/vc_redist.x64.exe".

However, Visual C++ 2017 is installed on the server.

I then tried to install ODBC Driver 2017 directly with the msi file from MS, but it too aborts with this error message - "Error 1723. Please install the Visual C++ 2017 Redistributable from https://aka.ms/vs/15/release/vc_redist.x64.exe before running this installer."

I appear to be caught in a installation loop. 

Has anyone come across this before? I appreciate any suggestions.

Thanks,

Herman

HI,

How can we upgrade SSRS from SQL Server 2014 to SQL Server 2019?

We understand Microsoft has decoupled SSRS from SQL Server installer set up and we need to download and install SSRS separately. If we upgrade SQL Server 2014 to SQL Server 2019, followings steps are involved. 

1. Upgrade SSAS, SSIS and Database Engine services in one shot
2. backup encryption key and Uninstall SSRS 2014 
3. Install SSRS 2019 
4. Restore encryption key
5. Perform all the reports related configuration and point to old ReportServer database

In this way we need to do minimal changes and all reports and their configuration would be retained. 

My questions are:

1. Is there is a way to upgrade SSRS seamlessly ? I meant avoid all the changes in configuration, just uninstall old SSRS and install new SSRS 
2. Is there a better way to do SSRS upgrade, other then above mentioned steps?

As always, Appreciate your insights and valuable help.

Thank you. 

I am trying to perform this upgrade (nothing newer will run on the server I have), and am so far batting zero. After starting and selecting "Upgrade existing installation", the package says it is unable to search for updates through the Windows Update service. When I skip over that step, I get a popup with the message "The specified service does not exist as an installed service", but no clue what that "...specified service..." might be. When I close that, the table of check behind says that everything has passed, but has a warning about .NET Application Security. When I click on the warning, it says that this computer cannot access the Internet, which is nonsense - it is connected and browsers work just fine. It also directed me to some Microsoft Root Authority website, but says that if I am prompted to download a .crl file, I do NOT have a security validation issue. I don't get it - if I am prompted to download this file, and that means I don't have a problem, should I download it? If so, what should I then do with it? In any case, it says it's a warning, not a show-stopper.

When I click next, it shows me the existing instance. I click on Next and that is the end of the show. The installer hangs and does not respond any further.

Nothing I have found on the net has been helpful.

Hi 

we are currently in windows 2019 with SQL 2019.  due to cost cutting , planned for moving SQL server to Linux Platform .

we have 5 SQL Boxes in windows with Transnational replication configured.  SSRS & SSAS &SSIS.

am very new with this Linux  .  Can you share Pros & cons of this migration?

can we have SSMS to interact this Linux SQL server?  what  are the main Cos for this Linux environment ? 

During the installation of SQL 2014 the Windows feature 'PowerShell 2.0' will be installed.
It's also mentioned on the website of Microsoft as an 'installation prerequisite' (https://docs.microsoft.com/en-us/sql/sql-server/install/hardware-and-software-requirements-for-installing-sql-server?view=sql-server-2014).
But is PowerShell 2.0 really required? As far a I can see PowerShell 2.0 isn't used by SQL 2014 (sqlps is also working with only PowerShell 5 installed).

My question is: is it safe to remove PowerShell 2.0 on a server (Server 2012R2/2016) with SQL 2014?

Trying to apply the Cumulative Update 4 for SQL Server 2014 SP3 I receive this error:

'There are no sql server instances that can be updated on this computer'.