DetailPage-MSS-KB

Base de Dados de Conhecimento

Article ID: 2708726 - Last Review: November 21, 2012 - Revision: 6.1

Microsoft distributes Microsoft SQL Server 2008 R2 Service Pack 1 (SP1) fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 R2 Service Pack 1 (SP1) fix release.

On This Page

Symptoms

After you apply an update SQL Server 2008 R2 or SQL Server 2012 that is beyond a certain version, the Performance Monitor files sqlagentctr100.dll and sqlctr100.dll in the system32 folder are not updated as expected. For detailed information, see the "More information" section.

Cause

This issue occurs because the SQL Server Agent setup extension does not perform the copy operation correctly when you apply the SQL Server updates. The SQL Server Agent setup extension is responsible for copying the Performance Monitor .dll files from the SQL Server instance's Binn folder to the system32 folder.

Resolution

Cumulative update information

SQL Server 2012

The fix for this issue was first released in Cumulative Update 3 for SQL Server 2012. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
2723749  (http://support.microsoft.com/kb/2723749/LN/ ) Cumulative update package 3 for SQL Server 2012
Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2012 fix release. Microsoft recommends that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
2692828  (http://support.microsoft.com/kb/2692828/LN/ ) The SQL Server 2012 builds that were released after SQL Server 2012 was released
You must apply a SQL Server 2012 hotfix to an installation of SQL Server 2012.

SQL Server 2008 R2 Service Pack 2

The fix for this issue was first released in Cumulative Update 1 for SQL Server 2008 R2 Service Pack 2. For more information about how to obtain this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
2720425  (http://support.microsoft.com/kb/2720425/ ) Cumulative Update package 1 for SQL Server 2008 R2 Service Pack 2
Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 R2 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
2730301  (http://support.microsoft.com/kb/2730301/ ) The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 Service Pack 2 was released

SQL Server 2008 R2 Service Pack 1

The fix for this issue was first released in Cumulative Update 7. For more information about how to obtain this cumulative update package for SQL Server 2008 R2 SP1, click the following article number to view the article in the Microsoft Knowledge Base:
2703282  (http://support.microsoft.com/kb/2703282/ ) Cumulative Update package 7 for SQL Server 2008 R2 Service Pack 1
Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 R2 SP1 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
2567616  (http://support.microsoft.com/kb/2567616/ ) The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 Service Pack 1 was released

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

More information

You may experience one of the following situation when this issue occurs:
  • After you install a SQL Server 2008 R2 instance or SQL Server 2012 instance on a computer, you find the following file information in the Drive:\Program Files\Microsoft SQL Server\MSSQL10_50.SQL2008R2\MSSQL\Binn\DllTmp64 folder:
    • The version of sqlagentctr100.dll file is 10.50.1600.
    • The version of sqlctr100.dll is 10.50.1600
    Additionally, you find the following file information in the Drive:\Windows\System32 folder:
    • The version of perf-MSSQL10_50.SQL2008R2-sqlagtctr.dll is 10.50.1600.
    • The version of perf-MSSQL$SQL2008R2-sqlctr10.50.1600.1.dll is 10.50.1600.
  • After you install a SQL Server 2008 R2 Service Pack 1 (SP1) instance on a computer, you find the following file information in the Drive:\Program Files\Microsoft SQL Server\MSSQL10_50.SQL2008R2\MSSQL\Binn\DllTmp64 folder:
    • The version of sqlagentctr100.dll file is 10.50.1600.
    • The version of sqlctr100.dll is 10.50.1600.
    Additionally, you find the following file information in the Drive:\Windows\System32 folder:
    • The version of perf-MSSQL10_50.SQL2008R2-sqlagtctr.dll is 10.50.1600. This file does not show any time stamp changes or indications of update.
    • The version of perf-MSSQL$SQL2008R2-sqlctr10.50.1600.1.dll is 10.50.1600. This file seems to have been copied and put in the system32 folder, as the naming convention indicates 2500 build. However, the counters in the BINN folder are still 1600 build.
  • After you install a SQL Server 2008 R2 SP1 Cumulative Update 4 instance on a computer, you find the following file information in the Drive:\Program Files\Microsoft SQL Server\MSSQL10_50.SQL2008R2\MSSQL\Binn\DllTmp64 folder:
    • The version of sqlagentctr100.dll file is 10.50.2796 as expected.
    • The version of sqlctr100.dll file is 10.50.2796 as expected.
    Additionally, you find the following file information in the Drive:\Windows\System32 folder:
    • The version of perf-MSSQL10_50.SQL2008R2-sqlagtctr.dll is 10.50.1600. This file does not show any time stamp changes or indications of update.
    • The version of perf-MSSQL$SQL2008R2-sqlctr10.50.2796.1.dll is 10.50.2796 and is copied from the BINN folder and put in the system32 folder.
Keywords: 
kbtshoot kbqfe kbfix kbexpertiseadvanced kbsurveynew KB2708726
Partilhar
Opções de suporte adicionais
Fóruns de Suporte da Comunidade Microsoft
Contacte-nos directamente
Encontre um parceiro certificado Microsoft
Loja Microsoft