Sage 50 Error 3110: Multi-User Network Access Failed

12-minute fixVerified for Sage 50 2024/2025Medium difficulty

Quick Answer:

Sage 50 Error 3110 occurs when the Actian database service (formerly Pervasive SQL) cannot establish network communication between workstations and the server. Common causes include stopped Actian services, orphaned user sessions locking the company file, firewall blocking port 1583, or incorrect server name configuration. Fix by restarting Actian services, clearing locked sessions, and verifying network settings.

What is Sage 50 Error 3110?

Sage 50 Error 3110 is a multi-user network communication error preventing workstations from connecting to the company file stored on a server. This error specifically relates to the Actian database engine (formerly Pervasive SQL/PSQL) that Sage 50 uses for multi-user access. When workstations cannot communicate with the Actian service on the server, users receive Error 3110 and cannot open the company file in multi-user mode.

Error 3110: Multi-User Network Access Communication Failure

Sage 50 cannot establish network communication with the Actian database service on the server, preventing multi-user access to the company file.

Symptoms:
  • •Error 3110: Unable to access company file in multi-user mode
  • •Message: Cannot connect to Actian database service
  • •Workstations cannot open company file stored on server
  • •Server can open file but workstations cannot
  • •Error after server restart or Windows updates
  • •Intermittent connection drops during work
  • •New users cannot connect to existing multi-user session
Resolution Steps:
  1. 1.
    Restart Actian database services on server
  2. 2.
    Clear orphaned user sessions in Session Manager
  3. 3.
    Verify firewall allows port 1583 communication
  4. 4.
    Update server name configuration in Sage 50
  5. 5.
    Repair Actian database engine installation
  6. 6.
    Check Windows permissions on company file folder

Quick Fix for Error 3110 (12 Minutes)

Fastest Solution

  1. On server: Close Sage 50 on all workstations (verify no one is logged in)
  2. On server: Press Windows + R → type services.msc → Enter
  3. Find "Sage 50 Actian Database Engine" service
  4. Right-click → Restart (wait 30 seconds for full restart)
  5. Find "Sage 50 Session Manager" service
  6. Right-click → Restart
  7. Close Services window
  8. On server: Open Sage 50 → Open company file
  9. On workstations: Open Sage 50 → Open company file from network path
  10. If error persists: Server → Tools → Session Manager → Clear all orphaned sessions
  11. Try connecting workstations again

Detailed Solution Steps

  • 1
    Verify All Users Are Logged Out

    Ensure no one is accessing the company file:

    1. Contact all Sage 50 users to close the program
    2. On server, open Sage 50
    3. Go to Tools → Session Manager
    4. Review list of active users/sessions
    5. Look for orphaned sessions (users who force-quit or crashed)
    6. Select orphaned sessions → Click "Clear Session"
    7. Close Session Manager
    8. Close Sage 50 on server
    9. Verify all workstations have Sage 50 completely closed

    Orphaned Sessions

    Orphaned sessions occur when Sage 50 crashes, computers lose power, or users force-quit without proper logout. These "ghost" sessions lock the company file and prevent new connections, causing Error 3110.
  • 2
    Restart Actian Database Services on Server

    Restart the database engine that handles multi-user connections:

    1. On server, press Windows + R
    2. Type: services.msc
    3. Press Enter to open Services
    4. Scroll to find these Sage services:
    5. Sage 50 Actian Database Engine
    6. Sage 50 Session Manager
    7. Sage 50 Session Manager Proxy (if present)
    8. Right-click "Sage 50 Actian Database Engine" → Restart
    9. Wait 30 seconds for service to fully restart
    10. Right-click "Sage 50 Session Manager" → Restart
    11. Wait 30 seconds
    12. If "Sage 50 Session Manager Proxy" exists → Restart it too
    13. Verify all three services show "Running" status
    14. Close Services window

    Service Startup Type:

    All Sage services should be set to "Automatic" startup type
    Right-click service → Properties → Startup type: Automatic → Apply → OK
    This ensures services start automatically after server reboots
  • 3
    Configure Windows Firewall Exceptions

    Ensure firewall allows Sage 50 network communication:

    1. On server, open Windows Defender Firewall
    2. Click "Advanced settings" (opens Windows Firewall with Advanced Security)
    3. Click "Inbound Rules" in left pane
    4. Look for existing Sage 50 rules (may be created during installation)
    5. If no Sage rules exist, create new rule:
    6. Click "New Rule" in right pane
    7. Select "Port" → Next
    8. Select "TCP" → Specific local ports: 1583
    9. Next → Allow the connection → Next
    10. Check all profiles (Domain, Private, Public) → Next
    11. Name: "Sage 50 Actian Database" → Finish
    12. Repeat to create UDP rule for port 1583
    13. Also allow these Sage programs through firewall:
    14. C:\Program Files (x86)\Sage\Sage 50 [Edition]\PeachtreeAccounting.exe
    15. C:\Program Files (x86)\Common Files\Actian\PSQL\bin\w3dbsmgr.exe
    Sage 50 Network Ports
    Port 1583: Actian database communication (TCP/UDP)
    Port 3389: Remote Desktop (if using RDP)
    SMB Ports: 445, 139 (file sharing - usually open by default)
  • 4
    Update Server Name Configuration in Sage 50

    Ensure workstations use correct server name:

    1. On server, determine correct server name:
    2. Right-click "This PC" or "Computer" → Properties
    3. Note the "Computer name" (e.g., SAGESERVER)
    4. On each workstation:
    5. Open Sage 50
    6. Click "Open an existing company"
    7. In "Open Company" window, click "Browse"
    8. In location bar, type: \\SERVERNAME\SharedFolder
    9. Replace SERVERNAME with actual server computer name
    10. Navigate to company file folder
    11. Select company file (.SAJ or .SAI file)
    12. Click "Open"
    13. Sage 50 saves this network path for future use
    14. Repeat for all workstations

    Avoid Using IP Addresses: Always use the server computer name (e.g., \\SAGESERVER) instead of IP address (e.g., \\192.168.1.10). Server names resolve correctly even if IP changes via DHCP.

  • 5
    Verify Network Folder Permissions

    Ensure all users have proper access rights to company file folder:

    1. On server, navigate to Sage 50 company file folder
    2. Typical location: C:\Sage\Sage 50 [Edition]\Company
    3. Right-click the folder → Properties
    4. Go to "Sharing" tab
    5. Click "Advanced Sharing"
    6. Check "Share this folder"
    7. Note the share name (e.g., "Company" or "Sage50Data")
    8. Click "Permissions" button
    9. Ensure "Everyone" or specific user group has "Full Control"
    10. Click OK to close Sharing Permissions
    11. Go to "Security" tab
    12. Click "Edit" button
    13. Ensure all Sage users have "Full Control" permissions
    14. If user/group missing, click "Add" → Add users → Grant Full Control
    15. Click OK → Apply → OK to save changes

    Why Full Control?

    Sage 50 requires Full Control permissions to create temporary lock files (.LCK), transaction logs, and index files during multi-user operations. "Modify" or "Read/Write" permissions are insufficient.
  • 6
    Clear Session Manager and Test Connection

    Remove any remaining locked sessions and verify connectivity:

    1. On server, open Sage 50
    2. Go to Tools → Session Manager
    3. If any sessions show in the list:
    4. Select each session
    5. Click "Clear Session" button
    6. Confirm clearing
    7. Continue until session list is empty
    8. Close Session Manager
    9. Open your company file on server
    10. Should open without errors
    11. On workstation #1: Open Sage 50
    12. Open company file using network path (\\SERVERNAME\...)
    13. Should connect successfully
    14. On server: Tools → Session Manager
    15. Verify workstation appears in session list
    16. Test additional workstations
  • 7
    Repair Actian Database Engine (If Error Persists)

    Reinstall Actian database components if services fail:

    1. On server, close all Sage 50 instances
    2. Press Windows + R → appwiz.cpl → Enter
    3. Opens Programs and Features
    4. Find "Actian PSQL [version]" in program list
    5. Right-click → Change or Repair
    6. Select "Repair" option
    7. Follow repair wizard prompts
    8. Restart server when repair completes
    9. After restart, verify Actian services are running
    10. Open Sage 50 and test multi-user connection

    Alternative Method: Download and run Sage 50 Database Manager from Sage's website. This utility can repair Actian installation without full reinstall.

  • 8
    Update Sage 50 to Latest Version

    Ensure all installations have latest patches:

    1. On server and all workstations:
    2. Open Sage 50
    3. Go to Help → About Sage 50
    4. Note current version number
    5. Close Sage 50
    6. Visit Sage website or use Sage Knowledgebase
    7. Download latest update/service pack for your version
    8. Run update installer as Administrator
    9. Follow installation prompts
    10. Restart computer after update completes
    11. Repeat on all computers (server first, then workstations)
    12. Verify all computers are on same version number
    13. Test multi-user connection after all updates

    • Why Does Error 3110 Occur?

    Root Causes

    • Actian Service Stopped: Sage 50 Actian Database Engine service crashed or failed to start after Windows updates or server restart
    • Orphaned User Sessions: Previous Sage 50 sessions didn't close properly (crashes, power loss, force quit), leaving lock files preventing new connections
    • Firewall Blocking Port 1583: Windows Firewall or third-party firewall blocking TCP/UDP port 1583 used for Actian database communication
    • Network Path Configuration: Workstations using incorrect server name, IP address instead of computer name, or outdated mapped drive letters
    • Permission Issues: Windows user accounts lack Full Control permissions on company file folder, preventing lock file creation
    • Corrupted Actian Installation: Database engine files damaged by antivirus quarantine, disk errors, or incomplete installation
    • Network Communication Failure: Router/switch issues, network cable problems, or subnet misconfiguration preventing server-workstation communication
    • Version Mismatch: Server and workstations running different Sage 50 versions or service pack levels, causing protocol incompatibility

    How to Prevent Error 3110

    Best Practices:

    • Set all Sage services to "Automatic" startup in Windows Services to survive reboots
    • Configure firewall exceptions during initial Sage 50 installation, not after errors occur
    • Always close Sage 50 properly using File → Exit - never force quit or shut down with Sage open
    • Keep all Sage 50 installations updated to the same version across server and workstations
    • Use UPS backup power for server to prevent abrupt shutdowns that create orphaned sessions
    • Exclude Sage 50 and Actian folders from antivirus real-time scanning to prevent file locks

    Frequently Asked Questions

    What is the Actian database engine and why does Sage 50 use it?

    Actian PSQL (formerly Pervasive SQL) is a high-performance database engine that Sage 50 uses to manage company files in multi-user environments. It handles concurrent access, transaction locking, and data integrity when multiple users work simultaneously. Actian runs as a Windows service on the server and allows workstations to read/write accounting data through network connections on port 1583.

    Can I work in single-user mode to avoid Error 3110?

    Yes, you can temporarily work in single-user mode by opening the company file directly on the server without multi-user access. However, this prevents other users from accessing the file simultaneously. Single-user mode is a temporary workaround while you troubleshoot Error 3110, but you should fix the multi-user connectivity to restore normal collaborative access.

    Error 3110 appeared after Windows Update - what happened?

    Windows Updates sometimes reset firewall rules, change network adapter settings, or prevent Actian services from auto-starting. After major Windows updates, verify that Sage 50 firewall exceptions still exist, Actian services are running, and service startup type is set to "Automatic". Windows Updates can also create orphaned sessions if users were logged in when the update forced a restart.

    Should I use the server's computer name or IP address in workstation setup?

    Always use the server's computer name (e.g., \\SAGESERVER\Company) rather than IP address (e.g., \\192.168.1.10\Company). Computer names are resolved through DNS/NetBIOS and work correctly even if the server's IP changes via DHCP. IP addresses can change and break connections, especially in networks without static IP assignments. Using the computer name provides more reliable, maintenance-free connectivity.

    Related Resources

    Sage Error 54 Solution

    Fix file corruption errors

    Remote Data Access Failure

    Fix remote connection issues

    Cloud Sync Connectivity

    Fix cloud synchronization errors

    Multi-User Setup Guide

    Complete network configuration

    Need Professional Help?

    If you're still experiencing Error 3110 after following these steps, or need help with Sage 50 multi-user configuration, Actian database repair, or network setup, our Sage specialists are here to help.

    Get Expert Support