Eaglesoft Errors: How to Fix the Most Common Problems

An Eaglesoft error at the front desk can stop a check-in, a claim, or an X-ray. This guide covers the most common Eaglesoft errors dental offices face, explains what each one means, and gives clear steps to fix it or escalate it.

TL;DR

• Most Eaglesoft errors trace back to the workstation losing contact with the server, so check the network and the Patterson server status first.

• Installation errors like 1310 and 1935 come from Windows permissions and the .NET Framework, not from patient data.

• Imaging errors, such as the Windows Driver Model device message, usually mean the camera driver or the in-software capture setting needs attention.

• Call Patterson Eaglesoft support for anything touching the database, the registry, or a repair install, and back up first.

What Eaglesoft Is, in Brief

A quick look at the software helps the fixes below make sense.

Eaglesoft is a Windows-based dental practice management system made by Patterson Dental. The Eaglesoft dental software runs front-office work from scheduling and charting to billing, imaging, and claims. The Eaglesoft dental program earns generally positive marks from dental teams for ease of use and support, with the most common complaint being occasional freezing during a busy day.

One detail explains most of the errors below. Eaglesoft runs on a Sybase SQL Anywhere database with a server-and-workstation setup. One machine runs the Patterson Eaglesoft Server, and the other computers connect to it as workstations. Many alarming Eaglesoft errors are connection or permission problems between a workstation and the server, not damage to the software itself. Practices comparing options can read more in our overview of dental practice management software, and a look at Dentrix shows how a competing platform handles similar workflows.

Read This First: Universal First Steps

A few checks solve a large share of Eaglesoft errors before any deeper troubleshooting.

Work through these in order whenever an error appears.

1. Write down the exact error text and what you were doing when it appeared, such as sending claims, opening an X-ray, or posting a payment. Each Eaglesoft error is specific.

2. Close and reopen Eaglesoft, then restart the workstation if the error returns.

3. If several workstations show the same error, suspect the server or the network. Reboot the server when no one is working in Eaglesoft, and confirm the Patterson server icon is green.

4. Keep your escalation path ready. Patterson Eaglesoft support is the official line for anything involving the database, the registry, or a repair install. Some steps also need your practice IT contact and Windows administrator rights.

5. Back up your data before anyone edits the registry or deletes configuration files.

A documented routine here keeps downtime short and protects the schedule. Our guide to dental clinic efficiency covers wider workflow habits that reduce these interruptions.

Installation and Update Errors: The 1000 Series

These errors appear while installing or updating Eaglesoft, not during daily use. They come from the Windows Installer and the .NET Framework, so the patient database stays untouched.

Eaglesoft Error 1310

This error shows up during an install or update and points to a folder permission problem.

The message reads “Error 1310. Error writing to file. Verify that you have access to that directory.” It means the installer cannot write to a target folder, often because leftover files from a previous Eaglesoft version are in the way, or the account lacks write permission. The Windows Club and Appuals document the same pattern across many Windows programs.

Work through these steps.

1. Sign in to Windows as a user with administrator rights.

2. Close all programs, right-click the Eaglesoft installer, and choose Run as administrator.

3. Set folder permissions if it still fails. Right-click the target folder, open Properties, open the Security tab, click Edit, select the Administrators group, check Full control, then click Apply and OK.

4. Re-register Windows Installer. Press Windows plus R, run msiexec /unregister, press Windows plus R again, run msiexec /regserver, then reboot.

5. Remove leftover files from any failed Eaglesoft install before trying again, with your IT contact confirming what is safe to delete.

Contact Patterson Eaglesoft support if the error continues, since the install may need a deeper cleanup.

Eaglesoft Error 1935

This error interrupts an install and traces back to the .NET Framework that Eaglesoft depends on.

The message reads “Error 1935. An error occurred during the installation of the assembly component.” It signals a damaged .NET state or a corrupted Windows file-system transaction log. Microsoft Support describes the assembly installation failure in detail.

Try these steps.

1. Reboot first and retry, which clears a surprising share of 1935 errors.

2. Run Windows Update fully, install all pending updates, including .NET updates, reboot, and retry.

3. Ask your IT contact to clear the file-system transaction log from an elevated Command Prompt, then reboot.

4. Repair or reinstall the .NET Framework if the steps above do not resolve it.

The .NET repair and transaction-log reset are good points to involve IT or Patterson Eaglesoft support.

Connection, Database, and Server Errors

This group covers the day-to-day errors that interrupt scheduling and claims. A frequent root cause is the network card going to sleep after a Windows update resets its power settings.

One fix repeats across this whole group, so it helps to learn it once.

1. Open Device Manager and expand Network adapters.

2. Right-click each adapter, open Properties, open the Power Management tab, and uncheck “Allow the computer to turn off this device to save power.”

3. Repeat for the USB Root Hubs if USB devices drop, then reboot.

This network-card fix is documented across the practitioner Eaglesoft Field Guide, an independent community resource that is not affiliated with Patterson.

Eaglesoft Error: Database Server Not Found

This error usually appears at login and means the workstation cannot reach the database service on the server.

The full message reads “[Sybase][ODBC Driver][SQL Anywhere] Database server not found.” Common causes include a workstation that started before the server finished booting, a server service that is not running, network card power settings, a firewall, or a DNS problem.

Work through these steps.

1. Confirm the server is on and finished booting, and check that the Patterson server icon is green. If it is red, right-click it and start the Patterson Eaglesoft Server.

2. Close Eaglesoft fully on the workstation, wait, and reopen it once the server is up.

3. Apply the network-card power fix above.

4. Open Start, then Eaglesoft, then Technical References, then Database Setup, and confirm the server name or IP matches a known-good workstation exactly. If auto-search is failing, uncheck it and enter the server IP as HOST equals the server IP.

Call Patterson Eaglesoft support if the service will not start, or if the database may be damaged.

Eaglesoft Error 503

This error appears when sending statements and reflects a refusal from the remote processing host.

A 500-series error, such as 503, reads “The request connection has been refused by the remote host” during a High Speed Statement submission. The number points to the processing service, usually Patterson eServices or the clearinghouse, rather than something broken on the workstation.

Try these steps.

1. Confirm the practice internet connection is working.

2. Wait and retry, since a 500-series refusal is often a temporary outage at the host.

3. Check whether eligibility and eClaims are also failing. Several services failing at once point to an outage, not your setup.

4. Confirm your statement service enrollment and credentials are current.

Patterson eServices can confirm whether the statement service is down. For context on how claims data is built, see our explainer on dental codes and claims.

Eaglesoft Error 800706BA

This error appears during real-time eligibility or an eServices sync, and the code is a Windows networking message.

The message references “CreateInstance failed” with “The RPC server is unavailable,” and 800706BA is the Windows code for that condition. A Windows component on the workstation cannot reach the local service it expects, or the eServices computer registration points to the wrong machine name. It often follows a Windows update, a computer name change, or a firewall or antivirus change. Microsoft Learn covers RPC troubleshooting at the Windows level.

Work through these steps.

1. Reboot the workstation, which clears many transient RPC failures.

2. Confirm the network is healthy and that the antivirus or firewall is not blocking Eaglesoft eServices.

3. Re-register the eServices computer. Close Eaglesoft, open Start, then Eaglesoft, then Technical References, then eServices, and confirm this desktop is listed. If it is missing, browse to it, click OK, exit, and reopen Eaglesoft.

4. For the advanced fix, the RemoteServerName registry value may need to point to the correct computer name. Back up the registry first, or have Patterson make the change.

Do not edit the registry without a backup, and lean on Patterson Eaglesoft support for that step.

Crashes, Freezes, and Corrupted Local Settings

Eaglesoft stores per-user preferences in a local configuration file. A power outage or a crash during a write can corrupt that file and produce cryptic errors on one workstation.

