none
Object reference not set to an instance of an object. RRS feed

  • Question

  • Hey Guys,

    I have imported 130 users from a file management agent, some of those users (13 to be exact) started giveing the error below, while they have been created in in the portal, they also lack the display name. 

    The users also gets synced to a central AD after that, and the error indicates something about the sync rule to AD 

    There is nothing different about those users and the other imported within the same file. Any ideas about the this ?

    Microsoft.MetadirectoryServices.FunctionEvaluationException: Error encountered during evaluation of Sync Rule: 'Central AD Outbound'. Details: Object reference not set to an instance of an object.
       at Microsoft.MetadirectoryServices.FunctionLibrary.AttributeFlowMappingHandler.ExecuteOutboundTransformation(CSEntry csentry, MVEntry mventry, String strSyncRuleGuid, String xmlExpression, String workflowParameterTypes, String workflowParameterValues)

    If i look at the error i can see the below 


    Hany George | Consultant | IDC S.p.A | MCITP: Lync Server | MCITP: Exchange 2010 | MCTS: OCS | Blog: http://dusk1911.wordpress.com/ | If this post has been useful please click the green arrow to the left or click Propose as answer



    • Edited by Hany George Thursday, March 27, 2014 12:32 PM
    Thursday, March 27, 2014 12:23 PM

All replies

  • Need more info. What run profile were you running when you got the errors? And what are your flow rules? The error indicates something like there is a reference field somewhere (a field that contains a GUID that points at another object) but what it's pointing to doesn't exist. 
    Thursday, March 27, 2014 9:51 PM
  • In my experience this mostly originates when your sync rule tries to reference some value in the MV which doesn't exist.

    For instance, if your outbound SR says firstName => FirstName (which means flow the MV "firstName" to the connected data source "FirstName"), but the "firstName" attribute doesn't exist in the MV, then you will get this error.

    I suggest you take one of your problematic users and walk through the sync rule. You can also do a full sync preview on one of the objects and see which attribute flow is generating the error

    Monday, March 31, 2014 9:02 PM
  • Fixed this already, it turned out to be the DisplayName, for some reason it was in the MV but wont sync according to the rule. Manually added it and it works

    Hany George | Consultant | IDC S.p.A | MCITP: Lync Server | MCITP: Exchange 2010 | MCTS: OCS | Blog: http://dusk1911.wordpress.com/ | If this post has been useful please click the green arrow to the left or click Propose as answer

    Tuesday, April 1, 2014 9:08 AM