none
.NET Framework 4 Performance Counters status not restored after using NetFxRepairTool (KB2698555)... RRS feed

  • General discussion

  • Hello all,

    after all time spent yesterday on my Windows XP SP3 (always updated via MU and mainly with QFE fixes only) using NetFxRepairTool (KB2698555) to check proper installation status for .NET Framework 3.5 SP1, .NET Framework 3.0 SP2, .NET Framework 2.0 SP2 and .NET Framework .NET Framework 4 Extended and .NET Framework 4 Client Profile (including related .NET Framework 4 Extended ITA Language Pack and .NET Framework 4 Client Profile ITA Language Pack) I've discovered this :

    A) Application Event Log contained 6 Event IDs 1001 for removing Performance Counters for following components (older Event is 1st):

    - ServiceModelEndpoint 4.0.0.0 (ServiceModelEndpoint 4.0.0.0)

    - ServiceModelOperation 4.0.0.0 (ServiceModelOperation 4.0.0.0)

    - ServiceModelService 4.0.0.0 (ServiceModelService 4.0.0.0)

    - SMSvcHost 4.0.0.0 (SMSvcHost 4.0.0.0)

    - MSDTC Bridge 4.0.0.0 (MSDTC Bridge 4.0.0.0)

    - Windows Workflow Foundation 4.0.0.0 (Windows Workflow Foundation 4.0.0.0)

    B) above Event IDs were followed by 9 more Event IDs 11728 confirming successful setup completion for following components (again older Event is 1st):

    - Microsoft .NET Framework 4 Client Profile

    - Microsoft .NET Framework 4 Extended

    - Microsoft .NET Framework 4 Client Profile ITA Language Pack

    - Microsoft .NET Framework 4 Extended ITA Language Pack

    - Microsoft .NET Framework 2.0 Service Pack 2

    - Microsoft .NET Framework 2.0 Service Pack 2

    - Microsoft .NET Framework 3.0 Service Pack 2

    - Microsoft .NET Framework 3.0 Service Pack 2

    - Microsoft .NET Framework 3.5 SP1

    and after all this I've determined that now removed Performance Counters were no more restored and also NetFxRepairTool (KB2698555) completed all its operations while not detecting this.

    Is this a new problem for NetFxRepairTool (KB2698555) or expected to happen ?

    If such strange effect was expected to happen, is there a quick known way for me to solve and reload again all above listed Performance Counters again ?

    Thanks in advance for any help.

    Rob


    • Edited by _RobMer_ Friday, June 14, 2013 6:12 PM Subject now more specific... ;-)
    Friday, June 14, 2013 6:02 PM

