November 20, 2011 at 11:27 am
When I tried to upgrade to SP1, I'm getting an error "Given key was not present in the dictionary."
Any ideas as to why I might be seeing this?
We are running 2008 R2 Enterprise 64-bit on a two-node active/passive cluster with 4 named instances.
I evicted the node from the cluster, and attempted to upgrade just one of the instances. I tried it with and without the SQL Browser service running. None of the services were running for any of the instances. I attempted to upgrade a different instance on the other node after it was evicted and had the same results.
In the summary log, it lists the following:
Instance InstanceName1 overall summary:
Final result: The patch installer has failed to update the shared features. To determine the reason for failure, review the log files.
Exit code (Decimal): 2064843076
Exit facility code: 787
Exit error code: 324
Exit message: The given key was not present in the dictionary.
I'm not sure what is relevant info in the detail log, but I did find this in it:
2011-11-20 09:17:14 Slp: Error: Action Microsoft.SqlServer.Configuration.SetupExtension.FinalCalculateSettingsAction" threw an exception during execution.
2011-11-20 09:17:14 Slp: Microsoft.SqlServer.Setup.Chainer.Workflow.ActionExecutionException: The given key was not present in the dictionary. ---> System.InvalidOperationException: The given key was not present in the dictionary. ---> System.Collections.Generic.KeyNotFoundException: The given key was not present in the dictionary.
2011-11-20 09:17:14 Slp: at System.ThrowHelper.ThrowKeyNotFoundException()
2011-11-20 09:17:14 Slp: at System.Collections.Generic.SortedList`2.get_Item(TKey key)
2011-11-20 09:17:14 Slp: at Microsoft.SqlServer.Chainer.Infrastructure.ServiceContainer.GetService(Type serviceType)
December 9, 2012 at 10:10 pm
I;m getting same error. Did you find a solution for it?
October 21, 2016 at 12:02 pm
Hi, I am getting the same error messages. Do we know the cause of the issue.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply