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 IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Pervasive database connection errors

Status
Not open for further replies.

CRUhoob

IS-IT--Management
Apr 13, 2007
7
US
We have finally installed Pervasive 7.0 and got away from the w32mkde (single user version) but now we have a problem with database connections.

When we look in the logs, it says there isn’t a suitable communication protocol installed. But when you run setup32 and look in the enabled protocols, it shows both SPX and TCP/IP protocols installed and enabled. When we go into setup and click the connect button, it times out and says it cannot connect but you can change settings locally and they save.

So because of this, we can only work off the server. If we change the connection target to workstation only, it fails. It only works on server only and workstation first then server. We have a 40-user license and it shows in the database manager.

We believe that once we get this connection issue resolved…we will be up and running again.

Any help on this matter would be very appreciated.

Thank you in advance for your help.
 
Jerry,

Did you run the Pervasive client install on the workstation(s)? If so did the communication tests pass?

Software Sales, Training, Implementation and Support for Macola, eSynergy, and Crystal Reports

"If you have a big enough dictionary, just about everything is a word"
--Dave Barry
 
Yes we ran the client install on the workstations and they failed the communications test. The server is also failing to communicate to itself when we click the connect button.

But I can ping the server from workstations and I can ping the server itself with communication success so I don’t think it is a bad network card.

Any suggestions on what could be wrong and why it says there isn’t a suitable communication protocol?


 
In setup 32 and 16 (I always do both because the original v7 macola was 16 bit, and I suspect there may be underlying components that are still 16 bit), you should set the local off and the remote on, use server then workstation, and turn off the spx protocol: leave tcpip only. Can you save your settings on the server itself? Can you change and save settings on the workstation? You may need to change the registry keys manually for pervasive. I remember having to do that from time to time. Have you verified that all 6.15 btrieve components are off the workstations? Did you run the renbtdll? Did you grant full permissions on the hkey local software keys for macola, pervasive, and odbc? Did you remove any btrieve 6.15 keys from the registry? Can you create a database on the server and from an attached workstation? Does the btrieve maintenance utility return file information if you browse to apvenfil, for example? If you can, then you know the workstation is connecting with the database engine on the server. Do you have both the transactional and relational services started on the server?
 
What other protocols besides TCP/IP and IPX/SPX are present?

Software Sales, Training, Implementation and Support for Macola, eSynergy, and Crystal Reports

"If you have a big enough dictionary, just about everything is a word"
--Dave Barry
 
Did you run delbtdll.exe in the Macola root directory to remove the 6.15 components?
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top