Hello

I have an aleatory exception : stopped-server on all of my FIM sync service 2010 R2 sp1.

I don't have this error on FIM sync service 2010 

This exception occurs on different ECMA and different execution profile (Import, Synchro).

With restarting the service, the excption doesn't appear anymore but for an unknow reason it reappears:

in the event viewer I have thos kind of error :

Faulting application name: miiserver.exe, version: 4.1.3419.0, time stamp: 0x511d9c79
Faulting module name: clr.dll, version: 4.0.30319.17929, time stamp: 0x4ffa59b1
Exception code: 0xc0000005
Fault offset: 0x00000000004e5900
Faulting process id: 0xf8c
Faulting application start time: 0x01cefcaa20d1eda1
Faulting application path: C:\Program Files\Microsoft Forefront Identity Manager\2010\Synchronization Service\Bin\miiserver.exe
Faulting module path: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll
Report Id: 9f8b2bbb-689d-11e3-b2ce-000a30ffa3a5

OR 

Faulting application name: miiserver.exe, version: 4.1.3419.0, time stamp: 0x511d9c79
Faulting module name: ntdll.dll, version: 6.1.7601.17514, time stamp: 0x4ce7c8f9
Exception code: 0xc0000005
Fault offset: 0x0000000000018e3d
Faulting process id: 0xed4
Faulting application start time: 0x01cefc16c915f872
Faulting application path: C:\Program Files\Microsoft Forefront Identity Manager\2010\Synchronization Service\Bin\miiserver.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: f00f29a1-6895-11e3-b2ce-000a30ffa3a5

Thanks for your help.

I added the following tags to avoid garbage collection concurrency in the runtime tag in the configuration file (miisserver.exe.config):

<gcServer enabled="true"/>
<gcConcurrent enabled="false"/>

It seems to be better when running full synchros, but when I run a full sync after 10 minutes,

FIM goes stop-server again

Has someone ever heard about this issue?

Hi,

After Migrating from ILM 2007 to FIM 2010 R2 SP1, the synchronization service stopped automatically when the sync run and on re-start the service it work fine again.

Any reason why this behaviour.

The Link https://support.microsoft.com/en-us/kb/2640103 suggest to apply hotfix

Event Log

Faulting application name: miiserver.exe, version: 4.1.3627.0, time stamp: 0xXXXXXX
Faulting module name: clr.dll, version: 4.0.30319.34209, time stamp: 0xXXXXXX
Exception code: 0xc0000005
Fault offset: 0x00000000005e2d30
Faulting process id: 0x1080
Faulting application start time: 0xXXXXXXXX
Faulting application path: C:\FIMTest\2010\Synchronization Service\Bin\miiserver.exe

Kindly advice and what is the root cause of it and how to get this fix.

Regards,
RajaVillage Sync

• Edited by RajavillageSync 10 hours 31 minutes ago correction

Hi,

After Migrating from ILM 2007 to FIM 2010 R2 SP1, the synchronization service stopped automatically when the sync run and on re-start the service it work fine again.

Any reason why this behaviour.

The Link https://support.microsoft.com/en-us/kb/2640103 suggest to apply hotfix

Event Log

Faulting application name: miiserver.exe, version: 4.1.3627.0, time stamp: 0xXXXXXX
Faulting module name: clr.dll, version: 4.0.30319.34209, time stamp: 0xXXXXXX
Exception code: 0xc0000005
Fault offset: 0x00000000005e2d30
Faulting process id: 0x1080
Faulting application start time: 0xXXXXXXXX
Faulting application path: C:\FIMTest\2010\Synchronization Service\Bin\miiserver.exe

Kindly advice and what is the root cause of it and how to get this fix.

Regards,
RajaVillage Sync

• Edited by RajavillageSync Wednesday, August 19, 2015 8:50 PM correction