Let us help you tackle any Software issues and optimize your accounting workflow. 

Sage 50 crashes when saving transactions

Sage 50 File System Error 43: Causes, Troubleshooting, and Fixes

Sage 50 File System Error 43 can prevent you from opening a shared company file, accessing accounting records, or continuing work through Remote Data Access (RDA). The error is particularly associated with opening a company shared through Sage 50’s remote access service.

When this error appears, you may be unable to access the company even though your Sage 50 login credentials are correct. In some cases, another computer can still open the same company, while the affected workstation cannot.

The most effective solution depends on where the error occurs and whether another computer can successfully access the company. Sage’s recommended troubleshooting process starts by rebasing the shared company from a working computer. If the problem continues on a particular workstation, you may need to download a fresh copy of the shared company on that computer.

What Is Sage 50 File System Error 43?

Sage 50 File System Error 43 is an error that can occur when Sage 50 cannot successfully open a company shared through Remote Data Access. It may appear with a message similar to:

“File system 43 in [filename]”

The filename shown in the message can help identify the file involved, but the error alone does not establish that your entire company database is damaged. The issue may involve the local copy of a shared company, synchronization between computers, a connection problem, or company data that needs to be refreshed through the supported RDA process. Before changing files, determine whether the error affects one workstation or every computer that accesses the company.

Common Causes of Sage 50 Error 43

Possible causeWhat you may noticeWhat to check
Local RDA company copy has a problemOne computer reports Error 43 while another can open the companyRe-download the shared company on the affected computer.
Shared company needs to be rebasedThe company opens on one computer but not on othersRebase from a computer that can still access the company.
Unstable network connectionThe error appears intermittently during remote accessCheck internet stability and prefer a wired connection.
Different Sage 50 buildsComputers running the shared company have different program buildsCompare the installed build numbers.
Remote Data Access synchronization issueThe company reports that data must synchronize or that synchronization failedFollow the procedure for the exact synchronization message.
Firewall or connectivity restrictionThe shared company cannot download or synchronizeCheck network and firewall settings against Sage’s requirements.
Company data or local database service problemThe error continues after refreshing the shared companyInvestigate the company data and database service with the appropriate support procedure.

These are possible causes, not a guarantee that every Error 43 has the same origin. Follow the steps in order and stop when the company opens successfully.

How to Fix Sage 50 File System Error 43 

Step 1: Identify Whether the Problem Affects One Computer or Everyone

Start by determining how widely the error occurs. This helps you choose the correct recovery method and avoid unnecessary changes to the company data.

Follow these checks:

  1. Close the error message and exit Sage 50 on the affected computer.
  2. Ask whether another authorized user can open the same shared company.
  3. If another computer can open it, confirm that the company displays the latest expected transactions.
  4. If the company opens successfully elsewhere, identify which workstation is experiencing the error.
  5. If every computer is affected, record that fact before proceeding.

If only one computer has the problem, the local copy of the shared company may need to be refreshed. If another computer can open the company, do not immediately remove or recreate the shared company. First try Sage’s recommended rebase procedure. If no computer can access the company, avoid guessing which copy is authoritative. You may need additional troubleshooting or help from Sage support before changing the shared data.

Step 2: Check Your Internet Connection

Remote Data Access depends on a reliable connection between the computer and the shared company service. An unstable connection can interrupt access or synchronization. To check the connection:

  1. Confirm that the computer has internet access.
  2. Open a few trusted websites to verify that the connection is working.
  3. If you are connected through Wi-Fi, try a wired network connection if available.
  4. Avoid switching networks while Sage 50 is downloading or synchronizing company data.
  5. Retry opening the shared company.

Sage recommends a hard-wired connection for Remote Data Access because wireless connections can be unstable. If other internet services work but Sage 50 continues to report Error 43, move to the next step. The issue may be related to the local company copy or the synchronization process rather than the general internet connection.

Step 3: Rebase the Remote Data Access Company

If another computer can still open the company, Sage recommends rebasing the shared company from that working computer. Rebasing refreshes the shared company’s remote data state through Sage’s supported process. It is not the same as manually copying individual company files. Follow these steps on the computer that can successfully open the company:

  1. Open Sage 50 and access the affected company.
  2. Select Help.
  3. Open Support Utilities.
  4. Select Rebase Remote Data Access Company.
  5. Follow the on-screen instructions and wait for the operation to complete.
  6. Close the confirmation message indicating that the company was successfully uploaded to Remote Data Access.
  7. Check whether the company opens correctly on the working computer.
  8. Ask the affected users to retry opening the company.

If all computers can now open the company, verify that the expected transactions are present. If the original workstation still reports File System Error 43, continue to the re-download procedure.

Important: If multiple users have made changes while working with different copies of the data, confirm which copy contains the latest valid transactions before performing recovery actions. Do not assume that every computer has identical data.

Step 4: Re-download the Shared Company on the Affected Computer

