P.SQL V8.5 - turning off security - comp.databases.btrieve

We've recently installed Pervasive.SQL V8.5 as we plan to move from P.SQL 2000i to V8.5 One thing we can't seem to do is turn off security! In the PCC we can select the database properties (for say demodata) and check the security tab. Here it tells us Database security: Disabled However when we try to connect using the OLD DB provider we keep getting error -4828 which does not seen to be documented. On a hunch we configured the server to automatically prompt for a userid and password if one was not supplied (Prompt for CLient Credentials = On) and rebooted. Now we're asked for a userid and password automatically. How can I turn this all off? For the moment I don't want to have to enter a userid and password at all! TIA! Guy -- -------------------------------------------------------------------- Guy Dawson I.T. Manager Crossflight Ltd gnues@crossflight.co.uk

Check your security settings for "DefaultDB". This database is used whenever there is no explicit database login. If you have enabled security (or changed the mode away from "Classic"), then this would cause the problems you indicate. Also, we've found that if you have Btrieve 6.15 Workstation Engine on your machine, you can get Status 170 (security) error messages. I've not seen a -4828 yet, though. Goldstar Software Inc. Building on Btrieve(R) for the Future(SM) Bill Bach BillBach@goldstarsoftware.com http://www.goldstarsoftware.com *** Pervasive.SQL Service & Support Classes *** Chicago: August, 2004: See our web site for details! Guy Dawson wrote: > Gordon wrote: > > > Security *is* disabled by default. > > Which is why I'm stuck! > > > You have to configure the server specifically to enable security. > > Minimum requirements to do this are: > > > > A - enable database security > > Taking demodata as the test database, in the PCC the properties for > the database are > > <SERVER> > Databases > DEMODATA > - right click for menu and select Properties > - click Security tab > the setting is > > Database security: Disabled > > > B - change Btrieve security policy through dbnames configuration > > Checking this as well > > <SERVER> > Configuration > - right click for menu and select Maintain named database > - click on DEMODATA in Registered DB Names pannel > the setting is > > Btrieve security policy: Classic (OS authen... and author...) > > So, as far as A and are are concerned all P.SQL V8.5 security is > turned off. > > > C - set server to prompt for client credentials > > If I set the prompting for client credentials to off I get the > error code -4828, if I set it to on I get prompted for credentials! > > > You only did C and that won't work. You should change it back to the > > original setting. > > I'm now going to turn all the security on and create a use and see > I can actually login... > > > I'm not familiar with code -4828; are you sure it's a Pervasive > > message? > > As far as I can tell. It's not listed in the documentation though. > > > > > Gordon > > > > > > On Mon, 21 Jun 2004 14:13:41 +0100, Guy Dawson > > <gnues@crossflight.co.uk> wrote: > > > > > >>We've recently installed Pervasive.SQL V8.5 as we plan to move from > >>P.SQL 2000i to V8.5 > >> > >>One thing we can't seem to do is turn off security! In the PCC we can > >>select the database properties (for say demodata) and check the > >>security tab. Here it tells us > >> > >> Database security: Disabled > >> > >>However when we try to connect using the OLD DB provider we keep getting > >>error -4828 which does not seen to be documented. > >> > >>On a hunch we configured the server to automatically prompt for a userid > >>and password if one was not supplied (Prompt for CLient Credentials = On) > >>and rebooted. > >> > >>Now we're asked for a userid and password automatically. > >> > >>How can I turn this all off? For the moment I don't want to have to > >>enter a userid and password at all! > >> > >>TIA! > >> > >>Guy > >>-- -------------------------------------------------------------------- > >>Guy Dawson I.T. Manager Crossflight Ltd > >>gnues@crossflight.co.uk > > > > > > > > Gordon Bos > > Q-RY Solutions > > +31-(0)15-2564035 > > > > http://www.q-ry.nl/ > > -- > Guy > -- -------------------------------------------------------------------- > Guy Dawson I.T. Manager Crossflight Ltd > gnues@crossflight.co.uk

