Sign in
 
Home20122008 R2200820052000LibraryForums
SQL Server >
> 
> 
Error Installing Cumulative Update 3 for SQL Server 2008 R2 SP2

Answered Error Installing Cumulative Update 3 for SQL Server 2008 R2 SP2

  • Wednesday, March 06, 2013 7:05 PM
     
     
    Sign In to Vote
    0

    I am trying to install CU3 for SQL Server 2008 R2 on a clustered environment to resolve the verbose log issue with SQLAgent as described in KB2718920 but the installer has failed on the servers I have tried installing.This is the error message I see in the Detail.txt file created by the installer. I have also looked at the solution provided in the Forum Thread. The solution was to rename a file but I do not even see the folder in the C drive.

    Try to rename the C:\Windows\system32\perf-MSSQL10_50.MSSQLSERVER-sqlagtctr.dll file. 

    Error Message from the Detail.txt

    2013-03-06 11:18:38 Slp: Error: Action "Microsoft.SqlServer.Configuration.ScoExtension.VerifiedCopyFileAction" threw an exception during execution.
    2013-03-06 11:18:38 Slp: Microsoft.SqlServer.Setup.Chainer.Workflow.ActionExecutionException: File d:\MSSQL\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\DllTmp64\sqlagentctr100.dll could not be copied to file path C:\Windows\system32\perf-MSSQL10_50.MSSQLSERVER-sqlagtctr.dll. ---> Microsoft.SqlServer.Configuration.ScoExtension.CopyFileException: File d:\MSSQL\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\DllTmp64\sqlagentctr100.dll could not be copied to file path C:\Windows\system32\perf-MSSQL10_50.MSSQLSERVER-sqlagtctr.dll. ---> Microsoft.SqlServer.Configuration.Sco.ScoException: The process cannot access the file 'C:\Windows\system32\perf-MSSQL10_50.MSSQLSERVER-sqlagtctr.dll' because it is being used by another process. ---> System.IO.IOException: The process cannot access the file 'C:\Windows\system32\perf-MSSQL10_50.MSSQLSERVER-sqlagtctr.dll' because it is being used by another process.
    2013-03-06 11:18:38 Slp:    at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
    2013-03-06 11:18:38 Slp:    at System.IO.File.InternalCopy(String sourceFileName, String destFileName, Boolean overwrite)
    2013-03-06 11:18:38 Slp:    at Microsoft.SqlServer.Configuration.Sco.SqlFile.CopyTo(String targetFileFullPath, Boolean bCopyAcl)
    2013-03-06 11:18:38 Slp:    --- End of inner exception stack trace ---
    2013-03-06 11:18:38 Slp:    at Microsoft.SqlServer.Configuration.Sco.SqlFile.CopyTo(String targetFileFullPath, Boolean bCopyAcl)
    2013-03-06 11:18:38 Slp:    at Microsoft.SqlServer.Configuration.ScoExtension.VerifiedCopyFileAction.ExecuteAction(String actionId)
    2013-03-06 11:18:38 Slp:    --- End of inner exception stack trace ---
    2013-03-06 11:18:38 Slp:    at Microsoft.SqlServer.Configuration.ScoExtension.VerifiedCopyFileAction.ExecuteAction(String actionId)
    2013-03-06 11:18:38 Slp:    at Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)
    2013-03-06 11:18:38 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(TextWriter statusStream, ISequencedAction actionToRun)
    2013-03-06 11:18:38 Slp:    --- End of inner exception stack trace ---
    2013-03-06 11:18:38 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(TextWriter statusStream, ISequencedAction actionToRun)
    2013-03-06 11:18:38 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionWithRetryHelper(WorkflowObject metaDb, ActionKey action, ActionMetadata actionMetadata, TextWriter statusStream)
    2013-03-06 11:18:38 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.InvokeAction(WorkflowObject metabase, TextWriter statusStream)
    2013-03-06 11:18:38 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.PendingActions.InvokeActions(WorkflowObject metaDb, TextWriter loggingStream)
    2013-03-06 11:18:38 Slp: The configuration failure category of current exception is ConfigurationFailure
    2013-03-06 11:18:38 Slp: Watson Bucket 1
     Original Parameter Values

    NM


    • Edited by NMan47 Wednesday, March 06, 2013 7:07 PM
    •  
     

