[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference orarep::nomahs::dbintegrator_public_public

Title:DB Integrator Public Conference
Notice:Database Integration - today! Kit/Doc info see note 36
Moderator:BROKE::ABUGOV
Created:Mon Sep 21 1992
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:1171
Total number of notes:5187

1144.0. "WSAENO_DATA from gateway to PC" by AVMSV1::EKREISLE (Erich Kreisler) Fri Apr 04 1997 10:53

Hello,
I tried to get the gateway to PC up and running again (it worked it 7.0 FT2),
but now the agent always fails when with
Network error WSAENO_DATA error while error getting hostname f....(here is the
message cut off and I'cant incrase the window).

Versions:
Windows 3.1 with LAN Workplace
Gateway to PC Data 7.0.00

The ALpha from where I want to connect is running Rdb 7.0 with DBI 7.0.

The most annoying thing is that you can't get to the message because of the
OK-box and then the agent window is gone.
I also tried to enable logging for the agen, but this did not work.

Normal TCP connections like telnet and ftp from the PC to the Alpha work ok.

What else should I look for ?

Thank you in advance,
	erich
T.RTitleUserPersonal
Name		DateLines
1144.1Can the PC ping itself?BROKE::ABROWNMon Apr 07 1997 08:5722
Are you saying that you have a working version of PC data
gateway on a particular PC, then installed version 7 ON
THAT SAME PC and it no longer works?  Very strange.

A typical cause of the error you are seeing is a
problem with TCP/IP on the PC where the agent and
executor are installed.  The things I would do are:
     a) Reboot - I'm sure you've tried this.  There
                 are a few resource related problems
                 that occur on certain error paths
                 that can only be fully cured by
                 a reboot.
     b) Check that the PC's own name/address is correctly
        defined where the PC can access it.  A problem
        of this sort is consistant with the error that
        you are seeing.  (Try pinging yourself.)

If you can dig out the correct settings to make
in the PCGWY.INI (either by looking at the comments
in the file, or by using help) you should be able
to capture the entire text of the error message into
a log file.
1144.2AVMSV1::EKREISLEErich KreislerMon Apr 07 1997 10:1618
Thank you for your reply.

pinging the PC works, also I see that the client (AXP) connects, as the executor
is started up, but then hangs until I terminate on the PC side.

I also enabled logging using the PCGWY.INI file, but could not capture the log
as no file is produced:
[PC Gateway Executor]
Loggingenabled="Y"
KeepAlive="N"
ReadOnly="N"
LogToFile="Y"
LoggingDirectory="c:\temp"

Can you tell me what I is wrong with that section ?

Ciao,
	erich