Sage Remote Data Access Failure Fix (After 2025 Update)

12-minute fixVerified for Sage 50 2025Medium difficulty

Critical Issue Alert:

The Sage 2025 and 2025.1 updates have caused widespread Remote Data Access failures. Do not update if you rely on RDA until this fix is applied. Accountants and bookkeepers have been locked out for weeks, risking VAT return deadlines and critical accounting work.

What is Remote Data Access Failure?

Remote Data Access (RDA) allows external accountants and bookkeepers to access Sage company files remotely without being on the local network. RDA failure prevents these remote users from connecting to company data, often occurring after Sage updates, particularly the 2025 and 2025.1 versions which have known RDA issues.

Error RDA Failure: Remote accountant cannot access company file

External users cannot connect via Remote Data Access despite correct credentials and permissions.

Symptoms:
  • •Connection timeout when trying to access via RDA
  • •Error message: "Unable to connect to company data"
  • •"Service unavailable" or "Connection refused" errors
  • •RDA worked before Sage 2025 update
  • •Local users can access file but remote users cannot
  • •Multi-user to single-user switching issues preventing RDA
  • •Critical deadline risks (VAT returns, year-end, etc.)
Resolution Steps:
  1. 1.
    Verify Sage Services are running
  2. 2.
    Check firewall and port configuration
  3. 3.
    Reconfigure Remote Data Access settings
  4. 4.
    Update to latest Sage patch (post-2025.1)
  5. 5.
    Restart Sage Database Server
  6. 6.
    Re-authorize remote user access

Quick Fix for RDA Failure (12 Minutes)

Before You Start

If you haven't updated to Sage 2025 yet and use RDA regularly:

  • DO NOT UPDATE until Sage releases a confirmed fix
  • Contact Sage support to verify RDA issues are resolved
  • Check Sage community forums for latest update status

Fastest Solution (If Already Updated)

  1. Check Windows Services - ensure "Sage Remote Data Access Service" is running
  2. Restart Sage Database Server service
  3. Open Sage → Tools → Remote Data Access → Reconfigure
  4. Re-authorize remote user access permissions
  5. Verify firewall allows ports 5493 and 5494 (RDA default ports)
  6. Test connection from remote accountant's computer