If rebasing does not resolve the issue, Sage’s documented Error 43 procedure recommends downloading a fresh copy of the shared company on the computer receiving the error. This procedure should be performed only on the affected computer when another computer can still access the company.

Before proceeding, confirm that the working computer has the expected company data. If the affected workstation contains any unique changes that have not synchronized, stop and seek guidance before moving its local company folder.

Follow these steps:

  1. Close Sage 50 completely on the affected computer.
  2. Locate the company data directory used by Sage 50.
  3. Identify the directory for the company reporting Error 43.
  4. Right-click that company directory and select Cut.
  5. Paste the directory in a safe temporary location, such as the desktop, rather than permanently deleting it.
  6. Open Sage 50.
  7. Select File, then Connect to a Shared Company.
  8. Sign in using the Sage account associated with the shared company.
  9. Select the appropriate company and follow the prompts to download it again.
  10. Wait for the download to finish and then open the company.

The exact prompts may vary by release. Moving the old local folder aside allows you to retain it temporarily while testing the newly downloaded copy. Do not delete the old folder until the new company opens successfully and you have confirmed that the expected data is available.

If the company opens without the error, verify several recent transactions and confirm that you are working with the correct company.

Step 5: Compare Sage 50 Builds on All Computers

If different computers access the same Remote Data Access company, verify that they are using compatible Sage 50 program builds. A difference between installed builds can interfere with shared-company operations. To compare builds:

  1. Open Sage 50 on each relevant computer.
  2. Select Help, then About Sage 50 Accounting.
  3. Locate the Build information.
  4. Record the build number from each computer.
  5. Compare the results.
  6. Install the appropriate program update on computers that are behind, following Sage’s instructions.

Do not compare only the product year. Two computers showing the same product year may still have different installed builds. After updating, reopen Sage 50 and retry the shared company. If Error 43 remains, continue with the network and service checks.

Step 6: Check Firewall and Network Access

Firewall restrictions or network settings can prevent Sage 50 from communicating with Remote Data Access correctly. If the company still fails to download or synchronize, review the network environment.

  1. Confirm that the affected computer can access the internet.
  2. Check whether the firewall or security software has recently changed.
  3. Review Sage’s current Remote Data Access connectivity requirements.
  4. Confirm that any required ports and application permissions are configured according to Sage’s instructions.
  5. Retry the supported connection or download process.

Sage’s troubleshooting guidance for certain Remote Data Access download and synchronization errors specifically identifies port 5222 as a port that may need to be allowed through the firewall. Confirm the current requirements for your version and network before changing firewall rules.

Do not disable your firewall permanently or open unnecessary ports. If your company uses managed network security, ask the network administrator to review the required permissions. If the firewall configuration is correct and Error 43 persists, the issue may require a closer review of the local data or database service.

Step 7: Check for Related Remote Data Access Synchronization Errors

File System Error 43 can occur in an RDA workflow, but it is important to distinguish it from a separate synchronization message.

For example, Sage 50 may display a message stating that Remote Data Access needs to synchronize company data. Sage’s troubleshooting guidance identifies locked files and damaged company-folder files as possible causes of that separate message. If you receive a synchronization message instead of—or in addition to—Error 43:

  1. Record the exact message shown on the screen.
  2. Close the company in Sage 50.
  3. Check Sage’s instructions for that specific synchronization error.
  4. If the documented procedure identifies a locked syncstate.txt file, follow the instructions for closing the company and removing that file.
  5. Reopen the company and allow Sage to run the required synchronization or rebase process.

Do not delete random files from the company directory. The syncstate.txt procedure applies to a particular synchronization problem and should not be treated as a universal fix for every file system error.

If synchronization fails again, verify the Sage account being used. In Sage 50, check the user under Maintain, Users, Set Up User Security, and confirm that the account used for Remote Data Access matches the intended user account. If the problem continues, stop and use Sage’s documented cleanup or support procedure rather than repeatedly deleting files.

Step 8: Check the Actian Database Service if the Error Persists

Sage 50 uses the Actian database engine for company data operations. Problems with the database service can contribute to broader data access or synchronization issues. Consider this step only after the simpler checks have failed or when other symptoms point to a database service problem. Before proceeding:

  1. Make sure all users have exited Sage 50.
  2. Confirm that a current backup is available where possible.
  3. Review Sage’s instructions for checking the Actian Zen database service for your installed version.
  4. Follow the supported procedure to restart the service if directed.
  5. Reopen Sage 50 and test the company.

If Sage identifies a need to reinstall Actian Zen, follow the specific removal and installation instructions for your version. Do not uninstall database components casually, especially on a computer that hosts company data. If the service is running normally but the company still cannot open, gather the error details and contact Sage support for further diagnosis.

Step 9: Stop and Protect the Data if No Computer Can Open the Company

