Hello,

we have here at a customer an environment which consists of:

File-server without P-SQL engine (not allowed). But the data bases are
located here.
Three Workstations (1 * P-SQL 8.0, 2 * P-SQL 9.1, acting as local
workstation engine) with different applications. They access the
databases at the fileserver only every few minutes.

We think, that having no server engine is acceptable because until now
there is only ab few kilobytes traffic in a minute.

But from time to time we get an Btrieve Error 116.
I don't understand the message concerning "gateway", because I want to
have a local engine. So I deactivated remote access for request and
external request.
The problem is mostly present, when the network is weak or when (seldom)
a workstation application fails and can only be solved by restarting the
workstation(s).

How have I to configure P-SQL to act as an simple local workstation engine?

Axel

You should not mix versions of Pervasive. Move all to version 8 or 9.

Below is the text for this error and notice the last paragraph.

Gil

116: The file is owned by another Microkernel engine acting as a
Gateway
The MicroKernel cannot contact the engine running on the gateway
computer even though it can read the locator file. This might occur the
following reasons:

When the two computers are separated by a router so they can both see
the server, but cannot see one another. Try the following:
Use the Gateway Locator utility to identify the owner of the gateway.
Use either the InstallScout or SmartScout utility to connect to that
computer.

You may have attempted to open a file with two different workgroup
engines that are mapped to the files using different share names. The
MicroKernel attempts to correct this, but cannot do so in all cases.
Make sure each computer is mapping to the same share name.

Axel Potthoff wrote:

Gil is correct. If any of the applications access the same data set
or database they should all be the same version.
Gil, I don't believe that the status 116 existed before Pevasive.SQL
2000 WGE.

Now the flip side is, I don't believe that the WGE product works the
way you think it does. While each user has a WGE, if two of them
access the same data the architecture turns into "client / server"
under the covers. The WGE does not know how to "share" files between
engines so one of the engine is the database engine for ALL users that
access the data set. If everybody has truly independent data sets
then the default behavior wuould be for everyone to use their own
engine. Technically this happens on a directory by directory basis
with the first engine to open a file in the directory "claiming" to be
the engine "Gateway" for that directory to all the other users of data
in the directory.

You can tell which workstaion is acting as the gateway for a directory
by looking into the "~pvsw~.loc" (gateway locator) file. The first
line will be the name of the workstation that is acting as the
gateway. All other database requests for data from that directory are
passed (or tried to be passed) client / server to that workstatioin.
For that to work every workstation that is in the workgroup MUST have
"Use Remote MicroKernel" set to YES as well as the engine MUST have
"Accept Remote Requests" set to YES to work.

If the users aren't supposed to share any data directories then this
would indicate that they are. If they are needing to share (even one)
file from a directory then you would need to turn those settings back
to YES for the product to work without getting the 116.

Leonard


On 14 Feb 2006 11:11:35 -0800, "nelsonsoft" <nelsonsoft (AT) hotmail (DOT) com>
wrote:

Hi,

Leonard wrote:
All the databases are version 7 due to history.
But one question: Do you go to your customer an tell him to upgrade 9
workstations to version 9 because of one new system? Are they willing to
pay for it? For the licenses, for the installation, the configuration and
(if you act consequently) converting the databases to the latest version?
We are out of the job, when we offer somenthing like that to our customers.

I accept, that Pervasive turns the back to version 5 databases when stepping
to version 9. But I don't accept updates to every workstation every year.

An one other question:
Isn't it possible to adjust an local Pervasive engine as a LOCAL WORKSTATION
ENGINE?
* no workgroup functions
* no gateway functions
* no remote requests
* no acception of remote requests
* working only local

This worked well with Version 6 (or was it 7?), when workSTATION engines
were availiable!

Because of changing our applications from native btrieve calls to SQL, we
think of changing to other database engines.

Axel

In a workgroup environment if the engines are only accessing their own
data you can mix and match versions as you like.

Perhaps I wasn't clear enough though.
If you are getting a 116 the multiple users are sharing a single
database instead of only woking on their own local database.
From what you say this is not what you want. You may want to check on
just how the users are running the application to get the status 116.

In answer to your question, "can you turn off the Workgroup features
and run in "Workstation" mode?" Yes. Just turn off the "use remote
Microkernel" in the client settings and turn off the "Allow Remote
Requests" in the engine settings. And yes if they try to access data
another user (engine) has open they will then get a status 116.

Leonard

On Fri, 17 Feb 2006 17:26:19 +0100, Axel Potthoff <apn51 (AT) web (DOT) de>
wrote: