"Error details: Synchronization steps aborted. Details: Invalid object name '1004_1796_targetData (4226858)

"Error details: Synchronization steps aborted. Details: Invalid object name '1004_1796_targetData

Intermittently when attempting to run a workflow on schedule you will receive a failure message:

Error details: Synchronization steps aborted. Details: Invalid object name '1004_1796_targetData'. Invalid object name '1004_1796_targetData'.

This error is also recorded in the Quick Connect Server event log.

The number in object name is not fixed, it can vary:

'somenumber_somenumber_targetData'

You might experience this issue in the following scenarios:

1. The workflow task runs for more than an hour. The task starts on schedule or manually.
2. Quick Connect is installed on a VMWare box and the workflow task runs on schedule.

This issue may be caused by:

1. Windows Garbage Collector task that runs every 1 hour by default
2. The synchronize guest time with host option is turned on for the VMWare hosting Quick Connect
3. In some rare cases this issue may be caused by defect ID TF00262091 - a few seconds after starting a scheduled workflow, Quick Connect may unexpectedly start the workflow again.

1. If Quick Connect service is hosted on a VMWare machine, make sure the synchronize guest time with host option is turned off
2. Add a new DWORD value named StorageCollectorPeriod under the following registry hive:
   
   HKEY_LOCAL_MACHINE | SOFTWARE | Quest Software | Quick Connect | Service
3. Set the value of StorageCollectorPeriod to 720 (decimal), or 1440 (decimal) if your task runs for more than 8 hours.
4. Restart Quick Connect service.
5. If you are still experiencing the issue after completing steps 1 - 4, please contact support and reference Knowledge Base Article 82115.

TF00262091

The gargbage collector task runs every 1 hour by default. It cleans up the unused memory for every task that has not completed yet. If the StorageCollectorPeriod value is specified in the registry, it changes the interval between collector task runs to the specified number of minutes. If QC is hosted on a VMWare machine and the workflow runs on schedule, the workflow might be triggered twice. This is related to the way VMWare time is synchronized with the host time. The corresponding events are usually recorded in the QC Event log. The task starts first before the scheduled time, and then another attempt occurs right on time, or slighly later. Then, the gargbage collector task kicks in and breaks the task.