Not only do you have to install it, but it has to be running to accept
the requests. If it is not running you would get an error message as
the client could not connect to it.

Leonard

On 24 Feb 2004 01:01:14 -0800, email1 (AT) lighthouse-its (DOT) com (Gary) wrote:

On 24 Feb 2004 01:01:14 -0800, email1 (AT) lighthouse-its (DOT) com (Gary) wrote:

Gary,

When you access BusinessVision, check in the Help>About menu item. Is your
gateway unassigned, floating, or permanent? Have you downloaded or at least read
the BusinessVision technical papers regarding installing Pervasive, BV, and
networking issues?

Are you a BV consultant or an end user? (That may answer some of the questions
above)

I am the poor designated end user who has to try to sort out BV issues. I
have looked at the documentation and understand the concepts about floating
gateways vs assigned. The docs said as long as the engine is installed and
running on the server there was nothing else to do. I have tried leaving it
blank and assigning it to the server and neither seem to work for any length
of time.

In BV I was unable to see where you would get the status. of the gateway..
we are running 5.6 if that matters.

I had a brain flash caused by the question about the workgroup engine
running. Do I have to be logged onto the server to allow it to run? Could
this by why it seems to work for a while as an assigned gateway and then
switch back to floating after a period of time? (my server logs me off
after a period of inactivity).

Thanks for everybody's patience in this... Glad to see I can count on this
community to stick with me to the end.

Gary

Martha says: "Brain flashes are a good thing."

If you are using the WGE, then you MUST be logged into the server to have the
WGE loaded, unless you set it up as a service. Check the white paper about
launching the WGE as a Service on my web site at
www.goldstarsoftware.com/press.asp for more infromation and details.


kermythefrog wrote:

OK, what all the experts here didn't tell you is that if you want the
permanent gateway to be set on the 'server' so that the engine and the
data are on the same PC (ideally a PC running a stable OS with the
most RAM and fastest CPU - usually the newest PC or a dedicated PC
that doesn't have a user) is that not only do you have to load the
engine on that PC, but YOU have to set the gateway locator files to
permanent (unless BV does it for you) because Pervasive.SQL doesn't do
this for you. In this instance, it's apparent that BV isn't getting
this done, so there are two ways you can do this.

1) Check to see if the engine is loaded and running on that PC. Then
make sure everyone else is out of BV. Then look in the data directory
to see if there is a file called ~PVSW~.LOC. This is the locator file.
If that file is present, then use a text editor to read it and make
sure it directs anyone reading it to the right PC. Basically, the
locator file is a file that has the name of the PC that owns the data
in that directory. The engine creates the locator file when it opens
the first file in any directory and deletes it when it closes the last
file. Any other engine that is told to open a file in that directory
first checks for a ~PVSW~.LOC file and if there is one there it tries
to open the file through the first engine rather than opening it
directly. Engines cannot share files like they could in very old
versions and less robust databases than Pervasive.SQL. A "permanent
gateway" is simply a read-only locator file. If you have a locator
file and it points to the correct PC, then just make it read-only.

2) There is a utility shipped with every workgroup engine, but I don't
know if BV shipped it with the embedded version of Pervasive.SQL that
they use. It's the Gateway Locator Utility and the file is
pvlocate.exe. If you have this it has a nice GUI for setting a
Permanent Gateway. If you have the documentation you can look in
Getting Started or search on ~PVSW~.LOC or locator file and read all
about how to do this. It's really really easy, but you can't set a
locator with this utility when the engine has the files in that
directory open.

You can also set ip the Workgroup engine as a service if you want. Our
V8 documentation tells you how to do it, Bill's white paper does that
too, and there is a utility called PVSW Support Toolbox that will do
it for you. You can find that utility on the Pervasive Web site, I
believe in Component Zone.

You can also call Pervasive Tech Support and pay for an incident and
they will walk you through troubleshooting and setting all this if you
need that help. It's cheap at twice the price if you're spending more
than an hour or two trying to resolve this.

I hope this does it for you and good luck.

JohnR

On 27 Feb 2004 16:54:04 -0800, jrothgeb (AT) pervasive (DOT) com (JohnR) wrote:

Note that the latter is a violation of Microsoft EULA if it is not a
server OS with sufficient licenses. Obviously this does not apply if
the dedicated machine does not run a Microsoft OS but then you will
not be able to run a Pervasive Workgroup Engine on it.


Gordon Bos
Q-RY Solutions
+31-(0)15-2564035

http://www.q-ry.nl/