Sybase NNTP forums - End Of Life (EOL)

The NNTP forums from Sybase - forums.sybase.com - are now closed.

All new questions should be directed to the appropriate forum at the SAP Community Network (SCN).

Individual products have links to the respective forums on SCN, or you can go to SCN and search for your product in the search box (upper right corner) to find your specific developer center.

6420 Errors - why, why, why?

6 posts in Networking Last posting was on 2006-08-03 17:19:12.0Z
Ian Thompson Posted on 2006-07-28 15:59:35.0Z
From: "Ian Thompson" <irt@cygnetlodge.co.uk>
Newsgroups: Advantage.Networking
Subject: 6420 Errors - why, why, why?
Date: Fri, 28 Jul 2006 16:59:35 +0100
Lines: 49
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.2869
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2869
X-RFC2646: Format=Flowed; Original
NNTP-Posting-Host: 84.51.164.172
Message-ID: <44ca336a@solutions.advantagedatabase.com>
X-Trace: 28 Jul 2006 09:55:22 -0700, 84.51.164.172
Path: solutions.advantagedatabase.com!solutions.advantagedatabase.com!84.51.164.172
Xref: solutions.advantagedatabase.com Advantage.Networking:632
Article PK: 1132051

Hi Everyone.

I just thought I'd share this with you.

We have a WS2K3 ADS 7.0 system with multiple clients. Mixed local and
remote tables. Other stuff is immaterial, it transpires. After an orderly,
system-wide restart, we started getting the dreaded 6420 error with some
clients, both with our app and the ARC. Searched the newsgroups, gleaned a
bit about the discovery process and about eliminating it and hit upon the
COMMCALLTRACE=1 ADS.INI flag and the

[MYServerName]
LAN_IP=10.0.0.111 (for example)
LAN_PORT=2001

entry for ADS.INI.

Thought we'd cracked it. Tried it.

No.

So, looked at the ADSCOM.TXT file produced (due to COMMCALLTRACE=1) which
said that it was using the correct IP for the server, but despite the above
MYSERVERNAME entry, it reported no port was specified, when clearly it is,
in the format stated by ADS tech guys. Strange stuff.

Then noticed that the trace file mentioned that it had determined that
SIN_PORT=0, i.e., not LAN_PORT=0 as you might expect if the text in the INI
file had been read in.

So, thinking "nah!",changed the INI to say SIN_PORT=2001 instead and - guess
what!!!

Yup, it works.

SO, 2 things:
(1) I have no idea why a perfectly working system suddenly decides not to
function.
(2) why does Advantage tech support not supply the correct info? What's
SIN_PORT?

Or am I missing something?

Cheers,

Ian Thompson


Mark Wilkins Posted on 2006-07-28 20:13:52.0Z
From: "Mark Wilkins" <tired@of.spam>
Newsgroups: Advantage.Networking
References: <44ca336a@solutions.advantagedatabase.com>
Subject: Re: 6420 Errors - why, why, why?
Date: Fri, 28 Jul 2006 14:13:52 -0600
Lines: 92
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.2869
X-RFC2646: Format=Flowed; Response
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2869
NNTP-Posting-Host: 10.24.38.161
Message-ID: <44ca6f1e@solutions.advantagedatabase.com>
X-Trace: 28 Jul 2006 14:10:06 -0700, 10.24.38.161
Path: solutions.advantagedatabase.com!solutions.advantagedatabase.com!10.24.38.161
Xref: solutions.advantagedatabase.com Advantage.Networking:633
Article PK: 1132052

Hi Ian,

The code does not read any value named "sin_port" from the ads.ini file. The
"sin_port" value reported in the call trace is referring to a member of the
windows socket structure (struct sockaddr_in). I think "sin" stands for
"socket address, internet style" ... it's defined in the Microsoft header
file winsock2.h if you are curious. Note that without the Advantage comm
layer source code in front of you, it is pretty hard interpreting the
contents of that trace file. I have looked at lots of them, but I rarely
can make sense of them unless I look at the source code. That file is
definitely not for end user consumption.

If you added an ads.ini entry as you stated below with LAN_PORT=2001, and it
did not work, then it seems possible that Advantage is not using that port.
Did you specify a port for it to use in the configuration utility? If not,
then I think it defaults to 6262. If that is the case, then specifying an
incorrect port number in ads.ini would definitely cause some kind of error
(possibly a 6420). Changing it from "lan_port" to "sin_port" would
effectively remove the entry, and Advantage would not see the port number in
the ads.ini file. I think then that it would read the IP address from the
LAN_IP entry and try to contact the server using that address via multicast
or possibly netbios. The server would then respond with the correct port
number to use. You should be able to delete the sin_port entry from
ads.ini, and nothing will change.

