none
FIMSynchronizationService Event ID 6313 RRS feed

  • Question

  • Hello,
    I installed and configured DirSync v1.0.7020.0 on Windows Server 2012 R2. All is working fine but every time Forefront Identity Manager Synchronization Service is restarted, these errors appears under Application Log:

    • Source: FIMSynchronizationService
    • Event ID: 6313
    • Description: The server encountered an unexpected error creating performance counters for management agent "Active Directory Connector". Performance counters will not be available for this management agent.

    • Source: FIMSynchronizationService
    • Event ID: 6313
    • Description: The server encountered an unexpected error creating performance counters for management agent "Windows Azure Active Directory Connector". Performance counters will not be available for this management agent.

    I already followed these links without any success:

    If I run perfmon, these are performance counters already present (regarding DirSync):

    • FIM 2010: Connector Space
    • FIM 2010: Management Agents
    • FIM 2010: Synchronization Engine

    Could you help me ?

    Thank you,
    Luca


    Disclaimer: This posting is provided AS IS with no warranties or guarantees, and confers no rights. Whenever you see a helpful reply, click on [Vote As Help] and click on [Mark As Answer] if a post answers your question.

    Monday, March 16, 2015 3:48 PM

All replies

  • Try this: http://www.integrationtrench.com/2010/08/sync-performance-counters.html

    David Lundell, Get your copy of FIM Best Practices Volume 1 http://blog.ilmbestpractices.com/2010/08/book-is-here-fim-best-practices-volume.html

    • Proposed as answer by UNIFYBobMVP Saturday, May 30, 2015 5:16 PM
    Wednesday, April 29, 2015 9:37 PM
  • Hello David,
    the fix you suggested is the same written on my first post (Office 365 Forums DSync - Services Stopped & Disabled); I tried it without any success.

    Bye,
    Luca


    Disclaimer: This posting is provided AS IS with no warranties or guarantees, and confers no rights. Whenever you see a helpful reply, click on [Vote As Help] and click on [Mark As Answer] if a post answers your question.

    Sunday, May 31, 2015 2:13 PM
  • Luca, have you tried to just delete and recreate those counters?

    as per http://c--shark.blogspot.ru/2013/02/fixed-fim-sync-hangcrash-and.html it will be something like that:

    Stop-Service ADSync
    Remove-Item -Path HKLM:\SYSTEM\CurrentControlSet\Services\ADSync\Performance
    New-Item -Path HKLM:\SYSTEM\CurrentControlSet\Services\ADSync -Name Performance –Force
    unlodctr.exe ADSync
    lodctr.exe "C:\Program Files\Microsoft Azure AD Sync\Bin\mmsperf.ini"
    Start-Service ADSync

    Friday, June 5, 2015 6:50 AM
  • Hello Vladimir,
    even if I delete and recreate counters (and also registry key), the problem is still the same.

    Bye,
    Luca


    Disclaimer: This posting is provided AS IS with no warranties or guarantees, and confers no rights. Whenever you see a helpful reply, click on [Vote As Help] and click on [Mark As Answer] if a post answers your question.

    Friday, June 5, 2015 1:59 PM