Elliott Startup Btrieve Error 196 or 3012 on S/M Users File

Elliott Startup Btrieve Error 196 or 3012 on S/M Users File

Release Date: 11/16/2022
Version: 8.5 & Up

Q - I try to access Elliott software and I get this error on my startup:
    EL860CC: Btrieve Error 196 on S/M Users File (32-Bit)
If I click on the "Details," I see the status code 3012 when I try to access C:\Users\Administrators\AppData... See sample screen below:


A - The C:\Users\Administrator\AppData... folder is the Elliott run local folder. Elliott is trying to access the SM Users File from your run local folder and hence the error. The likely reason for this is because the mapped network drive disappeared. Go to Windows Explorer and see if your Elliott mapped drive is still available.  If not, you should try to remap it to the following format:
    M: = \\Server\Share
See the KB article https://support.netcellent.com/portal/en/kb/articles/elliott-8-6-installation-directory-structures and look for the Map Drive section for details. 

Below is the explanation of Status Code 3012 from the following KB article:

https://support.netcellent.com/portal/en/kb/articles/btrieve-error-codes-3000-3099

3012: Local engine is not accessible to the MicroKernel router

Access to the local engine is not possible because it is not loaded or could not be launched. You can receive this status code if you try to access a local file on a client and you do not have a Workgroup engine installed or if you try to access a local file on a server and the server engine is not running.

If you have only a server engine installed and your Pervasive Event Log (PVSW.LOG) contains Status Code 3012 warning entries, perform the following steps:

To Turn Off Local Engine support (for clients and workstations only):

  1. Start Pervasive PSQL Control Center (see "Starting PCC on Windows" on page 3-3 in Pervasive PSQL User's Guide).
  2. Expand Local Client. Right-click MicroKernel Router and select Properties. Login if prompted.
  3. Click Access.
  4. In the right-hand frame, change the value of Use Local MicroKernel Engine to Off.
  5. In the right-hand frame, change the value of Use Remote MicroKernel Engine to On. Click OK.
  6. Restart the engines for the new settings to take effect.
To put it in layman terms, Elliott is trying to access a data file in the local C:\Users\Administrator\AppData... folder (because the mapped network drive is lost).  Since you only have the PSQL client and not the PSQL engine install on your workstation, you receive the error "Local engine is not accessible to the MicroKernel router."  MicroKernel is another name for Btrieve.



EMK


    • Related Articles

    • Btrieve Error 46 on S/M Activity Log File

      Last Update: 06/20/2024 Q - I receive the following error message when I start up Elliott and launch a session: Btrieve Error 046 on S/M Activity Log File But this only happens to company 1. When I access another company, I do not receive this ...
    • EL850US: Btrieve Error 094 on USERS SY Users Lic. File

      Release Date: 02/18/2019 Q - I just implemented Elliott on a Windows 2019 server, when I started up Elliott for the first time, I received the following message: EL850US: Btrieve Error 094 on USERS SY Users Lic. File 94: The application encountered a ...
    • Btrieve Error Codes 001 - 199

      MicroKernel (Btrieve) Database Engine Status Codes This section describes status codes that the MicroKernel returns. All status codes are provided in 3-digit formats since the search on this website cannot search 1 or 2-digit words correctly. That is ...
    • Symantec Endpoint Protection Versions 12 and 14 Cause Elliott Startup Error

      Release Date: 05/15/2017 Overview There are some Elliott users who reported between 5/12/17 and 5/15/17 that using the latest anti-virus definition update of Symantec Endpoint Protection Versions 12 and 14 caused an Elliott startup error. The problem ...
    • Btrieve Error USE on COP Lock File

      Q - Today, for whatever reason, we experienced a large amount of locking issues in the warehouse. Several times today we ran into the problem with printing invoices where we received a message "Btrieve Error USE on COP Lock File," and it stops ...