Company File Is Locked by Another Client Running at Machine Named

While a sync is running, the Web Connector may display Company file is locked by another client running at machine named .... This message is generated by QuickBooks Desktop itself when it can't get exclusive access to the company file, and it is a temporary locking issue that is unrelated to Maxio Platform.

Why the company file gets locked during a sync

QuickBooks Desktop uses a true, sophisticated relational database. A property of relational databases is "record locking": while one person or process is updating a record, that record is locked so nothing else can update it at the same time. The same property can apply to the file as a whole, which the operating system can also lock. It's unusual for this locking to actually block a user, because "simultaneous" access in computer terms is a matter of nanoseconds, so it's rare for anyone to ever see a locking error message.

However, a process can start and not finish, the same way even Mac users occasionally experience a hung application. Problems and errors do happen with QuickBooks Desktop; it's no more stable than most Windows applications. Running in multiuser mode, running in server mode, running with the QuickBooks file on a different machine, or using a hosting service over the web all increase the number of possible break points that can leave a process starting but never finishing, which results in a locked file or a locked record.

This is a claim about QuickBooks Desktop's own behavior as a third-party product, not something verifiable in Maxio's codebase. What is verifiable is how Maxio's Web Connector service handles the error once QuickBooks reports it: when QuickBooks returns an empty response to a sync request, Maxio logs it as an error returned by QuickBooks, saves the message, and stops the sync rather than generating or altering the error itself. That confirms the lock originates inside QuickBooks Desktop and is simply relayed to the Web Connector, not created by Maxio Platform.

Retry the Update, then restart QuickBooks and the Web Connector

Most locking errors clear on their own within a few minutes, so there's no need to jump straight to closing anything down. To resolve a persistent locking error.

1. Wait a few minutes, then select Update in the Web Connector to retry the sync. Rebooting terminates the broken process, and this typically resolves the QuickBooks locking issue on its own.
2. If the error persists, close QuickBooks and all QuickBooks-related applications, including the Web Connector, and reboot the machine or machines involved.
3. If rebooting doesn't resolve the issue, contact Intuit support, since the lock itself lives inside QuickBooks Desktop rather than in Maxio Platform.

Related information

For a list of other Web Connector error codes and how to find the exact error text to send to support, see QuickBooks Web Connector Errors.

If the Web Connector instead appears stuck partway through a sync rather than showing a locking message, see Web Connector Progress Bar Appears Frozen During a Long Sync.