Hi

We have a Pervasive.SQL 2000i Server with SP4 runing on a Windows 2000 SP4
Server. When we try to connect to the
Database from a Client via ODBC we get the error message:

[08S01] [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)

We already installed the Pervasive.SQL 2000i Client Requesters (2 Meg) on
the clients (NT, 2000, XP) and also
copied all w1*.dll and w3.dll from the server \PVSW\BIN to the client
\PVSW\BIN.
We are able to establish a TCP/IP from the client to the server using Telnet
and connecting to the port 1583.
We successfully checked the connection server- and client side with netstat.
So the service is running on the
server an listens for new connection. So the error message "SQL Connection
Manager is not running at the
specified port number" seems to be wrong!
We already reinstalled the whole Pervasive.SQL 2000i part with no success.
Connecting from the server to
the server via the same ODBC-Driver works fine. So the first idea was a
communication problem with was
disproved by the telnet check.

Has anyone solved this problem yet or an idea how to solve it?

Thanks in advance and many regards

stefan wrote:
The 10065 is a Winsock error. Here's a little more info for your problem:

(From Microsoft MSDN)
http://msdn.microsoft.com/library/de...or_codes_2.asp

10065 WSAEHOSTUNREACH
No route to host.
A socket operation was attempted to an unreachable host. See
WSAENETUNREACH.

10051 WSAENETUNREACH
Network is unreachable.
A socket operation was attempted to an unreachable network. This usually
means the local software knows no route to reach the remote host.

You may want to check the Pervasive protocol settings - the client and
server have to match (and should be set appropriately for your network).
You may try running PSA (Pervasive System Analyzer) to see what it
says also.

Paul

To clarify, the ODBC driver uses the protocol settings inside the
client DSN. See the "transport hint" setting. They also get their
port information there.

Since it is a 10065 - No route to host, it might be something as
simple as the client DSN pointing to the wrong server or address. If
the server has a fixed IP address you can just put the server IP
address in the "Server" box of the client DSN.

If that does not work, the 10065 does point squarely towards IP
routing and to diagnose those issues the "tracert" program is your
friend.

Leonard

On Thu, 10 Feb 2005 02:57:59 GMT, Paul Rodden
<nospam_prodden (AT) jwscorp (DOT) com_nospam> wrote:

hello,

thank you for your help.

to resolve the problem, i try the following: i install a complete new
server on a new machine with the same pervasive-version in the same
lan-segment.

and all looks fine!!

the only difference is the server-name: the old name have hyphen in
the machine-name (just like: server-bdc-01) and the new name is
without hyphen (like: serverbdc01).

is this the reason for the problem? can pervasive-sql 2000 i not work
with those machine-names?

Hyphens in a server name should be a non-issue.
In fact based on the original description it did not sound like it
was. It looked like the Pervasive client was able to properly (I
hope) get the IP address of the server from the OS on the client. It
looks like it was just failing to get a TCP/IP network session
established because of a routing issue between the client and server.

At this point I am curious as to whether it worked on the old server
as opposed to across the network.

Leonard

On 16 Feb 2005 00:59:06 -0800, s_leitl (AT) lutronik (DOT) de (stefan) wrote: