Common Errors For Web Connector
Common Errors for Web Connector
- Error message: "Invalid password for username"
Try to log in again, or reset your password in ProfitSee.
- Error message: "Max connection retries exceeded."
This error occurs when the user doesn't open the appropriate QB file for the initial sync.
To resolve, open the corresponding QB file and run the first sync in Web Connector again.
- Error message: "Application is busy. Try again later."
This error occurs when a user tries to sync a company that is already in the processing queue.
Web Connector has already received the commands, please wait until the sync is completed.
- Error message: "A QuickBooks company data file is already open and it is different from the one requested or there are multiple company files open." This error may occur when the user tries to sync in a different company after the initial sync.
Close the QuickBooks file and click on ‘Update Selected’ in Web Connector to re-sync.
- Error message: “ We detected an error, please contact support.”
Please contact support, we will pass your case on to our tech team immediately.
- When a sync is successfully completed, you will see the message: "Sync completed."
Common Errors for Quickbooks
We have also attached some errors that are connected with QuickBooks. If you would like to learn more, please visit QuickBooks support:https://support.quickbooks.intuit.com/support/default.aspx
- When a user doesn’t close the pop up in QuickBooks, Web Connector will display the error below. To proceed, simply close the pop up in QB and run Web Connector again.
- If a user signs into QuickBooks in multiple user mode, they will see the error below.
Remember, you must sign into QB in single user mode in order to sync with Web Connector.
- When a user uploads the same file in Web Connector, they will receive the message below.
Please make sure you are opening the correct QB file, and try to re-sync.
- If a user opens the wrong company file in QB for deletion, the error message below will be returned.
To resolve this issue, the user should simply open the correct file from the location they are referring to.