• Only happening at one workstation indicates that the problem is localized to this one system.
• Pervasive/Actian was prevented from starting and running due to User Account Control (UAC) Settings running at a strict level.
• Most often happens on the Windows 8/8.1/10 operating system.
• Terminal Server services does not have adequate permissions across the network.

• For versions 14.1 and older, verify that the Pervasive Pre-load or Pervasive Auto-load icon is not running in the bottom right corner near the computer's time and date. (It is possible the icon is hidden, click on the arrow pointing up for more icons of running applications. If Pervasive is not running:
  

1. Navigate to C:\Program Files (x86)\Pervasive Software\PSQL\bin to manually launch the program.
2. You will find w3dbsmgr.exe and right-click on the icon. Select Properties, Compatibility tab, check-mark Run This Program As An Administrator
3. Select Apply, OK
4. Launch w3dbsmgr.exe and verify the icon now shows in the system tray
5. Launch TS-Main, log in and verify log in completes successfully

• For versions 15.1 and later, verify that the Pervasive/Actian service is running.

1. Press the Windows key + R
2. Type in services.msc
3. For version 15.1, locate the Pervasive PSQL Workgroup service. For versions 16.1 and later, locate the Actian PSQL Workgroup service.
4. Check the status of the service. If it is blank, right click on the service and choose Start. If the status shows Running, right click on the service and choose Restart.
5. Try opening Sage again.
   

Note: On a Terminal Server/Windows 10 (or 15.1 and greater) Pervasive runs as a service:

1. Select Start, Control Panel, Administrative Tools, Services
2. Browse to find Pervasive/Actian PSQL Workgroup Engine
3. Right-click and select Properties, Log On tab
4. Select This Account:
5. Enter a domain administrator account user name and password
6. Select Apply, Ok, Ok
7. Restart the service
8. Launch TS-Main, log in and verify log in completes successfully