Sage 50 Data Verification Error: How to Rebuild Company Files Safely

Start with a separate backup and exclusive access, then review the Data Verification error log to identify the affected module or records. Rebuild only the relevant documented module through Utilities > Rebuild [Module] Data Files; for Accounts Receivable, Inventory Control, and Order Entry, use AR, then IC, then OE. If “REBUILD COMPLETE” does not appear, treat the rebuild as failed, restore the backup, and do not use the partially rebuilt data.

Menu names and procedures can vary by Sage 50 version, so confirm your version before following these steps.

What a Sage 50 Data Verification error means

What Data Verification checks

Sage 50 Data Verification checks company data for missing or potentially damaged files and records. To run it, open the company and select File > Data Verification. When the test finishes, Sage 50 displays a completion window and records its findings in a verification error log.

A completed verification does not necessarily mean that every underlying issue has been corrected. The log may identify errors, show the test’s start and finish times, describe changes made during verification, and record corrupt data records deleted during the process.

How the verification result differs from a rebuild

Process	Purpose and output	Limitation
Data Verification	Checks for missing or potentially damaged company files and records and writes findings to a verification log.	It does not establish that every issue has been corrected.
Module-level rebuilding	Reindexes and checks data for certain problems within a selected module and produces a rebuild result or log.	It is not a universal fix for every verification error.

Protect the company data before rebuilding

Create a separate backup

Create a new, separate backup before rebuilding. Do not overwrite an existing backup, because you may need the earlier copy if the rebuild fails or makes the condition worse. Keep the backup available for restoration rather than treating the rebuild as guaranteed recovery.

Confirm exclusive access and server conditions

• Have every other user log out of the company file.
• Check Network Status and confirm that only the current user is shown.
• Do not proceed while another user or task has the company open.
• Use exclusive access when Sage 50 presents that requirement.
• Where the company data is centralized, perform the rebuild directly at the server when appropriate.
• Confirm your Sage 50 release and menu labels before applying the procedure.

Review the Data Verification error log first

What the verification log contains

The verification error log is stored in the company data directory and receives information when verification tests are run. It can include:

• Errors found during testing
• Test start and finish times
• Changes made during verification
• Corrupt records deleted during the verification process

How to use the affected module or record information

Read the log before choosing a rebuild. Identify the affected module or records and select only a documented rebuild that corresponds to the problem. The available guidance does not map every individual verification-log code to a specific repair, so do not rebuild modules indiscriminately.

When rebuilding may be appropriate

Documented symptoms and triggers

Module-level rebuilding may be appropriate when the company has documented symptoms such as:

• Missing transactions
• Orders that cannot be selected for invoicing
• Duplicate checks
• Frozen options
• Missing lookup data
• A message saying that rebuilding is required
• A recommendation to rebuild from support

These symptoms do not prove that every Data Verification error should be rebuilt. Use the verification log to determine the affected area first. A complete company backup restoration is a different recovery action from rebuilding one module.

How to rebuild the documented company data files

Open the module rebuild utility

From the relevant Sage 50 module, select Utilities > Rebuild [Module] Data Files. Sage 50 may display an exclusive-access warning. Stop at that warning if another user or task is still in the company, and resolve the access issue before continuing.

Choose the module indicated by the verification findings or documented symptoms. Do not assume that rebuilding one module repairs unrelated company data.

Use the AR, IC, and OE sequence when applicable

When the affected documented modules are:

• Accounts Receivable (AR)
• Inventory Control (IC)
• Order Entry (OE)

Use this sequence: AR, then IC, then OE. This order applies to those named modules only; do not generalize it to unspecified modules.

Check the rebuild result and recover safely if it fails

Interpret the rebuild completion message

A successful rebuild displays a message in the form “REBUILD COMPLETE. # ERRORS FOUND.” The number reports the errors found during that rebuild. If errors are reported, review or print the rebuild log so you have a record of the result and can determine whether escalation is needed.

Restore the backup after an incomplete rebuild

If the “REBUILD COMPLETE” message does not appear, treat the operation as failed. Restore the separate backup and do not use the partially rebuilt company data. Stop rather than repeatedly modifying the same damaged files.

If Sage 50 cannot open the company file

An access problem can prevent you from reaching Data Verification or the rebuild utility. Keep this checklist secondary to the verification and rebuild process:

• Confirm that Sage 50 is pointing to the correct company data path.
• Check whether a mapped drive is connected and available.
• Confirm permissions for the shared folder containing the company data.
• Check that the required company files are present.
• Compare the Sage 50 release installed on the server and workstation; they should match.
• Check server-to-workstation connectivity when centralized company data cannot be accessed.

These checks are possible access causes, not a definitive diagnosis for every company-file opening failure. Resolve access safely without bypassing the backup and exclusive-access requirements.

After repair or rebuilding

Do not assume that a successful completion message guarantees complete recovery. Review the rebuild result, preserve any repaired state with a new backup where supported, and follow only version-specific post-rebuild validation steps. The exact process for rerunning verification or validating every restored record can vary by Sage 50 version and is not covered here.

When to stop and escalate

Stop conditions

Stop using the company data and preserve the backup if:

• Verification errors persist or become worse.
• The rebuild does not complete.
• The completion message does not appear.
• You cannot obtain exclusive access.
• The rebuild log reports errors that you cannot safely interpret.

After an incomplete rebuild, restore the verified backup rather than continuing with partially rebuilt data.

Support or Data Repair options

Persistent corruption may require current, version-specific guidance from official Sage support or an applicable Sage Data Repair service. Confirm the current procedure for your Sage 50 release before using any support or repair option. Do not assume that rebuilding will recover or preserve every record.