If Error 43 appears on every computer, or if rebase and re-download attempts do not work, avoid repeatedly replacing company folders. At this point, determine which data copy is current and whether a backup is available. Use this approach:

  1. Stop making further changes to the affected company copies.
  2. Identify the computer that last successfully opened the company.
  3. Check whether a recent backup exists.
  4. Record which computers have made changes since the last successful synchronization.
  5. Preserve the affected data folders until the recovery method is confirmed.
  6. Contact Sage support or an experienced Sage 50 data specialist if the company remains inaccessible.

Do not restore a backup over the current company without verifying the backup date and the transactions that may be missing. Restoring the wrong copy can cause data loss even if it removes the original error.

Sage 50 Error 43 When Opening a Company File: Local vs. Remote Access

Not every Sage 50 company file is shared through Remote Data Access. If the error occurs with a company stored locally or on a traditional office network, the RDA rebase and re-download procedure may not apply. Use the following guide to narrow down the situation.

Where the company is storedRecommended approach
Shared through Remote Data AccessFollow the rebase and affected-computer re-download procedures.
Stored on a local computerCheck the exact error message, company data location, and applicable Sage data troubleshooting instructions.
Stored on an office networkCheck network access, permissions, the hosting computer, and the supported database service configuration.
Accessible from one workstation but not anotherCompare Sage 50 builds and investigate the affected workstation’s local company copy.
Inaccessible from all workstationsPreserve the data, verify backup availability, and escalate before attempting recovery.

For a locally stored company, do not move or rename database files unless the applicable Sage instructions specifically direct you to do so. The correct solution depends on the filename in the error message and the way the company is stored.

How to Prevent Sage 50 File System Error 43

You cannot prevent every connection or data access problem, but the following practices reduce the risk of recurring RDA errors.

  1. Keep Sage 50 Updated: Use the appropriate program updates on computers that access the shared company. Confirm the build number after updates rather than assuming that the installation completed successfully.
  2. Use a Reliable Connection: Prefer a stable, wired connection when working with Remote Data Access. Avoid interrupting downloads or synchronization processes.
  3. Confirm the Correct Company Data: Before rebasing or downloading a fresh copy, confirm which computer has the most recent valid data. This is especially important if users have been working from separate copies.
  4. Maintain Regular Backups: Create and verify backups according to your organization’s backup schedule. Store backups separately from the working company folder so that a local data problem does not affect both.
  5. Avoid Unnecessary File Changes: Do not manually delete company files, synchronization files, or database components without a documented reason. Use the recovery method intended for the exact error.
  6. Document Recurring Problems: If Error 43 appears repeatedly, record the affected computer, Sage 50 build, connection type, error message, and steps that preceded the failure. This information helps distinguish a workstation issue from a shared-company or network problem.

Conclusion

Sage 50 File System Error 43 is commonly associated with opening a company shared through Remote Data Access. The recommended first approach is to rebase the company from a computer that can still open it. If the error remains on one workstation, download a fresh copy of the shared company on that computer using Sage’s supported procedure.

If these steps do not resolve the issue, compare Sage 50 builds, review the network connection and firewall requirements, and investigate any related synchronization or database service errors. Protect the company data throughout the process, and avoid deleting or replacing files until you know which copy contains the latest valid transactions.

FAQs of Sage 50 File System Error 43:

How do I fix Sage 50 Error 43 when opening a company file?

If the company is shared through Remote Data Access, first rebase it from a computer that can still open it. If the error continues on the affected workstation, move the local company directory to a safe temporary location and re-download the shared company using File, Connect to a Shared Company.

Can Sage 50 Error 43 be caused by a poor internet connection?

An unstable internet connection can interfere with Remote Data Access and synchronization. Try a reliable connection, preferably wired, and retry the company access process. If the error persists, investigate the local company copy and the shared-company synchronization state.

Should I delete the company folder to resolve File System Error 43?

No. Do not permanently delete the company folder as a first step. Sage’s documented procedure for re-downloading a shared company instructs users to move the affected local directory aside before downloading a fresh copy. Confirm that the working company has the expected data and retain the old folder until the new copy has been verified.

What if Sage 50 Error 43 appears on every computer?

If no computer can open the company, stop making changes to the different copies and identify which one contains the latest valid data. Check backup availability and seek further assistance before restoring or replacing company files. A re-download should not be performed blindly when no known-good shared copy is available.

Can different Sage 50 versions cause Remote Data Access errors?

Different program builds can contribute to shared-company problems. Check Help, About Sage 50 Accounting on each computer and compare the build numbers. Install the appropriate updates according to Sage’s instructions, then test the company again.

What should I do if rebasing and re-downloading do not fix Sage 50 File System Error 43?

Confirm the connection and firewall requirements, compare program builds, and check whether another synchronization error is present. If the problem remains, preserve the company data and backups, record the exact error and affected computer, and contact Sage support or a qualified Sage 50 data specialist.

Related Articles