A second QWC file with the same AppName becomes a cloned Web Connector entry ("App-1") whose scheduled runs sent the first entry's saved password; a per-file AppUniqueName keeps each entry apart
Observed 2026-10-06 on QuickBooks Enterprise Solutions 24.0 (US), reporting qbXML 17.0; Web Connector version not recorded.
When a QWC file has an AppName the Web Connector already lists and no AppUniqueName, the Web Connector adds a cloned entry with a suffix, such as "App-1". In one case the clone's scheduled runs sent the first entry's saved password, while "Update Selected" on the same row sent the right one. A file with its own AppUniqueName becomes its own entry, keyed by that name, and adding a newer file with the same AppUniqueName replaces that entry instead of cloning it. QuickBooks still identifies the application by AppName, so adding these tags did not make QuickBooks ask for authorization again.
<AppName>…</AppName>
<AppUniqueName>…</AppUniqueName>
<AppDisplayName>…</AppDisplayName>
When a file is added with QuickBooks open on the company file, the Web Connector stamps a FileID data extension under the file's OwnerID in the company file. While that stamp exists, any later add with the same OwnerID is refused, whether its FileID matches the stamp or not:
QBWC1039 Unique OwnerID/FileID pair value required
The refusal leaves the existing entry working. Removing the entry with that company file open clears the stamp. An entry added with QuickBooks closed had no stamp, and removing it failed with "QBWC1078: An error occured while clearing FileID from QuickBooks". An entry that disappears without Remove leaves its stamp behind. This request, sent through another application on the same file, cleared one and was answered statusCode="0":
<DataExtDelRq>
<DataExtDel>
<OwnerID>…</OwnerID>
<DataExtName>FileID</DataExtName>
<OtherDataExtType>Company</OtherDataExtType>
</DataExtDel>
</DataExtDelRq>
Intuit's CP3 tool ("SDK File Stamp Removing Tool") also cleared it, deleting the FileID value but not the definitions. A fresh file then replaced the entry under the same key, kept its saved password and turned Auto-Run on.
While the Web Connector shows a dialog or hangs, none of its entries run.
What to do
Give every QWC file you hand out its own AppUniqueName, and keep AppName the same if you do not want QuickBooks to ask for authorization again. Expect a second add of a file for the same OwnerID and company file to fail with QBWC1039, whatever FileID it carries. Tell users to remove the old entry with that company file open first, or clear the stamp, and to add files with QuickBooks open on the company file.
Not observed
- Why the clone sent the other entry's password; a later clone sent its own after the Web Connector was restarted.
- Removing an entry and then adding its newer file.
- The Web Connector version for the cloned entry; the
FileIDrefusals were on 34.0.10010.76.
QuBe Sync is a JSON API for QuickBooks Desktop that is built on what these findings show.