Security *is* disabled by default. You have to configure the server specifically to enable security. Minimum requirements to do this are: A - enable database security B - change Btrieve security policy through dbnames configuration C - set server to prompt for client credentials You only did C and that won't work. You should change it back to the original setting. I'm not familiar with code -4828; are you sure it's a Pervasive message? Gordon On Mon, 21 Jun 2004 14:13:41 +0100, Guy Dawson <gnues@crossflight.co.uk> wrote: > >We've recently installed Pervasive.SQL V8.5 as we plan to move from >P.SQL 2000i to V8.5 > >One thing we can't seem to do is turn off security! In the PCC we can >select the database properties (for say demodata) and check the >security tab. Here it tells us > > Database security: Disabled > >However when we try to connect using the OLD DB provider we keep getting >error -4828 which does not seen to be documented. > >On a hunch we configured the server to automatically prompt for a userid >and password if one was not supplied (Prompt for CLient Credentials = On) >and rebooted. > >Now we're asked for a userid and password automatically. > >How can I turn this all off? For the moment I don't want to have to >enter a userid and password at all! > >TIA! > >Guy >-- -------------------------------------------------------------------- >Guy Dawson I.T. Manager Crossflight Ltd >gnues@crossflight.co.uk Gordon Bos Q-RY Solutions +31-(0)15-2564035 http://www.q-ry.nl/

Gordon wrote: > Security *is* disabled by default. Which is why I'm stuck! > You have to configure the server specifically to enable security. > Minimum requirements to do this are: > > A - enable database security Taking demodata as the test database, in the PCC the properties for the database are <SERVER> Databases DEMODATA - right click for menu and select Properties - click Security tab the setting is Database security: Disabled > B - change Btrieve security policy through dbnames configuration Checking this as well <SERVER> Configuration - right click for menu and select Maintain named database - click on DEMODATA in Registered DB Names pannel the setting is Btrieve security policy: Classic (OS authen... and author...) So, as far as A and are are concerned all P.SQL V8.5 security is turned off. > C - set server to prompt for client credentials If I set the prompting for client credentials to off I get the error code -4828, if I set it to on I get prompted for credentials! > You only did C and that won't work. You should change it back to the > original setting. I'm now going to turn all the security on and create a use and see I can actually login... > I'm not familiar with code -4828; are you sure it's a Pervasive > message? As far as I can tell. It's not listed in the documentation though. > > Gordon > > > On Mon, 21 Jun 2004 14:13:41 +0100, Guy Dawson > <gnues@crossflight.co.uk> wrote: > > >>We've recently installed Pervasive.SQL V8.5 as we plan to move from >>P.SQL 2000i to V8.5 >> >>One thing we can't seem to do is turn off security! In the PCC we can >>select the database properties (for say demodata) and check the >>security tab. Here it tells us >> >> Database security: Disabled >> >>However when we try to connect using the OLD DB provider we keep getting >>error -4828 which does not seen to be documented. >> >>On a hunch we configured the server to automatically prompt for a userid >>and password if one was not supplied (Prompt for CLient Credentials = On) >>and rebooted. >> >>Now we're asked for a userid and password automatically. >> >>How can I turn this all off? For the moment I don't want to have to >>enter a userid and password at all! >> >>TIA! >> >>Guy >>-- -------------------------------------------------------------------- >>Guy Dawson I.T. Manager Crossflight Ltd >>gnues@crossflight.co.uk > > > > Gordon Bos > Q-RY Solutions > +31-(0)15-2564035 > > http://www.q-ry.nl/ -- Guy -- -------------------------------------------------------------------- Guy Dawson I.T. Manager Crossflight Ltd gnues@crossflight.co.uk

