Pervasive Database Pre-Load (Not Starting even though in Startup Menu)

SUGGESTED

We installed Estimating 13.1 two weeks ago and are now experiencing some problems with the Pervasive Database Pre-Load not starting up when the computer starts.  We have verified that the Pervasive Pre-Load is in the Start Menu and have done a reinstallation on one of the machines.  We usually discover the problem when the user goes in to open estimating and it will give a I\O error, we have tried stopping the Pervasive Pre-Load and re-starting it, but the machine will not allow this action as it says "it is already running".  Our temporary solution has been to reboot the computer and then immediately go in and Start the Pervasive Database Pre-Load.  If we do this then Estimating will work correctly.  Curious if others are having this problem and whether they have discovered a solution.  Additional information, we are experiencing this issue on 5-6 machines.  Thank you  

  • 0

    Thank you for your post Shane!

    This is definitely not typical behavior of the Pervasive Database. We need to get more information to accurately assess what is going on and diagnose the issue. I will message you my contact information and will await your email.

  • 0

    We upgraded Sage 300 CRE Accounting from 9.7 to 13.1 a month ago and are also experiencing problems with the Pervasive Pre-Load not always starting up when PCs are restarted.  Sometimes it starts and sometimes it doesn't.  The problem seems to wander around the Payroll office cubes.  We are at Update 5 (2013 year end upate).  We know that Update 5 incorporates 'critical patching for Pervasive Licensing' in Update 1.  Puzzlingly, we also get occasional repetition of the 'key activation' messages from the Pervasive Notification Viewer.

    This morning, I responded to a help request from our Payroll Chief on Pre-Load launch failure at her PC.  While investigating, after a reboot and not seeing the blue-green Pervasive Database - Pre-Load icon on the task bar, I ran Task Manager where I found McAfee on-access security scanner and w3dbsmgr.exe both gobbling CPU without end, until I rebooted again.  

    We have long known that the server side processes of Pervasive DB tend to spin the CPU after virus scanning of the DB, but this is first time we've detected what may be conflict between PC antivirus and Pervasive.

  • 0 in reply to RobertDS

    Have you followed the documentation regarding directory exclusions for your anti-virus app?

  • 0
    SUGGESTED

    Hello Shane, when reinstalling Pervasive you may want to try installing it as a service from the prerequisites folder. Before the reinstall you should delete all leftover relevant folders and registry keys.

    For uninstalling -

    Make sure all users are out of Sage if you are uninstalling on the server.

    Go to Programs and Features, uninstall Pervasive

    Delete these folders if they didn't already uninstall:

    C:\ProgramData\Pervasive Software

    C:\Program Files (x86)\Pervasive Software

    Go to Regedit.exe and check for a left over Pervasive registry key in this location and delete it: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Pervasive Software

    To reinstall as a service (and you may want to go with the server install as a service on the workstaiton estimating sometimes prefers that, it runs fine as it would on the server)

    For a Sage 300 CRE workstation on a non-server operating system such as Windows 7 (32-bit or 64-bit), install the PSQL v11 Workgroup Engine

    1.Pre PSQL Install

    2.PrePSQLInstall.exe

    3.Runs silently, you will not be able to see when it completes but you can monitor in Task Manager

    4.Pervasive PSQL v11 Workgroup as Service

    5.SetupWorkgroup_x86.exe

    6. Select Run as Service

    7. Pervasive PSQL v11 Workgroup Patch (x86)

    8. PSQLv11Patch_WGE_x86.msp

    9. Post PSQL Install

    10. PostPSQLInstall.exe

    11. Runs silently, you will not be able to see when it completes but you can monitor in Task Manager

    For a Sage 300 CRE file server, such as Windows 2008 R2 (32-bit) or any 32-bit computer with Sage Estimating (regardless of operating system), install the Pervasive PSQL v11 Server Edition (x86)

    1.Pre PSQL Install

    2.PrePSQLInstall.exe

    3. Runs silently, you will not be able to see when it completes but you can monitor in Task Manager

    4. Pervasive PSQL v11 Server Edition (x86)

    5. SetupServer_x86.exe

    6. Pervasive PSQL v11 Server Patch (x86)

    7. PSQLv11Patch_Server_x86.msp

    8. Post PSQL Install

    9. PostPSQLInstall.exe

    10. Runs silently, you will not be able to see when it completes but you can monitor in Task Manager

    For a Sage 300 CRE file server, such as Windows 2008 R2 (64-bit) or any 64-bit computer with Sage

    Estimating (regardless of operating system), install the Pervasive PSQL v11 Server Edition (x64)