Eaglesoft Error 1310 During Install or Update: Causes and How to Fix It

Short answer: Error 1310 (“Error writing to file … Verify that you have access to that directory”) is a Windows Installer error. It means the Eaglesoft installer tried to write a file and Windows would not let it. The usual reasons are that the installer is not running with administrator rights, the file is in use because Eaglesoft is open on this or another computer, security software is locking the file, or the drive is full. Note the file path in the message: it tells you where the problem is.

What the error means

When you install or update Eaglesoft, the installer copies files into the Eaglesoft folders. Error 1310 appears when one of those copies fails. The message always includes the path of the file it could not write, and that path is the best clue to the cause.

Common causes

• Eaglesoft is still open somewhere, so its files are locked. On the server, this includes any workstation still connected.
• The installer is not running as an administrator, or the Windows account does not have permission to the target folder.
• Antivirus or endpoint security is scanning or blocking the file as it is written.
• Leftover files from a previous failed install are in the way.
• The drive is out of space, or the disk has errors.

What to check first

1. Write down the full error message, especially the file path.
2. Make sure Eaglesoft is closed on every computer, not only the one you are updating. For a server update, everyone must be out.
3. Make sure a good backup was made before the update started. Patterson recommends a backup before any installation (KB 1871).
4. Check free disk space on the drive in the error path.
5. Confirm you are logged in to Windows with an administrator account, and that the installer was started with “Run as administrator.”

How to fix it

[[TECH INPUT NEEDED: actual fix steps from tickets for Eaglesoft error 1310, e.g. which antivirus exclusions to set, how to clean up a partial install safely, and Patterson’s preferred retry procedure]]

How to avoid it next time

• Run Eaglesoft updates after hours, with every workstation logged out.
• Take and confirm a backup first.
• Set your security software’s exclusions for Eaglesoft before updating.
• Keep plenty of free space on the server and workstations.
• Update the server first, then the workstations, as Patterson’s installation instructions describe.

Frequently asked questions

Did the failed update damage our data?

Usually not, but a half-finished update can leave versions out of step. That is why a backup before every update matters, and why the server should be handled by IT or Patterson.

It failed on one workstation only. Is that serious?

Less so. Eaglesoft was probably open on that machine or security software blocked a file. The workstation will not connect until it matches the server version, so get it fixed before the next clinical day.

Can we just run the installer again?

On a workstation, after closing Eaglesoft and running as administrator, often yes. On the server, call first.

Still down? Call (716) 463-5111

If an Eaglesoft update has left your office unable to work, call Buffalo IT Services at (716) 463-5111. We plan and run Eaglesoft updates after hours, with backups first. See our Eaglesoft IT support page.