Bill Bach wrote: > Check your security settings for "DefaultDB". This database is used whenever > there is no explicit database login. If you have enabled security (or changed > the mode away from "Classic"), then this would cause the problems you indicate. Hmmm. I have no DefaultDB database! I assume that when I installed V8.50 over V5.0 over V2000i SP3 that it should have been created at some stage. > Also, we've found that if you have Btrieve 6.15 Workstation Engine on your > machine, you can get Status 170 (security) error messages. Definatly no V6.15 stuff on the client worksation. As far as I know we've never had a V6.15 workstation engine in the office. > I've not seen a -4828 yet, though. Lucky me! Guy > Goldstar Software Inc. > Building on Btrieve(R) for the Future(SM) > Bill Bach > BillBach@goldstarsoftware.com > http://www.goldstarsoftware.com > *** Pervasive.SQL Service & Support Classes *** > Chicago: August, 2004: See our web site for details! > > > Guy Dawson wrote: > > >>Gordon wrote: >> >> >>>Security *is* disabled by default. >> >>Which is why I'm stuck! >> >> >>>You have to configure the server specifically to enable security. >> >> > Minimum requirements to do this are: >> > >> >>> A - enable database security >> >>Taking demodata as the test database, in the PCC the properties for >>the database are >> >> <SERVER> >> Databases >> DEMODATA >> - right click for menu and select Properties >> - click Security tab >> the setting is >> >> Database security: Disabled >> >> >>> B - change Btrieve security policy through dbnames configuration >> >>Checking this as well >> >> <SERVER> >> Configuration >> - right click for menu and select Maintain named database >> - click on DEMODATA in Registered DB Names pannel >> the setting is >> >> Btrieve security policy: Classic (OS authen... and author...) >> >>So, as far as A and are are concerned all P.SQL V8.5 security is >>turned off. >> >> >>> C - set server to prompt for client credentials >> >>If I set the prompting for client credentials to off I get the >>error code -4828, if I set it to on I get prompted for credentials! >> >> >>>You only did C and that won't work. You should change it back to the >>>original setting. >> >>I'm now going to turn all the security on and create a use and see >>I can actually login... >> >> >>>I'm not familiar with code -4828; are you sure it's a Pervasive >>>message? >> >>As far as I can tell. It's not listed in the documentation though. >> >> >>>Gordon >>> >>> >>>On Mon, 21 Jun 2004 14:13:41 +0100, Guy Dawson >>><gnues@crossflight.co.uk> wrote: >>> >>> >>> >>>>We've recently installed Pervasive.SQL V8.5 as we plan to move from >>>>P.SQL 2000i to V8.5 >>>> >>>>One thing we can't seem to do is turn off security! In the PCC we can >>>>select the database properties (for say demodata) and check the >>>>security tab. Here it tells us >>>> >>>> Database security: Disabled >>>> >>>>However when we try to connect using the OLD DB provider we keep getting >>>>error -4828 which does not seen to be documented. >>>> >>>>On a hunch we configured the server to automatically prompt for a userid >>>>and password if one was not supplied (Prompt for CLient Credentials = On) >>>>and rebooted. >>>> >>>>Now we're asked for a userid and password automatically. >>>> >>>>How can I turn this all off? For the moment I don't want to have to >>>>enter a userid and password at all! >>>> >>>>TIA! >>>> >>>>Guy >>>>-- -------------------------------------------------------------------- >>>>Guy Dawson I.T. Manager Crossflight Ltd >>>>gnues@crossflight.co.uk >>> >>> >>> >>> Gordon Bos >>> Q-RY Solutions >>> +31-(0)15-2564035 >>> >>> http://www.q-ry.nl/ >> >>-- >>Guy >>-- -------------------------------------------------------------------- >>Guy Dawson I.T. Manager Crossflight Ltd >>gnues@crossflight.co.uk > > -- Guy -- -------------------------------------------------------------------- Guy Dawson I.T. Manager Crossflight Ltd gnues@crossflight.co.uk

Guy Dawson wrote: > Hmmm. I have no DefaultDB database! > > I assume that when I installed V8.50 over V5.0 over V2000i SP3 that it > should have been created at some stage. In the above please replace V5.0 with V8.0 Guy -- -------------------------------------------------------------------- Guy Dawson I.T. Manager Crossflight Ltd gnues@crossflight.co.uk

Bill Bach wrote: > Check your security settings for "DefaultDB". This database is used whenever > there is no explicit database login. If you have enabled security (or changed > the mode away from "Classic"), then this would cause the problems you indicate. In the OLD DB connection string I'm specifying the server (Location=) and the database (Data source=). I'm assuming this is what you mean by explicit database login. Guy -- -------------------------------------------------------------------- Guy Dawson I.T. Manager Crossflight Ltd gnues@crossflight.co.uk

Pervasive left the "DefaultDB" stuff out of the documentation. On an upgrade, the NetWare install does NOT create the DefaultDB database, for certain technical reasons. However, the DefaultDB database *is* quite important in terms of security. To fix this: - Start the PCC - Connect to the server & open the Databases group. - Right-Click/Create Database - Provide the name of "DefaultDB" - Provide the path to the server's Samples directory, usually SYS:PVSW\SAMPLES, by browsing in the dialog box and selecting this directory. - Click through to complete the wizard and create the database. See the section in the Advanced Operations Guide (on-line manual) on Pervasive.SQL Security for more information about this database and how it controls security. Goldstar Software Inc. Building on Btrieve(R) for the Future(SM) Bill Bach BillBach@goldstarsoftware.com http://www.goldstarsoftware.com *** Pervasive.SQL Service & Support Classes *** Chicago: August, 2004: See our web site for details! Guy Dawson wrote: > Bill Bach wrote: > > > Check your security settings for "DefaultDB". This database is used whenever > > there is no explicit database login. If you have enabled security (or changed > > the mode away from "Classic"), then this would cause the problems you indicate. > > In the OLD DB connection string I'm specifying the server (Location=) and > the database (Data source=). I'm assuming this is what you mean by explicit > database login. > > Guy > -- -------------------------------------------------------------------- > Guy Dawson I.T. Manager Crossflight Ltd > gnues@crossflight.co.uk

