Summary
An "I/O error in variable length part of record" occurs in Sage 50 Accounting. This error usually happens with DAT files that are a part of the company data and can indicate severe damage to the file.
Cause
- Badly damaged file
- Network error
Resolution
1. Identify whether the error is related to your network
- Skip to the next section if you're on a standalone
- With a network configuration, open Sage 50 on the server to see if you receive the error
- In the instance that the error affects only the workstation, have your IT admin check the server/workstation connection
- If the error occurs on the server, proceed to the next section
2. Resolve the damaged .DAT file
- Verify if the .DAT file mentioned in the error is safe to delete. See What files can be reindexed? for deleting files safely.
- If the file mentioned in the error is safe to delete.
- Go to your company directory. See How to locate company directories
- Move, rename, or delete the file
- Run Data Verification on the company. See How do I load, access, and run Data Verification?
- If the file in error isn’t safe to delete, restore a backup made before receiving the error. See How to restore a backup.
Occurs in a shared Remote Data Access company
- Stop sharing the company. See How to stop sharing a company with Remote Data Access.
- Then go to each machine that has Sage 50. Try reindexing only the .DAT file noted in the error. See Integrity Check Guide.
- We need to find the machine that can successfully finish the file reindex, without displaying any errors during the reindex process
- Just because the other machines aren’t getting the error doesn’t mean the .DAT file is good. Only reindexing will tell us whether it’s good or not
- If you find one machine that can reindex the .DAT without error, reshare from that machine. Then re-download the data to the other computers. See Successfully using Remote Data Access.
- If reindexing fails on all the machines, then you’ll need to restore a backup. Then reindex the .DAT, until you find a backup where the reindex finishes without error, then reshare that copy.
CAUTION: Don't rebase an RDA company when dealing with I/O errors. Unshare the company and run data tests.
Need more help?