Link to home
Start Free TrialLog in
Avatar of jeftech
jeftech

asked on

Error: "Failed to create database. Insufficient rights to get or set information."

I am trying to create an ODBC DSN using the Pervasive ODBC Engine Interface.  After entering the database name (see question below), the data file locations and dictionary locations, I click OK and receive this error.  I am logged on to the server as an administrator (on the server itself, not through a terminal session).

Just a question about the "Database Name" field - is that something I create, or do I need to find out what the database name is?  (This is the first time I have used Pervasive.)  I know all the tables are listed in the BTrieve file.ddf file, but I'm not sure where to find out the database name.

Thanks

Phil Jeffrey
Avatar of jeftech
jeftech

ASKER

OK, I have been able to create an Engine Interface DSN by creating a Client Interface DSN first (not sure why or how, but it just happened that way).

However, when I tried to "Test" the DSN, I was asked to "Log on to <DSN name>" and to enter a username/password.  Same thing when I try to use the DSN by linking tables in MS Access.  What is the username/password that needs to be entered?  Is it a database administrator account or something?  Unfortunately someone else installed the Pervasive database so getting hold of these credentials may be difficult.
ASKER CERTIFIED SOLUTION
Avatar of Mirtheil
Mirtheil
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Just to clarify the error a little further:  In my experience, in order to create a database on the server, you must be logged on as THE administrator, not as AN administrator.  I run into this all the time when a customer knows I'm going to be connecting to his server (not through TS, that's another issue) and installing a Pervasive Server, so his system admin logs in for me.  I always ask them to log in as Administrator, but the sys admin sometimes hears something different.

So, during the installation, the creation of the DEMODATA database fails with the above error and I have to get the sys admin involved again and get him to re-login as THE administrator so I can complete the installation.

Then, and here's the other issue, when he calls me I don't know whether he's sitting at the console or on a TS session.  If he's on a TS session, re-logging in as The Administrator doesn't work, so I need to clarify how he's connected.  If it's a TS session, then there is a registry setting that allows a workaround to that.