none
MIM 2016 issue

    질문

  • Hello,

    I´ve got solution deployed at customer, where HR (SQL 2008 R2 database) manage accounts in AD. Sync flow is HR (SQL) -> MIM -> AD. MIM 2016 version: 4.4.1237.0. Only MIM synchronization service is used with custom VB code for customized provisioning. MIM anchor: attribute called EmployeeID.

    Two MA -one for HR (SQL), second one AD obviously for AD. Order & run of MA:

    HR MA Full Import
    HR MA Full Synchronization
    AD MA Export
    AD MA Full Import
    AD MA Full Synchronization
    HR MA Export

    Some updates in the SQL structure have been done time ago. I run Schema Update on HR MA to get latest columns/data from SQL database.

    I´m getting error message on HR MA Full Import:
    Status: failed-connection
    Error: column-list-reordering
    Error code: 0x80004005

    Eventlog error IDs: 6401 & 6005

    Also notified that many objects are disconnected and could not find the match in Metaverse. In the metaverse 90% of objects have got only AD MA Connetor visible, that means the connection between Metaverse and AD is established, but not with SQL database!

    Question 1: How to get it back (link on the EmployeeID in between SQL and AD in Metaverse)?

    Question 2: Is the issue connected to the changed structure of SQL database or is it a MIM bug? -> Update to the lastest version will fix it? Can the issue be caused by the invalid or updated data type in SQL?

    Thanks in advance.


    Petr Weiner









    • 편집됨 Petr Weiner 2018년 5월 15일 화요일 오전 9:35
    2018년 5월 15일 화요일 오전 9:02

모든 응답


  • I did update of .NET and Metaverse looked good for few syncs. Same problem again now. In the App.log getting:

    ID 6401 

    The management agent controller encountered an unexpected error.

     "ERR_: MMS(1256): ..\libutils.cpp(10186): Failed to start run because of undiagnosed MA error
    Forefront Identity Manager 4.4.1237.0"

    ID 6005:

    The management agent "HR MA" failed on run profile "HR MA Full Import (Stage only)" because of an unspecified management agent error.
     Additional Information
     
     %3

    I did uninstall of latest Win.updates and starts working or 6 automatic schedules and then it revert back in to the hell... 

    Petr Weiner







    • 편집됨 Petr Weiner 2018년 5월 15일 화요일 오후 1:49
    2018년 5월 15일 화요일 오전 10:17
  • Hi Petr,

    Question 1: How to get it back (link on the EmployeeID in between SQL and AD in Metaverse)?

    - Do you see these objects in Connector Space (right click on MA, Search CS)?

    Question 2: Is the issue connected to the changed structure of SQL database or is it a MIM bug? -> Update to the lastest version will fix it? Can the issue be caused by the invalid or updated data type in SQL?

    - Looks like SQL DB problem.


    Emil Valiev


    • 편집됨 Emil Valiev 2018년 5월 15일 화요일 오후 1:06
    2018년 5월 15일 화요일 오후 1:06
  • Hello Emil thanks for your reply.

    Add 1/ Yes I doo see about 419 users there now (should be about 7500). It changes each time. At some point I get all records in metaverse. 

    Add 2/ SQL server backend where databases are store is running SQL 2008 R2 version 10.50.6542.0
    MIM is using SQL Native clients 2008R2 (updated from 10.50.1600.1 to 10.51.2500.0) and 2012 on version 11.3.6518.0

    Issue still persist. I got a tip to check if the anchor´s data type in SQL did not changed, but it is still same data type (varchar50).

    Last attempt will be to upgrade to the lastest MIM version tomorrow. I will investigate more on this topic.

    Thank you.


    Petr Weiner

    2018년 5월 16일 수요일 오전 9:35
  • I tried to reconfigure  SQL MA on Configure Externsions to "Run this rules extension in a separate process", but does not work either.

    Petr Weiner

    2018년 5월 17일 목요일 오전 9:33
  • Probably you can resolve the issue with the next method. Attention! These actions may corrupt your MA.

    1. Save MA - right-click, Export Management Agent.

    2. Open saved xml file. Look for 

    <schema>some text here</schema>

    Check this block and modify if needed.

    3. Delete old MA.

    4. Create new MA - Import Management Agent, select saved file.


    Emil Valiev

    2018년 5월 17일 목요일 오전 9:47
  • It does not look it needs some modification...

    Petr Weiner

    2018년 5월 18일 금요일 오전 8:52