Diagnosing the Most Common ChiroTouch Connectivity Errors

In a server-based ChiroTouch environment, every workstation depends on a stable network link back to the machine that hosts the practice database. When that link drops—after a Windows update, a password change, a router reboot, or a simple overnight sleep cycle—front-desk staff see error dialogs and the provider's charting screen goes blank. The good news is that the vast majority of these interruptions trace back to one of three root causes: a broken network drive mapping, a stopped database service, or a credential mismatch. Knowing which one you are dealing with can cut a thirty-minute scramble down to a two-minute fix.

The error that shows up most often is Error 76, displayed as "Lost connection to the directory," followed by a variant that reads "Path not found…(76)/No common files directory found." Both messages mean the same thing: the workstation can no longer see the CTData folder on the ChiroTouch server. The short-term fix is to remap the network drive. In File Explorer, choose "Map network drive," enter the UNC path as \\SERVERNAME\CTData (replacing SERVERNAME with the actual computer name of your server), check "Reconnect at sign-in," and select "Connect using different credentials" if the workstation uses a local Windows account rather than the server's. Enter the username and password that your IT professional has granted access to the shared folder, check "Remember my credentials," and click OK. If a Windows File Explorer window pops open afterward, close it and relaunch ChiroTouch. The application should connect without further prompt.

Before you remap anything, confirm that the database service on the server is actually running. On the server computer, press the Windows key, type Services.msc, and press Enter. In the Services window, locate "SQL Server (MSSQLSERVER)" and verify its status reads "Running." If it is stopped, right-click and select Start, then try reopening ChiroTouch on the affected workstation. A related but distinct issue is the "Optimistic concurrency check failed. The row was modified outside of this cursor" message, which typically appears when a user double-clicks an item in the ChiroTouch Launcher and the system attempts to run its startup routine twice in rapid succession. Clicking OK on that dialog is usually all that is needed; the error should not recur on the next launch.

For practices that run a Self Check-In kiosk or an iPad connected to the office network, the same underlying connectivity rules apply, but the diagnostic path shifts. If the iPad loses its connection, run the Mobile Service Manager on the server as an administrator and confirm the device is pointing at the correct IP address. If the kiosk's check-in station stops recognizing a patient's pin pad, barcode, or fingerprint, open that patient's record and verify the "Enable Self Patient Check-In" box is actually checked on the Patient Information page under the Self Check-In tab—without that flag, no biometric or code method will work regardless of how the device is registered.

When the quick fixes above do not resolve the issue, the ChiroTouch Community remains the fastest route to a live representative. Log in to the community portal for your specific deployment (server-based or Cloud) and start a chat or submit a ticket. If the portal itself is unreachable, the direct phone lines are (844) 307-4901 for server-based practices and (619) 854-2998 for ChiroTouch Cloud. Having the server computer name, the affected workstation's IP address, and a screenshot of the exact error message ready before you call will help the support team narrow the problem quickly and keep your front desk back in patient flow in the shortest time possible.

Sources and further reading