Results 1 to 11 of 11
  1. #1
    Join Date
    May 2006
    Posts
    6

    Unanswered: PSQL 9.1 and Magic 9.3

    Anyone have any knowledge or experience running Pervasive SQL 9.1 and Magic 9.3 together ?
    We yust migrated our system from Btrv 6.15, and now all hell is loose with our magic system. From fatal errors to printing errors, the works.

  2. #2
    Join Date
    Dec 2001
    Posts
    1,109
    Provided Answers: 4
    First, how about a list of specific errors including specific Btrieve/Pervasive error codes?
    Second, did any of these problems crop up in testing or did you migrate your production application without testing?
    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
    May 2006
    Posts
    6
    Got none of these errors while using btrv 6.15. Getting error 3112, and the printing, it only prints the header, not the whole transaction requested.
    We didn't have time to test the stuff. Was on a VERY short deadline.

  4. #4
    Join Date
    Dec 2001
    Posts
    1,109
    Provided Answers: 4
    How's your PSQL set up? Is it client/server or WGE?
    The 3112 means:
    3112: Failure during receive from the target server
    The Pervasive Network Services Layer attempted to receive data from the target server and encountered a network specific error. Check the Pervasive Event Log (PVSW.LOG) for more information.
    You may receive this error when attempting to connect to a Workgroup engine on Windows 95 if the machine has not been upgraded to Winsock 2. If you are not running Winsock 2 on your Windows 95 computer with Workgroup engine installed, you should download the WinSock 2 update from Microsoft: http://www.microsoft.com/windows95/d...lt.asp?site=95.
    Note
    If there is a problem with AutoReconnect, a further status code 3131 will be issued.

    You may also receive this error under the following circumstances:
    When using only the NetBIOS protocol with a remote Workgroup engine, the client is sending more bytes than can fit into the engine's network read buffer. Go the machine where the remote Workgroup engine is installed, and try increasing the value of the configuration parameter, Server Communication Buffer Size Read Buffer Size.
    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
    May 2006
    Posts
    6
    It's a client/server setup. no Win95 machines though, running tcp/ip and ipx/spx for the novell server. Will increase these values and see wot it does.

  6. #6
    Join Date
    Dec 2001
    Posts
    1,109
    Provided Answers: 4
    Is there anything in the PVSW.LOG on the client or server?
    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.

  7. #7
    Join Date
    May 2006
    Posts
    6
    Nothing out of the ordinary that I can see. Wot exactly should I be looking for ?
    Most of the errors seem to have disappeared, although, when 2 users work on the same data, we get printing errors. We gave each user their own .ini file in wich to store their temp data. That sorted out a lot of stuff. Wot settings should one edit in on the server?

  8. #8
    Join Date
    Dec 2001
    Posts
    1,109
    Provided Answers: 4
    POst the Log. Sometimes things that don't look out of the ordinary are.
    What "printing errors"? Pervasive itself doesn't have any printing functions.
    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.

  9. #9
    Join Date
    May 2006
    Posts
    6
    Date Time Component Process Process Name Machine Name Type Category Msg ID Message
    ---------- -------- --------------- -------- --------------- --------------- ---- ---------- -------- --------------------------------------------------
    05-20-2006 09:15:05 MKDE 000009D0 NTDBSMGR.EXE SERVER I MicroKernel is using the default setting for Balanced Trees.
    05-20-2006 09:15:05 MKDE 000009D0 NTDBSMGR.EXE SERVER I MicroKernel is using the default setting for File Version.
    05-20-2006 09:15:05 MKDE 000009D0 NTDBSMGR.EXE SERVER I MicroKernel is using the default setting for System Data.
    05-20-2006 09:15:05 MKDE 000009D0 NTDBSMGR.EXE SERVER I MicroKernel is using the default setting for Max MicroKernel Memory Usage.
    05-20-2006 09:15:05 MKDE 000009D0 NTDBSMGR.EXE SERVER I MicroKernel is using the default setting for Logging.
    05-20-2006 09:15:05 MKDE 000009D0 NTDBSMGR.EXE SERVER I MicroKernel is using the default setting for Cache Size.
    05-20-2006 09:15:05 MKDE 000009D0 NTDBSMGR.EXE SERVER I MicroKernel is using the default setting for Merge Sort Buffer Size.
    05-20-2006 09:15:05 MKDE 000009D0 NTDBSMGR.EXE SERVER I MicroKernel is using the default setting for Transaction Durability.
    05-20-2006 09:15:05 MKDE 000009D0 NTDBSMGR.EXE SERVER I MicroKernel is using the default setting for Transaction Log Buffer Size.
    05-20-2006 09:15:05 MKDE 000009D0 NTDBSMGR.EXE SERVER I MicroKernel is using the default setting for Transaction Log File Size.
    05-20-2006 09:15:05 MKDE 000009D0 NTDBSMGR.EXE SERVER I MicroKernel is using the default setting for Systrans Bundle Limit.
    05-20-2006 09:15:05 MKDE 000009D0 NTDBSMGR.EXE SERVER I MicroKernel is using the default setting for Systrans Time Limit.
    05-20-2006 09:15:05 MKDE 000009D0 NTDBSMGR.EXE SERVER I MicroKernel is using the default setting for Transaction Logging.
    05-20-2006 09:15:05 MKDE 000009D0 NTDBSMGR.EXE SERVER I MicroKernel is using the default setting for Background Threads.
    05-20-2006 09:15:05 MKDE 000009D0 NTDBSMGR.EXE SERVER I MicroKernel is using the default setting for Wait-lock Timeout.
    05-20-2006 09:15:05 MKDE 000009D0 NTDBSMGR.EXE SERVER I MicroKernel is using the default setting for Transaction Log Directory.
    05-20-2006 09:15:05 MKDE 000009D0 NTDBSMGR.EXE SERVER I MicroKernel is using the default setting for Trace.
    05-20-2006 09:15:05 MKDE 000009D0 NTDBSMGR.EXE SERVER I MicroKernel is using the default setting for Trace File.
    05-20-2006 09:15:05 MKDE 000009D0 NTDBSMGR.EXE SERVER I MicroKernel is using the default setting for Trace Databuf Len.
    05-20-2006 09:15:05 MKDE 000009D0 NTDBSMGR.EXE SERVER I MicroKernel is using the default setting for Trace Keybuf Len.
    05-20-2006 09:15:05 MKDE 000009D0 NTDBSMGR.EXE SERVER I MicroKernel is using the default setting for Trace Ops.
    05-20-2006 09:15:05 MKDE 000009D0 NTDBSMGR.EXE SERVER I MicroKernel is using the default setting for Limit Segment Size to 2Gb.
    05-20-2006 09:15:05 MKDE 000009D0 NTDBSMGR.EXE SERVER I MicroKernel is using the default setting for File Growth Factor.
    05-20-2006 09:15:05 MKDE 000009D0 NTDBSMGR.EXE SERVER I MicroKernel is using the default setting for Prompt For Client Credentials.
    05-20-2006 09:15:05 MKDE 000009D0 NTDBSMGR.EXE SERVER I MicroKernel is using the default setting for Allow Client-Stored Credentials.
    05-20-2006 09:15:05 MKDE 000009D0 NTDBSMGR.EXE SERVER I MicroKernel is using the default setting for Enable Watchdog.
    05-20-2006 09:15:05 MKDE 000009D0 NTDBSMGR.EXE SERVER I MicroKernel is using the default setting for System Cache.
    05-20-2006 09:15:05 MKDE 000009D0 NTDBSMGR.EXE SERVER I MicroKernel is using the default setting for Preallocate.
    05-20-2006 09:15:05 MKDE 000009D0 NTDBSMGR.EXE SERVER I MicroKernel is using the default setting for Minimal States.
    05-20-2006 09:15:05 MKDE 000009D0 NTDBSMGR.EXE SERVER I MicroKernel is using the default setting for Minimal States Delay.
    05-20-2006 09:15:05 MKDE 000009D0 NTDBSMGR.EXE SERVER I MicroKernel is using the default setting for Worker Threads.
    05-20-2006 09:15:05 MKDE 000009D0 NTDBSMGR.EXE SERVER I MicroKernel is using the default setting for Remote Worker Threads.
    05-20-2006 09:15:05 MKDE 000009D0 NTDBSMGR.EXE SERVER I MicroKernel is using the default setting for Remote Sessions Enabled.
    05-20-2006 09:15:05 MKDE 000009D0 NTDBSMGR.EXE SERVER I MicroKernel is using the default setting for Supported Protocols.
    05-20-2006 09:15:05 MKDE 000009D0 NTDBSMGR.EXE SERVER I MicroKernel is using the default setting for Protocol Init Timeout.
    05-20-2006 09:15:05 MKDE 000009D0 NTDBSMGR.EXE SERVER I MicroKernel is using the default setting for TCPIP Multi-Homed.
    05-20-2006 09:15:05 MKDE 000009D0 NTDBSMGR.EXE SERVER I MicroKernel is using the default setting for Listen IP Address.
    05-20-2006 09:15:05 MKDE 000009D0 NTDBSMGR.EXE SERVER I MicroKernel is using the default setting for Home Directory.
    05-20-2006 09:15:05 MKDE 000009D0 NTDBSMGR.EXE SERVER I MicroKernel is using the default setting for Enable AutoReconnect.
    05-20-2006 09:15:05 MKDE 000009D0 NTDBSMGR.EXE SERVER I MicroKernel is using the default setting for AutoReconnect Timeout.
    05-20-2006 09:15:05 MKDE 000009D0 NTDBSMGR.EXE SERVER I MicroKernel is using the default setting for DBNamesDirectory.
    05-20-2006 09:15:06 MKDE 000009D0 NTDBSMGR.EXE SERVER I Error initializing the SPX protocol. Error code: 6.
    05-20-2006 09:15:11 MKDE 000009D0 NTDBSMGR.EXE SERVER W Resources allocated
    05-20-2006 09:19:44 MKDE 000009D0 NTDBSMGR.EXE SERVER I Resources released
    05-20-2006 09:21:52 MKDE 000003AC NTDBSMGR.EXE SERVER I Error initializing the SPX protocol. Error code: 6.
    05-20-2006 10:00:27 MKDE 000003AC NTDBSMGR.EXE SERVER W Resources allocated
    05-22-2006 14:56:55 MKDE 000003AC NTDBSMGR.EXE SERVER I Resources released
    05-22-2006 14:57:00 MKDE 00000490 NTDBSMGR.EXE SERVER I Error initializing the SPX protocol. Error code: 6.
    05-22-2006 14:57:03 MKDE 00000490 NTDBSMGR.EXE SERVER W Resources allocated
    05-22-2006 16:38:12 MKDE 00000490 NTDBSMGR.EXE SERVER I Resources released
    05-22-2006 16:38:15 MKDE 000004F8 NTDBSMGR.EXE SERVER I MicroKernel is using the default setting for Listen IP Address.
    05-22-2006 16:38:15 MKDE 000004F8 NTDBSMGR.EXE SERVER I Error initializing the SPX protocol. Error code: 6.
    05-22-2006 16:41:37 MKDE 000004F8 NTDBSMGR.EXE SERVER W Resources allocated
    05-22-2006 16:41:50 MKDE 000004F8 NTDBSMGR.EXE SERVER I Resources released
    05-22-2006 16:44:05 MKDE 000003E0 NTDBSMGR.EXE SERVER I Error initializing the SPX protocol. Error code: 6.
    05-22-2006 16:48:30 MKDE 000003E0 NTDBSMGR.EXE SERVER W Resources allocated
    05-22-2006 16:58:23 MKDE 000003E0 NTDBSMGR.EXE SERVER I Resources released
    05-22-2006 17:02:09 MKDE 0000059C NTDBSMGR.EXE SERVER W Resources allocated
    05-22-2006 17:26:29 MKDE 0000059C NTDBSMGR.EXE SERVER I Resources released
    05-22-2006 17:47:04 MKDE 0000059C NTDBSMGR.EXE SERVER W Resources allocated
    05-22-2006 18:59:21 MKDE 0000059C NTDBSMGR.EXE SERVER I Resources released
    05-23-2006 06:44:41 MKDE 0000059C NTDBSMGR.EXE SERVER W Resources allocated

  10. #10
    Join Date
    Dec 2001
    Posts
    1,109
    Provided Answers: 4
    Only thing in there that might cause problems down the road (doubt it has anything to do with this problem) is the SPX isn't working. Take SPX out of the supported protocols in the Pervasive Configuration and restart the engine.
    Post the client PVSW.LOG too..
    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.

  11. #11
    Join Date
    May 2006
    Posts
    6
    Looks like the problems are solved !
    Yust a few settings that had to be set. Printing problem also solved.
    TA for the help

Posting Permissions

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