Our WebPublisher server has been giving a lot of internal errors (usually 4212, but today also 5656). We are running WebPublisher Pro v9.0 on Windows Server 2003 (IIS 6).

I have checked out the database locally (check textbase, dump/reload, etc.) but have not come up with any problems). Rebooting the server gets rid of the errors, but they start again after a while.

I suspect it may be a file locking problem; if I try to upload a fresh copy of the textbase and overwrite the old one, the server cannot delete the TBA file.

Any suggestions?
Thanks

The first thing I would use a file unlocking tool to check which process holds the lock on the tba.

There is a few unlocker tools, both the ones listed can provide you with the locking app, and directly terminate that app.

WhoLockMe
Unlocker

Thanks for the suggestion - I don't have direct access to the server, but will keep this in mind if it happens again. I have seen references to a similar problem that happens when there are many users using the textbase, as in a web environment where connections may not get closed properly. I've increased the maximum textbase users to 2000 (was 200 previously, though there are never that many concurrent users).