July 27, 2015 at 5:37 am
hi,
We have a cluster with 8 nodes. this instance is installed on 2 nodes S141 (active) and S142 (passive)
I want to uninstall with the command:
Setup.exe /Action=RemoveNode /qs /INSTANCENAME="SQL16" /SkipRules=Cluster_VerifyForErrors, ServerCoreBlockUnsupportedSxSCheck
I receive the following error in the command prompt:
Microsoft (R) SQL Server 2008 R2 Setup 10.50.4000.00
Copyright (c) Microsoft Corporation. All rights reserved.
The following error occurred:
Failed to retrieve data for this request.
Error result: -1554760125
Result facility code: 852
Result error code: 15939
Please review the summary.txt log for further details
In the full log:
2015-07-27 10:33:10 Slp: Running Action: RunDiscoveryAction
2015-07-27 10:33:10 Slp: Running discovery on local machine
2015-07-27 10:33:15 Slp: Discovery on local machine is complete
2015-07-27 10:33:15 Slp: Running discovery on remote machine: 99-001-003-S122
2015-07-27 10:33:38 Slp: Discovery on 99-001-003-S122 is complete
2015-07-27 10:33:38 Slp: Running discovery on remote machine: 99-001-003-S121
2015-07-27 10:34:01 Slp: Discovery on 99-001-003-S121 is complete
2015-07-27 10:34:01 Slp: Running discovery on remote machine: 99-002-003-S141
2015-07-27 10:34:01 Slp: Discovery on 99-002-003-S141 failed due to exception
2015-07-27 10:34:01 Slp: Microsoft.SqlServer.Management.Sdk.Sfc.EnumeratorException: Failed to retrieve data for this request. ---> Microsoft.SqlServer.Configuration.Sco.SqlRegistryException: The network path was not found.
In the log the exception:
Exception summary:
The following is an exception stack listing the exceptions in outermost to innermost order
Inner exceptions are being indented
Exception type: Microsoft.SqlServer.Management.Sdk.Sfc.EnumeratorException
Message:
Failed to retrieve data for this request.
Data:
HelpLink.ProdName = Microsoft SQL Server
HelpLink.BaseHelpUrl = http://go.microsoft.com/fwlink
HelpLink.LinkId = 20476
DisableWatson = true
Stack:
at Microsoft.SqlServer.Management.Sdk.Sfc.Enumerator.Process(Object connectionInfo, Request request)
at Microsoft.SqlServer.Chainer.Infrastructure.SqlDiscoveryDatastoreInterface.ProcessDTbl(DataTable dt, Int32 level)
at Microsoft.SqlServer.Chainer.Infrastructure.SqlDiscoveryDatastoreInterface.CollectSqlDiscoveryData(String machineName)
at Microsoft.SqlServer.Chainer.Infrastructure.SqlDiscoveryDatastoreInterface.CollectDiscoveryData(String machineName)
at Microsoft.SqlServer.Chainer.Infrastructure.SqlDiscoveryDatastoreInterface.LoadData(IEnumerable`1 machineNames, String discoveryDocRootPath, String clusterDiscoveryDocRootPath)
at Microsoft.SqlServer.Configuration.SetupExtension.RunDiscoveryAction.ExecuteAction(String actionId)
at Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)
at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(TextWriter statusStream, ISequencedAction actionToRun)
Inner exception type: Microsoft.SqlServer.Configuration.Sco.SqlRegistryException
Message:
The network path was not found.
Data:
WatsonData = Microsoft.SqlServer.Configuration.Sco.SqlRegistryException@Win32Error
Stack:
at Microsoft.SqlServer.Configuration.Sco.SqlRegistry.CreateBaseKey(ServiceContainer ctx, String machineName, IntPtr hKey, String keyName, RegistryAccess access, RegistryView view)
at Microsoft.SqlServer.Configuration.Sco.SqlRegistry.GetLocalMachine(ServiceContainer ctx, String machineName, RegistryAccess access, RegistryView view)
at Microsoft.SqlServer.Discovery.DiscoveryEnumObject.GetSql2kMsiInstanceListInHive(String machineName, RegistryView regView)
at Microsoft.SqlServer.Discovery.DiscoveryEnumObject.LoadSql2kInstanceList(String machineName)
at Microsoft.SqlServer.Discovery.Product.GetData(EnumResult erParent)
at Microsoft.SqlServer.Management.Sdk.Sfc.Environment.GetData()
at Microsoft.SqlServer.Management.Sdk.Sfc.Environment.GetData(Request req, Object ci)
at Microsoft.SqlServer.Management.Sdk.Sfc.Enumerator.GetData(Object connectionInfo, Request request)
at Microsoft.SqlServer.Management.Sdk.Sfc.Enumerator.Process(Object connectionInfo, Request request)
I have previously uninstalled once a node on test with no problems, now I encounter this problem on production. Any idea what I'm missing here? I have already checked the registry key type, the service remote registry that is running,...
thanks!
July 27, 2015 at 8:37 am
Don't know much about clustering, but from the look of the error message, it appears to be doing some kind of discovery for every node. Does the uninstall perhaps need to be able to talk to each and every node ? Might that particular node have been unavailable at that moment, even if it was just a network burp of some kind?
Steve (aka sgmunson) 🙂 🙂 🙂
Rent Servers for Income (picks and shovels strategy)
July 30, 2015 at 12:52 am
hi,
thank you for the reply. I have uninstalled all sql instances on the node that gives the problem and evicted the node. after that I was able to do the second node. uninstall and evict node.
Since this was an issue that was going to take too much time, I did it this way. problem is that the cause is not known in case it happens in the future.
July 21, 2017 at 8:19 am
I had a similar issue and that was fixed using below method..
Look at the error " Discovery on 99-002-003-S141 failed due to exception"
Go to the server 99-002-003-S141 and check from services.msc if remote registry service is running or not.
In my case, after running this service the patch installation went fine.
Due to this service was stopped/disabled, the nodes were not able to communicate to this particular 99-002-003-S141 machine in the cluster and causing the issue..
Happy Helping 🙂
Rajeev
SQL DBA
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply