• State Not Answered
  • +1 person also asked this people also asked this
  • Locked Locked
  • Replies 24 replies
  • Subscribers 94 subscribers
  • Views 10001 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 Reply Children
  • 0 over 5 years ago in reply to Markus Weiss-Ehlers

    I don't see any error on Ad-hoc provisioning, The error appear if I create a workflow and do Full Projection

    The error show as:

    <e>2019-03-10 06:53:05 +08:00 - \1IM-JOBSERV - VI.Projector.JobComponent.ProjectorComponent - 350b972b-117d-4d5b-a7d9-93842ca6658e: Errors occurred
        [2134003] Error executing synchronization.
        [1777018] Error executing synchronization project (Active Directory Domain (DC=WT,DC=COM))'s workflow (Daily workflow 1IM is master).
        [1777124] Error executing projection step (user - Phase #2) of projection configuration (Daily workflow 1IM is master (e2321504-6724-4496-8637-8141e03b016a)).
        [1777219] Error executing synchronization step (user - Phase #2)!
        [1777218] The synchronization step (user - 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 (user).
           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)
           ---- 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.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
        --- 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.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
        --- 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)

     

  • 0 over 5 years ago in reply to davidhsu

    I can see from the error that you are using a custom workflow. Just curious does the out of the box initial synchronization work without any issues?  Looking at mine the user phase 2 from the ootb sync is trying to bring over the secretary and the manager attribute values. What is yours trying to do? Sounds like the mapping you have set for that workflow step is not correct based on the error. 

  • 0 over 5 years ago in reply to Troy Grandy

    If you load up the problem sync project in the synchrnization editor and then click on workflows and the work flow that is causing the issue, there is an option to provide the execution plan, this will show you what user phase #2 is doing. See screenshot

  • 0 over 5 years ago in reply to Troy Grandy

    Hi Troy,

    The initial synchronization sync is work fine, at least it is not frozen if watch it from the job queue info tool.

    But if run from the customer workflow with phase 2 step like sync manager or otherwise, It generate the error.

     So I wonder how it process phase 2 step because it execute the  function. 

    VI.Projector.Projection.ProjectionStrategyBase._CheckMandatoryMethodProperties(IProjectionStep step, ProjectionDirection EffectiveProjectionDirection)

    and check the mandatory attribute then if you don;t give the all attribute it show the error.

    I use default mappings come from the wizard.

  • 0 over 5 years ago in reply to davidhsu

    Can you follow the link below and provide a copy of your sync project that is causing the issue? support.oneidentity.com/.../how-to-export-the-synchronization-project-shell-from-the-synchronization-editor

     

  • 0 over 5 years ago in reply to Troy Grandy

    Hi Troy,

    The attachment is sync proj, please help , very thanks!