QuickBooks Error QBWC1012: Duplicate Application Name in Web Connector

QuickBooks Web Connector reports QBWC1012 when an application tries to register under a name already in use, and this guide resolves the blockage.

QBWC1012 appears in the QuickBooks Web Connector when a third-party integration tries to register itself under a name the Web Connector already has on file. The synchronization stops before any data moves. Our engineers clear this error by resolving the duplicate registration and re-authorizing the application, and the steps below cover every scenario we see in practice.

What the error message says

In its most common form the message reads:

QBWC1012: Authentication failed due to following reason: Application with same name already exist in QuickBooks.

Wording can vary slightly between Web Connector releases, but the code QBWC1012 and the reference to an application name that already exists are constant. The message typically appears in the Web Connector status column, or in its log, at the moment the application attempts its first authentication after being added.

What the code means

The Web Connector keeps a list of every application registered on the workstation, and each entry must carry a unique name. That name comes from the AppName value inside the .QWC file supplied by the integration vendor. When the Web Connector is asked to add an application whose AppName matches an entry already present in its list, it refuses the registration and raises QBWC1012. The refusal happens during the authentication handshake, before any exchange of financial data, so nothing is partially written to the company file when it appears.

What triggers the error

• The integration was uninstalled and reinstalled, but its old entry was never removed from the Web Connector list.
• The same .QWC file was added twice, often because a fresh copy was downloaded to a different folder and added again.
• A vendor update shipped a new .QWC file carrying the same AppName as the one already registered.
• Two integrations, or test and production copies of the same integration, declare identical AppName values.
• A workstation was rebuilt or a profile was migrated, and a stale registration survived the move.

How to fix it

The fixes below are the ones our engineers apply, ordered by how often each resolves the error.

Scenario 1: a leftover entry from a previous installation (most common)

1. Close the third-party application and open the QuickBooks Web Connector.
2. In the application list, click the entry whose name matches the application you are adding.
3. Click Remove and confirm.
4. Click Add an Application, browse to the .QWC file, and open it.
5. Confirm the prompt in the Web Connector, then approve the access request inside QuickBooks, choosing an option such as "Yes, always allow access" and clicking Continue.
6. Select the application in the list, enter the password supplied by the integration vendor, and click Update Selected to run a first synchronization.

Scenario 2: the same .QWC file added twice

1. Open the Web Connector and review the list for two entries with the same name.
2. Decide which copy of the .QWC file is the keeper, store it in one fixed folder, and delete stray copies so the file can never be added from two locations.
3. Remove both entries from the Web Connector.
4. Re-add the single keeper file and authorize it as described in scenario 1.

Scenario 3: a genuine name collision between integrations

1. Open the .QWC file in a text editor and locate the AppName element.
2. Change the value to a unique name, for example by appending a short suffix that identifies the second integration.
3. Save the file, add it in the Web Connector, and authorize it as before.
4. Confirm with the provider of the integration that renaming is acceptable, since some services match server-side records on the application name.

Scenario 4: the duplicate does not appear in the list

1. Close the Web Connector and QuickBooks, restart the workstation, and reopen the Web Connector.
2. Run the Web Connector as administrator, then check the application list again.
3. If the name still refuses to register, uninstall and reinstall the QuickBooks Web Connector, then re-add the .QWC file and re-enter its password.

How to prevent it recurring

• Remove an application from the Web Connector before uninstalling or reinstalling it.
• Store each .QWC file in one dedicated folder and always add it from that location.
• Give test and production integrations distinct AppName values from the outset.
• Keep a secure record of the password assigned to each .QWC file so re-authorization is never blocked.
• After any QuickBooks or Web Connector upgrade, open the application list and confirm each integration appears exactly once.