Most of our workstations have both the client engine and the
workstation engine installed. this is so we can go in an offline mode
if the server goes down. It has worked well for many years. The only
problem is if one system looses connection and the workstation engine
starts, a connection is recreated and the workstation engine stays
running. This will cause error messages throughout the entire system.

Last night I upgraded the application and it did not do anything(that I
know of) to Pervasive. But today when the workstations that have the
WSE installed opened the application, everyone of them opened the WSE
instead of the client. The network appears to be fine. The workstations
without the WSE are running fine as are the WSE units. I am just
waiting for errors to pop up like they always have in the past.

Any ideas why this would happen all the sudden?

Thanks

The WSE is supposed to AutoStart -- i.e. it should be in the "Startup"
folder for Windows.

To keep the WSE out of memory, go into the PCC, Configuration, Client,
Access, then set the Use Local Microkernel Engine to OFF. This will
prevent the local engine from being used.

In the event of a failure for which the WSE is required, users will
need to manually enable this setting again. (It can also be done with
a RegEdit file, if you want to make it easier.)
Goldstar Software Inc.
Providing Pervasive.SQL Training & Services
Bill Bach
BillBach (AT) goldstarsoftware (DOT) com
http://www.goldstarsoftware.com
*** Chicago: Pervasive Service & Support Class - 03/27/06 ***

smeyer56 wrote:

As Bill Bach mentions you could turn off "Use Local MicroKernel" in
the settings, but that would interfere with using the engine in
off-line mode.

Short of that the engine is supposed to start when a request for a
local data file is made. Is the new version of the application
opening local data files by any chance? You could easily enough check
in the Pervasive Monitor utility to see which file is open.

As to a workstation engine "taking over" after the machine loses
communication to the server engine, you can easily enough set a
permanent gateway on the server machine that points to the server.
The server engine does not make them for performance reasons, but the
other workstation engines would respect the locator files if they are
present. The gateway locator needs to be set in each data directory.
In the meantime you can easily enough tell which machine, if any, is
causing the problem by looking in the gateway locator file,
~pvsw~.loc. The first entry in the file is the name of the machine
the active workgroup engine is running on.

Leonard

On 29 Mar 2006 09:43:54 -0800, "smeyer56" <smeyer56 (AT) earthlink (DOT) net>
wrote:

After more research and looking at the monitors on the server and
workstation, what seems to be happening is:
When the application opens, the WSE opens. I do not see any files
accessed at the time on the WSE. Then all the files open for the client
on the server. The WSE stays open with no files being accessed and as
long as no files are accessed through the WSE there are no conflicts.

We have been running this way for almost a week and have had no
problems. Support for the application finally got back to me and don't
seem to concerned, although they say V8.5 has a cache setting that
should prevent this and suggest that I should think about upgrading(but
not necessary).

I think I will upgrade in the fall when our company is over the busy
season.

Thanks
Steve

There is no cache engine on your current engine, PSQL2000i. Again, if
you really want to disable the local engine, just change the setting in
the PCC,. and you'll be all set!
Goldstar Software Inc.
Pervasive-based Products, Training & Services
Bill Bach
BillBach (AT) goldstarsoftware (DOT) com
http://www.goldstarsoftware.com
*** Austin: Pervasive Service & Support Class - 05/2006 ***
*** Chicago: Pervasive Service & Support Class - 07/2006 ***

smeyer56 wrote: