We help IT Professionals succeed at work.

Pervasive Database Engine is craching

Gerhardpet asked
I have a Pervasive SQL database where I'm trying to import data in to with Access using an ODBC connection.
When importing the pervasive service stops running and I get an error.

In the Applications events I have the following error
Log Name:      Application
Source:        Application Error
Date:          11/3/2011 3:47:45 PM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      Thor.Zena.Locksmith.Store
Faulting application name: w3dbsmgr.exe, version:, time stamp: 0x4b02dc72
Faulting module name: ntdll.dll, version: 6.1.7600.16695, time stamp: 0x4cc7ab86
Exception code: 0xc0000005
Fault offset: 0x0002e41b
Faulting process id: 0x414
Faulting application start time: 0x01cc9a68863e10d1
Faulting application path: C:\Program Files (x86)\Pervasive Software\PSQL\bin\w3dbsmgr.exe
Faulting module path: C:\Windows\SysWOW64\ntdll.dll
Report Id: 144ff375-065d-11e1-b274-782bcb43438f

Open in new window

Any ideas why this is happening?
Watch Question

President and Btrieve Guru
Unfortunately, there's not enough info in this error log to day for sure.

My first recommendation is to patch the PSQLv10 Workgroup engine to the latest release.  Update 17 is available from Pervasive's web site (www.pervasivedb.com), and will provide you with the latest and greatest code base.  Try that first & see if the problem goes away.

Second, verify that the DDF's match the underlying data files.  Start the DDF Builder, then right-click on the database you are importing to and select Check Database.  Verify that the tables you are accessing from MSAccess return no errors.  If they do, then fix the problems (may need to work with the app developer on this) first.

Beyond that, you may need to post your sample code and data.  Or, once you are patched, if the problem continues, logged a formal support incident with Pervasive support would be a good step.  If you can send them a core dump when the problem occurs, they can examine it and (hopefully) find a resolution for you before the product becomes unsupported on March 1.


Yep...installing the update fixed the problem. Thank you Bill!