Sync error:
Error processing Customer: String length is either shorter or longer than supported by specification - String length specified does not match the supported length. Min:0 Max:30 supported. Supplied length:39
Category: Customer
Cause: The customer’s name or phone number has more than 30 characters, which exceeds QuickBooks’ limit.
Resolution: Edit the phone number in BuildOps so it is 30 characters or fewer, then re-sync.
Sync error:
There was an error adding, modifying or deleting <xxxxx> because it is already in use. QuickBooks error message: The transaction could not be locked. It is in use by another user.
Category: Customer/Vendor
Cause: The customer/vendor/invoice/receipt you’re trying to add/modify/delete via the QBD connector is currently open in QuickBooks by a user (or in a center/window), so QBD won’t let the integration change it.
Resolution: Close the Customer and Vendor Center (and any open customer/vendor records) in QuickBooks, then attempt to post again.
Sync error:
Element 'xxxxx': [facet 'maxLength'] The value has a length of 'xx'; this exceeds the allowed maximum length of '41'
Category: Invoice
Cause: A field referenced in the error (often a customer name, company name, or another invoice-related text field has more characters than 41 characters QuickBooks allows.
Resolution: Review the record mentioned in the element ID, shorten the value to meet QuickBooks’ character limits, then re-sync. You can reference QuickBooks’ limits here: Character limitations for fields in QuickBooks.
Sync error (examples):
CustomerProperty 'xxxxx xxxxxxx xxxxxx' companyName exceeds 41 charactersCustomer 'xxxxx xxxxxxx xxxxxx' customerName exceeds 41 charactersThe string "Client Name: xxxxxxxxx xxxxx xxxx" in the field "Addr1" is too longCategory: Invoice
Cause: The customer name or address in BuildOps exceeds QuickBooks’ character limits for that field.
Resolution: Shorten the customer name or address so it fits within QuickBooks’ allowed character limit, then re-sync. Reference: Character limitations for fields in QuickBooks.
Sync error:
There was an error when saving a invoice. The internals could not be locked, they are in use by another user
Category: Invoice
Cause: A related customer or vendor record is open in QuickBooks.
Resolution:
Try reposting; the record may already have been closed.
If it still fails, close any open customer records (for invoices or payments) or vendor records (for receipts) in QuickBooks, then run the sync again.
Sync error:
Error processing item “xxxxxxx”: there is an invalid reference to post account “xxxxxx-xxxxxx” in the Item: to change the posting account, you must switch to single-user mode
Category: Invoice
Cause: The GL account assigned to the item in BuildOps does not match the GL account assignment for that item in QuickBooks.
Resolution:
Put the QuickBooks company file into single-user mode: in QuickBooks, click File → Switch to Single-user Mode.
Sync the item from BuildOps.
After it succeeds, switch QuickBooks back to multi-user mode and then sync the transaction that was failing.
Sync error:
A related transaction object specified by the ID xxxxxxx-xxxxxx is already in use, or failed to acquire the lock for this object
Category: Invoice
Cause: A related customer (or vendor) record is open in QuickBooks, preventing the transaction from being updated.
Resolution:
Try reposting; the record may already have been closed.
If it still fails, close any open customer records (for invoices/payments) or vendor records (for receipts) in QuickBooks, then run the sync again.
Sync error:
An attempt was made to modify a Bill with a date that is on or before the closing date of the company. If you are sure you really want to do this, please ask a user with Admin privileges to remove the password for editing transactions on or before the closing date (this setting is in the Accounting Company Preferences), then try again.
Category: Invoice
Cause: The transaction is trying to sync to a date that is in a closed accounting period in QuickBooks (the bill date is on or before the company’s closing date).
Resolution:
In BuildOps, change the transaction date to a date after the closing date, then sync again; or
Bypass this transaction in BuildOps and enter it directly in QBO with the desired historical date.
Sync error:
Product 'xxxxxxx': GL Expense Account is required! Please correct the error above and try syncing again
Category: Invoice
Cause: The item used on the invoice in BuildOps is missing the GL Expense Account from the item list. All items must have both income and expense GL accounts to sync successfully.
Resolution: Check all items used on the invoice and make sure they have GL Expense Account at the item level from the item list, editing the item will resync it to QB, then re-sync the transaction that was failing.
Sync error:
Product 'xxxxxxx': GL Income Account is required! Please correct the error above and try syncing again
Category: Invoice
Cause: The item used on the invoice in BuildOps is missing the GL Expense Account from the item list. All items must have both income and expense GL accounts to sync successfully.
Resolution: Check all items used on the invoice and make sure they have GL Expense Account at the item level from the item list, editing the item will resync it to QB, then re-sync the transaction that was failing.
Sync error:
"Error processing item - undefined: There is an invalid reference to QuickBooks Post Account "8000000B-1207156583" in the ItemOtherCharge. QuickBooks error message: To change the posting account, you must switch to single-user mode."
Category: Product
Cause: The GL posting account on the item in BuildOps does not match the posting account for that item in QuickBooks.
Resolution:
Put the QuickBooks company file into single-user mode: in QuickBooks, click File → Switch to Single-user Mode.
Sync this item from BuildOps.
After it succeeds, switch QuickBooks back to multi-user mode and then sync any transactions that were failing with this error.