Results 1 to 3 of 3
  1. #1
    Join Date
    Jun 2004
    Posts
    2

    Unanswered: Pervasive SQL 2000 (7.5) error 8020

    Hi

    I'm currently upgrading a windows nt computer to a windows xp one which has visual accouting set up for worksation access with the help of pervasive 7.5

    I have upgraded the system succelfully but whenever I start the application I get an error of a missing dll (Wbtrv32.dll). After putting said dll in the visual accounting directory (from the pvsw directory) the application boots up but gives me an error code 8020. As I understand it, this code is usually because there are missing dll in the windows system folder so I would be wondering which ones those were and in what directory I should put them into for an english windows xp pro install upgraded from an nt 4 install.

    I don't have the files needed to reinstall the workstation server either as the people who installed the sotware back then didn't leave the install files behind but only the files for a normal client install.

    Thanks in advance for any replies.

  2. #2
    Join Date
    Dec 2001
    Posts
    1,109
    Provided Answers: 4
    First off, Pervasive v7.5 is very old. You really should path to v7.94 (the last version of the Pervasive.SQL 2000 line). Secondly, I would suggest reinstalling. If you update to 7.94, that will take care of the reinstall.
    You can look in the PVSW.LOG to see what component is missing.
    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
    Jun 2004
    Posts
    2
    I'll try and find the update package to see if updating would solve the issue.

    But the application is pretty old too though so the fact that we're using an old version doesn't change much I think.

    However, I suppose I would also need to upgrade the other worksations to he latest service pack releases as well ?

    Also, I have pasted down below the latest excerpts of the pvsw.log

    06-03-2004 15:55:46 W3COMSRV 00000748 n\W3dbsmgr.exe" SRVNT_2 E WinSock socket() error=10047.
    06-03-2004 15:55:46 W3MKDE 00000748 n\W3dbsmgr.exe" SRVNT_2 I Error initializing the SPX protocol. Error code: 11.
    06-03-2004 15:55:47 W3COMSRV 00000748 n\W3dbsmgr.exe" SRVNT_2 E WinSock socket() error=10022.
    06-03-2004 15:55:47 W3COMSRV 00000748 n\W3dbsmgr.exe" SRVNT_2 E WinSock socket() error=10022.
    06-03-2004 20:40:24 W3COMSRV 000000D8 n\W3dbsmgr.exe" SRVNT_2 E WinSock socket() error=10047.
    06-03-2004 20:40:25 W3MKDE 000000D8 n\W3dbsmgr.exe" SRVNT_2 I Error initializing the SPX protocol. Error code: 11.
    06-03-2004 20:40:25 W3COMSRV 000000D8 n\W3dbsmgr.exe" SRVNT_2 E WinSock socket() error=10022.
    06-03-2004 20:40:25 W3COMSRV 000000D8 n\W3dbsmgr.exe" SRVNT_2 E WinSock socket() error=10022.
    06-03-2004 20:48:20 W3COMSRV 00000170 n\W3dbsmgr.exe" SRVNT_2 E WinSock socket() error=10047.
    06-03-2004 20:48:20 W3MKDE 00000170 n\W3dbsmgr.exe" SRVNT_2 I Error initializing the SPX protocol. Error code: 11.
    06-03-2004 20:48:20 W3COMSRV 00000170 n\W3dbsmgr.exe" SRVNT_2 E WinSock socket() error=10022.
    06-03-2004 20:48:20 W3COMSRV 00000170 n\W3dbsmgr.exe" SRVNT_2 E WinSock socket() error=10022.
    06-04-2004 15:12:45 W3COMSRV 00000798 n\W3dbsmgr.exe" SRVNT_2 E WinSock socket() error=10047.
    06-04-2004 15:12:45 W3MKDE 00000798 n\W3dbsmgr.exe" SRVNT_2 I Error initializing the SPX protocol. Error code: 11.
    06-04-2004 15:12:45 W3COMSRV 00000798 n\W3dbsmgr.exe" SRVNT_2 E WinSock socket() error=10022.
    06-04-2004 15:12:45 W3COMSRV 00000798 n\W3dbsmgr.exe" SRVNT_2 E WinSock socket() error=10022.

    looking back at older entries of the log when the software was working all errors seem normal (they occured when it was working fine).

Posting Permissions

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