Encountering an error code while managing your business accounts can be a stressful experience, especially when you have a payroll to run or invoices to send. If you are using ABSS (formerly MYOB) and see Termination Code 1244, don’t panic. This is a common database-related error that usually points to a communication breakdown between the software and your company file.

Here is a breakdown of what this error means, why it happens, and how you can get back to work.

What is ABSS Termination Code 1244?

In technical terms, Error 1244 is often categorized as a “Network Protocol Error” or a “Request Timed Out” signal. It occurs when the ABSS application attempts to perform a task, like saving a transaction or generating a report, but the connection to the database is interrupted or “terminated” prematurely.

Essentially, the software expected a response from your data file, but the line went dead before the task could finish.

Common Causes of Error 1244

Several factors can cause this digital “miscommunication.” Understanding the root cause helps prevent the error from recurring.

  • Unstable Network Connection: If your company file is stored on a server or a shared drive, any flicker in your Wi-Fi or LAN connection can trigger a 1244 error.
  • Antivirus or Firewall Interference: Sometimes, overly aggressive security software views the data exchange between ABSS and your server as suspicious and “kills” the connection.
  • Large Data Files: If your company file is exceptionally large or hasn’t been optimized recently, the system may time out while trying to process complex requests.
  • Power Fluctuations: A sudden surge or drop in power to your router or server can cause a momentary lapse in data transmission.
  • Concurrent User Conflict: In multi-user environments, if two people attempt to modify the same record simultaneously, the database may terminate the session to prevent data corruption.

How to Resolve Error 1244

Follow these steps in order to clear the error and secure your data.

1. Restart and Refresh

The simplest fix is often the most effective.

  • Close ABSS on all workstations.
  • Restart the “Host” computer (where the data file is physically stored).
  • Restart your workstation and your router/modem.

2. Run the “Verify” and “Optimize” Tools

Since this error can sometimes be linked to minor database inconsistencies, use the built-in ABSS utilities:

  1. Go to File, Verify Company File. This checks for errors.
  2. If errors are found (or even if they aren’t), go to File, Optimize Company File. This re-indexes your data and can resolve timeout issues.

3. Check Power Management Settings

Ensure your network adapter isn’t “falling asleep” to save power.

  • Go to Device Manager, Network Adapters.
  • Right-click your adapter Properties and Power Management.
  • Uncheck “Allow the computer to turn off this device to save power.”

4. Configure Firewall Exceptions

Ensure that your Firewall or Antivirus is not blocking the ABSS executable files. Add ABSSAcct.exe or ABSSPrem.exe and the library folders to your “Exclusions” list.

5. Local Testing

If the error persists while working over a network, try moving a backup of the company file to your local C: drive. If the error disappears, you know the issue lies within your network hardware or cables rather than the software itself.

Best Practices to Prevent Future Errors

  • Go Wired: Always use a stable Ethernet (LAN) connection instead of Wi-Fi for accounting software.
  • Regular Backups: Ensure you take a manual backup daily.
  • Periodic Optimization: Run the “Optimize” tool once a month to keep the file size manageable and the database healthy.

Note: If you’ve tried these steps and the 1244 error persists, it may indicate more severe file corruption. In such cases, it is best to send the file in for data repair.