Synchronization Process Stuck in 'PROCESSING' status.

Hi, 

I'm having an issue with the One Identity Manager Connector (One Identity Manager ver. 8.1). The Synchronization Process is Stuck in PROCESSING Status and Job Server Log file (Debug Mode ON ) gives no information about a possible error during the execution. Checking out the StdioProcessor Logs, I discovered some errors returned at the beginning of the synchronization. 

  2021-03-01 18:02:43.5286 ERROR (DatabaseJournalRecorder 5eb69c46-ca19-405b-a1c6-a5a6aeacebe5) : One or more errors occurred. System.AggregateException: One or more errors occurred. ---> VI.Base.ViException: The object was already saved. Reload it to do any further changes.

After a few minutes, I saw (in the Synchronization Editor) the button ''RESET'' on the StartUp Configuration page.

The process has been in 'PROCESSING' for two days , then I had to delete it manually. 

The problem occurs every time  I execute the StartUp Configuration.

 Kind regards

Parents Reply Children
  • Hi Barry, 

    Thank you for the answer. The Connector i'm using is the 'One Identity Manager Connector', to sync from a custom view (created with the Schema Extension Tool) to the Person Table. I tried setting the log level to 'TRACE' as you suggested on the Thread that you linked but the only error message i see is the same I had before :

    2021-03-02 12:53:17.5103 ERROR (DatabaseJournalRecorder 210ac3f0-566c-409b-a5f6-60c86b557a59) : One or more errors occurred. System.AggregateException: One or more errors occurred. ---> VI.Base.ViException: The object was already saved. Reload it to do any further changes.
    at VI.DB.Entities.UnitOfWorkImpl.<PutAsync>d__37.MoveNext()
    --- End of stack trace from previous location where exception was thrown ---
    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
    at VI.DB.Entities.EventUnitOfWork.<PutAsync>d__2.MoveNext()
    --- End of stack trace from previous location where exception was thrown ---
    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
    at VI.DB.Entities.PermissionsUnitOfWork.<PutAsync>d__11.MoveNext()
    --- End of stack trace from previous location where exception was thrown ---
    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
    at VI.DB.Entities.EventUnitOfWork.<PutAsync>d__2.MoveNext()
    --- End of inner exception stack trace ---
    at System.Threading.Tasks.Task.ThrowIfExceptional(Boolean includeTaskCanceledExceptions)
    at System.Threading.Tasks.Task.Wait(Int32 millisecondsTimeout, CancellationToken cancellationToken)
    at VI.Base.SyncActions.Do(Func`1 action)
    at VI.Projector.Database.DatabaseJournalRecorder._AsyncSaveQueueProcessEntry(Object sender, EntryEventArgs`1 e)
    ---> (Inner Exception #0) VI.Base.ViException: The object was already saved. Reload it to do any further changes.
    at VI.DB.Entities.UnitOfWorkImpl.<PutAsync>d__37.MoveNext()
    --- End of stack trace from previous location where exception was thrown ---
    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
    at VI.DB.Entities.EventUnitOfWork.<PutAsync>d__2.MoveNext()
    --- End of stack trace from previous location where exception was thrown ---
    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
    at VI.DB.Entities.PermissionsUnitOfWork.<PutAsync>d__11.MoveNext()
    --- End of stack trace from previous location where exception was thrown ---
    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
    at VI.DB.Entities.EventUnitOfWork.<PutAsync>d__2.MoveNext()<---
    at System.Threading.Tasks.Task.ThrowIfExceptional(Boolean includeTaskCanceledExceptions)
    at System.Threading.Tasks.Task.Wait(Int32 millisecondsTimeout, CancellationToken cancellationToken)
    at VI.Base.SyncActions.Do(Func`1 action)
    at VI.Projector.Database.DatabaseJournalRecorder._AsyncSaveQueueProcessEntry(Object sender, EntryEventArgs`1 e)

    I had a similar situation during another sync of the same connector, but in that case the problem was about some email addresses violating the formatting script of the  Person@DefaultEmailAddress field. Even in this situation, the synch process was stuck in 'PROCESSING' status and the logs of the Synchronization Editor ended in 'Broken' status. I solved removing the mapping of the DefaultEmailAddress. But I can't undestand why in these cases of error, the synch process remains in PROCESSING Status. 

  • Hi Barry,

    Thank you for the answer. The Connector i'm using it's the 'One Identity Manager Connector', to sync from a custom view i created with the Schema Extension Tool to the Person Table. I tried setting the log level to 'TRACE' as you suggested on the Thread you linked but the only error message i see is the same I had before :

    2021-03-02 12:53:17.5103 ERROR (DatabaseJournalRecorder  ... ) : One or more errors occurred. System.AggregateException: One or more errors occurred. ---> VI.Base.ViException: The object was already saved. Reload it to do any further changes.

    I had a similar situation during another sync of te same connector, but in that case the problem was about some email addresses violating the formatting script of the "DefaultEmailAddress" field of Person Table. Even in this situation, the synch process was stuck in 'PROCESSIGN' status and the logs of the Synchronization Editor ended in 'Broken' status. I solved removing the mapping of the DefaultEmailAddress. But I can't undestand why in these cases of error, the synch process remains in PROCESSING Status.

  • Hi Enrico,

    OK well then I'm as baffled as you are .... sounds like a job for support.

    Regards, Barry.

  • Thank a lot for your reply Barry, i'm going to contact support fo that. I'll post the solution here if I find one. 

    Regards, Enrico.