All Replies

  • Wednesday, March 06, 2013 7:21 PM
     
     Answered
    Sign In to Vote
    1

    Hello,

    1) Look for the below mentioned file at this location
    a. C:\Windows\system32\perf-MSSQL10_50.MSSQLSERVER-sqlagtctr.dll
    b. C:\Windows\SYSWOW64\perf-MSSQL10_50.MSSQLSERVER-sqlagtctr.dll

    2) Rename both the files by appending .old at the end.
    3) Apply the CU3 patch.

     
  • Wednesday, March 06, 2013 7:52 PM
     
     
    Sign In to Vote
    0
    I believe you must have got an option to retry in the setup UI when the failure happens, if yes then you can rename the files mentioned in the error message and click on retry. You need to repeat this for all files reporting this issue
     
  • Wednesday, March 06, 2013 8:37 PM
     
     
    Sign In to Vote
    0

    Thanks Don. I renamed the files you mentioned and was able to get the install to complete succesfully on the passive node which only has one instance. I will be doing the active node tonorrow.

    I also tried installing the same CU3 on another SQL cluster with mutiple instances and the install failed on both nodes. However the error message was not the same. But when I bring up the SQL instances in SSMS, the version now shows it to be 10.50.4266 instead of 10.50.4000. Does this mean the installer succeeded? It can't be because I still see the same verbose logging in the event application log file. Below is the error message from the Details.txt.

    2013-03-04 12:14:26 Slp: Skipping service control for the following instance because it has one or more clustered features: Instance3
    2013-03-04 12:14:26 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine
    2013-03-04 12:14:26 Slp: Sco: Attempting to open registry subkey Software\Microsoft\Microsoft SQL Server\Instance Names\SQL
    2013-03-04 12:14:26 Slp: Sco: Attempting to get registry value Instance1
    2013-03-04 12:14:26 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine
    2013-03-04 12:14:26 Slp: Sco: Attempting to open registry subkey Software\Microsoft\Microsoft SQL Server\MSSQL10_50.Instance1\ClusterState
    2013-03-04 12:14:26 Slp: Sco: Attempting to get registry value SQL_Replication_Core_Inst
    2013-03-04 12:14:26 Slp: Skipping service control for the following instance because it has one or more clustered features: Instance1
    2013-03-04 12:14:26 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine
    2013-03-04 12:14:26 Slp: Sco: Attempting to open registry subkey Software\Microsoft\Microsoft SQL Server\Instance Names\SQL
    2013-03-04 12:14:26 Slp: Sco: Attempting to get registry value Instance2
    2013-03-04 12:14:26 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine
    2013-03-04 12:14:26 Slp: Sco: Attempting to open registry subkey Software\Microsoft\Microsoft SQL Server\MSSQL10_50.Instance2\ClusterState
    2013-03-04 12:14:26 Slp: Sco: Attempting to get registry value SQL_Replication_Core_Inst
    2013-03-04 12:14:26 Slp: Skipping service control for the following instance because it has one or more clustered features: Instance2
    2013-03-04 12:14:26 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine
    2013-03-04 12:14:26 Slp: Sco: Attempting to open registry subkey Software\Microsoft\Microsoft SQL Server\Instance Names\SQL
    2013-03-04 12:14:26 Slp: Sco: Attempting to get registry value Instance3
    2013-03-04 12:14:26 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine
    2013-03-04 12:14:26 Slp: Sco: Attempting to open registry subkey Software\Microsoft\Microsoft SQL Server\MSSQL10_50.Instance3\ClusterState
    2013-03-04 12:14:26 Slp: Sco: Attempting to get registry value SQL_Replication_Core_Inst
    2013-03-04 12:14:26 Slp: Skipping service control for the following instance because it has one or more clustered features: Instance3
    2013-03-04 12:14:26 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine
    2013-03-04 12:14:26 Slp: Sco: Attempting to open registry subkey Software\Microsoft\Microsoft SQL Server\Instance Names\OLAP
    2013-03-04 12:14:26 Slp: Sco: Failed to open service handle for service MSOLAP$Instance1
    2013-03-04 12:14:26 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine
    2013-03-04 12:14:26 Slp: Sco: Attempting to open registry subkey Software\Microsoft\Microsoft SQL Server\Instance Names\OLAP
    2013-03-04 12:14:26 Slp: Sco: Failed to open service handle for service MSOLAP$Instance2
    2013-03-04 12:14:26 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine
    2013-03-04 12:14:26 Slp: Sco: Attempting to open registry subkey Software\Microsoft\Microsoft SQL Server\Instance Names\OLAP
    2013-03-04 12:14:26 Slp: Sco: Failed to open service handle for service MSOLAP$Instance3
    2013-03-04 12:14:26 Slp: Sco: Failed to open service handle for service ReportServer$Instance1
    2013-03-04 12:14:26 Slp: Sco: Failed to open service handle for service ReportServer$Instance2
    2013-03-04 12:14:26 Slp: Sco: Failed to open service handle for service ReportServer$Instance3
    2013-03-04 12:14:26 Slp: Attempting to run patch request for instance: Instance1
    2013-03-04 12:18:01 Slp: Error: Failed to run patch request for instance: Instance1 (exit code: -2058354685)
    2013-03-04 12:18:01 Slp: Attempting to run patch request for instance: Instance2
    2013-03-04 12:19:13 Slp: Error: Failed to run patch request for instance: Instance2 (exit code: -2058354685)
    2013-03-04 12:19:13 Slp: Attempting to run patch request for instance: Instance3
    2013-03-04 12:20:27 Slp: Error: Failed to run patch request for instance: Instance3 (exit code: -2058354685)

    NM


    • Edited by NMan47 Wednesday, March 06, 2013 8:39 PM
    •  
     
  • Thursday, March 07, 2013 8:24 PM
     
     
    Sign In to Vote
    0

    I was able to get the patch installed on the cluster with multiple instances as well. The issue turned out to be similar to the one above with a different file even though the log file didn't state so. I renamed those files for each of the instances and the patch installed with no issues.

    Thanks all.

    NM