Synchronization Process Stuck in 'PROCESSING' status.

Hi,

See my response on this thread:  https://www.oneidentity.com/community/identity-manager/f/forum/32211/unable-to-create-ldap-objects-with-a-custom-structural-object-class/78438#78438

It might help you to track down what is going on.

You get the 'RESET' on the StartUp Configuration page because the sync has started and set the LastRun date .... this must be RESET or cleared at the end of a successful (or failed) sync so that the next run knows it is OK to proceed.  If the date is not RESET and the sync runs again you will see a message stating that the sync cannot run as another sync with the same configuration is running.

By the way, you didn't mention which connector it was ..... I'm guessing AD.

HTH, Barry,

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 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.