Troubleshooting FIM Sync EventID 6313: Unable to Load Performance Counters for Management Agent

Troubleshooting FIM Sync EventID 6313: Unable to Load Performance Counters for Management Agent

Symptoms

Errors in the application event log stating that the performance counters for a given management agent were unable to load.

Event ID:      6313

Task Category: Server

Level:         Error

Keywords:      Classic

User:          N/A

Computer:      FIMSync

Description:

The server encountered an unexpected error creating performance counters for management agent "Active Directory MA".

Performance counters will not be available for this management agent.

Solution

Option 1. Perform a change mode install.

Option 2. Running the following commands from an elevated command prompt, he was able to reload the performance counters for the MA in question:

  1. Delete registry key: [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\FIMSynchronizationService\Performance]
  2. Recreate the 'Performance' registry key.
  3. unlodctr.exe FIMSynchronizationService
  4. lodctr.exe "C:\Program Files\Microsoft Forefront Identity Manager\2010\Synchronization Service\Bin\mmsperf.ini"

This executable is installed on all servers and is used to unload and re-load performance counters.

Credits

Joe Zamora : c--shark.blogspot.com/.../fixed-fim-sync-hangcrash-and.html

Sort by: Published Date | Most Recent | Most Useful
Comments
  • We've hit this issue in the past and used to restart the server which caused the errors to go away. The errors seemed to coincide with the Synchronization Service being restarted and I can reliably reproduce it on at least one FIM instance here. The above fix appears to work intermittently in testing it, but it does seem pretty hit and miss and successive service restarts caused the issue to return. About 40% of the time the above seemed to cause the issue to resolve itself (as long as I didn't restart the Sync service again)...the other times the errors continued.

    Currently on 4.1.2548.0

  • Indeed, this solution works... until you restart the service.  I had to hack the registry to get rid of the event log errors (use at your own risk!):

    1. Deleted registry key

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\FIMSynchronizationService\Performance]

    2. Manually created 'Performance' registry key.

    3. Reinstalled performance counters --> FIXED!

    lodctr.exe "C:\Program Files\Microsoft Forefront Identity Manager\2010\Synchronization Service\Bin\mmsperf.ini"

    c--shark.blogspot.com/.../fixed-fim-sync-hangcrash-and.html

  • The additional steps detailed by Joe Zamora appear to have been working well for me so far. Service seems more resiliant to restarts, and to be sure I've also done a few server reboots and restarting the service hasn't been causing any issues thus far.

  • The work-around worked for me too! thank you, finally my problem is solved.

  • The work-around worked for me too! thank you, finally my problem is solved.

  • c--shark.blogspot.in/.../fixed-fim-sync-hangcrash-and.html

    www.exchangedude.net/.../fim-synchronization-service-event-id-6313