Error: 1053: The service did not respond to the start or control request in a timely fashion. When restarting Pervasive Services

Error: 1053: The service did not respond to the start or control request in a timely fashion. When restarting Pervasive Services

Error:
Windows could not stop the Pervasive PSQL Relational Engine
1053: The service did not respond to the start or control request in a timely fashion.


Solution:
In Task Manager, on the Processes tab find DATABASE SERVICE MANAGER (32 bit) or
W3dbsmgr.exe Right click on the process and End task
Once this is complete restart the Pervasive services.
If the problem persists reboot the server.

    • Related Articles

    • Updating Pervasive

      All users will need to be logged out of FOS for Pervasive to be updated. Also, if users are accessing FOS using a shortcut on their computer once the version of Pervasive has been updated on the server the local machines will also need to update to ...

    • Error: Pervasive Database is already in use

      Error: Pervasive Database is already in use. Solution: If the FOS Database is not listed in the Pervasive Control Center, however the user receives an error that the database already exists when trying to create the database open the registry editor. ...

    • Error: The program can’t start because W3BTRV7.DLL is missing from your computer. Try reinstalling the program to fix this problem.

      Error: The program can’t start because W3BTRV7.DLL is missing from your computer. Try reinstalling the program to fix this problem. Solution: The workstation will need the 32-bit client version on Pervasive installed. If Pervasive is already ...

    • Extracting Data from FOS Pervasive Tables

      Installing Pervasive & Initial Information *If Pervasive is already installed on the machine, please skip to the next section (Extracting Data from the Pervasive Database)* Before beginning the extraction, you will need to download and install ...

    • Btrieve Error: Btrieve error 3006 userinfo: btrieve_status(Thread3524) (Thread 0)

      Error: Btrieve error 3006 userinfo: btrieve_status(Thread3524) (Thread 0) Solution: Btrieve error 3006 generally means the client machine and FOS server are not communicating. It is possible that there are hung sessions in Pervasive which may be ...