Detailed Solution Steps

  • 1
    Verify Sage Services Status

    First, check if critical Sage services are running on the host computer:

    1. Press Windows + R, type services.msc
    2. Look for "Sage Remote Data Access Service" - ensure Status is "Running"
    3. Check "Sage Database Server" service - should also be "Running"
    4. If either is stopped, right-click and select "Start"
    5. Set both to "Automatic" startup type
    6. If services won't start, check Windows Event Log for error details
  • 2
    Reconfigure Remote Data Access

    Reconfigure RDA settings in Sage to reset the connection:

    1. Open Sage 50 on the server/host computer
    2. Go to Tools → Options → Remote Data Access
    3. Click "Configure" or "Setup Remote Access"
    4. Verify company files are listed and enabled for remote access
    5. Check "Enable Remote Data Access" is selected
    6. Note the connection URL/address for remote users
    7. Click "Apply" then "OK"
  • 3
    Configure Firewall Ports

    Ensure firewall allows Remote Data Access communication:

    Required Ports for RDA
    Default RDA Ports: 5493 and 5494 (TCP)
    Alternative Ports: May vary if custom configuration
     
    Also verify:
    - Port 8019 (Sage general communication)
    - Sage Database Server ports (55xxx range)
    1. Open Windows Defender Firewall with Advanced Security
    2. Click "Inbound Rules" → "New Rule"
    3. Select "Port" → TCP → Enter specific ports: 5493, 5494, 8019
    4. Allow the connection → Apply to all profiles
    5. Name it "Sage Remote Data Access"
    6. Repeat for "Outbound Rules"

    If using third-party firewall or router, you may need to configure port forwarding to the Sage server's internal IP address.

  • 4
    Re-authorize Remote Users

    Grant or refresh permissions for remote accountants:

    1. In Sage, go to Settings → Access Rights (or User Management)
    2. Select the remote user's account
    3. Verify "Remote Access" permission is enabled
    4. Check company file access permissions are correct
    5. If user account was created pre-update, try removing and re-adding
    6. Set access level (Read Only, Full Access, etc.) as appropriate
    7. Save changes and have remote user test connection
  • 5
    Apply Latest Sage Updates

    Install the latest Sage patches that address RDA issues:

    1. Go to Help → Check for Updates in Sage
    2. Install any available updates (especially post-2025.1 patches)
    3. Alternatively, download latest update from Sage City website
    4. Run update installer as Administrator
    5. Restart computer after update completes
    6. Retest RDA connection

    Sage has acknowledged RDA issues in 2025 and 2025.1. Check Sage City Community Hub for latest patch notes specifically mentioning RDA fixes.

  • 6
    Test Remote Connection

    Have the remote accountant test the connection:

    1. Remote user opens their Sage 50 application
    2. Select "Open Company Data" → "Remote"
    3. Enter connection URL/server address provided by host
    4. Enter their username and password
    5. Select company file from list
    6. Attempt to open the file
    7. If successful, verify they can view and edit data as expected
    Common Connection Errors
    "Cannot connect to server" → Check firewall/ports
    "Authentication failed" → Verify user credentials
    "Service unavailable" → Restart Sage RDA Service
    "Connection timeout" → Check network/internet connection
  • 7
    Temporary Workaround (If Nothing Else Works)

    If RDA continues to fail and you have urgent work:

    1. Consider using TeamViewer, AnyDesk, or Windows Remote Desktop as temporary solution
    2. Remote user connects to host computer desktop remotely
    3. Opens Sage locally on host machine (not via RDA)
    4. Performs necessary accounting work
    5. This is NOT ideal long-term but can prevent missing critical deadlines
    6. Continue working with Sage support for permanent RDA fix

    Remote desktop workarounds may have licensing implications. Check your Sage license terms and Windows Server/RDS requirements.

    • Why Does RDA Failure Occur?

    Common Causes (Especially After 2025 Update)

    • Sage 2025 Update Bugs: Known issues in 2025 and 2025.1 updates affecting RDA functionality and multi-user mode switching
    • Service Failure: Sage Remote Data Access Service stops running or fails to start after update
    • Port Blocking: Firewall or router blocking RDA communication ports after Windows or Sage updates
    • Permission Reset: Updates can reset user permissions, disabling remote access for external users
    • Configuration Corruption: RDA settings file becomes corrupted during update process
    • Database Server Issues: Update conflicts with Sage Database Server causing connection failures

    How to Prevent RDA Failures

    Best Practices:

    • Always check Sage Community Hub before updating to verify no reported RDA issues
    • Test RDA immediately after any Sage update to catch issues early
    • Maintain documentation of RDA configuration (ports, URLs, user permissions)
    • Keep backup remote access method available (VPN, remote desktop) for emergencies
    • Schedule updates well before critical deadlines (VAT returns, year-end, etc.)
    • Coordinate with accountant/bookkeeper before applying Sage updates

    Frequently Asked Questions

    Should I avoid updating to Sage 2025 if I use Remote Data Access?

    Yes, based on widespread user reports. The 2025 and 2025.1 updates have known RDA issues. Wait until Sage releases a confirmed fix or patch that specifically addresses RDA problems. Check Sage Community Hub for latest status before updating.

    Can I rollback to a previous Sage version if 2025 breaks my RDA?

    Rolling back Sage after a major version update is complex and risky, especially if you've already worked with data in the new version. Your best option is to apply the fixes in this guide or contact Sage support for a patch. Rollback should only be attempted with full backups and Sage support guidance.

    What's the difference between RDA and standard multi-user access?

    Multi-user access requires all users to be on the same local network. RDA (Remote Data Access) allows users outside your network (like external accountants) to connect over the internet. RDA requires specific configuration, services, and firewall settings that multi-user mode doesn't need.

    My accountant can't access via RDA and we have a VAT deadline approaching. What should I do?

    As an emergency workaround, set up Windows Remote Desktop or TeamViewer to give your accountant desktop access to the host computer. They can then work on Sage directly. This isn't ideal long-term but prevents missing critical deadlines while you fix the RDA issue properly.

    Related Resources

    Cloud Sync Connectivity Issues

    Fix cloud connection drop outs

    Bank Feeds Connection Error

    Fix bank feed import issues

    Need Professional Help?

    If you're still experiencing Remote Data Access failures after following these steps, or if you need emergency access restored for critical accounting work, our Sage experts can help configure RDA or set up alternative remote access solutions.

    Get Emergency Support