As far as question 1 goes, I am unsure. If it was working, and then
suddenly it stops working, then it is almost certain that something changed.
It seems quite possible that a system-wide restart could definitely result
in a change. For example, if you do not have a port number specified for
Advantage to use, then it is possible that it might get a different port
number when it restarted.

HTH,
Mark Wilkins
Advantage R&D

"Ian Thompson" <irt@cygnetlodge.co.uk> wrote in message
news:44ca336a@solutions.advantagedatabase.com...
> Hi Everyone.
>
> I just thought I'd share this with you.
>
> We have a WS2K3 ADS 7.0 system with multiple clients. Mixed local and
> remote tables. Other stuff is immaterial, it transpires. After an
> orderly, system-wide restart, we started getting the dreaded 6420 error
> with some clients, both with our app and the ARC. Searched the newsgroups,
> gleaned a bit about the discovery process and about eliminating it and hit
> upon the COMMCALLTRACE=1 ADS.INI flag and the
>
> [MYServerName]
> LAN_IP=10.0.0.111 (for example)
> LAN_PORT=2001
>
> entry for ADS.INI.
>
> Thought we'd cracked it. Tried it.
>
> No.
>
> So, looked at the ADSCOM.TXT file produced (due to COMMCALLTRACE=1) which
> said that it was using the correct IP for the server, but despite the
> above MYSERVERNAME entry, it reported no port was specified, when clearly
> it is, in the format stated by ADS tech guys. Strange stuff.
>
> Then noticed that the trace file mentioned that it had determined that
> SIN_PORT=0, i.e., not LAN_PORT=0 as you might expect if the text in the
> INI file had been read in.
>
> So, thinking "nah!",changed the INI to say SIN_PORT=2001 instead and -
> guess what!!!
>
> Yup, it works.
>
> SO, 2 things:
> (1) I have no idea why a perfectly working system suddenly decides not to
> function.
> (2) why does Advantage tech support not supply the correct info? What's
> SIN_PORT?
>
> Or am I missing something?
>
> Cheers,
>
> Ian Thompson
>
>
>


Ian Thompson Posted on 2006-07-29 07:52:13.0Z
From: "Ian Thompson" <irt@cygnetlodge.co.uk>
Newsgroups: Advantage.Networking
References: <44ca336a@solutions.advantagedatabase.com> <44ca6f1e@solutions.advantagedatabase.com>
Subject: Re: 6420 Errors - why, why, why?
Date: Sat, 29 Jul 2006 08:52:13 +0100
Lines: 123
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.2869
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2869
X-RFC2646: Format=Flowed; Response
NNTP-Posting-Host: 84.51.164.172
Message-ID: <44cb12b4@solutions.advantagedatabase.com>
X-Trace: 29 Jul 2006 01:48:04 -0700, 84.51.164.172
Path: solutions.advantagedatabase.com!solutions.advantagedatabase.com!84.51.164.172
Xref: solutions.advantagedatabase.com Advantage.Networking:634
Article PK: 1132053

Hi Mark,

Fascinating stuff. I tried removing the SIN_PORT entry and, sure enough, the
system carries on working.

The ADS server is CONFIGed to use port 2001 and that's the reason for my
SIN_PORT assumptions. It's very weird (and, I accept, possibly entirely
coincidental) that everything jumped to attention when I made this change.
I have no clue as to what else might have changed - certainly there was no
catastrophe or disorder in the shut-down or start-up that prompted the
problem. And we haven't seen it before, so, bottom of the class for
consistency!!

Reading through the groups, it certainly seems to me that 6420 errors live
in some mystical corners in the ADS world - there are lots of posts which
claim inconsistency and/or difficulties of some kind. Can the
'auto-discovery' methods not be rationalised or simplified? Why have them at
all? Why not force the establishment of the connection to be the
responsibilty of the programmer? Questions from a naiive mind, I
fear........

Anyway, many thanks for your response - if I have any more weirdies, I'll be
back......

Regards,

Ian

