Results 1 to 6 of 6
  1. #1
    Join Date
    Aug 2006
    Posts
    4

    Angry Unanswered: Pervasive Error/Crash Problem

    I'm running Pervasive 2000i on a W2K3 server. We have a local intranet web site that we use to retrieve data from the database. There are at most about 10-15 people who use it regularly throughout the day. The intranet site is a VB.NET application that hits the database through ODBC.

    More and more frequently, we get an Application Error in the event log:

    "Faulting application NTDBSMGR.EXE. version 7.94.251.3, faulting module W3SQLMGR.DLL, version 7.94.251.2, fault address 0x0001ee07."

    The intranet site locks up and I have to stop and restart the PSQL services to get it running again.

    This is happening more and more frequently, and it's really frustrating.

    Any ideas why this might be happening?

  2. #2
    Join Date
    Dec 2001
    Posts
    1,109
    Provided Answers: 4
    What's occurring when the crash occurs? Is it the same SQL statement? You mention that this is "happening more and more frequently," when did it start and what's changed that might contribute to it's frequency?
    Is there anything in the PVSW.LOG?
    Have you considered upgrading to V9? It's the current version and is supported by PVSW. If the crash still occurs, you can call them and ask them what's causing it.
    Mirtheil Software
    Certified Pervasive Developer
    Certified Pervasive Technician
    Custom Btrieve/VB development
    http://www.mirtheil.com
    I do not answer questions by email. Please post on the forum.

  3. #3
    Join Date
    Aug 2006
    Posts
    4
    The pervasive database is the back end for our Great Plains system. We have created a small VB.NET intranet site that we use to update certain tables in Great Plains.

    I'm not exactly sure what's happening when the crash occurs. Our intranet site reads and writes to a bunch of different tables. I don't know how I could figure out exactly which SQL statement was being executed because there are 10-15 people that are actively updating it all day long.

    Right after the crash happens, if I look at the PVSW.LOG file, I can see a few different lines where it's saying that a .BTR file is rolling back, followed by one or two lines where it says the log file is corrupt.

    I don't know if we can upgrade to V9. That might have to be done as part of an upgrade to our Great Plains system.

  4. #4
    Join Date
    Dec 2001
    Posts
    1,109
    Provided Answers: 4
    Please post your PVSW.LOG, specifically around the time of a crash. If files are "rolling back", you might have some corruption and need to rebuild the files.
    Mirtheil Software
    Certified Pervasive Developer
    Certified Pervasive Technician
    Custom Btrieve/VB development
    http://www.mirtheil.com
    I do not answer questions by email. Please post on the forum.

  5. #5
    Join Date
    Aug 2006
    Posts
    4
    Here's today's portion of the PVSW.LOG file:

    08-14-2006 04:56:53 NTMKDE 000006E8 NTDBSMGR.EXE LMSSQL01 I Resources allocated
    08-14-2006 12:53:08 NTMKDE 00000954 NTDBSMGR.EXE LMSSQL01 I Resources allocated
    08-14-2006 12:56:03 NTMKDE 00000954 NTDBSMGR.EXE LMSSQL01 I The file D:\LMSPROD\SERVICE\SV00300.BTR is rolling back.
    08-14-2006 12:56:03 NTMKDE 00000954 NTDBSMGR.EXE LMSSQL01 W The log file is corrupt.


    08-14-2006 12:56:39 NTMKDE 00000954 NTDBSMGR.EXE LMSSQL01 I The file D:\LMSPROD\CALLNOTES.MKD is rolling back.
    08-14-2006 12:56:41 NTMKDE 00000954 NTDBSMGR.EXE LMSSQL01 W The log file is corrupt.


    08-14-2006 12:57:44 NTMKDE 00000954 NTDBSMGR.EXE LMSSQL01 W The log file is corrupt.


    08-14-2006 12:57:48 NTMKDE 00000954 NTDBSMGR.EXE LMSSQL01 W The log file is corrupt.


    08-14-2006 12:58:50 NTMKDE 00000954 NTDBSMGR.EXE LMSSQL01 I The file D:\LMSPROD\SERVICE\SV00340.BTR is rolling back.
    08-14-2006 12:58:51 NTMKDE 00000954 NTDBSMGR.EXE LMSSQL01 W The log file is corrupt.


    08-14-2006 13:36:35 NTMKDE 00000AA8 NTDBSMGR.EXE LMSSQL01 I Resources allocated
    08-14-2006 13:37:58 NTMKDE 000003B8 NTDBSMGR.EXE LMSSQL01 I Resources allocated
    08-14-2006 13:39:21 NTMKDE 000003B8 NTDBSMGR.EXE LMSSQL01 I The file D:\LMSPROD\CALLNOTES.MKD is rolling back.
    08-14-2006 13:39:23 NTMKDE 000003B8 NTDBSMGR.EXE LMSSQL01 W The log file is corrupt.


    08-14-2006 13:41:11 NTMKDE 000003B8 NTDBSMGR.EXE LMSSQL01 I The file D:\LMSPROD\SERVICE\SV00340.BTR is rolling back.
    08-14-2006 13:41:13 NTMKDE 000003B8 NTDBSMGR.EXE LMSSQL01 W The log file is corrupt.


    08-14-2006 13:48:30 NTMKDE 00000630 NTDBSMGR.EXE LMSSQL01 I Resources allocated
    08-14-2006 13:51:29 NTMKDE 00000630 NTDBSMGR.EXE LMSSQL01 I The file D:\LMSPROD\SYSTEM\ACTIVITY.BTR is rolling back.
    08-14-2006 13:51:29 NTMKDE 00000630 NTDBSMGR.EXE LMSSQL01 W The log file is corrupt.


    08-14-2006 13:51:39 NTMKDE 00000630 NTDBSMGR.EXE LMSSQL01 W The log file is corrupt.


    08-14-2006 13:52:19 NTMKDE 00000630 NTDBSMGR.EXE LMSSQL01 W The log file is corrupt.


    08-14-2006 13:52:58 NTMKDE 00000630 NTDBSMGR.EXE LMSSQL01 I The file D:\LMSPROD\SERVICE\SV00519.BTR is rolling back.
    08-14-2006 13:53:26 NTMKDE 00000630 NTDBSMGR.EXE LMSSQL01 W The log file is corrupt.


    08-14-2006 13:58:14 NTMKDE 00000630 NTDBSMGR.EXE LMSSQL01 I The file D:\LMSPROD\SERVICE\SV00340.BTR is rolling back.
    08-14-2006 13:58:19 NTMKDE 00000630 NTDBSMGR.EXE LMSSQL01 W The log file is corrupt.

  6. #6
    Join Date
    Aug 2006
    Posts
    4
    Additionally, after reading some other posts, after the last crash I deleted the log files in the MKDE\LOG directory while the services were stopped.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •