Lock Table Full

[Backlacsh]

Like several others who have posted here, I'm also having a problem with a Lock Table Full error message; However, the network environment I'm running is different from anyone else who's posted here, so I thought it appropriate to start a new thread.

We are running Peachtree Complete Accounting version 9.033. Our 'server' is actually a Windows 98SE machine, as are the three client machines pulling the database from it. There were no problems until one of the machines burned itself up 'literally' and had to be replaced.

On the new machine only, we now frequently see the message, "Error in file h:\peachw\data\jrnlhdr.dat. Lock table full." The new machine is the only one that posts, which might be why we only see the error there.

I have tried everything I've found in Peachtree's knowledge base including:

Adding Files=250 and BUFFERS=32,0 to the server and Files=150 on the workstation.
Installing the newest drivers for the D-Link 530TX+ network card on the workstation.
Disconnecting the network drive, unsharing the drive, rebooting both, resharing and remapping the drive.
Making sure the workstation is using real time posting.
Checking the database for errors and the machines for communications problems using the tests under the file menu, which always show both tests passing.

I, myself, cannot reproduce the error for testing purposes because it only happens at random while the user is posting through-out the day.

Any advise would be greatly appreciated. Also, if anyone knows a way that I could reproduce the error, for testing, without messing up there books it would be very helpful.

[Robert Walraven]

You didn't say where you changed the Btrieve limits. If you did it in the BTI.INI file and are running version 7 or later, that is the wrong place. You must make modifications to the Btrieve entries in the registry. You might try adjusting "Record Locks per Client"

[Backlacsh]

Do you have any suggestions as to what I should change it to?

[Robert Walraven]

Here is what the Btrieve documentation says:

Record Locks per Client

Range: 1 through 64,000 locks
Default: 20 locks
Approximate memory required: 35 bytes per lock

The setting specifies the maximum number of records a
client instance can lock at one time. This maximum applies
to both single and multiple-record read locks.

I would think you could set it to at least 100.

[Paul]

What is the operating system of the workstation. If it Windows 2000 or Windows XP you can not have the data source on a windows 98 computer. It is ok to have the data on a Windows 2000 computer and interact with Windows 98 work stations, but you can not reverse the process.

If you have questions please email me a paul@e-controller.com

[Backlacsh]

They are all Windows 98 SE machines.

I will post an update as soon as I'm able to attempt the try the suggested change to the Btrieve registry setting and see the results.

In the mean time, any more suggestions of things to try would also be appreciated.

Thanks for your time.

[Backlacsh]

I went back to the location and checked all through the registry. There doesn't appear to be a 'Record Locks per Client ' entry. The closest thing I could find was
HKEY_LOCAL_MACHINE\Software\Btrieve Technologies\Microkernel\Max Locks
which is already set at 1000.
The entry you were refering to sounded exactly like what I needed, can you advise me on this?

Again, I'm working with Peachtree Complete Accounting version 9.033, and apparently the Btrieve is version 6.15.

Thank you again for your time and advise.

[Robert Walraven]

The "Record Locks per Client" doesn't seem to appear in the registry entries that appear when the standard version of Peachtree is installed. However, I did see "Max Locks" and "Max Clients", so I would guess that the locks per client is just the ratio of these two.

I don't think there is any harm in setting the value of Max Locks higher just to see what happens. That will use a small amount of additional memory but that shouldn't be a problem.

[jacarrollco]

Originally posted by Backlacsh
They are all Windows 98 SE machines...


We have Win 98SE/P2P/NetBEUI/multi-user Complete 8.02 network. As soon as the boss got his new Win XP laptop Peachtree started blowing up. Tech support said no-no to accessing Peachtree on the old Win 98SE machine so now I'm ordering a new XP machine. Ouch! I wonder if this XP/98 is going to be a problem with all kinds of programs on small networks? And what about security? NetBEUI is, I guess, absolute but XP's TCP/IP "firewall"? I'll bet there are thousands of kids developing ways to bust through. We'll be installing a patch a week like OutLook just to keep the kids out.