"Mark Wilkins" <tired@of.spam> wrote in message
news:44ca6f1e@solutions.advantagedatabase.com...
> Hi Ian,
>
> The code does not read any value named "sin_port" from the ads.ini file.
> The "sin_port" value reported in the call trace is referring to a member
> of the windows socket structure (struct sockaddr_in). I think "sin"
> stands for "socket address, internet style" ... it's defined in the
> Microsoft header file winsock2.h if you are curious. Note that without
> the Advantage comm layer source code in front of you, it is pretty hard
> interpreting the contents of that trace file. I have looked at lots of
> them, but I rarely can make sense of them unless I look at the source
> code. That file is definitely not for end user consumption.
>
> If you added an ads.ini entry as you stated below with LAN_PORT=2001, and
> it did not work, then it seems possible that Advantage is not using that
> port. Did you specify a port for it to use in the configuration utility?
> If not, then I think it defaults to 6262. If that is the case, then
> specifying an incorrect port number in ads.ini would definitely cause some
> kind of error (possibly a 6420). Changing it from "lan_port" to
> "sin_port" would effectively remove the entry, and Advantage would not see
> the port number in the ads.ini file. I think then that it would read the
> IP address from the LAN_IP entry and try to contact the server using that
> address via multicast or possibly netbios. The server would then respond
> with the correct port number to use. You should be able to delete the
> sin_port entry from ads.ini, and nothing will change.
>
> As far as question 1 goes, I am unsure. If it was working, and then
> suddenly it stops working, then it is almost certain that something
> changed. It seems quite possible that a system-wide restart could
> definitely result in a change. For example, if you do not have a port
> number specified for Advantage to use, then it is possible that it might
> get a different port number when it restarted.
>
> HTH,
> Mark Wilkins
> Advantage R&D
>
>
>
>
> "Ian Thompson" <irt@cygnetlodge.co.uk> wrote in message
> news:44ca336a@solutions.advantagedatabase.com...
>> Hi Everyone.
>>
>> I just thought I'd share this with you.
>>
>> We have a WS2K3 ADS 7.0 system with multiple clients. Mixed local and
>> remote tables. Other stuff is immaterial, it transpires. After an
>> orderly, system-wide restart, we started getting the dreaded 6420 error
>> with some clients, both with our app and the ARC. Searched the
>> newsgroups, gleaned a bit about the discovery process and about
>> eliminating it and hit upon the COMMCALLTRACE=1 ADS.INI flag and the
>>
>> [MYServerName]
>> LAN_IP=10.0.0.111 (for example)
>> LAN_PORT=2001
>>
>> entry for ADS.INI.
>>
>> Thought we'd cracked it. Tried it.
>>
>> No.
>>
>> So, looked at the ADSCOM.TXT file produced (due to COMMCALLTRACE=1) which
>> said that it was using the correct IP for the server, but despite the
>> above MYSERVERNAME entry, it reported no port was specified, when clearly
>> it is, in the format stated by ADS tech guys. Strange stuff.
>>
>> Then noticed that the trace file mentioned that it had determined that
>> SIN_PORT=0, i.e., not LAN_PORT=0 as you might expect if the text in the
>> INI file had been read in.
>>
>> So, thinking "nah!",changed the INI to say SIN_PORT=2001 instead and -
>> guess what!!!
>>
>> Yup, it works.
>>
>> SO, 2 things:
>> (1) I have no idea why a perfectly working system suddenly decides not to
>> function.
>> (2) why does Advantage tech support not supply the correct info? What's
>> SIN_PORT?
>>
>> Or am I missing something?
>>
>> Cheers,
>>
>> Ian Thompson
>>
>>
>>
>
>


Ian Thompson Posted on 2006-08-01 11:34:55.0Z
From: "Ian Thompson" <irt@cygnetlodge.co.uk>
Newsgroups: Advantage.Networking
References: <44ca336a@solutions.advantagedatabase.com> <44ca6f1e@solutions.advantagedatabase.com> <44cb12b4@solutions.advantagedatabase.com>
Subject: Re: 6420 Errors - why, why, why?
Date: Tue, 1 Aug 2006 12:34:55 +0100
Lines: 138
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.2869
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2869
X-RFC2646: Format=Flowed; Response
NNTP-Posting-Host: 84.51.164.172
Message-ID: <44cf3b63@solutions.advantagedatabase.com>
X-Trace: 1 Aug 2006 05:30:43 -0700, 84.51.164.172
Path: solutions.advantagedatabase.com!solutions.advantagedatabase.com!84.51.164.172
Xref: solutions.advantagedatabase.com Advantage.Networking:635
Article PK: 1132054

