The process cannot access the file 'C:Windowssystem32perf-MSSQL10_50.MSSQLSERVER-sqlagtctr.dll' because it is being used by another process.
SQL Server CU’s update fails with error
“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.
”
In Detail.txt you will find errors like one listed below
Sco: Attempting to normalize directory path 'C:\Windows\system32\perf-MSSQL10_50.MSSQLSERVER-sqlagtctr.dll'
Error: Action "Microsoft.SqlServer.Configuration.ScoExtension.VerifiedCopyFileAction" threw an exception during execution.
Microsoft.SqlServer.Setup.Chainer.Workflow.ActionExecutionException: File C:\Program Files\Microsoft SQL Server\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 C:\Program Files\Microsoft SQL Server\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.
at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
at System.IO.File.InternalCopy(String sourceFileName, String destFileName, Boolean overwrite)
at Microsoft.SqlServer.Configuration.Sco.SqlFile.CopyTo(String targetFileFullPath, Boolean bCopyAcl)
--- End of inner exception stack trace ---
tion, ActionMetadata actionMetadata, TextWriter statusStream)
Slp: at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.InvokeAction(WorkflowObject metabase, TextWriter statusStream)
Slp: at Microsoft.SqlServer.Setup.Chainer.Workflow.PendingActions.InvokeActions(WorkflowObject metaDb, TextWriter loggingStream)
Slp: The configuration failure category of current exception is ConfigurationFailure
Slp: Watson Bucket 1
Original Parameter Values
2012-07-25 11:01:36 Slp: Parameter 0 : SQL2008@RTM@KB2703282
2012-07-25 11:01:36 Slp: Parameter 1 : Microsoft.SqlServer.Configuration.ScoExtension.VerifiedCopyFileAction.ExecuteAction
2012-07-25 11:01:36 Slp: Parameter 2 : System.IO.__Error.WinIOError
2012-07-25 11:01:36 Slp: Parameter 3 : Microsoft.SqlServer.Configuration.ScoExtension.CopyFileException@1360@3
2012-07-25 11:01:36 Slp: Parameter 4 : System.IO.IOException@-2147024864
2012-07-25 11:01:36 Slp: Parameter 5 : CopyPerfCounterDllToSystemDir
2012-07-25 11:01:36 Slp: Parameter 7 : Microsoft.SqlServer.Configuration.ScoExtension.CopyFileException@CopyFileFailed
2012-07-25 11:01:36 Slp: Parameter 8 : sqlagentctr100.dll
2012-07-25 11:01:36 Slp:
Final Parameter Values
2012-07-25 11:01:36 Slp: Parameter 0 : SQL2008@RTM@KB2703282
2012-07-25 11:01:36 Slp: Parameter 1 : 0x31492EED
2012-07-25 11:01:36 Slp: Parameter 2 : 0x60797DC7
2012-07-25 11:01:36 Slp: Parameter 3 : 0xFDBE3E6D@1360@3
2012-07-25 11:01:36 Slp: Parameter 4 : 0x24C2C4E7
2012-07-25 11:01:36 Slp: Parameter 5 : CopyPerfCounterDllToSystemDir
2012-07-25 11:01:36 Slp: Parameter 7 : 0xCDC6E6DD
2012-07-25 11:01:36 Slp: Parameter 8 : 0xDD73CFED
Resolution:
Rename C:\Windows\system32\perf-MSSQL10_50.MSSQLSERVER-sqlagtctr.dll and Re-run the setup.
Note: Name of the above mentioned file would change based on the instance name. so review the detail.txt to get the correct file name,rename it and then re-run the setup.
Similar SQL Server setup issues
Service pack ,Hotfix and CU installation for SQL Server might fail with “Unable to install Windows Installer MSI file“
A failure was detected for a previous installation, patch, or repair during configuration for features [SQL_PowerShell_Engine_CNS,SQL_PowerShell_Tools_ANS]. In order to apply this patch package (KB968369), you must resolve any issues with the previous operation that failed.
SQLServer2008: Script level upgrade for database ‘master’ failed because upgrade step ‘sqlagent100_msdb_upgrade.sql’ encountered error 574, state 0, severity 16
Installation of SQLserver2008 cluster fails on windows2008.(The group or resource is not in the correct state to perform the requested operation. (Exception from HRESULT: 0x8007139F)
SQLServer 2008 Fails to come online on cluster after upgrade
Installation of SQLServer2005/2008 Fails on Windows2008 Cluster.
Unable to start SQLServer agent resource on cluster after upgrading to 9.00.3186 or Higher
Thank you,
Karthick P.K |Technical Lead | Microsoft SQL Server Support |