Sign in
 
HomeLibraryWikiLearnGalleryDownloadsSupportForumsBlogs
Resources for IT Professionals >
> 
> 
> 
When exporting error happened , how to debug ?

Answered When exporting error happened , how to debug ?

All Replies

  • Saturday, October 06, 2012 5:29 PM
     
     
    Sign In to Vote
    0

    Hi,

    Yes' It's possible. the process to attach is miiserver.exe (not fimserver.exe).

    Patrick.

    Patrick Layani

     
  • Saturday, October 06, 2012 10:44 PM
     
     
    Sign In to Vote
    0

    Thank you.

    I think actually using is compiled DLL.

    1.

    If I set break point in source code and attach proccess, it will stop ?

    2.

    And where is attach proccess in option menu of VS express 2010 VB?I could not find.

     
  • Sunday, October 07, 2012 5:16 AM
     
     
    Sign In to Vote
    0

    1. yes.

    2. Debug --> Attach to Process --> miiserver.exe (not miisclient.exe)

    If you don't find the process then click, in the bottom of the windows, the checkboxes: Shows processes from all users and Show processes in all sessions

    If you still don't find the process, then make sure that the service Forefront Identity Manager Synchronization Service is running (from services.msc)

    Patrick.

    Patrick Layani

     
  • Sunday, October 07, 2012 11:37 AM
     
     
    Sign In to Vote
    0

    Thank you.

    There is no attach to process in debug menu in VB2010.

    I can see only window , start debug, step in, step over,exception, set/unset break point,unset all break point.

     
  • Sunday, October 07, 2012 11:01 PM
    Moderator
     
     
    Sign In to Vote
    0
    The issue here is that you're not using a full version of Visual Studio - this is VS Tools for Applications. You need to install a copy of Visual Studio 2010 - the express version is sufficient.

    My Book - Active Directory, 4th Edition
    My Blog - www.briandesmond.com

     
  • Monday, October 08, 2012 12:03 AM
     
     
    Sign In to Vote
    0

    Thank you.

    I opened and looked for Visutal Basic 2010 Express,

    But , there is no  Attach to Process menu.

     
  • Monday, October 08, 2012 1:02 AM
     
     
    Sign In to Vote
    0

    Two things.......

    -First, I am under the impression that the full version of VS is necessary in order to debug by attaching to process........

    -Second and more important, the errors you show in the first screenshot are from export profile; debugging the code above, which looks like MA extension code, won't help.

    I have seen unexpected errors when the CS objects are corrupt or you are attempting to perform an operation such as add attribute value which won't work for your target directly. As your target directly looks like AD, I would surmise it is CS corruption which is causing this. Try moving all of those objects into an OU that is not in scope and go through Full import stage only followed by synchronization on that MA. Then bring the objects back into in-scope OU, do the errors continue to occur?

    BTW, any discovery errors during import will break this process.

     
  • Monday, October 08, 2012 3:37 AM
     
     
    Sign In to Vote
    0

    Thank you.

    I think production env has VS2003.net not express edition.

    But , I wonder Configured DLL is already complied one, so if I set break point to source code of DLL, it will stop in break point ?

     
  • Monday, October 08, 2012 12:12 PM
     
     
    Sign In to Vote
    0

    Normally when you have the *.pdb files that match the assembly you are able to debug it, but as Glenn already noted the code you have is not the code that is being executed during a export run.

    Can you open the error object and show the error code / message?

    Need realtime FIM synchronization and advanced reporting? check out the new http://www.imsequencer.com that supports FIM 2010, Omada Identity Manager, SQL, File, AD or Powershell real time synchronization!

     
  • Tuesday, October 09, 2012 3:55 AM
     
     
    Sign In to Vote
    0

    Thank you.

    About error, I will investigate as another prombem.

    But , I wonder about debuging Why we set break point to source code(not setting break point to source code??) , and attach proccess, it will stop at break point ?? 

     
  • Tuesday, October 09, 2012 9:10 AM
     
     
    Sign In to Vote
    0

    Thank you.

    I found production env Visutal Studio has attach process.

    But where could I set break point to debug custom extension DLL ? (the source code of Visual Basic before compiled to that DLL ?)

     
  • Wednesday, October 10, 2012 8:40 AM
     
     
    Sign In to Vote
    0

    As replied above, Open the project GALSync project, set the wanted breakpoints in the project and compile.

    Then attach the FIM Sync process: Debug --> Attach to Process --> miiserver.exe

    After process attachment run a full sync.

    Patrick.

    Patrick Layani

     
  • Wednesday, October 10, 2012 9:03 AM
     
     
    Sign In to Vote
    0

    Thank you.

    I think I understand.

    Before compiling the source code, set break point to that source code , and attach to process ,and compile that source code and use that compiled DLL in MIIS ?

     
  • Wednesday, October 10, 2012 9:28 AM
     
     Answered
    Sign In to Vote
    0
    It will work.

    Patrick Layani

    • Marked As Answer by blackjack08 Thursday, October 11, 2012 2:00 AM
    •