Error: 3012 (Local engine is not accessible to the MicroKernel router)

From Agency Systems Wiki
Jump to: navigation, search
Related Pages
Related Categories

For each of the steps below, the machine which hosts the Newton database will be referred to as a server, even if the office only uses a workgroup engine with 5 or less users.

Contents

Scope of the Problem

You receive the error message Error 3012 (Local engine is not accessible to the MicroKernel router) opening [S:\Empire\programs\EMPFILES.NDX] opening Newton by Agency Systems.

Fatal-error-3012.png

The server may have been recently restarted due to Microsoft Windows updates, power failure, or a network configuration change such as a new router.

Resolution

Before You Begin

If the error only occurs on a single workstation which is not the server, verify the shortcut and network connection are working.

Step 1: Verify the Pervasive Database Service is Running

If the error occurs on multiple workstations, first try restarting the server. If that does not work, review the steps below.

  1. Log into the desktop of the server, either remotely or directly with a keyboard and mouse.
  2. Press Windows Key + R. (For Windows 8/10 or Server 2012/2016, optionally right-click on the Windows Start Button and select Run).
  3. Type services.msc
    Services-run.png
  4. Select Ok.
  5. Scroll down to the letter P and look for Pervasive PSQL ....... Verify each of the Pervasive services are listed at Status: Running.
    • For offices with less than five users, find Pervasive PSQL Workgroup Engine.
      Services-psqlwge.png
    • For offices with more than five users, find Pervasive PSQL Relational Engine and Pervasive PSQL Transactional Engine.
      Services-psqlserver.png
    • Notes for Pervasive V12:
      For offices with five or less users, Pervasive will be listed as Actian PSQL Workgroup Engine.
      For offices with more than five users using Pervasive 12, find Actian PSQL Relational Engine and Actian PSQL Transactional Engine.
      Services-actianpsqlserver.png
  6. If the Status is not Running, select Start the Service. (If the service fails to start, contact Agency Systems Support).
  7. Wait for the service start. If both services are listed, start the Relational Engine first, followed by the Transactional Engine.
  8. Test Newton to see if the 3012 error is fixed.

If the service was already running, or if starting the service did not fix the error, see the next section below.

Step 2: Verify the Windows Network Type is Not Public

  1. Log into the desktop of the server, either remotely or directly with a keyboard and mouse.
  2. In the Microsoft Windows system tray next to the clock, find the network connections icon.
  3. Right-Click and select Open Network and Sharing Center. (Optionally use start search and enter "Network and Sharing Center".)
    Network-rightclick-networkandsharing.png
  4. Find the View your active networks section.
  5. If the listed network is configured as Public follow the steps below. If the network is configured as Work, or Domain network, skip to the next section below.
  6. Left-Click the link text Public Network.
    Network-public.png
  7. Select Work Network.
    Network-select-work.png
  8. Verify the listed network is now configured as Work.
  9. Test Newton to see if the 3012 error is fixed.

If the error still occurs, see the next section below.

Step 3: Verify Antivirus Software Exceptions

  1. Log into the desktop of the server, either remotely or directly with a keyboard and mouse.
  2. Open the installed Antivirus Software.
  3. Temporarily disable any antivirus protection, specifically anything mentioning a firewall or intrusion prevention.
  4. Test Newton to see if the 3012 error is fixed. If the error is fixed, see Installation Environment and Network Requirements for exception instructions.

If the error still occurs, see the next section below.

Step 4: Restart Entire Network

  1. Shut down the server.
  2. Shut down the workstations.
  3. Unplug the router.
  4. Unplug any network switches.
  5. Plug in the router and wait 30 seconds.
  6. Plug in any network switches.
  7. Start the server, and wait for it to fully boot.
  8. Start the workstations.
  9. Verify the workstations can access the network share on the server.
  10. Test Newton to see if the 3012 error is fixed.

If the error still occurs, contact Agency Systems Support.