Maximizer Remote Problem

Hi,

Damage to MXZM is not unknown MXZF is quite rare.

There is a known problem with this version of max exchange on windows 2000 which requires you to run the old btrieve files Have you got these in place? (w32mkde.exe,w32mkrc.dll & wbtrv32.dll) + settings for 6.15.

Corruption of the central files is a bit of a problem though I suspect MXZF may not be replicated as its really a part of the identity of the database. MXZM is normally replicated, though the corruption has probably not been sent out it just doesn't work like that. You can probably restore this file from a recent backup (if its really damaged). You will, technically, be out of sync on this file but the effect will be minor (mostly macros). I think you need to be sure the files are really damaged. What error codes do you get?

Are you running the full pervasive.sql 2000 server engine? With 10 remotes we would recommend this even if you have few LAN users as its becomes so important to protect the central files from damage.

If you'd like to discuss this in detail you can contact me at ian.wallace@cabc.co.uk

Regards,

Ian Wallace
CABC Newbury

i have on machine (ibm thinkpad laptop) that is a remote user with exectly the smae errors. I replaced the files and it worked for about 2 days but then we started getting error 82. Now the system is completely down. and the collums table get currupt ervery time we syncronize.

Thanks for the reply.. It appears that the Sales team were docking and undocking their notebooks frequently and the pervasive database was getting a bit upset.

My advice to anybody else using this is to ensure that the users do not randomly unplug their network connections....

We have created a simple recovery procedure that seems to work... Thanks for all of your help.