QuickBooks Error QBWC1062: Web Connector Password Mismatch

QuickBooks Web Connector reports QBWC1062 when the stored password stops matching your web app credentials; our guide clears it and restores syncing.

QBWC1062 stops a QuickBooks Web Connector run before any data moves. The Web Connector tries to sign in to your web application, the application refuses the credential it was given, and the update ends at once. Your company file is untouched. In nearly every case our engineers see, the fix is a password update on one side or the other.

The exact error message

The Web Connector window lists the application with its latest run marked as failed, and the log records a line of this form:

QBWC1062: Authentication failed

Some builds append a reason string returned by the web service, such as an expired token. You can open the log from the Web Connector window, and the failure shows on the application's entry there as well.

What does QBWC1062 mean?

The QBWC prefix marks an error raised by the QuickBooks Web Connector rather than by QuickBooks itself. Every sync begins with a sign-in call. The Web Connector sends the password saved for that application, and the web service checks it. When the service rejects the credential, it returns no session ticket, and the Web Connector reports QBWC1062 and stops. Nothing has been exchanged at that point, so no transaction is left half-written in your books.

Common triggers

These are the causes our engineers find, in rough order of frequency.

• The password changed in the web application, and the Web Connector still holds the old one. This is the most common cause.
• The credential was entered with an error. Passwords are case-sensitive, and a trailing space from a copy operation is invisible on screen.
• The integration was reset on the application side, which issued a new token while the old entry kept running.
• The application account is locked, or its plan lapsed, so the service refuses even a correct password.
• Two entries exist for the same application on one machine, each with a different saved password.
• A scheduled auto-run fires with a stored credential that no longer matches.

How do you fix QBWC1062?

Work through the scenarios in order; the first one clears the error in most cases.

The saved password is out of date

1. Open your web application's integrations or connected-apps settings and find the QuickBooks connector password or token.
2. Copy it exactly.
3. Open QuickBooks Web Connector on the machine that runs the sync.
4. Select the application in the list.
5. Choose Update Selected.
6. When the password prompt appears, enter the current credential. Retype it if a paste might carry a hidden space.
7. Tick the option to save the password, then let the update run to completion.

You do not know the current password

1. In the web application, open the settings page for the QuickBooks connection.
2. Reset the connector password, or generate a new token if that is what the application issues.
3. Update the Web Connector with the new value, following the steps above.
4. If the application offers no reset option, ask its support team to reissue the connector credential.

The correct password is still rejected

1. Sign in to the web application in a browser with the same account. If the account is locked or the plan lapsed, clear that first.
2. In the Web Connector, look for two entries for the same application. Select the duplicate and remove it.
3. Remove the application, add it again from the original .QWC file, approve the access prompt in QuickBooks, and enter the password when asked.
4. Open the Web Connector log and read the lines beside the code. Many services print the reason there, such as an expired token, which tells you which reset to perform.

Keeping the connection from breaking again

• Store the connector credential in a password manager next to the application login.
• Change credentials in one direction: reset in the application first, then update the Web Connector the same day.
• Keep one entry per application per machine.
• After any password change, run one manual update before you trust the schedule again.
• Keep the original .QWC file, so you can re-add the application quickly if an entry ever misbehaves.

QBWC1062 never damages your data. Once the two credentials match, the next run completes normally and the code disappears from the log.