none
Faulting module name: clr.dll, version: 4.0.30319.34209 RRS feed

  • Question

  • Hi All,

    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. The service stopped randomly and not frequently.

    I am not a .Net expert and suspecting some issue with my .net Framework.

    Current .Net version is 4.5.2

    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.

    Thanks in Advance,
    Raja Village Sync

    Tuesday, August 25, 2015 7:49 PM

All replies

  • Hi RajavillageSync,

    What's your OS version?

    As you may know, some .NET Frameworks are embed with OS, to make sure whehter your system files are missing or corrupted, please first try to run sfc /scannow, refer to: https://support.microsoft.com/en-us/kb/929833

    Besides, we need to verify the .NET Frameworks on your machine by using .NET Framework Setup Verification Tool, by running it, it will show all the .NET frameworks on your machine in the dropdown list, please verify them.

    You will find the log file at %TEMP% folder, please check the first 15 lines and the last 15 lines, if the exit code != 0, it means that the .NET is installed incorrectly.

    Please use .NET Framework Repair Tool to repair it.

    If the repair tool doesn't help, I need your log file to troubleshoot, please use  http://aka.ms/vscollect to gather the installation logs. After using it, you will find vslogs.cab from %temp% folder. Please upload the file to https://skydrive.live.com/ and share the link here.

    Best Regards,


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.

    Click HERE to participate the survey.

    Wednesday, August 26, 2015 1:58 AM
    Moderator
  • Thanks Jiayi,

    I have ran the .Net Frame Setup Verification Tool and see the error log as below.

    ======================================================================
    [08/27/15,16:59:36] Beginning of new SetupVerifier error logging session
    [08/27/15,16:59:36] Build created on July 31, 2015
    [08/27/15,16:59:36] For more information about repairing the .NET Framework, see http://support.microsoft.com/kb/2698555 and http://go.microsoft.com/fwlink/?LinkID=246062
    [08/27/15,16:59:36] Activity log file location: C:\Users\CGASIN~1\AppData\Local\Temp\2\setupverifier_main_08-27-15_16.59.36.txt
    [08/27/15,16:59:36] Error log file location: C:\Users\CGASIN~1\AppData\Local\Temp\2\setupverifier_errors_08-27-15_16.59.36.txt
    [08/27/15,16:59:36] Detected operating system: Windows 7 (x64)
    [08/27/15,16:59:36] Windows directory: C:\windows
    [08/27/15,16:59:36] System directory: C:\windows\system32
    [08/27/15,16:59:36] Program Files directory: C:\Program Files (x86)
    [08/27/15,16:59:36] Common Files directory: C:\Program Files (x86)\Common Files
    [08/27/15,17:03:09] ****ERROR**** Process 'change user /execute' exited with return code 1
    [08/27/15,17:03:09] SetupVerifier exiting with return value 0

    I can see there is ***Error*** in the logs, Shall I believe  .NET is installed incorrectly and have to use the Repair tool to fix it.

    I am a bit extra caution, because of lack of knowledge of .Net framework.

    Kindly advice.

    Thank You,

    Best Regards,
    RajaVillage Sync

    Thursday, August 27, 2015 7:56 PM
  • Hi PajavillageSync,

    Exited code 1  just means that required file setupverifier.ini was not found in the same path as setupverifier.exe.

    Have you run the .NET Framework Repair Tool?

    If you haven't, please run it to see whether it helps.

    Best Regards,


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.

    Click HERE to participate the survey.

    Friday, August 28, 2015 7:15 AM
    Moderator