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:

• Office 365 Forums - DSync - Services Stopped & Disabled
• TechNet Forums - Event 6313: registry keys are present

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,

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

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, 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

• Proposed as answer by Vladimir Zanadvorov 32 minutes ago

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

• Proposed as answer by Vladimir Zanadvorov Friday, June 05, 2015 6:51 AM

Hello Vladimir,
even if I delete and recreate counters (and also registry key), the problem is still the same.

Bye,
Luca