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!

Need help with Pervasive ODBC Interface error

Status
Not open for further replies.

cubfanbob

MIS
Oct 17, 2002
1
US
Hello. I'm trying to use Microsoft Access on a client workstation to connect (via the Pervasive ODBC interface) to ACCPAC tables (in Pervasive SQL 2000i) on a server.

Technical info:

Server OS: Microsoft Windows 2000 Server 5.00.2195, Service Pack 2
Client OS: Microsoft Windows 2000 Professional, 5.00.2195, Service Pack 1
ACCPAC is Enterprise edition, Version 4.2
DBMS version: Pervasive SQL 2000i - SP3
Pervasive ODBC Engine Interface is version 7.90.23036, date is 3/21/01
Pervasive ODBC Client Interface is version 7.90.23036, date is 3/21/01
MS Access: Access 2000 9.0.3821 SR-1

Following the instructions in this manual:


and using the Pervasive Control Center, I registered an engine on the server, and a database that pointed to the ACCPAC tables, and was able to use PCC to open and view the ACCPAC tables.

I then used PCC on the client to register an engine/database there as well. But when I tried to use the client PCC to open the ACCPAC tables, I received the following error message:

[Pervasive] [ODBC Client Interface] [Client LNA] The ODBC Client Interface cannot access the data source because SQL connection Manager is not running at the specified port number. Contact your system administrator for assistance.

The documentation on this error on the Pervasive website implies that there is a problem with using IP addresses instead of database names. I never used IP addresses during the engine/database install process, and all port numbers have been left at the default (1583). I uninstalled then reinstalled the server engine/driver and client engine/driver, same result. Rebooted both client and server, same result.

Just for grins, I then tried to link to the ACCPAC tables from within MS Access, using Machine Data Source. To my surprise it worked, and for the rest of the evening I was able to link tables, and create/run queries.

But this morning, I'm back to the same error(s) as before. When I try to run the query to open the tables I get the following error:

ODBC – connection to “[link name]” failed.

When I try to add an ACCPAC table to Access I get:

[Pervasive] [ODBC Client Interface] [Client LNA] The ODBC Client Interface cannot access the data source because SQL connection Manager is not running at the specified port number. Contact your system administrator for assistance. (#10065) [Microsoft] [ODBC Driver Manager] Drivers SQLsetConnectAttr failed (#10).

The Help Tab on the error message says:

ODBC – call failed. (Error 3146)

Using an ODBC connection, you tried to perform an operation on data in an ODBC data source. This error may occur when the ODBC data source is on a network drive and you are not connected to the network. Make sure the network is available, and then try the operation again.


I rebooted both my computer and the server, but continue to receive the same error messages.

Thoughts? Thanks in advance for your help.

Bob
 
Hey CubFanBob,

Did you ever find an answer to your problem? Did your relational engine go down and not come back up? I have an ACCPAC client in the same boat. We're writing a report and have aliased a table so I think the complexity of the linking pooped out the engine somehow. I can run the report on my machine but it's a nice workhorse and always works better than my client's machines.

Djangman
 
HI Bob,

have you ever solved the Pervasive Interface error?
I got the same error message!! If you have found an answer, please help me!

steve

 
I had been receiving this error on occasion and other issues with the driver for our website.

I found that if I put an entry in the services file on the server with PSQL 2000i

\system32\drivers\etc
w3sqlmgr 1583/tcp

this solved my problem and actually speed up my connect significantly.

Apparently this allocates the port to the relational service.

Todd

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top