All replies

  • Hello again,

    after some more quick investigations I've be able to manually reload all 6 .NET Framework 4.0 PerfMon Counters as follows (while in %windir%\Microsoft.NET\Framework\v4.0.30319):

        lodctr _ServiceModelEndpointPerfCounters.ini

        lodctr _ServiceModelOperationPerfCounters.ini

        lodctr _ServiceModelServicePerfCounters.ini

        lodctr _SMSvcHostPerfCounters.ini

        lodctr _TransactionBridgePerfCounters.ini

        lodctr PerfCounters.ini

    Now because to reload them I decided to follow same order in which they were unloaded, could anyone please be so kind to tell me if I really did this correctly ?

    I'm asking this only because only after I started I also wondered that if all those PerfMon Counters above were built in additive layers, then my approach might not be best, so also to mean that best solution to reload them all would instead have been to follow an inverse ordering like this :

        lodctr PerfCounters.ini

        lodctr _TransactionBridgePerfCounters.ini

        lodctr _SMSvcHostPerfCounters.ini

        lodctr _ServiceModelServicePerfCounters.ini

        lodctr _ServiceModelOperationPerfCounters.ini

        lodctr _ServiceModelEndpointPerfCounters.ini

    Thanks in advance for next replies. Regards

    Rob

    Saturday, June 15, 2013 5:14 PM
  • You can use .Net Framework Verification tool to verify your .Net Framework.

    崖山之後無中國,明亡之後無華夏

    Monday, June 17, 2013 7:22 AM
  • OK, I'll try this step ASAP ... ;-D

    Anyway because KB2698555 title is : "Version 2 of the Microsoft .NET Framework repair tool is available" and I've already run an offline repair (NetFxRepairTool /addsource [LocalDrive]:\[FolderPath]) I really thought that if existing, any error (at least for .NET Framework 3.5 SP1, .NET Framework 3.0 SP2, .NET Framework 2.0 SP2 and .NET Framework 4 Client Profile and Full) should have already been fixed.

    Or was I wrongly supposing this ?

    Thanks

    Rob

    Monday, June 24, 2013 2:50 PM
  • Fine, now I've also run .NET Framework Verification Tool but it really found no problems (see below excerpt from my_main_log.txt). So any other ideas ?

    Regards

    Rob

    ...

    [06/24/13,17:12:00] Install state for .NET Framework 1.0: not installed.
    [06/24/13,17:12:00] Install state for .NET Framework 1.1: installed with service pack 1.
    [06/24/13,17:12:00] Install state for .NET Framework 2.0: installed with service pack 2.
    [06/24/13,17:12:00] Install state for .NET Framework 3.0: installed with service pack 2.
    [06/24/13,17:12:00] Install state for .NET Framework 3.5: installed with service pack 1.
    [06/24/13,17:12:00] Install state for .NET Framework 4 Client: installed with no service packs.
    [06/24/13,17:12:00] Install state for .NET Framework 4 Full: installed with no service packs.
    [06/24/13,17:12:00] Install state for .NET Framework 4.5: not installed.

    ...

    [06/24/13,17:13:20] Starting verification for product .NET Framework 1.1
    [06/24/13,17:13:20] Section [Files - .NET Framework 1.1] - start parsing entries
    [06/24/13,17:13:20] File E:\WINDOWS\system32\mscoree.dll (version 4.0.31106.0) is installed on the system
    [06/24/13,17:13:20] File E:\WINDOWS\system32\mscorier.dll (version 2.0.50727.3074) is installed on the system
    [06/24/13,17:13:20] File E:\WINDOWS\system32\mscories.dll (version 2.0.50727.3053) is installed on the system

    ...

    [06/24/13,17:13:34] Verification succeeded for product .NET Framework 1.1

    ...

    [06/24/13,17:14:52] Starting verification for product .NET Framework 1.1 SP1

    [06/24/13,17:15:00] Verification succeeded for product .NET Framework 1.1 SP1
    [06/24/13,17:15:34] Starting verification for product .NET Framework 2.0

    ...

    [06/24/13,17:15:49] Verification succeeded for product .NET Framework 2.0
    [06/24/13,17:16:34] Starting verification for product .NET Framework 2.0 SP1

    ...

    [06/24/13,17:16:37] Verification succeeded for product .NET Framework 2.0 SP1
    [06/24/13,17:17:10] Starting verification for product .NET Framework 2.0 SP2

    ...

    [06/24/13,17:17:12] Verification succeeded for product .NET Framework 2.0 SP2
    [06/24/13,17:17:37] Starting verification for product .NET Framework 3.0

    ...

    [06/24/13,17:17:44] Verification succeeded for product .NET Framework 3.0
    [06/24/13,17:18:10] Starting verification for product .NET Framework 3.0 SP1

    ...

    [06/24/13,17:18:17] Verification succeeded for product .NET Framework 3.0 SP1
    [06/24/13,17:19:05] Starting verification for product .NET Framework 3.0 SP2

    ...

    [06/24/13,17:19:09] Verification succeeded for product .NET Framework 3.0 SP2
    [06/24/13,17:19:35] Starting verification for product .NET Framework 3.5

    ...

    [06/24/13,17:19:44] Verification succeeded for product .NET Framework 3.5
    [06/24/13,17:20:01] Starting verification for product .NET Framework 3.5 SP1

    ...

    [06/24/13,17:20:07] Verification succeeded for product .NET Framework 3.5 SP1
    [06/24/13,17:20:56] Starting verification for product .NET Framework 4 Client

    ...

    [06/24/13,17:21:13] Verification succeeded for product .NET Framework 4 Client
    [06/24/13,17:21:41] Starting verification for product .NET Framework 4 Full

    ...

    [06/24/13,17:21:51] Verification succeeded for product .NET Framework 4 Full

    ...

    Monday, June 24, 2013 4:23 PM