This document was inspired by a recent and on going customer problem, when a DSN-Less connection is enabled, System Five would lock up completely when doing tasks such as looking up past invoices with live search, and statement runs etc. System Five would completely freeze, halting business for at least 30-60 seconds.

The way this issue was resolved in this instance, was to turn DSN-Less off, opening PCC on the machines that needed the DSN, and creating a DSN in there manually, using the network directory _datafiles, as the data source. The next step is to run either wwtweaktool or to manually remove SAT entries from the registry. See the following link http://wiki.wws5.com/doku.php?id=fixing_a_pervasive_status_94&s=sat this works up to PVSW 10, 11 you'll have to remove the entries manually from the registry under: HKEY_LOCAL_MACHINE\Software\Pervasive Software\Communications Requester\Version x\Settings. Set NumSatEntries to 0 and delete the SatEntryX keys. (Where x is equal to the entry number)

Once you've linked the DNS and removed the entries, there should be some performance speed. Do this only after ascertaining the network speed and performance, ordinarily however, a simple DSN-LESS connection really should be used in most cases. Also under PCC, make sure the communications protocols are set to TCP/IP only, threads and handles can also be increased to better performance, and turning on caching can help too.

If you have anything to add to this document, please go ahead

Leslie Cordell 2012/08/09