Pre-load & Login

Mike, the Pervasive Preload is a workgroup engine so it runs in the currently logged on windows session. It is possible to turn the engine into a service but this is not supported.

However, the error message you are talking about ('File in use, waiting for access to file') is generally caused by a locking issue, Maximizer is trying to open the Maximizer Database Files but they are already locked open so it cannot open them again.

I would check the file sharing on the pc acting as the server to see if any of the files are locked open.

It may also be an internal file lock inside one of the .max files, I would also suggest running a Backup/Optimised Restore of the address book in question.

Thank you CABC for responding.

I've checked the shares in MMC on the server and have found that none of them are locked. The thing is, this happens for all of our address books. If any user is logged into the server (meaning the Pervasive engine has pre-loaded), then all address books can be opened from client machines. If the server is logged off (meaning I suppose that the Pervasive engine has not been loaded on the server) then none of the address books can be opened and all client machines get the above "waiting..." message.

I could certainly recreate the address books, but these are newly created (we're deploying the app for thet first time now).

For the time being, I must leave the server logged on if there is to be any use of Maximizer by client machines. If I attempt to logoff the server while a client is making use of Maximizer, I get a "Remote application connected to the Pervasive database...if you continue shutting down, applications will fail...".

You mentioned that it's not supported to run the engine as a service...is it possible in any way for it to load & remain loaded regardless of logons/logoffs at the console?

How do most people handle this?

Thanks again.

Good Morning Mike,

You are indeed correct in assuming that if the server machine is logged off then the Pervasive Workgroup engine is also switched off, this is unfortunate but it is the way it works.

Most people who use the Pervasive Workgroup version of Maximizer Enterprise just leave the server machine logged on but locked.

If you don't want to keep it logged on, perhaps for the purposes of security, you may be better off with the Pervasive Client/Server engine which is designed to run purely as a service.

My thanks again, CABC - this is what I wanted to confirm. You have been most helpful.

Just noticed that the MaxExchange install process seems to have installed a service that loads the Pervasive engine: I can now login to all address books from a client machine while the server is logged off. I've taken the engine pre-load out of the startup group to suppress the "database already loaded" error on login.

This is good, and I hope expected news.