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

Overview:

This error commonly occurs during payment postings via payouts or order postings in QuickBooks. It signifies that a specific transaction object in QuickBooks 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.

 

Possible Cause:

The error typically arises due to the following reasons:

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

  • A related transaction, such as an invoice, is open in QuickBooks, 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:
    ​    Ensure that all users close their instances of QuickBooks to prevent conflicts. This includes logging out from all open sessions.

  2. Shut Down the Sync Dashboard:
    ​    All users should also exit the Webgility 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.

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

Need Help?

If you continue to experience issues or require further assistance, Webgility Support is here to help.