Hello.

The following error is displayed when installingSQL Server 2008 R2 software. What is the Cause and Solution?

TITLE: SQL Server 2008 R2 Setup

------------------------------

The following error has occurred:

SQL Server Setup has encountered an error when running a Windows Installer file.

Windows Installer error message: Error opening installation log file. Verify that the specified log file location exists and that you can write to it.

Windows Installer file: e:\7b977b327151b114bc11be15\x64\redist\watson\dw20sharedamd64.msi

Windows Installer log file: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20200218_182833\WatsonX64_Cpu64_1_ComponentUpdate.log

Click 'Retry' to retry the failed action, or click 'Cancel' to cancel this action and continue setup.

The file name is SQLEXPR_x64_ENU.

My windows is 8.1 Professional MSDN.

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

Can someone help me understand if this is a bug or otherwise? 

We have SQL 2016 SP2  (13.2.5102.14) with no CUs installed as far as I can tell.  However, there is a recently security update which has taken it to version 5102.

When I try to install the CU11 patch, I get the following error with an unexpected version number in brackets of (13.2.5620.xx). What does this mean and how can I install the CU patches? I can't show screenshots as MS is still parenting me and doesn't trust me yet.

"A SQL Server update with a higher version has already been installed on SQL Server instance MSSQLSERVER, so the current SQL Server update cannot be applied. The version of the SQL Server update that is already installed is GDR 13.2.5102.14(13.2.5620.0) with a KBKB4532097 and the current SQL Server update is 13.2.5598.27 with a KBKB4527378."

This website gives a good overview of the versions and how they sequence, but you'll have to Google that with the following

"sqlserverbuilds SQL2016 versions 2016/01"

Thanks

Cam

Hi,

I have a frustrating problem. I have installed SP4 onto well over 100 SQL Server 2012 instances over the last month or so. All instances are named instances, all with the same instance name, all were at the same patch level and all went without any issue until now. I'm getting an installation failure, but I'm not getting any logs to study. When I run setup, a black pop up window appears and disappears instantly. I get no errors in the Bootstrap/Logs directory (no new folder is created), nothing in SQL Server logs and nothing in event viewer. I can't find anything that can help me to determine what the problem is. I'm fairly sure I've seen this before somewhere in a different role, but I can't find any details to assist. Setup.exe does not appear in the Task  Manager at all, or if it does, it disappears so quickly it can't be spotted!

All of our SQL servers are created from a template and all are identical. They are running SCCM secondary sites and the server that is failing is running SCCM normally, no errors. This is purely an error in getting the Setup process to run.  The Server that is failing is currently running build 11.0.6567.

I've checked permissions on the directory I'm running the setup from, (local disk, not UNC), my user account has SQL sysadmin and domain admin rights.

I've scripted the installation of SP4 to run silently and this has run successfully on over 100 SQL Servers, but fails on this server. I've run it manually, but I get the same problem.

Where can I look to see why the installation is failing? Has anyone else seen this happen? If I can find something logging what's happening, I will have a base to work from, but at present, I don't know where to start.

I'm not the worlds greatest SQL expert, so my apologies if I've missed anything obvious.

Many Thanks

John

Regards, John

Travis McGee

Someone recently did some new sql server installs and also upgraded the OS of some servers running SQL server.

This is in the UK.

We have noticed that on one of the servers the server clock (bottom right of task bar) is showing as a 12 hour clock and using the US data format  (mm dd yyyy)

We have noticed that all databases on the above instances (mainly sql 2012/2016) have a dataformat setting of "mdy" (as seen via dbcc useroptions)

We are concerned about this as we would expect dateformat to be set to dmy as we are in the UK.

Can anyone see an issue that this might cause with our applications ?

Team,

recently installed SQL 2019 developer edition on my system,

Microsoft SQL Server 2019 (CTP2.5) - 15.0.1500.28 (X64)  Apr 15 2019 15:33:10   Copyright (C) 2019 Microsoft Corporation  Developer Edition (64-bit) on Windows Server 2019 Standard 10.0 <X64> (Build 17763: ) 

i tried to update CU am getting below msg,  why this CU not suite with this edition(version) ?

i tried all below CU , 

Hello All,

i am facing SQL SERVER 2014 SP3.0 Upgrade Issue like it does not show any error when i run the setup which i have download from from Microsoft 

as i am not an IT guy could anyone let me know how to resolve it 

Thanks in advance 

INSTALL sqlserver 2008r2 in windows2008 server sp1 error: MOF syntax error

I am trying to connect to a azure SQL server from my local SSMS and i Getting following error.azure SQL server is configured to connect with all required  firewall  IP and i can connect to the same server from other machines.The error am getting is as follows

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

Cannot connect to server_name.

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

A connection was successfully established with the server, but then an error occurred during the login process. (provider: SSL Provider, error: 0 - The certificate chain was issued by an authority that is not trusted.) (.Net SqlClient Data Provider)

------------------------------

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

------------------------------

Server Name: server_name

Error Number: -2146893019

Severity: 20

State: 0

------------------------------

Program Location:

   at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, SqlCredential credential, Object providerInfo, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance, SqlConnectionString userConnectionOptions, SessionData reconnectSessionData, DbConnectionPool pool, String accessToken, Boolean applyTransientFaultHandling, SqlAuthenticationProviderManager sqlAuthProviderManager)

   at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, DbConnectionPoolKey poolKey, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection, DbConnectionOptions userOptions)

   at System.Data.ProviderBase.DbConnectionFactory.CreateNonPooledConnection(DbConnection owningConnection, DbConnectionPoolGroup poolGroup, DbConnectionOptions userOptions)

   at System.Data.ProviderBase.DbConnectionFactory.TryGetConnection(DbConnection owningConnection, TaskCompletionSource`1 retry, DbConnectionOptions userOptions, DbConnectionInternal oldConnection, DbConnectionInternal& connection)

   at System.Data.ProviderBase.DbConnectionInternal.TryOpenConnectionInternal(DbConnection outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource`1 retry, DbConnectionOptions userOptions)

   at System.Data.ProviderBase.DbConnectionClosed.TryOpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource`1 retry, DbConnectionOptions userOptions)

   at System.Data.SqlClient.SqlConnection.TryOpenInner(TaskCompletionSource`1 retry)

   at System.Data.SqlClient.SqlConnection.TryOpen(TaskCompletionSource`1 retry)

   at System.Data.SqlClient.SqlConnection.Open()

   at Microsoft.SqlServer.Management.SqlStudio.Explorer.ObjectExplorerService.ValidateConnection(UIConnectionInfo ci, IServerType server)

   at Microsoft.SqlServer.Management.UI.ConnectionDlg.Connector.ConnectionThreadUser()

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

The certificate chain was issued by an authority that is not trusted

Hello,

We are currently facing this situation:

After each Windows update the SQL Server Launchpad fails to start.

The workaround that i'm currently apply is this.

Services - SQL Server Launchpad - Log On - Delete the autofilled password and confirm password - Apply. 

After this the service starts without a problem.

Any ideas on a permanent fix? ( It would be ideal if i don't have to create a separate account and would continue using the NT Service\MSSQLLaunchpad account)

Thank you,

Bogdan

Hi,

We tried upgrading SQL 2014 to SQL 2019 on Windows Server 2016 - Now there are two versions of SSIS, one for SQL 2014 and another for SQL 2019. This seems to be fresh install for SSIS and upgrade for other services. 

Appreciate your insightful response. Thank you.

Configuration manager

Also checked INI and summary file - all looks good. Attaching same in case you find some clue what is happening. 

Summary file

INI file

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