Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

V8.6 Provider cannot be found. It may not be properly installed.

Status
Not open for further replies.

Tankgirl

Programmer
Feb 3, 2003
24
0
0
NZ
Machine:
XP
Pervasive Workgroup V8.6
No domain controller / Workgroup is set up
P2P

Can't connect to a database on the server or locally on the machine.

Tried the following connection strings without any luck:
Provider=PervasiveOLEDB;Data Source=C:\Folder\Data;

Provider=PervasiveOLEDB.8.60;Data Source=DATA;LOCATION=SERVER

Driver={Pervasive ODBC Client Interface};ServerName=;dbq=DATA


 
Can you connect to the database using the PCC? If not, what error do you see?
What does your code look like (or what are you using to pass the connection string in)?
Just to be clear, the line:
Driver={Pervasive ODBC Client Interface};ServerName=;dbq=DATA
needs a ServerName. It can be localhost or the remote servername but there needs to be a name.
Can you connect using the DEMODATA database (instead of yours)?


Mirtheil
Certified Pervasive Developer
Certified Pervasive Technician
Custom VB and Btrieve development.
 
I can connect through PCC perfectly on both machines.

The connection string is: Driver={Pervasive ODBC Client Interface};ServerName=SERVER;dbq=DATA

I haven't tried the DEMODATA - will ask the client to test this and let you know.

Mostly the app can connect using the Provider=PervasiveOLEDB;Data Source=C:\Folder\Data; connection string
About 1 out of every 5 installations have to connect using one of the other connection methods.

The only difference I can see on this site is that they don't have a domain controller but a workgroup set up - not sure if this is relevant?

 
PSQL doesn't need a domain controller. What it does need is name resolution using either SPX, TCP/IP, or NetBios.
If the PCC always works but the OLEDB doesn't, then my next question would be to find out how the OLEDB is being installed. Is this PSQL 8.6 and is the install of PSQL being done by the Pervasive installer or a custom install?

Mirtheil
Certified Pervasive Developer
Certified Pervasive Technician
Custom VB and Btrieve development.
 
I am not sure how Pervasive is installed, our app is an add on to an accounting system which installs all the required programmes. Have requested the info from them.

How would I do the name resolution etc?
 
Easiest way to do name resolution would be a HOSTS file (in C:\WINDOWS\system32\drivers\etc on a WinXP system). Either that or make sure DNS is setup properly.


Mirtheil
Certified Pervasive Developer
Certified Pervasive Technician
Custom VB and Btrieve development.
 
Thanks.

When installing Pervasive WGE, they call the Pervasive Installation
 
No some clients are running Pervasive 2000i, V8.1 or V8.6.

The client getting the connection error is running 8.6
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top