Anmelden
 
HomeLibraryDownloadsSupportWebcasts & EventsCommunityForenBlogs
Ressourcen für IT-Professionals >
> 
> 
BAIL errors on full import on AD MA

Answered BAIL errors on full import on AD MA

  • Montag, 7. Mai 2012 08:28
     
     
    Anmelden
    0

    Hi

    I'm having strange errors on AD MA on FIM with latest update installed. Maybe someone has seen this before. 

    Initial full import is going OK, but later, if I will try to do subsequent full import on some occasions I'm getting:

    ERR: MMS(5012): obsoletionlist.cpp(319): 0 is not a valid DN depth
    BAIL: MMS(5012): obsoletionlist.cpp(321): 0x80070057 (The parameter is incorrect.)
    BAIL: MMS(5012): obsoletionlist.cpp(767): 0x80070057 (The parameter is incorrect.)
    BAIL: MMS(5012): obsoletionlist.cpp(1146): 0x80070057 (The parameter is incorrect.)
    BAIL: MMS(5012): syncimport.cpp(804): 0x80070057 (The parameter is incorrect.)
    BAIL: MMS(5012): syncimport.cpp(110): 0x80070057 (The parameter is incorrect.)
    BAIL: MMS(5012): ma.cpp(4461): 0x80070057 (The parameter is incorrect.)
    Forefront Identity Manager 4.0.3606.2"

    And subsequently:

    ERR: MMS(5012): libutils.cpp(10359): Unusual error code reported 0x80070057
    Forefront Identity Manager 4.0.3606.2

    Delta imports on the same agent works well. Only way to proceed with full import is to delete connector space and make full import again. 

    This is production but still in deployment mode so for now it is OK but it is making our live a bit harder :).  But for live deployment I would like to have it solved however right now I couldn't figure out what is wrong

     

Alle Antworten

  • Montag, 7. Mai 2012 22:12
     
     Beantwortet
    Anmelden
    0

    Any chance there's been an AD schema update since you installed the AD MA? I saw some similar errors after OCS/LINC was installed and something similar also with other products that make AD schema updates.

    If you haven't already, try doing a schema refresh on the AD MA and see if it helps.

    Frank C. Drewes III - Senior Consultant: Oxford Computer Group

     
  • Dienstag, 8. Mai 2012 06:28
     
     
    Anmelden
    0

    I have not been informed about that but will check it out - it is fairly easy to check on schema partition and in FIM. Will check it and get back here with result just for common knowledge

    Update: yes, it looks like this was a case. Actually in the meantime PCNS schema was deployed in AD. 

    Error message is not a helpful one in this case ;). Thanks for tip in good direction Frank.