QBWC - Error: 3391: The InteratorID is not valid

Modified on Tue, Dec 10 at 3:27 PM

1. Check the Web Connector Logs

  • Review the Web Connector log file to see if there are any specific error messages related to the integration. These logs may provide more details on the specific issue preventing the connection or integration with QuickBooks.

Location of Web Connector logs:

  • C:\ProgramData\Intuit\QBWebConnector\logs

2. Clear the Web Connector Cache

  • Try clearing the Web Connector cache or removing any pending transactions that might be stuck in the system. This could resolve issues related to corrupted or outdated information.

3. Check for Firewall/Antivirus Interference

  • Make sure that your firewall or antivirus is not blocking the connection between the Web Connector and QuickBooks. Temporarily disable them and try reconnecting to see if they are causing the issue.

4. Verify Date/Time Settings

  • Ensure that both the system date and time on the Merchant's machine and the QuickBooks company file are correct. Mismatched date or time settings can sometimes interfere with syncing or processing.

5. Test the Integration in a New Company File

  • Create a new test company file and attempt to set up the Web Connector there. If the integration works in the test file, it may indicate that there is an issue with the original company file itself.

6. Reinstall the QuickBooks Web Connector

  • Uninstall and reinstall the Web Connector on the machine. This can sometimes resolve issues caused by corrupted Web Connector files or configurations.

7. Ensure Compatibility

  • Verify that the version of the Web Connector and the QuickBooks Desktop you're using are fully compatible. Sometimes issues arise from version mismatches between QuickBooks Desktop and the Web Connector.

8. Check the User Permissions

  • Verify that the user account running the QuickBooks Web Connector has the appropriate permissions to interact with QuickBooks. This includes admin access or at least sufficient rights for integration.

9. Test on Another Machine

  • If possible, test the Web Connector integration on another machine to determine if the issue is specific to the Merchant's machine or if it’s related to the company file or QuickBooks configuration.

10. Consult QuickBooks Support

  • If none of these steps resolve the issue, it might be helpful to reach out to QuickBooks support for further assistance. They may have access to more detailed diagnostic tools that can pinpoint the exact issue.

 

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons

Feedback sent

We appreciate your effort and will try to fix the article