Set up
Is your data accessed across a network?
How to find out where your data is kept.
CAUTION: We recommend that IT professionals follow these steps. If you're unsure, contact your local IT support.
Corruption can result from power cuts, viruses, and interference from other software. We'll help you identify possible causes, especially if you experience recurring corruption.
We recommend you track where activities happen and on which computers to spot patterns. For example, the data always corrupts on a Tuesday after invoices update from a specific computer.
NOTE: This article helps troubleshoot the causes of corruption. Follow our A-Z index of Check Data errors, warnings, and comments article to fix corruption.
Do you log on to multiple computers using the same username?
Have you had any other problems with your computer recently?
For example, computer crashes or virus infection.
If you log on to more than one computer with the same username, you'll see the message:
'This username is already in use. Do you want to remove this user from the request list and logon again?'Removing the user from the request list while they're logged in on another computer can cause corruption.
To avoid this, before continuing to process on other computers, close Sage and log on again.
If the problem persists, select Next.
Have you had any other issues with any of your computers recently, including your server?
For example, computer crashes, virus infection or loss of network connection.
NOTE: Computer or software crashes can appear as software freezing and a message to end the program.
If you've had issues with any computers, this can contribute to the issues with your Sage data.
We recommend stopping the use of Sage 50 Accounts on these computers until you resolve the issues.
NOTE: When using Remote Data Access (RDA), ensure all computers meet the requirements when using RDA and use a wired internet connection.
If the problem persists, select Next.
NOTE: Sage Accounts has no numerical limit on transactions or records. Its capacity depends on available disk space. The following numbers are for guidance only and don't represent a data limit. Specific limits vary based on data size, network speed, and number of concurrent users.
As a guide, we recommend that to optimise performance you have:
If you've got too many transactions or records, reduce the numbers to less than the recommended limits. For help with reducing the number of records, use the articles below:
If the problem persists, select Next.
Copy the REPORTS folder from the client computer to the shared folder on the server computer. Time how long it takes to complete.
The standard location for the reports folder is C:\ProgramData\Sage\Accounts\20xx\Company.000.
NOTE: Ensure the folder contains other folders.
NOTE: Use the average of the second and third file transfers, as the first transfer takes longer. On a 100 Mbps network, the folder transfers in 30 to 40 seconds. On a 1 Gbps network, the folder transfers in 15 to 20 seconds.
If copying the file is twice as long as the time above, network speed affects Sage Accounts. The software will run slowly, which can cause data issues. Contact your network administrator for further help.
If the network transfer speed is OK, click Next.
Third-party software uses Sage Data Objects (SDO) to write data into Sage Accounts. SDO doesn't validate to prevent incorrect postings, for example, a sales invoice posted to the Purchase Tax Control Account nominal code. Such entries will cause data corruption in Sage Accounts.
Contact your provider to confirm compatibility with your Sage Accounts version. You can then back up and check your data is in good health. Do this before and after posting from this software.
Automatic backup software can run while users process in the data, which can lock the data files. Refer to your local IT support to adjust the backup settings.
If you haven't activated third-party integration and you don't use automated backup software, click Next.
There could be a problem with one of the Sage Accounts files.
If the problem persists, select Next.
Check the data directory in Help then About, then the Program Details section.
If the problem persists, select Next.
Follow the steps on every client computer that accesses Sage Accounts.
For example, if your server is called Server and your shared folder is Sage data, the UNC path starts with \\Server\Sage data
If the problem persists, select Next.
Check each computer that uses Sage Accounts.
NOTE: When using Remote Data Access (RDA), ensure all computers meet the RDA requirements and use a wired internet connection.
NOTE: Sage Accounts has no numerical limit on transactions or records. Its capacity depends on available disk space. The following numbers are for guidance only and don't represent a data limit. Specific limits vary based on data size, network speed, and number of concurrent users.
As a guide, we recommend that to optimise performance you have:
If you've got too many transactions or records, reduce the numbers to less than the recommended limits. For help with reducing the number of records, use the articles below:
Third-party software uses Sage Data Objects (SDO) to write data into Sage Accounts. SDO doesn't validate to prevent incorrect postings, for example, a sales invoice posted to the Purchase Tax Control Account nominal code. Such entries will cause data corruption in Sage Accounts.
Contact your provider to confirm compatibility with your Sage Accounts version. You can then back up and check your data is in good health. Do this before and after posting from this software.
Automatic backup software can run while users process, which can lock the data files. Refer to your local IT support to adjust the backup settings.
If you haven't activated third-party integration and you don't use automated backup software, click Next.
A common cause of corruption in Sage Accounts is a conflict with antivirus software. Modify your antivirus software to work alongside Sage 50 Accounts.
If you've had problems with any computers, this can contribute to the problems you're experiencing with your Sage data.
We recommend stopping the use of Sage 50 Accounts on these computers until you resolve the issues.
If you've had problems with any computers, this can contribute to the problems you're experiencing with your Sage data.
We recommend stopping the use of Sage 50 Accounts on these computers until you resolve the issues.
Have you had any other problems with your computer recently?
For example, computer crashes or virus infection.