Skip to content
  • There are no suggestions because the search field is empty.

Error: A related transaction object specified by the ID is already in use or failed to acquire the lock for this object

This article provides guidance for Webgility Desktop users encountering the error “A related transaction object specified by the ID is already in use or failed to acquire the lock for this object.” The issue typically arises while creating payments with payouts posting or for posted orders in QuickBooks Desktop and occurs because the related transaction object is already in use or locked by another session or open transaction. The article explains when this error occurs, outlines possible causes, and provides step-by-step instructions to resolve the conflict by closing active sessions or transactions before retrying.

Overview:

This error commonly occurs during payment postings via payouts or order postings in QuickBooks Desktop. It signifies that a specific transaction object in QuickBooks Desktop is either in use or locked, preventing further action.

When Does This Happen?

You might encounter this error under the following scenarios:

  • Posting payments through a payout.

  • Posting orders in QuickBooks Desktop. 

Possible Cause:

The error typically arises due to the following reasons:

  • Another instance of QuickBooks Desktop is already running and using the transaction.

  • A related transaction, such as an invoice, is open in QuickBooks Desktop, and another user is trying to sync the payment to that same transaction.

How to Resolve:

Follow these steps to resolve the issue:

  1. Close All Instances of QuickBooks Desktop:
    ​    Ensure that all users close their instances of QuickBooks Desktop to prevent conflicts. This includes logging out of all open sessions.

  2. Shut Down the Sync Dashboard:
    ​    All users should also exit the Webgility Desktop Sync Dashboard to free up any locked transactions.

  3. Close Any Open Transactions:
    ​    Review and close any related transactions, such as open invoices, bills, or payments, that may be causing the conflict within QuickBooks Desktop.

  4. Retry the Posting:
    ​    Once all instances are closed and no transactions remain open, retry posting the payout or order again.