How to connect to pervasive engine on NetWare

[delphidestructor]

How do I connect to a pervasive DB on a NetWare server? In the Pervasive Control Center, I can access the local DB's with no problem, but on the NW server I can only create and delete DB's. When I try to access the tables, stored procs, etc, I get the following message and I have not been able to locate the information to tell me what the two error codes mean.

[Pervasive][ODBC Client Interface][Client LNA]The ODBC Client Interface cannot communicate with SQL Connection Manager due to a network error (RPC = 65, Error = 129). Contact your system administrator if you still need assistance.

I have Pervasive.SQL 2000i with all service packs applied. I'm assuming the bstart and mgrstart commands should have everything on the server running correctly. I shouldn't need an ODBC connection when going through the PCC, should I?

Any help would be great. Thanks.

 

[Guest_imported]

rpc error 65 is --- The field offset is incorrect
with sql 2000i the only service pack that works correctly at the moment is sp3

 

[Vancouverite]

"I shouldn't need an ODBC connection when going through the PCC, should I?"

Yes, you should. ODBC is how PCC communicates with the server.

Check your pervasive log file on your workstation (Click Start/Programs/Pervasive/Documentation/Pervasive Event Log to open it), look at what it is reporting there, and post it here.

 

[delphidestructor]

These two error messages are repeated.


01-28-2002 14:22:48 ECAS_API FFF9DE2D SW\Bin\pcc.exe" IBM1085397 E ECASAPI (1.12.1.4083): Error 8505 - An initialization error occurred when trying to establish a session with the WSE
01-28-2002 14:22:48 ECAS_API FFF9DE2D SW\Bin\pcc.exe" IBM1085397 E ECASAPI (1.1.1.4083): Error 8517 - An error occurred when closing the session with the WSE

 

[Vancouverite]

Hmmm... those are pretty standard messages (they happen when you haven't configured the workstation to *not* look for a local engine). That shouldn't be the problem.

Try using Pervasive System Analyzer (Start/Programs/Pervasive/Pervasive.SQL 2000i/Utilities/Pervasive System Analyzer) to check your communications with the server. Use the Test Network, Test Transactional, and Test Relational tests. Any problems or errors?

 

[delphidestructor]

This is the message I always get when I run any of the network tests with NetBios and TCP/IP.


<The server you chose appears to have the SPX and TCP/IP protocol(s) but the network address returned does not look like a valid address.

Also verify that Pervasive.SQL is started on the server.>

Transactional tests work fine.

Relational tests do not complete. The following is what I get; the same as the PCC returns.

<Failed to connect to the database. The server name or the server DSN specified may not exist.

Make sure that the Pervasive.SQL 2000i Server Engine on the machine specified is started and the usercount is valid.

[Pervasive][ODBC Client Interface][Client LNA]The ODBC Client Interface cannot communicate with SQL Connection Manager due to a network error (RPC = 65, Error = 129). Contact your system administrator if you still need assistance.>

 

[sibemollbe]

did you find any solution to that &quot;address returned doesn't look like a valid address&quot;?

I need to solve this issue, since I'm setting up Netware 6's NAAS (Audit Service). When I use IPX, everything works fine with the connection tests. When I use TCP/IP or Netbios, I get the same message as you.

But then, when you get to ConsoleOne, select your tree and do the NAAS setup, you have to do a NAAS database setup. In this setup you can't give an IPX address, you must give an IP address; since the connection issue doesn't work, I can't setup the NAAS database.

tried on Novell forums and no luck...it looks like a hard issue.

hi, and thanks for your attention, Xavier Serra, IBV

 

[delphidestructor]

Yes, I did find the problem. Make sure the clients and the pervasive server are all on the same TCP/IP network; IP addresses and subnetmasks. You might have to to do some additional configuration of DNS and DHCP services but I would start by checking all the IP addresses and go fron there.

 

[sibemollbe]

well, I can't solve the problem. Both the server and the client are on the same class C network. I'm using netware 6 DNS service.

I also tried without DHCP; configured the client as static and no luck too. That &quot;address returned not valid&quot; seems to happen when connecting to the server, the previous steps work fine (resolving target and so on...).

still any idea? thanks in advance, Xavier

 

[Ramaiya]

Hi,
I am setting up NAAS on Netware 6. When I try to execute NAAS report thru' Console1 I get the following error
&quot;There was an error in getting the filter list from the database. Novell eDirectory has returned an error while authenticating the auditor.&quot;

The NAAS error log &quot;NAASERR.txt&quot; states
NAAS Server Error : Unable to Authenticate. Authentication information from Auditor incorrect or unavailable. Refer NAAS Troubleshooting Guide for more Information.. Error Code = 7115

I have followed novell's support TID 10067500 step by step, so I don't know what's wrong now Do not know any new test to see what's wrong.
Any suggestions??

 

[BKtechie]

Try replacing the server name with the IP address. That's the only way I got it to work on my network (TCP/IP).
BKtechie