Goldstar Logo
Your Source for PSQL Database Products, Services and Training Since 1997 EMail: 
Phone: 1-708-647-7665 
Web Site Login 
Free PSQL Support
Quick Links
Database Engines
+ Actian Zen v14
+ Actian Zen/PSQL v13
+ Actian PSQL v12
+ Actian PSQL v11
+ Pervasive PSQL v10
+ Pervasive PSQL v9
+ Pervasive.SQL V8
+ Pervasive.SQL 2000i
+ Pervasive.SQL 7
+ Btrieve 12
+ Btrieve 6.15
+ Actian Vector
+ Actian Zen Edge/Core

+ Data Protection Products

+ Goldstar Software Services

+ Goldstar Software Tools

+ Other Solutions

AMS Users: Click Me Fix My PSQL License Repair PSQL Files Get Support Now Join Our Mailing List

Navigation Background

White Papers About Pervasive Errors and Status Codes

By: Bill Bach

The Pervasive Database engine can return hundreds of different "Btrieve Status Codes" under normal operations. Many of these status codes are indicators to the application developer, such as "0: Success", "4: Record Not Found", and "9: End of File". A good developer will handle these status code values in their code, displaying a useful error message where appropriate.

Other status codes, however, can be returned when unusual situations arise, and these are often not handled by the application. (These are more akin to true "error codes".) Instead, the application may spit out the raw status code number to the screen in a message like "Btrieve Status 2", making it very difficult to know exactly what to do to fix it.

Of course, all of the Status Codes are documented in the Pervasive manuals, but sometimes you just need to do a quick lookup. You can find our Status Code Lookup tool on our Mobile web site, optimized for fast access from your smart phone. Point your phone or browser to to get started now!

The documents on this page contain some of the more common status or error codes, along with some suggestions on how to fix them. Of course, Goldstar Software also provides support for the Pervasive database products, and if these instructions get a bit too technical for you, then give us a call and (for a small fee) we can help get your system up and running again fast!


Status Code Information
Having problems with Status 46 (Unable to Write to File) messages coming back from your application, causing users to lose database changes? This paper can help! (Updated January 2007)
Many sites fight the dreaded Status 94 (Permission Denied) and cannot figure out how to get around it. This document reviews the primary causes of Status 94 errors with Btrieve and Pervasive.SQL.
Are you plagued by chronic Status 95 (Lost connection) problems? This FAQ list details the primary causes and provides some relief!
Pervasive returns a Status 161 to indicate that you have exceeded your license count. This paper explains how to verify your license and address the most common issues! (Updated March 2010) If you need more licenses for your environment, contact us today!
If you just installed Pervasive.SQL V8 or newer onto a system running Pervasive.SQL 7 and you are getting a Status 2009 when starting the application, here's how to fix it!
3111, 3112
Pervasive split the older Status 95 (Lost Connection) into two status codes, 3111 (Failure During Send to Server) and 3112 (Failure During Receive from Server). This FAQ list details the primary causes and how to fix them.
If you just installed Pervasive.SQL V8.5 or newer onto a system and you are now getting a Status 8013 when starting the application, here's how to fix it!

PDFAccessing Status Codes From Applications
Are you a developer that wants a way to access status code information directly from within your application? Check out this concept! (Updated May 2009)

Can't open the PDF files? Please visit for a free download of Adobe Acrobat Reader.

  Copyright © 1997-2019, Goldstar Software Inc., All rights reserved. PRODUCTS | SERVICES | TRAINING | SUPPORT | DOWNLOADS | ABOUT US  
Goldstar Software Inc. | 3007 Carmel Dr | Flossmoor IL 60422 Legal Statements | EULAs | Uninstall | Privacy Statements | Contact Us