Application running on SQL V 8 just "disappears"

[skyguy48]

I have a client who recently upgraded to Win Server 2003 for a Novell server. Installed Pervasive SQl 8 on server, removed IPX from all workstations, running strictly on IP now.

They are running an inventory application from Profit Systems, here in Colo Springs.

Since the upgrade, they have random systems (all on Win 98, Profit's choice) that the inventory/sales application will just "disappear" - the best way I can describe it. Plenty of RAM on workstations.

Seems to happen more when they are busy, especially on weekends. Profit's response, so far, has been to reboot the server. This seems to stabilze the problems for a day or so.

I am NOT a Pervasive guru, but pretty good on O/S's.

Any ideas???

 

[TomKane]

There is a pervasive monitoring utility you can check number of users logged in and the peak and maxumum settings - try to see if and of pervasive's configuraion settings are reach the max allowable setings - if they are then you may have to adjust these settings using the setup utility.

 

[mirtheil]

You might also want to check with Profit Systems to verify they haven't seen this type of problem before. It could be that the application isn't catching an error code properly. You might also try testing the setup with the Pervasive System Analyzer. It'll test the network connectivity and the Btrieve/ODBC connections to make sure everything is working from the Pervasive side of things.


info@mirtheil.com
Custom VB and Btrieve development.
Certified Pervasive Developer
Certified Pervasive Technician

 

[skyguy48]

Thanks for the quick replys. You both mention 1)a monitoring utility and 2)a system analyzer. If you could tell me the names of these, I will be happy to run them and see what's up.

As I said, I know almost nothing about Pervasive...

 

[mirtheil]

The Pervasive System Analyzer is named that. It should be in c:\program files\common files\pervasive software shared\psa and the EXE name is psawizrd.exe.
THe monitor is called Pervasive Monitor and is typically in the Utilities subgroup of the Pervasive program group. It's located in PVSW\BIN by default and is named W3MONV75.EXE and needs to connect to the engine if it's remote.
I don't see how an instability at the server would cause a client based application to disappear unless the client based application doesn't handle some errors properly.

info@mirtheil.com
Custom VB and Btrieve development.
Certified Pervasive Developer
Certified Pervasive Technician