The most useful fix in this group resets that local file.

1. Log off and close Eaglesoft on the affected workstation.

2. Press Start, type the local app data location, and press Enter.

3. Open Patterson_Companies, then the Eaglesoft folder, then the folder that matches your installed version.

4. Delete the user.config file, which holds only preferences such as toolbar and window layout.

5. Empty the Recycle Bin and reopen Eaglesoft, which writes a fresh file. You may need to redo toolbars and printer preferences.

Eaglesoft Error Code 32

This code carries two meanings worth covering, both tied to a device rather than to patient data.

In Windows Device Manager, Code 32 reads “A driver for this device has been disabled,” and it stops an imaging device from working in Eaglesoft. Eaglesoft also surfaces other small device numbers, such as “Printer not activated, error code -30,” which are print and driver errors. The driver is disabled, missing, or corrupted, so Windows cannot start it.

Work through these steps.

1. Open Device Manager and find the device, often under Imaging devices.

2. If it shows a warning, right-click and uninstall the device, then reboot so Windows reinstalls it, or install the current driver from the manufacturer.

3. Confirm the device appears cleanly with no warning icon before reopening Eaglesoft.

4. In Eaglesoft, re-select the device under File, then Preferences, choose X-ray tab, and then select Device Properties.

The device manufacturer handles driver issues, and Patterson handles the Eaglesoft setup. For background on the sensors involved, see our guide to dental phosphor plates.

Root Element Is Missing and the Invalid Character Error

These errors tend to appear after a power outage and point straight to a corrupted local configuration file.

Apply the local-configuration reset above to clear them. Add battery backups on the server and the front-desk computers so a power blip cannot corrupt the file during a write. A short runtime that lets each machine shut down cleanly is worth the cost.

Access Violation Crashes

These crashes read “Eaglesoft.exe caused EXCEPTION_ACCESS_VIOLATION” and appear when posting payments, opening X-rays, scanning, or running reports.

Confirm a valid default printer is set, since Eaglesoft renders many screens through the printer. Try a different USB port for sensors and cameras, apply the local-configuration reset, and update .NET through Windows Update. Our overview of radiographic imaging explains how these capture devices fit into the clinical workflow.

Imaging, Camera, and Video Capture Errors

Eaglesoft and Patterson Imaging need two things working together: a healthy device driver visible in Device Manager, and the correct capture setting inside the software. Most imaging errors mean one of those two is wrong.

Set the capture path once. In Eaglesoft, open File, Preferences, the X-ray tab, Device Properties, then Video, and set the Capture Card to Standard Windows Driver Model Device. Then pick your camera as the Default Device. Patterson documents this on its official intraoral camera troubleshooting page. On Windows 10 and 11, also confirm camera privacy settings are not blocking desktop apps.

Eaglesoft Error: Error Opening Windows Driver Model (WDM) Device

This error means Eaglesoft cannot open the video device when you try to go live or capture with an intraoral camera. The same message appears with and without the WDM abbreviation.

The camera driver is not loaded, another program is holding the camera, the wrong capture device is selected, or Windows camera privacy is blocking access.

Work through these steps.

1. Confirm the camera shows in Device Manager with no warning icon, and reinstall the manufacturer driver if it shows as an Unknown Device or flagged.

2. Close any other app that might be using the camera, since only one program can hold a video device at a time, then reboot to clear a stuck handle.

3. In Eaglesoft, re-select the Capture Card as Standard Windows Driver Model Device and pick the correct Default Device.

4. On Windows 10 and 11, allow desktop apps to access the camera in the privacy settings.

5. Try a different USB port, ideally USB 2.0 for older cameras and sensors.

The camera manufacturer handles the driver, and Patterson Eaglesoft support handles the in-software capture setup.

Eaglesoft Error: Error Opening Video for Windows Device on Iris Digital Doc Cameras

This error appears with an Iris camera from Digital Doc and points to the older capture mode or a missing capture utility.

Video for Windows is the legacy capture mode, so the error means Eaglesoft is set to a mode the camera does not support, or the Iris capture utility, driver, or service is missing. Digital Doc advises checking that the camera capture service is present in Windows Services, since a missing service means the utility did not install correctly.

Work through these steps.

1. Verify the Iris camera appears in Device Manager without a warning.

2. Confirm the Digital Doc capture service is listed in Services. If it is absent, reinstall the Iris capture utility and driver.

3. In Eaglesoft, set the Capture Card to Standard Windows Driver Model Device and select the Iris camera as the Default Device.

4. Reboot, test the live video, then test a capture.

Digital Doc handles the capture utility, and Patterson handles the Eaglesoft device settings.

Claims and Electronic Statement Errors

These errors involve a third party, such as Change Healthcare, Vyne, or NEA, working alongside Eaglesoft. Many are outages or a single bad claim rather than a broken system.

Eaglesoft Error Sending Electronic Statements

This error covers failures when statements do not transmit, including the High Speed Statement message described under error 503.

The cause is usually one of a few things: an outage at the processing host, an enrollment or credentials problem with the statement service, a single malformed account in the batch, or a local SmartDoc setting when statements are set to save a copy.

Work through these steps.

1. Confirm the internet is working and retry once to rule out a transient outage.

2. Check whether other online Eaglesoft services are failing at the same time, which points to an outage.

3. Send statements in smaller batches to isolate a single problem account, then review that account for bad data and resend.

4. Confirm the statement service enrollment and credentials are current.

5. If the error names SmartDoc, review File, Preferences, SmartDoc settings.

Patterson eServices can confirm service status. Practices that want to reduce billing friction overall can review how strong dental insurance options affect claim volume and patient balances.

Object Reference Not Set When Sending eClaims

This companion error appears during eClaims and almost always traces to one claim with changed or mismatched data.

Send claims one at a time or in small batches to find the claim that triggers the error. Close and recreate that claim, often after correcting a subscriber ID that was entered as a Social Security number, then resend. Accurate records prevent most of these.

Clean documentation starts with the chart. Our guides to the dental chart and to writing dental chart notes show how consistent records cut downstream claim errors.

How to Prevent Eaglesoft Errors

A short routine turns the patterns above into prevention and keeps the schedule moving.

• Restart the server on a weekly schedule when no one is in Eaglesoft, since a server left running too long causes freezes

• Put the server and front-desk computers on battery backups to prevent configuration corruption during power loss

• Recheck network-card and USB power-management settings after every Windows update, since updates reset them silently

• Keep all workstations on a supported, consistent Windows version to avoid imaging and .NET errors

• document one known-good workstation server name and IP, so you can match a broken workstation quickly

• Maintain current, tested backups before any update

• Invest in Eaglesoft training so front-desk staff can tell a quick-restart error from a call-Patterson error

Tighter daily systems help here, too. A solid dental practice business plan usually budgets for IT maintenance and staff training that keep software running. Clinical teams also lean on a clear dental treatment plan workflow to keep documentation clean, which reduces the data errors that surface in claims.

When to Call Patterson Eaglesoft Support

A clear escalation rule saves time and protects the database.

Call Patterson Eaglesoft support when the database may be damaged, when a fix needs a repair or reinstall, when a step requires registry edits, when the server service will not start, or when an online service, such as claims, statements, or eligibility, appears down. Contacting Patterson is always a safe first or second step with any Eaglesoft error. Your own IT contact handles Windows, network, and driver-level work.

Users rate Patterson support well for responsiveness, which makes the call worthwhile when an error sits outside the quick fixes above.

Bottom Line

Most Eaglesoft errors are connection and permission problems, resulting in alarming messages. Check the server status and the network first, reset the local configuration file for one-workstation crashes, and confirm both the driver and the in-software setting for imaging errors. Keep backups current, restart the server weekly, and call Patterson Eaglesoft support for anything touching the database or the registry. A short, documented routine keeps these errors from turning into lost clinical time.