Common Errors & Fixes

ERROR	Resolution
Duplicate Document Number Error : You must specify a different number. This number has already been used	This Error means the Transaction Number for this particular transaction already exists in QuickBooks Online for a different transaction. You can fix this by manually changing it in the source adapter
There is an invalid reference to QuickBooks Customer "XYZ" in the Invoice. QuickBooks error message: Invalid argument. The specified record does not exist in the list.	This error usually means it couldn't find a customer with the name in the error message in QuickBooks Desktop. It can be because this name already exists as a different entity in QBD( eg, vendor, Account ), hence could not be created as a customer. Another reason could be that DBSync couldn't create a new customer because of the incorrect data given at the Account level in the source adapter. Please review the Account details in the source adapter. If you aren't able to find the incorrect data, causing the issue, please reach out to our support team
here is an invalid reference to QuickBooks Item "Rest" in the Invoice. QuickBooks error message: Invalid argument. The specified record does not exist in the list.	This error usually means it couldn't find an Item with the name in the error message in QuickBooks Desktop. The main reason Dbsync couldn't create a new Item in QBD is because of incorrect data given in the Product /Item level in the source adapter. Please review the Product/Item details in the source adapter. If you aren't able to find the incorrect data, causing the issue, please reach out to our support team
Application Request to Abort error in webconnector	"We usually get this error when the QuickBooks company file path is changed. To fix this client can find the current QB file path in QB Desktop from the product information page in QBD, and open the correct QBD connector in DBSync ( usually the one with the connector name starting with the project name) and replace it with the newer location If this doesn't fix it, please reach out to support."
Question - Will DBSync sync get impacted if we upgrade our QBDesktop from one version to a higher version	No, as long as the QBfile path remains the same, it should not get impacted. If the file path is changed, you would have to replace the newer location in the Qbd connector in dbsync or reconfigure the web connector itself.
Salesforce conn is disconnectred and need steps to reconnect	Log in to the dbsync project Homepage Click on the Apps tab on the left side Click on the correct Salesforce connector Click on "Would you like to reconnect?" Choose the Endpoint as "Production" / "Sandbox" acc Click on "Connect (OAuth) " Enter SF username/password Once reconnected, click on " test connection " and verify "
QuickBooks Online disconnected and needs steps to reconnect	Log in to the DBSync project Homepage Click on the Apps tab on the left side Click on the correct QuickBooks Online connector Click on "Would you like to reconnect?" Choose the Environment as "Production" / "Sandbox" acc Click on "Connect To QuickBooks." Enter username/password Once reconnected, go to "Advanced properties" and click on "test connection" and verify.
Need a new instance/connector/ project( sandbox) to test our project	Since this question is very specific to your project and needs to be addressed by the Customer Success team, please send the above query to "[e-mail]" and one of the CSMs should reach back with you. Should be redirected to CSM directly.
Company file is locked by another client	"Solution: Actually, that error means someone else is updating the company file, and they are in single-user mode or performing an operation that locks the company file. QBWC cannot access the company file at that time. QBWC will try again the next time it runs. Also, chances are if you're running QuickBooks on a shared Windows Server, or in a hosted scenario with someone like Right Networks, Intuit Cloud, Cloud9, etc. If so, this error means that Windows Server auto-logged out some users and closed QuickBooks for them, but is still holding the file lock on the QuickBooks company file. Windows will automatically release the file lock after a short amount of time (usually 30 minutes to an hour) This error/issue should be taken care of by Right Networks, Intuit Cloud, Cloud9, like where your QB application is hosted on the remote server, and it is not a DBSync Issue.
invoice number / transaction number is empty in Invoices in Quickbooks online	"1. If the Invoice number in QuickBooks online is being sent from source connector (eg, SF, Shopify, etc), please check if that number is given in the source. If the Invoice number in QuickBooks online is NOT being sent from the source connector, and QBO is assigning it, then go to "Custom transaction numbers ", in the QBO, and make sure it's turned OFF. Qbonline can assign auto numbers to Invoices only if this "Custom transaction numbers " is turned OFF. Also, make sure this setting remains OFF. If, after manually turning it OFF, it changes back to ON on its own, reach out to the Intuit support team To find Custom transaction numbers in QBO - 1. Go to Settings 2. Select Account and settings 3. Select Sales 4. Select anywhere within the Sales form content section 5. Here you shall find - Custom transaction numbers"
“The record couldn't be saved as it was modified by another user.”	"This error very rarely occurs. Usually, if the record is resynced, it should disappear. But in case even after multiple resyncs, if it says the same error, you can ask the client to switch qb file to single user mode just for this one sync, resync this record, and it should fix the issue."
"Error : Something you're trying to use has been made inactive. Check the fields with accounts, customers, items, vendors or employees"	"Usually, when this error occurs in the response in logs for a Transaction request (like Invoice/Salesorder/estimate, etc), the first thing to check is if the Accounts/ vendors/or the multiple items Attached to that transaction in the request has been made inactive in The client’s QBO instance. Most of the time, this would be the case, and once the inactive Accounts/ vendors/Items have been reverted to Active status in QBO And then if the Transaction is synced again, it should sync over to QBO successfully."
"ERROR:Value is not supported by the QB API : ROSSI Design,"	"This error means the Customer/ Vendor/Items mentioned in the Error couldn't be found in QuickBooks. If its a new Customer, then new Customer creation would have failed, if another entity exists in QB with same name, so you can login to Qbonline and check if the same name exists in another entity, if so change that name, or come to you source connector and change the name in error mesaage and resync the records, this should fix it. If it's a new item, you can also check in the source connector if all necessary details have been provided, like qyt, rate, etc."
"Error - [UnexpectedErrorFault [ApiFault exceptionCode='REQUEST_LIMIT_EXCEEDED' exceptionMessage='TotalRequests Limit exceeded.'"	This error comes when the Salesforce daily api limit is exceeded, It goes away if the sync is not run for some time, and once the APi limit refreshes. You can go ot Salesofrce and find out which application consumed the highest APi to cause this.
Unable to update Opportunity. Id is empty or not specified.	"Firstly, you can check mapping itself for this field mentioned in the error, is absent or not in the respective transform and write. If the error is present, then the error usually means the field is used as a primary key/external ID in the update/upsert function. and couldn't find the record in the target connector to update. You can check in the target connectors object if the primary field value is absent or has an incorrect value."
Price Book Entry ID: id value of incorrect type: Drive Motor (AT-H600M)	"This error usually means the value passed for PricebookEntryId field mapping is incorrect. Please check the mapping for this field. You can also verify that the product mentioned in the error exists under the correct pricebook".
"field integrity exception: PricebookEntryId (pricebook entry is inactive) "	"This error means the items attached to the transaction in the source do not have an active pricebook in Salesforce. You could open the same item in Salesforce under the Products Object and check under the Standard / Custom Price book, and it would be inactive. Once you have made it active and resynced the transaction again, the line items should come over to Salesforce successfully "
field integrity exception: PricebookEntryId, unknown (versions 3.0 and higher must specify pricebook entry id, others must specify product id)	This error means the opportunity line item / Order line items couldn't be created in Salesforce, because the product involved in Salesforce is not attached to the correct procebook. Please open the product in SF, and confirm if it is attached the the respective pricebook mentioned in the mapping, if not, manually add it and resync the record
Not able to login to DBSync	In case you are not able to log in to DBSync, and errored out at the login page, most likely your DBSync license has expired. Please make sure the payment has been made from client's end. If it's already done, please contact your Customer Success Manager at DBSync or the DBSync Support Team
QuickBooksRestV3Adapter Required param missing, need to supply the required value for the API Required parameter Line is missing in the request	This error indicates that to the Transaction ( invoice, salesorder, Estimate etc) that you are trying to create does not have a line item attchaed in the source connector. Please open the record in Source connector and add 1 or more linitems to it
ERROR - An attempt was made to modify an Invoice 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.	This error indicates that the client QB Team updated the Closing date of the QB file to the latest date, and hence any records in the queue in the source connector before this date will not be allowed to be created by QBS
Error - Type field is required for Item CREATE/UPDATE requests for Minor Version 75 or above.	The type field mapping in Item ruleTransform and write has become mandatory, Usually this error comes if the Type field mapping is missing. Once the Type field is mapped, this error should be fixed