...and back I am, because the 6420 errors have recurred WITHOUT any changes
to the system. We went home last night - everything left switched on and
connected to the LAN. Came in this morning, run up Delphi (or any of the
EXE's so produced) on ANY of the 5 workstations and the 6420 error
re-appeared.

What gives, guys? I'm at my wits end with this one.

Regards,

Ian

"Ian Thompson" <irt@cygnetlodge.co.uk> wrote in message
news:44cb12b4@solutions.advantagedatabase.com...
> Hi Mark,
>
> Fascinating stuff. I tried removing the SIN_PORT entry and, sure enough,
> the system carries on working.
>
> The ADS server is CONFIGed to use port 2001 and that's the reason for my
> SIN_PORT assumptions. It's very weird (and, I accept, possibly entirely
> coincidental) that everything jumped to attention when I made this change.
> I have no clue as to what else might have changed - certainly there was no
> catastrophe or disorder in the shut-down or start-up that prompted the
> problem. And we haven't seen it before, so, bottom of the class for
> consistency!!
>
> Reading through the groups, it certainly seems to me that 6420 errors live
> in some mystical corners in the ADS world - there are lots of posts which
> claim inconsistency and/or difficulties of some kind. Can the
> 'auto-discovery' methods not be rationalised or simplified? Why have them
> at all? Why not force the establishment of the connection to be the
> responsibilty of the programmer? Questions from a naiive mind, I
> fear........
>
> Anyway, many thanks for your response - if I have any more weirdies, I'll
> be back......
>
> Regards,
>
> Ian
> "Mark Wilkins" <tired@of.spam> wrote in message
> news:44ca6f1e@solutions.advantagedatabase.com...
>> Hi Ian,
>>
>> The code does not read any value named "sin_port" from the ads.ini file.
>> The "sin_port" value reported in the call trace is referring to a member
>> of the windows socket structure (struct sockaddr_in). I think "sin"
>> stands for "socket address, internet style" ... it's defined in the
>> Microsoft header file winsock2.h if you are curious. Note that without
>> the Advantage comm layer source code in front of you, it is pretty hard
>> interpreting the contents of that trace file. I have looked at lots of
>> them, but I rarely can make sense of them unless I look at the source
>> code. That file is definitely not for end user consumption.
>>
>> If you added an ads.ini entry as you stated below with LAN_PORT=2001, and
>> it did not work, then it seems possible that Advantage is not using that
>> port. Did you specify a port for it to use in the configuration utility?
>> If not, then I think it defaults to 6262. If that is the case, then
>> specifying an incorrect port number in ads.ini would definitely cause
>> some kind of error (possibly a 6420). Changing it from "lan_port" to
>> "sin_port" would effectively remove the entry, and Advantage would not
>> see the port number in the ads.ini file. I think then that it would read
>> the IP address from the LAN_IP entry and try to contact the server using
>> that address via multicast or possibly netbios. The server would then
>> respond with the correct port number to use. You should be able to
>> delete the sin_port entry from ads.ini, and nothing will change.
>>
>> As far as question 1 goes, I am unsure. If it was working, and then
>> suddenly it stops working, then it is almost certain that something
>> changed. It seems quite possible that a system-wide restart could
>> definitely result in a change. For example, if you do not have a port
>> number specified for Advantage to use, then it is possible that it might
>> get a different port number when it restarted.
>>
>> HTH,
>> Mark Wilkins
>> Advantage R&D
>>
>>
>>
>>
>> "Ian Thompson" <irt@cygnetlodge.co.uk> wrote in message
>> news:44ca336a@solutions.advantagedatabase.com...
>>> Hi Everyone.
>>>
>>> I just thought I'd share this with you.
>>>
>>> We have a WS2K3 ADS 7.0 system with multiple clients. Mixed local and
>>> remote tables. Other stuff is immaterial, it transpires. After an
>>> orderly, system-wide restart, we started getting the dreaded 6420 error
>>> with some clients, both with our app and the ARC. Searched the
>>> newsgroups, gleaned a bit about the discovery process and about
>>> eliminating it and hit upon the COMMCALLTRACE=1 ADS.INI flag and the
>>>
>>> [MYServerName]
>>> LAN_IP=10.0.0.111 (for example)
>>> LAN_PORT=2001
>>>
>>> entry for ADS.INI.
>>>
>>> Thought we'd cracked it. Tried it.
>>>
>>> No.
>>>
>>> So, looked at the ADSCOM.TXT file produced (due to COMMCALLTRACE=1)
>>> which said that it was using the correct IP for the server, but despite
>>> the above MYSERVERNAME entry, it reported no port was specified, when
>>> clearly it is, in the format stated by ADS tech guys. Strange stuff.
>>>
>>> Then noticed that the trace file mentioned that it had determined that
>>> SIN_PORT=0, i.e., not LAN_PORT=0 as you might expect if the text in the
>>> INI file had been read in.
>>>
>>> So, thinking "nah!",changed the INI to say SIN_PORT=2001 instead and -
>>> guess what!!!
>>>
>>> Yup, it works.
>>>
>>> SO, 2 things:
>>> (1) I have no idea why a perfectly working system suddenly decides not
>>> to function.
>>> (2) why does Advantage tech support not supply the correct info? What's
>>> SIN_PORT?
>>>
>>> Or am I missing something?
>>>
>>> Cheers,
>>>
>>> Ian Thompson
>>>
>>>
>>>
>>
>>
>
>


Mark Wilkins Posted on 2006-08-01 13:24:36.0Z
From: "Mark Wilkins" <tired@of.spam>
Newsgroups: Advantage.Networking
References: <44ca336a@solutions.advantagedatabase.com> <44ca6f1e@solutions.advantagedatabase.com> <44cb12b4@solutions.advantagedatabase.com> <44cf3b63@solutions.advantagedatabase.com>
Subject: Re: 6420 Errors - why, why, why?
Date: Tue, 1 Aug 2006 07:24:36 -0600
Lines: 182
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.2869
X-RFC2646: Format=Flowed; Response
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2869
NNTP-Posting-Host: 10.24.38.161
Message-ID: <44cf5534@solutions.advantagedatabase.com>
X-Trace: 1 Aug 2006 07:20:52 -0700, 10.24.38.161
Path: solutions.advantagedatabase.com!solutions.advantagedatabase.com!10.24.38.161
Xref: solutions.advantagedatabase.com Advantage.Networking:636
Article PK: 1132055

Hi Ian,

If you can send a copy of the adscom.txt trace file to
advantage@extendedsystems.com, we can take a look at it and possibly
determine what is happening.

Another useful piece of information if you can get it is a network trace
(Ethereal is a good choice - it is free and works extremely well).

If you have the LAN_IP and LAN_PORT specified in the ads.ini file and are
connecting with a UNC style path \\myserver\myshare\datapath, then that
should be the most reliable method.

Another thing to check (although I don't think this would be the issue if
the problem is intermittent) is to see if the server on which Advantage is
running is multi-homed (multiple NICs). If so, you might want to use the
LAN_IP_ADDRESS setting at the server (search for "LAN IP Address" in the
help file). If you specify that entry, then Advantage will bind
specifically to the given address.

Are the client and server PCs on the same subnet, or are they going through
a router or a switch? There could be a configuration problem with a router.
Although, again, since the behavior is seemingly intermittent, I would not
think it was a configuration problem.

Do you have a firewall installed on the client PC? If so, you might try
disabling it temporarily to see if that is somehow involved. Some firewalls
are configured to allow outbound UDP traffic and will accept replies on the
same port if they are within a certain timeframe. If the network and/or
server were very busy and did not reply within that timeframe, then it could
result in connection problems

Finally, there is always the chance that there is a bad network card in the
mix somewhere. A faulty NIC could definitely cause intermittent
connectivity problems.


Mark Wilkins
Advantage R&D

"Ian Thompson" <irt@cygnetlodge.co.uk> wrote in message
news:44cf3b63@solutions.advantagedatabase.com...
> ...and back I am, because the 6420 errors have recurred WITHOUT any
> changes to the system. We went home last night - everything left switched
> on and connected to the LAN. Came in this morning, run up Delphi (or any
> of the EXE's so produced) on ANY of the 5 workstations and the 6420 error
> re-appeared.
>
> What gives, guys? I'm at my wits end with this one.
>
> Regards,
>
> Ian
> "Ian Thompson" <irt@cygnetlodge.co.uk> wrote in message
> news:44cb12b4@solutions.advantagedatabase.com...
>> Hi Mark,
>>
>> Fascinating stuff. I tried removing the SIN_PORT entry and, sure enough,
>> the system carries on working.
>>
>> The ADS server is CONFIGed to use port 2001 and that's the reason for my
>> SIN_PORT assumptions. It's very weird (and, I accept, possibly entirely
>> coincidental) that everything jumped to attention when I made this
>> change. I have no clue as to what else might have changed - certainly
>> there was no catastrophe or disorder in the shut-down or start-up that
>> prompted the problem. And we haven't seen it before, so, bottom of the
>> class for consistency!!
>>
>> Reading through the groups, it certainly seems to me that 6420 errors
>> live in some mystical corners in the ADS world - there are lots of posts
>> which claim inconsistency and/or difficulties of some kind. Can the
>> 'auto-discovery' methods not be rationalised or simplified? Why have them
>> at all? Why not force the establishment of the connection to be the
>> responsibilty of the programmer? Questions from a naiive mind, I
>> fear........
>>
>> Anyway, many thanks for your response - if I have any more weirdies, I'll
>> be back......
>>
>> Regards,
>>
>> Ian
>> "Mark Wilkins" <tired@of.spam> wrote in message
>> news:44ca6f1e@solutions.advantagedatabase.com...
>>> Hi Ian,
>>>
>>> The code does not read any value named "sin_port" from the ads.ini file.
>>> The "sin_port" value reported in the call trace is referring to a member
>>> of the windows socket structure (struct sockaddr_in). I think "sin"
>>> stands for "socket address, internet style" ... it's defined in the
>>> Microsoft header file winsock2.h if you are curious. Note that without
>>> the Advantage comm layer source code in front of you, it is pretty hard
>>> interpreting the contents of that trace file. I have looked at lots of
>>> them, but I rarely can make sense of them unless I look at the source
>>> code. That file is definitely not for end user consumption.
>>>
>>> If you added an ads.ini entry as you stated below with LAN_PORT=2001,
>>> and it did not work, then it seems possible that Advantage is not using
>>> that port. Did you specify a port for it to use in the configuration
>>> utility? If not, then I think it defaults to 6262. If that is the case,
>>> then specifying an incorrect port number in ads.ini would definitely
>>> cause some kind of error (possibly a 6420). Changing it from "lan_port"
>>> to "sin_port" would effectively remove the entry, and Advantage would
>>> not see the port number in the ads.ini file. I think then that it would
>>> read the IP address from the LAN_IP entry and try to contact the server
>>> using that address via multicast or possibly netbios. The server would
>>> then respond with the correct port number to use. You should be able to
>>> delete the sin_port entry from ads.ini, and nothing will change.
>>>
>>> As far as question 1 goes, I am unsure. If it was working, and then
>>> suddenly it stops working, then it is almost certain that something
>>> changed. It seems quite possible that a system-wide restart could
>>> definitely result in a change. For example, if you do not have a port
>>> number specified for Advantage to use, then it is possible that it might
>>> get a different port number when it restarted.
>>>
>>> HTH,
>>> Mark Wilkins
>>> Advantage R&D
>>>
>>>
>>>
>>>
>>> "Ian Thompson" <irt@cygnetlodge.co.uk> wrote in message
>>> news:44ca336a@solutions.advantagedatabase.com...
>>>> Hi Everyone.
>>>>
>>>> I just thought I'd share this with you.
>>>>
>>>> We have a WS2K3 ADS 7.0 system with multiple clients. Mixed local and
>>>> remote tables. Other stuff is immaterial, it transpires. After an
>>>> orderly, system-wide restart, we started getting the dreaded 6420 error
>>>> with some clients, both with our app and the ARC. Searched the
>>>> newsgroups, gleaned a bit about the discovery process and about
>>>> eliminating it and hit upon the COMMCALLTRACE=1 ADS.INI flag and the
>>>>
>>>> [MYServerName]
>>>> LAN_IP=10.0.0.111 (for example)
>>>> LAN_PORT=2001
>>>>
>>>> entry for ADS.INI.
>>>>
>>>> Thought we'd cracked it. Tried it.
>>>>
>>>> No.
>>>>
>>>> So, looked at the ADSCOM.TXT file produced (due to COMMCALLTRACE=1)
>>>> which said that it was using the correct IP for the server, but despite
>>>> the above MYSERVERNAME entry, it reported no port was specified, when
>>>> clearly it is, in the format stated by ADS tech guys. Strange stuff.
>>>>
>>>> Then noticed that the trace file mentioned that it had determined that
>>>> SIN_PORT=0, i.e., not LAN_PORT=0 as you might expect if the text in the
>>>> INI file had been read in.
>>>>
>>>> So, thinking "nah!",changed the INI to say SIN_PORT=2001 instead and -
>>>> guess what!!!
>>>>
>>>> Yup, it works.
>>>>
>>>> SO, 2 things:
>>>> (1) I have no idea why a perfectly working system suddenly decides not
>>>> to function.
>>>> (2) why does Advantage tech support not supply the correct info? What's
>>>> SIN_PORT?
>>>>
>>>> Or am I missing something?
>>>>
>>>> Cheers,
>>>>
>>>> Ian Thompson
>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>


Ian Thompson Posted on 2006-08-03 17:19:12.0Z
From: "Ian Thompson" <irt@cygnetlodge.co.uk>
Newsgroups: Advantage.Networking
References: <44ca336a@solutions.advantagedatabase.com> <44ca6f1e@solutions.advantagedatabase.com> <44cb12b4@solutions.advantagedatabase.com> <44cf3b63@solutions.advantagedatabase.com> <44cf5534@solutions.advantagedatabase.com>
Subject: Re: 6420 Errors - why, why, why?
Date: Thu, 3 Aug 2006 18:19:12 +0100
Lines: 230
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.2869
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2869
X-RFC2646: Format=Flowed; Response
NNTP-Posting-Host: 84.51.164.172
Message-ID: <44d22f15@solutions.advantagedatabase.com>
X-Trace: 3 Aug 2006 11:15:01 -0700, 84.51.164.172
Path: solutions.advantagedatabase.com!solutions.advantagedatabase.com!84.51.164.172
Xref: solutions.advantagedatabase.com Advantage.Networking:638
Article PK: 1132057

Hi Mark,

Curiouser and curiouser.

After posting my last message, I took another look at the LAN_IP and
LAN_PORT settings. I found a few more references to 6420 errors on another
NG and one in particular from Joachim Durr has helped out. If I refer to
the server with its IP (rather than its name) in the ADS.INI, then use port
6262 (it won't work with the default 2001, and I'm pretty sure that nothing
else is using that port, though a proper sniffer might tell me otherwise..)
e.g.

[10.0.0.111]
LAN_IP=10.0.0.111
LAN_PORT=6262

it all bursts into life, reliably. So, I guess there's something up with
the server name lookup on our system. The strange thing is that I haven't
seen this on any of our customers' sites. This isn't a problem for us,
because the server has a fixed IP and the machine that provides DHCP to the
rest of the LAN.

Anyway, many thanks for your interest and help. FYI, all PC's are on the
same private (10.0.0.X) subnet, no router in the way, no firewalls anywhere,
no multiple NIC's. Fast Dell Xeon server under light load, no network
problems of any other type ever experienced! Pretty unspectacular system,
really.

Having made the changes to the Server settings in the ADS.INI and having
waited a few days to see how stable it became, I'm pretty confident that
we've cracked it.

I'll continue to do some research into this - if I come up with anything
definitive, I'll post it.

Oh, great product by the way!!!

Regards,

Ian

"Mark Wilkins" <tired@of.spam> wrote in message
news:44cf5534@solutions.advantagedatabase.com...
> Hi Ian,
>
> If you can send a copy of the adscom.txt trace file to
> advantage@extendedsystems.com, we can take a look at it and possibly
> determine what is happening.
>
> Another useful piece of information if you can get it is a network trace
> (Ethereal is a good choice - it is free and works extremely well).
>
> If you have the LAN_IP and LAN_PORT specified in the ads.ini file and are
> connecting with a UNC style path \\myserver\myshare\datapath, then that
> should be the most reliable method.
>
> Another thing to check (although I don't think this would be the issue if
> the problem is intermittent) is to see if the server on which Advantage is
> running is multi-homed (multiple NICs). If so, you might want to use the
> LAN_IP_ADDRESS setting at the server (search for "LAN IP Address" in the
> help file). If you specify that entry, then Advantage will bind
> specifically to the given address.
>
> Are the client and server PCs on the same subnet, or are they going
> through a router or a switch? There could be a configuration problem with
> a router. Although, again, since the behavior is seemingly intermittent, I
> would not think it was a configuration problem.
>
> Do you have a firewall installed on the client PC? If so, you might try
> disabling it temporarily to see if that is somehow involved. Some
> firewalls are configured to allow outbound UDP traffic and will accept
> replies on the same port if they are within a certain timeframe. If the
> network and/or server were very busy and did not reply within that
> timeframe, then it could result in connection problems
>
> Finally, there is always the chance that there is a bad network card in
> the mix somewhere. A faulty NIC could definitely cause intermittent
> connectivity problems.
>
>
> Mark Wilkins
> Advantage R&D
>
> "Ian Thompson" <irt@cygnetlodge.co.uk> wrote in message
> news:44cf3b63@solutions.advantagedatabase.com...
>> ...and back I am, because the 6420 errors have recurred WITHOUT any
>> changes to the system. We went home last night - everything left
>> switched on and connected to the LAN. Came in this morning, run up
>> Delphi (or any of the EXE's so produced) on ANY of the 5 workstations and
>> the 6420 error re-appeared.
>>
>> What gives, guys? I'm at my wits end with this one.
>>
>> Regards,
>>
>> Ian
>> "Ian Thompson" <irt@cygnetlodge.co.uk> wrote in message
>> news:44cb12b4@solutions.advantagedatabase.com...
>>> Hi Mark,
>>>
>>> Fascinating stuff. I tried removing the SIN_PORT entry and, sure enough,
>>> the system carries on working.
>>>
>>> The ADS server is CONFIGed to use port 2001 and that's the reason for my
>>> SIN_PORT assumptions. It's very weird (and, I accept, possibly entirely
>>> coincidental) that everything jumped to attention when I made this
>>> change. I have no clue as to what else might have changed - certainly
>>> there was no catastrophe or disorder in the shut-down or start-up that
>>> prompted the problem. And we haven't seen it before, so, bottom of the
>>> class for consistency!!
>>>
>>> Reading through the groups, it certainly seems to me that 6420 errors
>>> live in some mystical corners in the ADS world - there are lots of posts
>>> which claim inconsistency and/or difficulties of some kind. Can the
>>> 'auto-discovery' methods not be rationalised or simplified? Why have
>>> them at all? Why not force the establishment of the connection to be the
>>> responsibilty of the programmer? Questions from a naiive mind, I
>>> fear........
>>>
>>> Anyway, many thanks for your response - if I have any more weirdies,
>>> I'll be back......
>>>
>>> Regards,
>>>
>>> Ian
>>> "Mark Wilkins" <tired@of.spam> wrote in message
>>> news:44ca6f1e@solutions.advantagedatabase.com...
>>>> Hi Ian,
>>>>
>>>> The code does not read any value named "sin_port" from the ads.ini
>>>> file. The "sin_port" value reported in the call trace is referring to a
>>>> member of the windows socket structure (struct sockaddr_in). I think
>>>> "sin" stands for "socket address, internet style" ... it's defined in
>>>> the Microsoft header file winsock2.h if you are curious. Note that
>>>> without the Advantage comm layer source code in front of you, it is
>>>> pretty hard interpreting the contents of that trace file. I have
>>>> looked at lots of them, but I rarely can make sense of them unless I
>>>> look at the source code. That file is definitely not for end user
>>>> consumption.
>>>>
>>>> If you added an ads.ini entry as you stated below with LAN_PORT=2001,
>>>> and it did not work, then it seems possible that Advantage is not using
>>>> that port. Did you specify a port for it to use in the configuration
>>>> utility? If not, then I think it defaults to 6262. If that is the
>>>> case, then specifying an incorrect port number in ads.ini would
>>>> definitely cause some kind of error (possibly a 6420). Changing it
>>>> from "lan_port" to "sin_port" would effectively remove the entry, and
>>>> Advantage would not see the port number in the ads.ini file. I think
>>>> then that it would read the IP address from the LAN_IP entry and try to
>>>> contact the server using that address via multicast or possibly
>>>> netbios. The server would then respond with the correct port number to
>>>> use. You should be able to delete the sin_port entry from ads.ini, and
>>>> nothing will change.
>>>>
>>>> As far as question 1 goes, I am unsure. If it was working, and then
>>>> suddenly it stops working, then it is almost certain that something
>>>> changed. It seems quite possible that a system-wide restart could
>>>> definitely result in a change. For example, if you do not have a port
>>>> number specified for Advantage to use, then it is possible that it
>>>> might get a different port number when it restarted.
>>>>
>>>> HTH,
>>>> Mark Wilkins
>>>> Advantage R&D
>>>>
>>>>
>>>>
>>>>
>>>> "Ian Thompson" <irt@cygnetlodge.co.uk> wrote in message
>>>> news:44ca336a@solutions.advantagedatabase.com...
>>>>> Hi Everyone.
>>>>>
>>>>> I just thought I'd share this with you.
>>>>>
>>>>> We have a WS2K3 ADS 7.0 system with multiple clients. Mixed local and
>>>>> remote tables. Other stuff is immaterial, it transpires. After an
>>>>> orderly, system-wide restart, we started getting the dreaded 6420
>>>>> error with some clients, both with our app and the ARC. Searched the
>>>>> newsgroups, gleaned a bit about the discovery process and about
>>>>> eliminating it and hit upon the COMMCALLTRACE=1 ADS.INI flag and the
>>>>>
>>>>> [MYServerName]
>>>>> LAN_IP=10.0.0.111 (for example)
>>>>> LAN_PORT=2001
>>>>>
>>>>> entry for ADS.INI.
>>>>>
>>>>> Thought we'd cracked it. Tried it.
>>>>>
>>>>> No.
>>>>>
>>>>> So, looked at the ADSCOM.TXT file produced (due to COMMCALLTRACE=1)
>>>>> which said that it was using the correct IP for the server, but
>>>>> despite the above MYSERVERNAME entry, it reported no port was
>>>>> specified, when clearly it is, in the format stated by ADS tech guys.
>>>>> Strange stuff.
>>>>>
>>>>> Then noticed that the trace file mentioned that it had determined that
>>>>> SIN_PORT=0, i.e., not LAN_PORT=0 as you might expect if the text in
>>>>> the INI file had been read in.
>>>>>
>>>>> So, thinking "nah!",changed the INI to say SIN_PORT=2001 instead and -
>>>>> guess what!!!
>>>>>
>>>>> Yup, it works.
>>>>>
>>>>> SO, 2 things:
>>>>> (1) I have no idea why a perfectly working system suddenly decides not
>>>>> to function.
>>>>> (2) why does Advantage tech support not supply the correct info?
>>>>> What's SIN_PORT?
>>>>>
>>>>> Or am I missing something?
>>>>>
>>>>> Cheers,
>>>>>
>>>>> Ian Thompson
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>