• State Not Answered
  • +1 person also asked this people also asked this
  • Locked Locked
  • Replies 24 replies
  • Subscribers 94 subscribers
  • Views 9908 views
  • Users 0 members are here
Options
Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

phase #2 provisioning for AD always raise the same error: 2 mandatory parameters are required

david.fernandez
over 5 years ago

Hello,

I have a fresh new installation with an AD target configured. With the default provisioning workflow I always receive this error:

 

ErrorMessages = (2018-05-21 19:57:59.027) [2134003] Error executing synchronization.
[1777018] Error executing synchronization project (Active Directory Domain (DC=XXXXX,DC=XXXXX,DC=XX))'s workflow (Provisioning).
[1777124] Error executing projection step (container - Phase #2) of projection configuration (Provisioning (Provisioning)).
[1777219] Error executing synchronization step (container - Phase #2)!
[1777218] The synchronization step (container - Phase #2) cannot be executed because not all of the 2 mandatory parameters of method (Insert object) are mapped through the active rules.

Add rules for each parameter of the method used to the mapping rule (container).
   at StdioProcessor.StdioProcessor._Execute(Job job)
   at VI.Projector.JobComponent.ProjectorComponent.Activate(String task)
   at VI.Projector.JobComponent.ProjectorComponent._FullProjection()
   ---- Start of Inner Exception ----
   at VI.Projector.JobComponent.ProjectorComponent._FullProjection()
   at VI.Projector.Database.ProjectorExecutor.Project(ISession session, IProjectionConfiguration configuration, ProjectionOption options, ISystemObject adHocObject, CancellationToken cancellationToken)
   at VI.Projector.Projection.Extensions.Execute(IProjectorEngine engine, IProjectionConfiguration configuration, ProjectionOption options, ISystemObject adHocObject, CancellationToken cancellationToken)
   at System.Threading.Tasks.Task.Wait(Int32 millisecondsTimeout, CancellationToken cancellationToken)
   at System.Threading.Tasks.Task.ThrowIfExceptional(Boolean includeTaskCanceledExceptions)
   ---- Start of Inner Exception ----
   at VI.Projector.Projection.ProjectorEngine.<ExecuteAsync>d__3.MoveNext()
   ---- Start of Inner Exception ----
   at VI.Projector.Projection.ProjectorEngine.<ExecuteAsync>d__3.MoveNext()
   ---- Start of Inner Exception ----
   at VI.Projector.Projection.ProjectorEngine.<ExecuteAsync>d__3.MoveNext()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
--- End of stack trace from previous location where exception was thrown ---
   at VI.Projector.Projection.ProjectionStrategy.<ExecuteStepAsync>d__2.MoveNext()
   ---- Start of Inner Exception ----
   at VI.Projector.Projection.ProjectionStrategy.<ExecuteStepAsync>d__2.MoveNext()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
--- End of stack trace from previous location where exception was thrown ---
   at VI.Projector.Projection.ProjectionStrategyBase.<OnExecuteStepAsync>d__2.MoveNext()
   at VI.Projector.Projection.ProjectionStrategyBase._CheckMandatoryMethodProperties(IProjectionStep step, ProjectionDirection EffectiveProjectionDirection)

 

I'm using the default workflow for provisioning. The initial sync is ok and if I try to generate a new container or OU, It is created in AD.

 

If I remove the insert/update action for the container, I receive the same error for organization units.

 

Probably it's a small error, but I can't identify it :-(

 

Best regards,

 

David

Parents
  • 0 over 5 years ago

    Hello David,

    Did you solve your issue? I have the same problem now. Default Fullsynch workflow from AD to IDM is ok and also default Provisioning workflow is ok. AdHoc provisioning works good. But I created new workflow from IDM to AD for update group memberships which manually manage on Target System (AD). Sometimes I want to use IDM as master. When I execute my workflow I got same error even my workflow simulation finished successfully . How did you solve it?

    BR.

Reply
  • 0 over 5 years ago

    Hello David,

    Did you solve your issue? I have the same problem now. Default Fullsynch workflow from AD to IDM is ok and also default Provisioning workflow is ok. AdHoc provisioning works good. But I created new workflow from IDM to AD for update group memberships which manually manage on Target System (AD). Sometimes I want to use IDM as master. When I execute my workflow I got same error even my workflow simulation finished successfully . How did you solve it?

    BR.

Children
  • 0 over 5 years ago in reply to ferhat.karakoyun

    I saw something similar but it was for the user object. One way to get some more information about what is failing is to go to the workflow that you're running and next to the button to add a new workflow there's a sheet of paper and when you hover over it says 'Show execution plan...'. If you run that report you'll be able to see what flows are ocurring in the second phase and change them as neccessary. For me, I just deleted the manager and secretary flows because I didn't need them.