Bill Bach wrote: > Pervasive left the "DefaultDB" stuff out of the documentation. Hurrah! > On an upgrade, the NetWare install does NOT create the DefaultDB > database, for certain technical reasons. Ho hum! > However, the DefaultDB database *is* quite important in terms of security. OK. > To fix this: > - Start the PCC > - Connect to the server & open the Databases group. > - Right-Click/Create Database > - Provide the name of "DefaultDB" > - Provide the path to the server's Samples directory, usually SYS:PVSW\SAMPLES, by > browsing in the dialog box and selecting this directory. > - Click through to complete the wizard and create the database. Done. > See the section in the Advanced Operations Guide (on-line manual) on Pervasive.SQL > Security for more information about this database and how it controls security. I'm reading it at the moment... Having created the DefaultDB which by default gets configured for Classic security, which is what we want, I still have no joy with the OLE DB connection. I still get the Login Window popping up. The login window title is Login to Pervasive.SQL Database The text is To proceed you need to log in to the Pervasive.SQL database Please specify a valid database user name and password to login. The user can input User name: Password: The system supplies (greyed out) Host: <server name> I understand that I get a pop up login screen because I've told the server to produce one if it needs credentials. I don't understand why the server thinks it does need credentails... Guy -- -------------------------------------------------------------------- Guy Dawson I.T. Manager Crossflight Ltd gnues@crossflight.co.uk

Similiar Articles:

P.SQL V8.5 - turning off security - comp.databases.btrieve ...
We've recently installed Pervasive.SQL V8.5 as we plan to move from P.SQL 2000i to V8.5 One thing we can't seem to do is turn off security! In the P...

pervasive code 94 - comp.databases.btrieve
P.SQL V8.5 - turning off security - comp.databases.btrieve ... We've recently installed Pervasive.SQL V8.5 as we plan to move from P.SQL 2000i ... pervasive code 94 - comp ...

Error 170 on one workstation using v8.7 PSQL - comp.databases ...
Error 170 on one workstation using v8.7 PSQL - comp.databases ... P.SQL V8.5 - turning off security - comp.databases.btrieve ..... as we plan to move from P.SQL 2000i to ...

CreateProcess with a specific user login credentials - comp.lang ...
P.SQL V8.5 - turning off security - comp.databases.btrieve ... > C - set server to prompt for client credentials If I ... does NOT create the DefaultDB database, for ...

putty connection manager - set title on your tab - comp.unix.shell ...
P.SQL V8.5 - turning off security - comp.databases.btrieve ..... SQL V8.5 security is > turned off. > > > C - set ... In the OLD DB connection string I'm specifying the ...

How WinXp close all connections at log off? - comp.os.ms-windows ...
... detect them with NET USE or WNetEnumResource); the only solution is to log off and ... extracting SFTP logs from PuTTY SSH logs - comp.security.ssh ..... closed network ...

iCal "server did not recognize your user name or password" - comp ...
P.SQL V8.5 - turning off security - comp.databases.btrieve ... As far as I know we've never had a V6.15 ... The user can input User name: Password: The system supplies ...

system requirements for solidworks 2004 - comp.cad.solidworks ...
P.SQL V8.5 - turning off security - comp.databases.btrieve ..... specifically to enable security. > > Minimum requirements to ... Service & Support Classes *** Chicago ...

file opening slows down - puzzling - comp.lang.xharbour
> > Yes, but that is considered an advantage from the > security point of view. > > > =A0 =A0Is modern SQL ... the usual registry tweaks like, for example, turning off ...

Btrieve tables dont appear - comp.databases.btrieve
I have Pervasive.SQL 2000i, but when I access the database, the only the ... True is, my program does not perform a simple USE. ... SQL V8.5 - turning off security - comp ...

P.SQL V8.5 - turning off security - Database Support @ dbaspot.com ...
We've recently installed Pervasive.SQL V8.5 as we plan to move from P.SQL 2000i to V8.5 One thing we can't seem to do is turn off security! In the PCC we can select ...

7/24/2012 8:54:21 PM