Shell Error : Process aborted, connection in use

Example Errors:

Fatal Error 
Process aborted, connection in use

or

Connection already running

These errors occurs during Discovery, Sync or Unsync if the process is unable to lock the connection in preparation for beginning the run process. This usually means that the connection is already running. It may also occur if an old process is hung, or if a permissions problem refuses access to the lock file.

• Determine if you are accidentally running the same connection twice, at the same time. The Discovery/Sync process will abort with the above error if you attempt to run a connection more than once.
• If you have not accidentally attempted to run the same connection more than once, it is possible that the connection is locked because the previous run of this connection is hung.
  • Check for instances of ldap-ldif.exe running on the server even if you don’t think any sync is running.
  • In rare cases an ldap-ldif.exe might not stop correctly, so the connection lock file is not unlocked.
  • Manually kill the left over ldap-ldif.exe process in order to resume syncing.
  • Hung connections often result from bad network connectivity in the sync environment.
  • If this becomes an ongoing problem, you can consider configuring your sync script to run via NT Scheduler. You can configure the scheduled task to stop running after X number of hours.
    • Open the NT Scheduled Task.
    • Go to the Settings tab.
    • Specify the appropriate time frame for Stop the task if it runs for ___ hours.
• It is possible the ‘lock’ of connection is throwing this error, because the sync process does not have permissions to the lock.txt file.
  • The failed attempt to lock the connection (by locking lock.txt) will result in the connection already running error.
  • Verify the user logged into the workstation has permissions on the lock.txt file of the connection.
  • Remember, the user logon in use may differ depending if you are running from the User Interface (UI) or if this is a scheduled batch sync, so one may work while the other throws an error.
• If you are sure this connection is not already running, delete the connection lock.txt file: \UntiySync-v1.x\Connections\YourConnectionName\lock.txt

If you need further assistance, contact Support.