I have set up Pervasive SQL v9 trial version on Linux (Debian/sarge)
from the tar distribution (Pervasive.SQL-9.50-077.002.i486.tar.gz).

So far things look fine, mkded is running, I can run tests from
a Windows client, the server is responding.

However, the application we try to migrate is complaining it is
not permitted to use the server. The server is operating in
"Emulate Workgroup Engine" authentication mode, PVPIPE$ share
is setup, BUT no file called "mkde.pip" was created by mkded
on startup though the documentation says this file must exist
and be readable by clients.

Now, I'm wondering if I'm missing something obvious. Any hints
are appreciated.

Best regards,
Tom

Hi, Tom,

PVPIPE$ is an invisible share. I don't think you would actually be
able to see mkde.pip.

All clients that you want to access the Pervasive Engine need to be
members of the group "pvsw". Is it possible that the client you can
test from is part of the group but the client you're trying to run the
application from is not?

Wayne Freeman
Analytica Business Systems
A Pervasive Premier Partner
www.analyticabiz.com

Thomas Aeby ha scritto:

Hello Wayne,

thanks for your reply.

On Sun, 10 Sep 2006 16:04:44 -0700, Wayne wrote:
Oh, in order to make sure to avoid any such problems I just look into
the physical directory on the server (/usr/local/psql/etc/pipe): no
mkde.pip, unfortunately.

I've trying to setup Pervasive SQL for the first time but am keen with
servers, so I might miss something obvious on the Pervasive side but
I'm not going to overlook an existing file :-))

I thought, maybe mkded needs something more than just authentication
settings in order to be motivated to create that file.

Yes, ignoring this was my first mistake, but now the users have the
necessary permissions. But according to the manual the client software
will try to read mkde.pip ...

Best regards,
Tom

Hi Thomas,

I'd have to say that the documentation is a bit vague on the subject of
mkde.pip.

mkde.pip is only created when you are NOT using Workgroup Emulation
mode. If you change to Standard Unix Authentication, you'll see
mkde.pip appear.

Wayne
Analytica Business Systems
www.analyticabiz.com

Thomas Aeby ha scritto:

Hello Wayne,

On Mon, 11 Sep 2006 12:04:26 -0700, Wayne wrote:
Ah, ok, then I completely misunderstood the docu - but you are
right, when I switch to "btpasswd" authentication, then mkde.pip
appears (when I try to enable UNIX authentication, I get a
"7004: General failure code" error). Then I assume the DB server
is operating correctly - thanks, that's a relief!

What I actually attempt to do is to switch to an authentication
mode where the users do not need login/password for Pervasive
SQL access. I thought that this is the case with "Emulate
Workgroup Engine" authentication and that in that case the clients
use the information in mkde.pip to authenticate - so that read
access to mkde.pip is sufficient in order to get access to the
Pervasive SQL server.

So, how does this setup actually work (the problem is that
currently it does not work - the DB client is asking users for
login/password)? What authentication mode do I need to use? I
thought that both btpasswd and Unix authentication will require
the users to login, while the "Emulate Workgroup Engine" will
work without login/password, but requiring mkde.pip.

Best regards,
Tom

Tom, I could be wrong, but I think you don't have your Samba set up
correctly. If your Samba client were authenticating correctly, you
would not have to log in. Also, Standard Unix Authentication would
work.

Do you have a Samba client set up in your Network Places? I believe
you should have one called "psqldata on Samba Server" or something like
that. It should be authenticating when you connect.

Wayne

Thomas Aeby ha scritto:

There are actually 2 different settings for security with the
Pervasive.SQL Linux product.
There is the setting you are talking about, WGE,BtAdmin and
UnixAuthenticate as well as the Btrieve API security setting which by
ordinarily configured on the DefaultDB database.

If the Btrieve security setting is set for anything other than
"Classic" then the users will have to "log in" no matter what the
engine is set to. If the engine is set to "Workgroup" then the named
pipe isn't even needed.

Leonard

On 12 Sep 2006 12:20:21 -0700, "Wayne" <sales (AT) analyticabiz (DOT) com> wrote: