Hi,

My Solution explorer is blank, I open a new solution or Project and all looks like its opened ok, but nothing in the explorer?

When I open the solution in SSMS 2008 it all works fine.

Help?

Hi all. 

I have an instance of SQL server that I have tried to inplace upgrade but failed. 

Current version SQL server 2014 Ent. 

Target version SQL server 2017 Ent. 

The upgrade failed with lack of permission to update the permission of the backup destination. 

<-------------------- OUTPUT FROM THE SETUP LOG ------------------------------->

  Feature:                       Database Engine Services
  Status:                        Failed
  Reason for failure:            An error occurred during the setup process of the feature.
  Next Step:                     The upgrade process for SQL Server failed. To continue the upgrade process, use the following information to resolve the error. Next, uninstall SQL Server by using this command line: setup /q /action=uninstall /instanceid=<INSTANCE_NAME_REMOVED> /features=FULLTEXT,SQLENGINE,REPLICATION. Then, run SQL Server Setup again.
  Component name:                SQL Server Database Engine Services Instance Features
  Component error code:          0x84CF0003
  Error description:            Updating permission setting for folder '\\SQLBackup-DCD02P.oneadr.net\SQLBackup\Backup' failed. The folder permission setting were supposed to be set to 'D:(A;OICI;FA;;;S-1-5-21-2077435073-541759679-708572619-1383108)'.
  Error help link:               https://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=14.0.1000.169&EvtType=0x88792597%400xBB814387&EvtType=0x88792597%400xBB814387

<-------------------- OUTPUT FROM THE SETUP LOG ------------------------------->

The log tell us to fix the issue by uninstalling the SQL server instance. I would prefer an alternative if possible :) 

I changed the backup destination to local folder and ran the upgrade wizzard again. Now it claims that it does not have anything to upgrade even though the SQL server instance has not been upgraded. 

The server was rebooted before the second try. 

Any good ideas of what to do ? 

Hi Team,

while connecting sql server 2012 from SSMS 2008, please help me with this on urgent basis.

error as follows "A connection was sucessfully established with server, but then an error occurred during the login process, (provider: SSL Provide : 0 -An existing connection was forcibly closed by the remote host.) (Microsoft SQL Server, Error : 10054)

                         An existing connection was forcibly closed by the remote host..........."

Regards,

v

Hi,

I have installed SQL Server 2017 Developer edition. I have Launchpad service running under Network Service account and Database engine running under NT Service\MSSQLSERVER. I have enabled external scripts as well launchpad and database engine is up and running, still I see the below error while executing python code.

Msg 39011, Level 16, State 1, Line 8
SQL Server was unable to communicate with the LaunchPad service. Please verify the configuration of the service.  

Can you please provide more info on this ? Do you require Launchpad and Database engine running under same service account.

Thanks,

Shantanu.

I wish I could share photos and a direct link to the code but my account won't even offer to verify me for some reason. Please remove spaces and replace the word dot with periods and slash with / to get the real addresses to the info I am sharing.

Hi Folks! I seem to be having difficulty installing SQL server 2008 on a laptop. Would any of you have any insights into how to get the install working?

Also, thank you for being here for everybody. I appreciate your help you guys provide to the community.

postimg DOTccSLASH imageSLASH yz5qefcx7

The setup fails (as per the picture above) to install the 3 main components, Database Engine Services, SQL Server Replication and Management Tools. I need to get these working to be able to get some health related people who I represent on the road :)

Here is my details.txt error log from the install:

pasted DOTcoSLASH bf757c69

Thank you again for your help on this matter. It makes a world of difference.

Hi All,

I installed a SQL server 2008 R2 on a 64 bit Stand alone system today morning

Now i am trying to apply SP1 on it. But it is not progressing further with the below. Please suggest me how to over cum this issue.

Note: Cluster services not installed on this server. Cluster service is not there in the services.msc as well.

This is just a query.

General best practice by us is not  to patch Windows Server 2012 R2 & SQL Server 2014 SP2 on same day (VM's and Clustered).

Can you please tell me the risks involved here?

none

TITLE: Microsoft SQL Server 2016 Setup
------------------------------

The following error has occurred:

An error occurred during the installation of assembly 'Microsoft.AnalysisServices.AdomdClient,fileVersion="13.0.1601.5",version="13.0.0.0000",culture="neutral",publicKeyToken="89845DCD8080CC91",processorArchitecture="MSIL"'. The signature or catalog could not be verified or is not valid

Trying to install it on windows server 2016 - virtual box 

Installed all patches below:

SQL 2012 Service Pack 1 SQL 2012 Service Pack 2 SQL 2012 Service Pack 3 SQL 2012 Service Pack 3 - Hotfix for TLS1.2 Still the SQL SERVER 2012 cannot start as per error below.

A fatal error occurred while creating an SSL client credential. The internal error state is 10013. The server was unable to initialize encryption because of a problem with a security library. The security library may be missing. Verify that security.dll exists on the system. TDSSNIClient initialization failed with error 0x139f, status code 0x80. Reason: Unable to initialize SSL support. The group or resource is not in the correct state to perform the requested operation. TDSSNIClient initialization failed with error 0x139f, status code 0x1. Reason: Initialization failed with an infrastructure error. Check for previous errors. The group or resource is not in the correct state to perform the requested operation. Could not start the network library because of an internal error in the network library. To determine the cause, review the errors immediately preceding this one in the error log. SQL Server could not spawn FRunCommunicationsManager thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.

SQLLog

2018-07-12 11:16:25.10 spid10s The server could not load the certificate it needs to initiate an SSL connection. It returned the following error: 0x80090331. Check certificates to make sure they are valid. 2018-07-12 11:16:25.11 spid10s Error: 26014, Severity: 16, State: 1. 2018-07-12 11:16:25.11 spid10s Unable to load user-specified certificate [Cert Hash(sha1) "1E40ACCA7AB499E2967FE691A9FBCCAA39A122CC"]. The server will not accept a connection. You should verify that the certificate is correctly installed. See "Configuring Certificate for Use by SSL" in Books Online. 2018-07-12 11:16:25.11 spid10s Error: 17182, Severity: 16, State: 1. 2018-07-12 11:16:25.11 spid10s TDSSNIClient initialization failed with error 0x80092004, status code 0x80. Reason: Unable to initialize SSL support. Cannot find object or property. 2018-07-12 11:16:25.11 spid10s Error: 17182, Severity: 16, State: 1. 2018-07-12 11:16:25.11 spid10s TDSSNIClient initialization failed with error 0x80092004, status code 0x1. Reason: Initialization failed with an infrastructure error. Check for previous errors. Cannot find object or property. 2018-07-12 11:16:25.11 spid10s Error: 17826, Severity: 18, State: 3. 2018-07-12 11:16:25.11 spid10s Could not start the network library because of an internal error in the network library. To determine the cause, review the errors immediately preceding this one in the error log. 2018-07-12 11:16:25.11 spid10s Error: 17120, Severity: 16, State: 1. 2018-07-12 11:16:25.11 spid10s SQL Server could not spawn FRunCommunicationsManager thread. Check the SQL Server error log and the Windows event logs for information about possible related problems. Is there really a solution for this?

HI,

Our customers are usually smaller ones and don't have their own DBA. We are working on a custom installer which could install SQL Server 2017, SSMS, SSRS instance and our own applications in one shot and in silent mode (start once and sit ideal till environment is set up) 

Once SQL Server engine is installed, SSMS installation fails as it asks for rebooting the server. Can we suppress server reboot ? in other case, we need to put lot of efforts to modify our custom installer.  Is there any other way to get things done ?

Appreciate your insight !! Thank you. 

I am getting the error: "Cannot connect to WMI provider. You do not have permission or the server is unreachable."

I tried the solution posted on the Microsoft support page involving a command prompt and themofcomp "%programfiles(x86)%\Microsoft SQL Server\<var class="sbody-var">number</var>\Shared\sqlmgmproviderxpsp2up.mof"

This still does not fix the problem, the result of running the above is:

Parsing MOF file: C:\Program Files (x86)\Microsoft SQL Server\110\Shared\sqlmgmp
roviderxpsp2up.mof
MOF file has been successfully parsed
Storing data in the repository...
An error occurred while processing item 1 defined on lines 4 - 7 in file C:\Prog
ram Files (x86)\Microsoft SQL Server\100\Shared\sqlmgmproviderxpsp2up.mof:
Error Number: 0x80041003, Facility: WMI
Description: Access denied
Compiler returned error 0x80041003

Is there way to completely re-install the Configuration Manager? One post suggested the Access denied was Administrator rights but I have full Administrative rights to everything so I don't see that being the problem. The command prompt is not working, what other solution can you suggest?

I'm working inside the government lab and Windows Update Service is disabled (they install updates).   SQL Server 2012 Setup insists on having Windows Update Service running. 

How can I install SQL Server 2012 in this situation?   I tried both 2012 and 2012 Sp4 ISOs and both failed exactly the same way, not able to find Windows Update Service running.

Hi ,

I am trying to install SQL Server 2014  evaluation version on my system 

(Windows 7) , all configuration & compatibility test passed but not able to install.

getting  below error at the end step.

SQL Server 2014\1033_ENU_LP\x64\setup\sql2008support.msi does not exist

Please help how to fix this error and complete the installation.

I'm getting the above error when trying to install a new instance of SQL Server 2017 developer edition. I've read that this can be caused by the installation trying to install an earlier version of the c++ distributable when visual studio 2017 is installed. So I've tried uninstalling visual studio, repairing then uninstalling the visual C++ redistributable (both) and running the installation under the windows administrator account, but not getting any luck. Are there any other ideas on what might work?

During cluster install just after setting up installation files get the above error. Tried on both the active and passive node, got domain admin to try but still the same. Checked for RemoteRegistry running on both nodes and looks like they are.

Log file on passive cluster gives (Cutdown version due to space) :

(01) 2018-07-16 10:43:29 Slp: Running Action: InitializeConfigAction
(01) 2018-07-16 10:43:29 Slp: Completed Action: InitializeConfigAction, returned True
(01) 2018-07-16 10:43:29 Slp: ----------------------------------------------------------------------
(01) 2018-07-16 10:43:29 Slp: Running Action: RunRemoteDiscoveryAction
(01) 2018-07-16 10:43:29 Slp: Running discovery on local machine
(01) 2018-07-16 10:43:31 Slp: Discovery on local machine is complete
(01) 2018-07-16 10:43:31 Slp: Running discovery on remote machine: UKRXM3S127
(01) 2018-07-16 10:43:31 Slp: Discovery on UKRXM3S127 failed due to exception
(01) 2018-07-16 10:43:31 Slp: Microsoft.SqlServer.Management.Sdk.Sfc.EnumeratorException: Failed to retrieve data for this request. ---> System.ComponentModel.Win32Exception: Not all privileges or groups referenced are assigned to the caller.

(01) 2018-07-16 10:43:31 Slp: Exception type: Microsoft.SqlServer.Management.Sdk.Sfc.EnumeratorException
(01) 2018-07-16 10:43:31 Slp:     Message:
(01) 2018-07-16 10:43:31 Slp:         Failed to retrieve data for this request.
(01) 2018-07-16 10:43:31 Slp:     HResult : 0x80131500
(01) 2018-07-16 10:43:31 Slp:     Data:
(01) 2018-07-16 10:43:31 Slp:       HelpLink.ProdName = Microsoft SQL Server
(01) 2018-07-16 10:43:31 Slp:       HelpLink.BaseHelpUrl =http://go.microsoft.com/fwlink
(01) 2018-07-16 10:43:31 Slp:       HelpLink.LinkId = 20476
(01) 2018-07-16 10:43:31 Slp:     Stack:
(01) 2018-07-16 10:43:31 Slp:         at Microsoft.SqlServer.Management.Sdk.Sfc.Enumerator.Process(Object connectionInfo, Request request)
(01) 2018-07-16 10:43:31 Slp:         at Microsoft.SqlServer.Chainer.Infrastructure.SqlDiscoveryDatastoreInterface.ProcessDTbl(DataTable dt, Int32 level)
(01) 2018-07-16 10:43:31 Slp:         at Microsoft.SqlServer.Chainer.Infrastructure.SqlDiscoveryDatastoreInterface.CollectSqlDiscoveryData(String machineName)
(01) 2018-07-16 10:43:31 Slp:         at Microsoft.SqlServer.Chainer.Infrastructure.SqlDiscoveryDatastoreInterface.CollectDiscoveryData(String machineName)
(01) 2018-07-16 10:43:31 Slp:         at Microsoft.SqlServer.Chainer.Infrastructure.SqlDiscoveryDatastoreInterface.LoadData(IEnumerable`1 machineNames, String discoveryDocRootPath, String clusterDiscoveryDocRootPath)
(01) 2018-07-16 10:43:31 Slp:         at Microsoft.SqlServer.Configuration.SetupExtension.RunDiscoveryAction.ExecuteAction(String actionId)
(01) 2018-07-16 10:43:31 Slp:         at Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)
(01) 2018-07-16 10:43:31 Slp:         at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(TextWriter statusStream, ISequencedAction actionToRun, ServiceContainer context)
(01) 2018-07-16 10:43:31 Slp:     Inner exception type: System.ComponentModel.Win32Exception
(01) 2018-07-16 10:43:31 Slp:         Message:
(01) 2018-07-16 10:43:31 Slp:                 Not all privileges or groups referenced are assigned to the caller.
(01) 2018-07-16 10:43:31 Slp:                
(01) 2018-07-16 10:43:31 Slp:         HResult : 0x80004005
(01) 2018-07-16 10:43:31 Slp:         Error : 1300
(01) 2018-07-16 10:43:31 Slp:         Stack:
(01) 2018-07-16 10:43:31 Slp:                 at Microsoft.SqlServer.Configuration.Sco.AdjustTokenPrivilege.SetPrivilege(Boolean enable)
(01) 2018-07-16 10:43:31 Slp:                 at Microsoft.SqlServer.Configuration.Sco.AdjustTokenPrivilege..ctor(String privilege)
(01) 2018-07-16 10:43:31 Slp:                 at Microsoft.SqlServer.Configuration.Sco.SqlRegistry.GetLocallyCachedLocalMachineSubKey(ServiceContainer ctx, String machineName, SqlRegistryKey key)
(01) 2018-07-16 10:43:31 Slp:                 at Microsoft.SqlServer.Discovery.DiscoveryUtils.TryLocallyCacheRegistryKey(ServiceContainer ctx, String machineName, SqlRegistryKey machineKey, String registryPath, RegistryView regView, String regPath, RegistryAccess registryAccess, Boolean& alreadyCached)
(01) 2018-07-16 10:43:31 Slp:                 at Microsoft.SqlServer.Discovery.DiscoveryUtils.GetLocalMachineSubKey(ServiceContainer ctx, String machineName, RegistryView regView, String regPath, RegistryAccess registryAccess)
(01) 2018-07-16 10:43:31 Slp:                 at Microsoft.SqlServer.Discovery.DiscoveryEnumObject.GetSql2kMsiInstanceListInHive(String machineName, RegistryView regView)
(01) 2018-07-16 10:43:31 Slp:                 at Microsoft.SqlServer.Discovery.DiscoveryEnumObject.LoadSql2kInstanceList(String machineName)
(01) 2018-07-16 10:43:31 Slp:                 at Microsoft.SqlServer.Discovery.Product.GetData(EnumResult erParent)
(01) 2018-07-16 10:43:31 Slp:                 at Microsoft.SqlServer.Management.Sdk.Sfc.Environment.GetData()
(01) 2018-07-16 10:43:31 Slp:                 at Microsoft.SqlServer.Management.Sdk.Sfc.Environment.GetData(Request req, Object ci)
(01) 2018-07-16 10:43:31 Slp:                 at Microsoft.SqlServer.Management.Sdk.Sfc.Enumerator.GetData(Object connectionInfo, Request request)
(01) 2018-07-16 10:43:31 Slp:                 at Microsoft.SqlServer.Management.Sdk.Sfc.Enumerator.Process(Object connectionInfo, Request request)
(01) 2018-07-16 10:43:34 Slp: Watson Bucket 2
 Original Parameter Values

(01) 2018-07-16 10:43:34 Slp: Parameter 0 : SQL Server 2012@RTM@

(01) 2018-07-16 10:43:34 Slp: Parameter 1 : Microsoft.SqlServer.Management.Sdk.Sfc.Enumerator.Process

(01) 2018-07-16 10:43:34 Slp: Parameter 2 : Microsoft.SqlServer.Configuration.Sco.AdjustTokenPrivilege.SetPrivilege

(01) 2018-07-16 10:43:34 Slp: Parameter 3 : Microsoft.SqlServer.Management.Sdk.Sfc.EnumeratorException@-2146233088

(01) 2018-07-16 10:43:34 Slp: Parameter 4 : System.ComponentModel.Win32Exception@-2147467259

(01) 2018-07-16 10:43:34 Slp: Parameter 5 : RunRemoteDiscoveryAction

(01) 2018-07-16 10:43:34 Slp: Parameter 8 : 1300

(01) 2018-07-16 10:43:34 Slp:
 Final Parameter Values

(01) 2018-07-16 10:43:34 Slp: Parameter 0 : SQL Server 2012@RTM@

(01) 2018-07-16 10:43:34 Slp: Parameter 1 : 0x6785B09D

(01) 2018-07-16 10:43:34 Slp: Parameter 2 : 0xB2652E58

(01) 2018-07-16 10:43:34 Slp: Parameter 3 : 0x74E34741

(01) 2018-07-16 10:43:34 Slp: Parameter 4 : 0xDC80C325

(01) 2018-07-16 10:43:34 Slp: Parameter 5 : RunRemoteDiscoveryAction

(01) 2018-07-16 10:43:34 Slp: Parameter 8 : 0xA05EFA62

(01) 2018-07-16 10:43:35 Slp: Sco: Attempting to write hklm registry key Microsoft SQL Server to file C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20180716_104255\Registry_SOFTWARE_Microsoft_Microsoft SQL Server.reg_
(01) 2018-07-16 10:43:35 Slp: Sco: Attempting to write hklm registry key Uninstall to file C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20180716_104255\Registry_SOFTWARE_Microsoft_Windows_CurrentVersion_Uninstall.reg_
(01) 2018-07-16 10:43:35 Slp: Sco: Attempting to write hklm registry key MSSQLServer to file C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20180716_104255\Registry_SOFTWARE_Microsoft_MSSQLServer.reg_
(01) 2018-07-16 10:43:35 Slp: Sco: Attempting to write hklm registry key Microsoft SQL Server to file C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20180716_104255\Registry_SOFTWARE_Wow6432Node_Microsoft_Microsoft SQL Server.reg_
(01) 2018-07-16 10:43:35 Slp: Sco: Attempting to write hklm registry key Uninstall to file C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20180716_104255\Registry_SOFTWARE_Wow6432Node_Microsoft_Windows_CurrentVersion_Uninstall.reg_
(01) 2018-07-16 10:43:35 Slp: Sco: Attempting to write hklm registry key MSSQLServer to file C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20180716_104255\Registry_SOFTWARE_Wow6432Node_Microsoft_MSSQLServer.reg_
(01) 2018-07-16 10:43:36 Slp: Failed to retrieve data for this request.
(01) 2018-07-16 10:43:36 Slp: Watson bucket for exception based failure has been created
(01) 2018-07-16 10:43:36 Slp: WER: Application level consent value 'False' was mapped to consent status 'WerConsentDenied'
(01) 2018-07-16 10:43:36 Slp: WER: Result of the submission:: 'WerDisabled'
(01) 2018-07-16 10:43:36 Slp: WER: Submitted 1 of 1 failures to the Watson data repository
(01) 2018-07-16 10:43:36 Slp: Sco: File 'C:\Windows\system32\Cluster.exe' does not exist
(01) 2018-07-16 10:43:36 Slp: Failed to collect cluster logs, cannot find Cluster.exe under system directory.
(01) 2018-07-16 10:43:36 Slp: Dumping final cluster state.
(01) 2018-07-16 10:43:40 Slp: Completed dumping final cluster state.
(01) 2018-07-16 10:43:40 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine
(01) 2018-07-16 10:43:40 Slp: Sco: Attempting to open registry subkey Software\Microsoft\Microsoft SQL Server\110
(01) 2018-07-16 10:43:40 Slp: Sco: Attempting to get registry value CustomerFeedback
(01) 2018-07-16 10:43:40 Slp:
(01) 2018-07-16 10:43:40 Slp: ----------------------------------------------------------------------
(01) 2018-07-16 10:43:40 Slp:
(01) 2018-07-16 10:43:40 Slp: Error result: -2146233088
(01) 2018-07-16 10:43:40 Slp: Result facility code: 19
(01) 2018-07-16 10:43:40 Slp: Result error code: 5376
(01) 2018-07-16 10:43:40 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine
(01) 2018-07-16 10:43:40 Slp: Sco: Attempting to open registry subkey Software\Microsoft\Microsoft SQL Server\110
(01) 2018-07-16 10:43:40 Slp: Sco: Attempting to get registry value CustomerFeedback

Hi all,

I have MS SQL 2014 SP2 Evaluation edition. Now i want to license it to continue working.

I start the Edition Upgrade option and all goes well until the rule check comes. In my case all rules pass except "AlwaysOn Availability Groups feature check".

On this check it seems stuck - for more than 1 hour it has not passed.

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

Hey there,

Maybe someone had a similar situation and could help me out a little bit.

We are currently planning a migration of all our SQL Instances from a non-clustered Microsoft SQL Server (Single VM, no Failover functionality) to a new Microsoft SQL Failover Cluster environment (2 Nodes, new SQL Failover Cluster Instance for every SQL Instance).

Currently all our database connections are in the following scheme:

SQLServer1/Instance1

SQLServer1/Instance2

SQLServer1/Instance3

Since all the new SQL Failover Cluster Instances require a new DNS/Network name for every single Instance, we will face some trouble (and alot of work) to change the database configuration on every single host. Is there an easier solution than changing every single config file to point to the new database url(s)? Is there a way to use the same old SQL Server DNS Name (SQLServer1) for multiple failover cluster instances?

DNS Aliases? CNames? Anything?

Best Regards

There are two options for setting up VCO (lisener object) for SQL AG creation.

1) Provide permission for CNO to create VCO object using permissions set at the OU level.

or

2) precreate VCO object as ENABLED.  Permissions provided to configure VCO.

Want to confirm if we use step 2 that VCO object is ENABLED when it is precreated?   In other words why is the VCO ENABLED before AG wizard is started?

dsk

After creating a database in a AG group do we only need to do a full backup to initialize the t log chain?

Can you please explain "initialize the t log chain"?

And do we only need to do a full backup on the new database?  Do we need to do a trn log backup?

dsk