Decoding QuickBooks Status Messages
When a synchronization fails, the InterWeave Integration Manager logs a specific numerical code. Use this guide to identify the root cause and apply the fix.
Error Code | QuickBooks Message | Meaning & Resolution |
3100 | The name already exists. | Problem: You are trying to create a record (Customer/Vendor) that already exists in QuickBooks but is not bound to Salesforce. Fix: Find the record in QuickBooks and manually paste the Salesforce ID into the binding field, or rename the record in Salesforce. |
3000 | The HTTP request is invalid. | Problem: There is a communication breakdown between the InterWeave Cloud and your local QRemote/QODBC connector. Fix: Ensure the QuickBooks server is powered on, QuickBooks is open, and the QRemote service is running. |
3120 | Object not found. | Problem: The integration is trying to update a record (like an Invoice or Item) that has been deleted or renamed in QuickBooks. Fix: Check if the record was recently deleted. If so, you must remove the binding ID from Salesforce to allow the integration to "re-create" it. |
3140 | Invalid Reference ID. | Problem: A "Child" record (like an Invoice) is trying to sync, but its "Parent" (the Customer) doesn't exist in QuickBooks yet. Fix: Run the Customer Sync flow first to ensure the Parent record is created and bound. |
3170 | The record is currently in use. | Problem: A human user has the record open in QuickBooks (editing it) while the integration is trying to update it. Fix: Close the Customer or Invoice window in QuickBooks and the SmartAgent will automatically retry on the next cycle. |
3250 | Feature not supported. | Problem: You are trying to sync a feature (like "Multi-Currency" or "Advanced Inventory") that is not enabled in your version of QuickBooks. Fix: Enable the corresponding feature in QuickBooks Preferences or contact InterWeave support to adjust your mapping. |
3260 | Insufficient Permission. | Problem: The QuickBooks user assigned to the integration (e.g., InterWeave_User) does not have "Create" or "Modify" rights for that specific object. Fix: Log in as Admin and elevate the permissions for the Integration User. |
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article