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.

6610 errors since upgrading to version 9

23 posts in Networking Last posting was on 2010-07-22 08:55:06.0Z
rodgerv Posted on 2008-10-14 15:49:18.0Z
Reply-To: <rodgerv@nospam.calsense.com>
From: <rodgerv@nospam.calsense.com>
Newsgroups: Advantage.Networking
Subject: 6610 errors since upgrading to version 9
Date: Tue, 14 Oct 2008 08:49:18 -0700
Lines: 15
Organization: Calsense
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Windows Mail 6.0.6001.18000
X-MimeOLE: Produced By Microsoft MimeOLE V6.0.6001.18049
NNTP-Posting-Host: 64.73.242.98
Message-ID: <48f4be04@solutions.advantagedatabase.com>
X-Trace: 14 Oct 2008 09:43:00 -0700, 64.73.242.98
Path: solutions.advantagedatabase.com!solutions.advantagedatabase.com!64.73.242.98
Xref: solutions.advantagedatabase.com Advantage.Networking:812
Article PK: 1132230

I have a 10 user ADS server with a Delphi service client running on 8
computers and I seem to be having 6610 error issues with 2 of my computers.
One of them is an XP computer that used to work until upgrading the server
to ADS version 9. Now every day in the afternoon this computer reports a
6610 error. Also I have a brand new Vista computer that was put on to the
network at the same time the ADS was upgraded to version 9. It seems to
report 6610 errors more frequently than the other computer. I have looked
through the knowledge base but nothing has worked so far.

Any ideas?

Thanks in advance,

Rodger Van Kirk


Mark Wilkins Posted on 2008-10-15 18:02:00.0Z
From: "Mark Wilkins" <mark@no.email>
Newsgroups: Advantage.Networking
References: <48f4be04@solutions.advantagedatabase.com>
Subject: Re: 6610 errors since upgrading to version 9
Date: Wed, 15 Oct 2008 12:02:00 -0600
Lines: 49
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.3138
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
X-RFC2646: Format=Flowed; Response
NNTP-Posting-Host: 10.24.38.228
Message-ID: <48f62e9d@solutions.advantagedatabase.com>
X-Trace: 15 Oct 2008 11:55:41 -0700, 10.24.38.228
Path: solutions.advantagedatabase.com!solutions.advantagedatabase.com!10.24.38.228
Xref: solutions.advantagedatabase.com Advantage.Networking:813
Article PK: 1132232

Hi,

I'm not aware of changes in the communications code that would explain this.
What version did you upgrade from?

It is possible that hardware changes could cause problems. Were there any
changes to the network when you upgraded to v9.0? For example, was a router
added or changed? A new switch? If so, then there might be some kind of
packet fragmentation. If so, you could test this by adding
"PACKET_SIZE=512" to the [SETTINGS] section of ads.ini.

Does the error log have any 7020 errors in it? These are logged by the
server if it drops connections because it decided that a client had been
disconnected. For example, if a client was inactive and the "keepalive"
packets were not reaching the server, then it would think that the client
was gone and would remove that connection.

Is there certain types of operations that seem to cause this problem? Is it
during connection time? After periods of inactivity? During large reads of
data?

While this would not answer the question of why it is happening, you might
try using TCP/IP for communications. You can add "use_tcp_ip=1" to the
[SETTINGS] section of ads.ini to force TCP/IP communications (instead of
UDP). This requires that the client be at least 8.x.

Mark Wilkins
Advantage R&D

<rodgerv@nospam.calsense.com> wrote in message
news:48f4be04@solutions.advantagedatabase.com...
>I have a 10 user ADS server with a Delphi service client running on 8
>computers and I seem to be having 6610 error issues with 2 of my computers.
>One of them is an XP computer that used to work until upgrading the server
>to ADS version 9. Now every day in the afternoon this computer reports a
>6610 error. Also I have a brand new Vista computer that was put on to the
>network at the same time the ADS was upgraded to version 9. It seems to
>report 6610 errors more frequently than the other computer. I have looked
>through the knowledge base but nothing has worked so far.
>
> Any ideas?
>
> Thanks in advance,
>
> Rodger Van Kirk


rodgerv Posted on 2008-10-15 18:14:34.0Z
Reply-To: <rodgerv@nospam.calsense.com>
From: <rodgerv@nospam.calsense.com>
Newsgroups: Advantage.Networking
References: <48f4be04@solutions.advantagedatabase.com> <48f62e9d@solutions.advantagedatabase.com>
In-Reply-To: <48f62e9d@solutions.advantagedatabase.com>
Subject: Re: 6610 errors since upgrading to version 9
Date: Wed, 15 Oct 2008 11:14:34 -0700
Lines: 70
Organization: Calsense
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=response
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Windows Mail 6.0.6001.18000
X-MimeOLE: Produced By Microsoft MimeOLE V6.0.6001.18049
NNTP-Posting-Host: 64.73.242.98
Message-ID: <48f63192@solutions.advantagedatabase.com>
X-Trace: 15 Oct 2008 12:08:18 -0700, 64.73.242.98
Path: solutions.advantagedatabase.com!solutions.advantagedatabase.com!64.73.242.98
Xref: solutions.advantagedatabase.com Advantage.Networking:814
Article PK: 1132234

We were using a server version of 8.1. There were no other network changes.

There are a lot (10 or so a day) of 7020 errors that also appear to have
started after upgrading to version 9. They don't necessarily coincide with
the same timestamps.

It does seem to happen at a particular time but I'm not completely sure what
the operation is it might be after a period of inactivity. and large reads
of data (or at least what my app would consider a large read 50 or so
records).

Unfortunately do to our clients and the way our application is distributed
the client side has to stay at version 7.

Rodger Van Kirk

"Mark Wilkins" <mark@no.email> wrote in message
news:48f62e9d@solutions.advantagedatabase.com...
> Hi,
>
> I'm not aware of changes in the communications code that would explain
> this. What version did you upgrade from?
>
> It is possible that hardware changes could cause problems. Were there any
> changes to the network when you upgraded to v9.0? For example, was a
> router added or changed? A new switch? If so, then there might be some
> kind of packet fragmentation. If so, you could test this by adding
> "PACKET_SIZE=512" to the [SETTINGS] section of ads.ini.
>
> Does the error log have any 7020 errors in it? These are logged by the
> server if it drops connections because it decided that a client had been
> disconnected. For example, if a client was inactive and the "keepalive"
> packets were not reaching the server, then it would think that the client
> was gone and would remove that connection.
>
> Is there certain types of operations that seem to cause this problem? Is
> it during connection time? After periods of inactivity? During large
> reads of data?
>
> While this would not answer the question of why it is happening, you might
> try using TCP/IP for communications. You can add "use_tcp_ip=1" to the
> [SETTINGS] section of ads.ini to force TCP/IP communications (instead of
> UDP). This requires that the client be at least 8.x.
>
> Mark Wilkins
> Advantage R&D
>
>
>
> <rodgerv@nospam.calsense.com> wrote in message
> news:48f4be04@solutions.advantagedatabase.com...
>>I have a 10 user ADS server with a Delphi service client running on 8
>>computers and I seem to be having 6610 error issues with 2 of my
>>computers. One of them is an XP computer that used to work until upgrading
>>the server to ADS version 9. Now every day in the afternoon this computer
>>reports a 6610 error. Also I have a brand new Vista computer that was put
>>on to the network at the same time the ADS was upgraded to version 9. It
>>seems to report 6610 errors more frequently than the other computer. I
>>have looked through the knowledge base but nothing has worked so far.
>>
>> Any ideas?
>>
>> Thanks in advance,
>>
>> Rodger Van Kirk
>
>


Mark Wilkins Posted on 2008-10-15 20:32:15.0Z
From: "Mark Wilkins" <mark@no.email>
Newsgroups: Advantage.Networking
References: <48f4be04@solutions.advantagedatabase.com> <48f62e9d@solutions.advantagedatabase.com> <48f63192@solutions.advantagedatabase.com>
Subject: Re: 6610 errors since upgrading to version 9
Date: Wed, 15 Oct 2008 14:32:15 -0600
Lines: 120
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.3138
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
X-RFC2646: Format=Flowed; Response
NNTP-Posting-Host: 10.24.38.228
Message-ID: <48f651d4@solutions.advantagedatabase.com>
X-Trace: 15 Oct 2008 14:25:56 -0700, 10.24.38.228
Path: solutions.advantagedatabase.com!solutions.advantagedatabase.com!10.24.38.228
Xref: solutions.advantagedatabase.com Advantage.Networking:815
Article PK: 1132233

It seems possible that the 7020 is the problem that is leading to the 6610
errors. The 7020 simply means that the server did not hear from the client
in the specified timeout period and so decided it was no longer active. If
the client then tries to communicate again, the server just ignores those
packets since the user is no longer logged in.

I think the error log shows the user name that was logged out with that 7020
error. There should be a "more_info" field in the ads_err.adt with the
login name and IP address of the client. Do those names correspond to the
clients getting the 6610? If there is not a more_info field, you can
rename/save/move the existing ads_err.* files and Advantage will create a
new one with that field included.

Here are some things to try:
It is maybe worth trying the PACKET_SIZE=512 entry in the ads.ini file.
That will limit the packet size to avoid any fragmentation potential.
However, I really don't think that is it. The packet sizes did not change
between 7.x and 9.x

Change the server's client timeout value. In the config utility (I'm
assuming ADS for Windows), there is a "Configuration Utility" tab with a
Communications tab under that. Change the Client Time Out value to a
smaller value. I think the default is 240; maybe change it to 60. That
value determines how often the client sends keepalive packets to the server
in periods of inactivity. The period is 1/4th of the timeout. So changing
it to 60 means the client will send a packet about every 15 seconds. If
there is some kind of odd problem on the PC or network where those packets
are not getting through, it may (non-intuitively) help if they are sent more
often.

One other thing too. If you put a commcalltrace=1 in a client's ads.ini
file that is experiencing these 6610 errors, it will cause it to create a
file named adscom.txt with some information about connecting and it may
include error info about the 6610 depending on when/where it occurs. If you
get such a file, send it to advantage@sybase.com attn: Mark Wilkins. I
might be able to decipher it.

I will test a bit here with a 7.x client and 9.x server to see if I can come
up with something.

Mark Wilkins
Advantage R&D

<rodgerv@nospam.calsense.com> wrote in message
news:48f63192@solutions.advantagedatabase.com...
> We were using a server version of 8.1. There were no other network
> changes.
>
> There are a lot (10 or so a day) of 7020 errors that also appear to have
> started after upgrading to version 9. They don't necessarily coincide
> with the same timestamps.
>
> It does seem to happen at a particular time but I'm not completely sure
> what the operation is it might be after a period of inactivity. and large
> reads of data (or at least what my app would consider a large read 50 or
> so records).
>
> Unfortunately do to our clients and the way our application is distributed
> the client side has to stay at version 7.
>
> Rodger Van Kirk
>
>
>
> "Mark Wilkins" <mark@no.email> wrote in message
> news:48f62e9d@solutions.advantagedatabase.com...
>> Hi,
>>
>> I'm not aware of changes in the communications code that would explain
>> this. What version did you upgrade from?
>>
>> It is possible that hardware changes could cause problems. Were there
>> any changes to the network when you upgraded to v9.0? For example, was a
>> router added or changed? A new switch? If so, then there might be some
>> kind of packet fragmentation. If so, you could test this by adding
>> "PACKET_SIZE=512" to the [SETTINGS] section of ads.ini.
>>
>> Does the error log have any 7020 errors in it? These are logged by the
>> server if it drops connections because it decided that a client had been
>> disconnected. For example, if a client was inactive and the "keepalive"
>> packets were not reaching the server, then it would think that the client
>> was gone and would remove that connection.
>>
>> Is there certain types of operations that seem to cause this problem? Is
>> it during connection time? After periods of inactivity? During large
>> reads of data?
>>
>> While this would not answer the question of why it is happening, you
>> might try using TCP/IP for communications. You can add "use_tcp_ip=1" to
>> the [SETTINGS] section of ads.ini to force TCP/IP communications (instead
>> of UDP). This requires that the client be at least 8.x.
>>
>> Mark Wilkins
>> Advantage R&D
>>
>>
>>
>> <rodgerv@nospam.calsense.com> wrote in message
>> news:48f4be04@solutions.advantagedatabase.com...
>>>I have a 10 user ADS server with a Delphi service client running on 8
>>>computers and I seem to be having 6610 error issues with 2 of my
>>>computers. One of them is an XP computer that used to work until
>>>upgrading the server to ADS version 9. Now every day in the afternoon
>>>this computer reports a 6610 error. Also I have a brand new Vista
>>>computer that was put on to the network at the same time the ADS was
>>>upgraded to version 9. It seems to report 6610 errors more frequently
>>>than the other computer. I have looked through the knowledge base but
>>>nothing has worked so far.
>>>
>>> Any ideas?
>>>
>>> Thanks in advance,
>>>
>>> Rodger Van Kirk
>>
>>
>


rodgerv Posted on 2008-10-28 23:23:56.0Z
Reply-To: <rodgerv@nospam.calsense.com>
From: <rodgerv@nospam.calsense.com>
Newsgroups: Advantage.Networking
References: <48f4be04@solutions.advantagedatabase.com> <48f62e9d@solutions.advantagedatabase.com> <48f63192@solutions.advantagedatabase.com> <48f651d4@solutions.advantagedatabase.com>
In-Reply-To: <48f651d4@solutions.advantagedatabase.com>
Subject: Re: 6610 errors since upgrading to version 9
Date: Tue, 28 Oct 2008 16:23:56 -0700
Lines: 133
Organization: Calsense
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=response
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Windows Mail 6.0.6001.18000
X-MimeOLE: Produced By Microsoft MimeOLE V6.0.6001.18049
NNTP-Posting-Host: 64.73.242.98
Message-ID: <49079d8e@solutions.advantagedatabase.com>
X-Trace: 28 Oct 2008 17:17:34 -0700, 64.73.242.98
Path: solutions.advantagedatabase.com!solutions.advantagedatabase.com!64.73.242.98
Xref: solutions.advantagedatabase.com Advantage.Networking:818
Article PK: 1132237

Sorry got side tracked here at work.

I did set the packet size to 512 and it seemed to make no difference. Also
the user that is listed in the ads_err table is the computer name not the
user that was set up in the data dictionary. Should it be the computer
name? I have not adjusted the time out or the commcalltrace yet I will do
those today.

Rodger Van Kirk

"Mark Wilkins" <mark@no.email> wrote in message
news:48f651d4@solutions.advantagedatabase.com...
> It seems possible that the 7020 is the problem that is leading to the 6610
> errors. The 7020 simply means that the server did not hear from the
> client in the specified timeout period and so decided it was no longer
> active. If the client then tries to communicate again, the server just
> ignores those packets since the user is no longer logged in.
>
> I think the error log shows the user name that was logged out with that
> 7020 error. There should be a "more_info" field in the ads_err.adt with
> the login name and IP address of the client. Do those names correspond to
> the clients getting the 6610? If there is not a more_info field, you can
> rename/save/move the existing ads_err.* files and Advantage will create a
> new one with that field included.
>
> Here are some things to try:
> It is maybe worth trying the PACKET_SIZE=512 entry in the ads.ini file.
> That will limit the packet size to avoid any fragmentation potential.
> However, I really don't think that is it. The packet sizes did not change
> between 7.x and 9.x
>
> Change the server's client timeout value. In the config utility (I'm
> assuming ADS for Windows), there is a "Configuration Utility" tab with a
> Communications tab under that. Change the Client Time Out value to a
> smaller value. I think the default is 240; maybe change it to 60. That
> value determines how often the client sends keepalive packets to the
> server in periods of inactivity. The period is 1/4th of the timeout. So
> changing it to 60 means the client will send a packet about every 15
> seconds. If there is some kind of odd problem on the PC or network where
> those packets are not getting through, it may (non-intuitively) help if
> they are sent more often.
>
> One other thing too. If you put a commcalltrace=1 in a client's ads.ini
> file that is experiencing these 6610 errors, it will cause it to create a
> file named adscom.txt with some information about connecting and it may
> include error info about the 6610 depending on when/where it occurs. If
> you get such a file, send it to advantage@sybase.com attn: Mark Wilkins.
> I might be able to decipher it.
>
> I will test a bit here with a 7.x client and 9.x server to see if I can
> come up with something.
>
> Mark Wilkins
> Advantage R&D
>
>
> <rodgerv@nospam.calsense.com> wrote in message
> news:48f63192@solutions.advantagedatabase.com...
>> We were using a server version of 8.1. There were no other network
>> changes.
>>
>> There are a lot (10 or so a day) of 7020 errors that also appear to have
>> started after upgrading to version 9. They don't necessarily coincide
>> with the same timestamps.
>>
>> It does seem to happen at a particular time but I'm not completely sure
>> what the operation is it might be after a period of inactivity. and large
>> reads of data (or at least what my app would consider a large read 50 or
>> so records).
>>
>> Unfortunately do to our clients and the way our application is
>> distributed the client side has to stay at version 7.
>>
>> Rodger Van Kirk
>>
>>
>>
>> "Mark Wilkins" <mark@no.email> wrote in message
>> news:48f62e9d@solutions.advantagedatabase.com...
>>> Hi,
>>>
>>> I'm not aware of changes in the communications code that would explain
>>> this. What version did you upgrade from?
>>>
>>> It is possible that hardware changes could cause problems. Were there
>>> any changes to the network when you upgraded to v9.0? For example, was
>>> a router added or changed? A new switch? If so, then there might be
>>> some kind of packet fragmentation. If so, you could test this by adding
>>> "PACKET_SIZE=512" to the [SETTINGS] section of ads.ini.
>>>
>>> Does the error log have any 7020 errors in it? These are logged by the
>>> server if it drops connections because it decided that a client had been
>>> disconnected. For example, if a client was inactive and the "keepalive"
>>> packets were not reaching the server, then it would think that the
>>> client was gone and would remove that connection.
>>>
>>> Is there certain types of operations that seem to cause this problem?
>>> Is it during connection time? After periods of inactivity? During
>>> large reads of data?
>>>
>>> While this would not answer the question of why it is happening, you
>>> might try using TCP/IP for communications. You can add "use_tcp_ip=1"
>>> to the [SETTINGS] section of ads.ini to force TCP/IP communications
>>> (instead of UDP). This requires that the client be at least 8.x.
>>>
>>> Mark Wilkins
>>> Advantage R&D
>>>
>>>
>>>
>>> <rodgerv@nospam.calsense.com> wrote in message
>>> news:48f4be04@solutions.advantagedatabase.com...
>>>>I have a 10 user ADS server with a Delphi service client running on 8
>>>>computers and I seem to be having 6610 error issues with 2 of my
>>>>computers. One of them is an XP computer that used to work until
>>>>upgrading the server to ADS version 9. Now every day in the afternoon
>>>>this computer reports a 6610 error. Also I have a brand new Vista
>>>>computer that was put on to the network at the same time the ADS was
>>>>upgraded to version 9. It seems to report 6610 errors more frequently
>>>>than the other computer. I have looked through the knowledge base but
>>>>nothing has worked so far.
>>>>
>>>> Any ideas?
>>>>
>>>> Thanks in advance,
>>>>
>>>> Rodger Van Kirk
>>>
>>>
>>
>
>


Mark Wilkins Posted on 2008-10-29 16:30:05.0Z
From: "Mark Wilkins" <mark@no.email>
Newsgroups: Advantage.Networking
References: <48f4be04@solutions.advantagedatabase.com> <48f62e9d@solutions.advantagedatabase.com> <48f63192@solutions.advantagedatabase.com> <48f651d4@solutions.advantagedatabase.com> <49079d8e@solutions.advantagedatabase.com>
Subject: Re: 6610 errors since upgrading to version 9
Date: Wed, 29 Oct 2008 10:30:05 -0600
Lines: 24
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.3138
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
X-RFC2646: Format=Flowed; Response
NNTP-Posting-Host: 10.24.38.228
Message-ID: <49088e0f@solutions.advantagedatabase.com>
X-Trace: 29 Oct 2008 10:23:43 -0700, 10.24.38.228
Path: solutions.advantagedatabase.com!solutions.advantagedatabase.com!10.24.38.228
Xref: solutions.advantagedatabase.com Advantage.Networking:819
Article PK: 1132238

The error log shows both computer name and user name. The somewhat
innappropriately named "FileName" field I think shows the computer name.
The "MoreInfo" field should show more details. I think the computer name is
the one you want in order to correlate the 6610 to the 7020.

What is the client timeout value setting at the server?

Mark Wilkins
Advantage R&D

<rodgerv@nospam.calsense.com> wrote in message
news:49079d8e@solutions.advantagedatabase.com...
> Sorry got side tracked here at work.
>
> I did set the packet size to 512 and it seemed to make no difference.
> Also the user that is listed in the ads_err table is the computer name not
> the user that was set up in the data dictionary. Should it be the
> computer name? I have not adjusted the time out or the commcalltrace yet
> I will do those today.
>
> Rodger Van Kirk
>


rodgerv Posted on 2008-10-29 20:30:20.0Z
Reply-To: <rodgerv@nospam.calsense.com>
From: <rodgerv@nospam.calsense.com>
Newsgroups: Advantage.Networking
References: <48f4be04@solutions.advantagedatabase.com> <48f62e9d@solutions.advantagedatabase.com> <48f63192@solutions.advantagedatabase.com> <48f651d4@solutions.advantagedatabase.com> <49079d8e@solutions.advantagedatabase.com> <49088e0f@solutions.advantagedatabase.com>
In-Reply-To: <49088e0f@solutions.advantagedatabase.com>
Subject: Re: 6610 errors since upgrading to version 9
Date: Wed, 29 Oct 2008 13:30:20 -0700
Lines: 33
Organization: Calsense
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=response
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Windows Mail 6.0.6001.18000
X-MimeOLE: Produced By Microsoft MimeOLE V6.0.6001.18049
NNTP-Posting-Host: 64.73.242.98
Message-ID: <4908c660@solutions.advantagedatabase.com>
X-Trace: 29 Oct 2008 14:24:00 -0700, 64.73.242.98
Path: solutions.advantagedatabase.com!solutions.advantagedatabase.com!64.73.242.98
Xref: solutions.advantagedatabase.com Advantage.Networking:820
Article PK: 1132239

It was set to 120. I changed it to 60 as one of the previous posts
suggested.

Rodger Van Kirk

"Mark Wilkins" <mark@no.email> wrote in message
news:49088e0f@solutions.advantagedatabase.com...
> The error log shows both computer name and user name. The somewhat
> innappropriately named "FileName" field I think shows the computer name.
> The "MoreInfo" field should show more details. I think the computer name
> is the one you want in order to correlate the 6610 to the 7020.
>
> What is the client timeout value setting at the server?
>
> Mark Wilkins
> Advantage R&D
>
> <rodgerv@nospam.calsense.com> wrote in message
> news:49079d8e@solutions.advantagedatabase.com...
>> Sorry got side tracked here at work.
>>
>> I did set the packet size to 512 and it seemed to make no difference.
>> Also the user that is listed in the ads_err table is the computer name
>> not the user that was set up in the data dictionary. Should it be the
>> computer name? I have not adjusted the time out or the commcalltrace yet
>> I will do those today.
>>
>> Rodger Van Kirk
>>
>
>


Mark Wilkins Posted on 2008-10-29 22:00:53.0Z
From: "Mark Wilkins" <mark@no.email>
Newsgroups: Advantage.Networking
References: <48f4be04@solutions.advantagedatabase.com> <48f62e9d@solutions.advantagedatabase.com> <48f63192@solutions.advantagedatabase.com> <48f651d4@solutions.advantagedatabase.com> <49079d8e@solutions.advantagedatabase.com> <49088e0f@solutions.advantagedatabase.com> <4908c660@solutions.advantagedatabase.com>
Subject: Re: 6610 errors since upgrading to version 9
Date: Wed, 29 Oct 2008 16:00:53 -0600
Lines: 56
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.3138
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
X-RFC2646: Format=Flowed; Response
NNTP-Posting-Host: 10.24.38.228
Message-ID: <4908db98@solutions.advantagedatabase.com>
X-Trace: 29 Oct 2008 15:54:32 -0700, 10.24.38.228
Path: solutions.advantagedatabase.com!solutions.advantagedatabase.com!10.24.38.228
Xref: solutions.advantagedatabase.com Advantage.Networking:821
Article PK: 1132240

I'm uncertain what could cause this. I have a few more questions:
-What OS is the server running?
-Are you using an Internet connection type (ADS_AIS_SERVER) or the "typical"
remote type (ADS_REMOTE_SERVER)?
-Are you using communications encryption or compression?
-Is the server multihomed (multiple NICs)?

One thing that changed between v8.x and v9.x in the server was the default
"Internet" timeout. I have been assuming you were using ADS_REMOTE_SERVER
connection types. If, though, it is ADS_AIS_SERVER, then the client timeout
setting I mentioned will have no affect. It is a different configuration
parameter and is not available from the configuration utility. The help
file discusses how to change it (registry value under
INTERNET_CLIENT_TIMEOUT). In v8.x, the default timeout was 10 minutes. It
was changed to 2 minutes in 9.x.

Mark Wilkins
Advantage R&D

<rodgerv@nospam.calsense.com> wrote in message
news:4908c660@solutions.advantagedatabase.com...
> It was set to 120. I changed it to 60 as one of the previous posts
> suggested.
>
> Rodger Van Kirk
>
>
> "Mark Wilkins" <mark@no.email> wrote in message
> news:49088e0f@solutions.advantagedatabase.com...
>> The error log shows both computer name and user name. The somewhat
>> innappropriately named "FileName" field I think shows the computer name.
>> The "MoreInfo" field should show more details. I think the computer name
>> is the one you want in order to correlate the 6610 to the 7020.
>>
>> What is the client timeout value setting at the server?
>>
>> Mark Wilkins
>> Advantage R&D
>>
>> <rodgerv@nospam.calsense.com> wrote in message
>> news:49079d8e@solutions.advantagedatabase.com...
>>> Sorry got side tracked here at work.
>>>
>>> I did set the packet size to 512 and it seemed to make no difference.
>>> Also the user that is listed in the ads_err table is the computer name
>>> not the user that was set up in the data dictionary. Should it be the
>>> computer name? I have not adjusted the time out or the commcalltrace
>>> yet I will do those today.
>>>
>>> Rodger Van Kirk
>>>
>>
>>
>


rodgerv Posted on 2008-11-05 16:18:21.0Z
Reply-To: <rodgerv@nospam.calsense.com>
From: <rodgerv@nospam.calsense.com>
Newsgroups: Advantage.Networking
References: <48f4be04@solutions.advantagedatabase.com> <48f62e9d@solutions.advantagedatabase.com> <48f63192@solutions.advantagedatabase.com> <48f651d4@solutions.advantagedatabase.com> <49079d8e@solutions.advantagedatabase.com> <49088e0f@solutions.advantagedatabase.com> <4908c660@solutions.advantagedatabase.com> <4908db98@solutions.advantagedatabase.com>
In-Reply-To: <4908db98@solutions.advantagedatabase.com>
Subject: Re: 6610 errors since upgrading to version 9
Date: Wed, 5 Nov 2008 08:18:21 -0800
Lines: 68
Organization: Calsense
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=response
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Windows Mail 6.0.6001.18000
X-MimeOLE: Produced By Microsoft MimeOLE V6.0.6001.18049
NNTP-Posting-Host: 64.73.242.98
Message-ID: <4911c5d0@solutions.advantagedatabase.com>
X-Trace: 5 Nov 2008 09:12:00 -0700, 64.73.242.98
Path: solutions.advantagedatabase.com!solutions.advantagedatabase.com!64.73.242.98
Xref: solutions.advantagedatabase.com Advantage.Networking:827
Article PK: 1132246

Here is the answer to your questions.

Windows Server 2003
ADS_REMOTE_SERVER
no encryption and compression for internet
It does have multiple NICs but only 1 is in use.

Rodger Van Kirk

"Mark Wilkins" <mark@no.email> wrote in message
news:4908db98@solutions.advantagedatabase.com...
> I'm uncertain what could cause this. I have a few more questions:
> -What OS is the server running?
> -Are you using an Internet connection type (ADS_AIS_SERVER) or the
> "typical" remote type (ADS_REMOTE_SERVER)?
> -Are you using communications encryption or compression?
> -Is the server multihomed (multiple NICs)?
>
> One thing that changed between v8.x and v9.x in the server was the default
> "Internet" timeout. I have been assuming you were using ADS_REMOTE_SERVER
> connection types. If, though, it is ADS_AIS_SERVER, then the client
> timeout setting I mentioned will have no affect. It is a different
> configuration parameter and is not available from the configuration
> utility. The help file discusses how to change it (registry value under
> INTERNET_CLIENT_TIMEOUT). In v8.x, the default timeout was 10 minutes.
> It was changed to 2 minutes in 9.x.
>
> Mark Wilkins
> Advantage R&D
>
> <rodgerv@nospam.calsense.com> wrote in message
> news:4908c660@solutions.advantagedatabase.com...
>> It was set to 120. I changed it to 60 as one of the previous posts
>> suggested.
>>
>> Rodger Van Kirk
>>
>>
>> "Mark Wilkins" <mark@no.email> wrote in message
>> news:49088e0f@solutions.advantagedatabase.com...
>>> The error log shows both computer name and user name. The somewhat
>>> innappropriately named "FileName" field I think shows the computer name.
>>> The "MoreInfo" field should show more details. I think the computer name
>>> is the one you want in order to correlate the 6610 to the 7020.
>>>
>>> What is the client timeout value setting at the server?
>>>
>>> Mark Wilkins
>>> Advantage R&D
>>>
>>> <rodgerv@nospam.calsense.com> wrote in message
>>> news:49079d8e@solutions.advantagedatabase.com...
>>>> Sorry got side tracked here at work.
>>>>
>>>> I did set the packet size to 512 and it seemed to make no difference.
>>>> Also the user that is listed in the ads_err table is the computer name
>>>> not the user that was set up in the data dictionary. Should it be the
>>>> computer name? I have not adjusted the time out or the commcalltrace
>>>> yet I will do those today.
>>>>
>>>> Rodger Van Kirk
>>>>
>>>
>>>
>>
>
>


Mark Wilkins Posted on 2008-11-05 17:41:15.0Z
From: "Mark Wilkins" <mark@no.email>
Newsgroups: Advantage.Networking
References: <48f4be04@solutions.advantagedatabase.com> <48f62e9d@solutions.advantagedatabase.com> <48f63192@solutions.advantagedatabase.com> <48f651d4@solutions.advantagedatabase.com> <49079d8e@solutions.advantagedatabase.com> <49088e0f@solutions.advantagedatabase.com> <4908c660@solutions.advantagedatabase.com> <4908db98@solutions.advantagedatabase.com> <4911c5d0@solutions.advantagedatabase.com>
Subject: Re: 6610 errors since upgrading to version 9
Date: Wed, 5 Nov 2008 10:41:15 -0700
Lines: 25
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.3138
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
X-RFC2646: Format=Flowed; Response
NNTP-Posting-Host: 10.24.38.228
Message-ID: <4911d93c@solutions.advantagedatabase.com>
X-Trace: 5 Nov 2008 10:34:52 -0700, 10.24.38.228
Path: solutions.advantagedatabase.com!solutions.advantagedatabase.com!10.24.38.228
Xref: solutions.advantagedatabase.com Advantage.Networking:829
Article PK: 1132248

Thanks for the information; unfortunately, it doesn't give me any additional
ideas. I posted yesterday on this thread about the change in timeout; I
assume you probably saw the post, but if not, you may want to read it.
Which version of 8.1 were you using? Was it older than 8.10.0.26? If it
was a version older than that, then it may be that this is caused by that
reduction in timeout. You could try changing the CLIENT_TIMEOUT value back
up to 240. And if you do, and it eliminates the 6610 problems, I would be
very interested in learning about that. It's still not clear to me how the
2 minute timeout could be an issue on a healthy network.

Mark Wilkins
Advantage R&D

<rodgerv@nospam.calsense.com> wrote in message
news:4911c5d0@solutions.advantagedatabase.com...
> Here is the answer to your questions.
>
> Windows Server 2003
> ADS_REMOTE_SERVER
> no encryption and compression for internet
> It does have multiple NICs but only 1 is in use.
>
> Rodger Van Kirk


Bill Seven Posted on 2008-10-27 13:06:51.0Z
Reply-To: "Bill Seven" <bill_nospam@include.com>
From: "Bill Seven" <bill_nospam@include.com>
Newsgroups: Advantage.Networking
References: <48f4be04@solutions.advantagedatabase.com> <48f62e9d@solutions.advantagedatabase.com> <48f63192@solutions.advantagedatabase.com>
In-Reply-To: <48f63192@solutions.advantagedatabase.com>
Subject: Re: 6610 errors since upgrading to version 9
Date: Mon, 27 Oct 2008 09:06:51 -0400
Lines: 8
Organization: Include Software
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=response
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Windows Mail 6.0.6001.18000
X-MimeOLE: Produced By Microsoft MimeOLE V6.0.6001.18049
NNTP-Posting-Host: 24.35.113.117
Message-ID: <4905bb76@solutions.advantagedatabase.com>
X-Trace: 27 Oct 2008 07:00:38 -0700, 24.35.113.117
Path: solutions.advantagedatabase.com!solutions.advantagedatabase.com!24.35.113.117
Xref: solutions.advantagedatabase.com Advantage.Networking:816
Article PK: 1132235

Hi Rodger,

Did Mark's suggestions solve your errors? We have had a similar situation
with many 6610 errors popping up on XP clients connected to Windows 2003
server. I'm also trying Mark's suggestions to see if they help.

Bill


Mark Wilkins Posted on 2008-10-27 14:08:12.0Z
From: "Mark Wilkins" <mark@no.email>
Newsgroups: Advantage.Networking
References: <48f4be04@solutions.advantagedatabase.com> <48f62e9d@solutions.advantagedatabase.com> <48f63192@solutions.advantagedatabase.com> <4905bb76@solutions.advantagedatabase.com>
Subject: Re: 6610 errors since upgrading to version 9
Date: Mon, 27 Oct 2008 08:08:12 -0600
Lines: 20
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.3138
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
X-RFC2646: Format=Flowed; Response
NNTP-Posting-Host: 10.24.38.228
Message-ID: <4905c9ce@solutions.advantagedatabase.com>
X-Trace: 27 Oct 2008 08:01:50 -0700, 10.24.38.228
Path: solutions.advantagedatabase.com!solutions.advantagedatabase.com!10.24.38.228
Xref: solutions.advantagedatabase.com Advantage.Networking:817
Article PK: 1132236

Hi Bill,

Are the clients using v7.x as well in your situation? I tested various
scenarios using a v7.1 client and 9.0 server but could not produce any
problems. So I am still unsure what it might be.

Mark Wilkins
Advantage R&D

"Bill Seven" <bill_nospam@include.com> wrote in message
news:4905bb76@solutions.advantagedatabase.com...
> Hi Rodger,
>
> Did Mark's suggestions solve your errors? We have had a similar situation
> with many 6610 errors popping up on XP clients connected to Windows 2003
> server. I'm also trying Mark's suggestions to see if they help.
>
> Bill


evaded Posted on 2008-10-30 15:47:23.0Z
From: "evaded" <not@set.yet>
Newsgroups: Advantage.Networking
References: <48f4be04@solutions.advantagedatabase.com> <48f62e9d@solutions.advantagedatabase.com> <48f63192@solutions.advantagedatabase.com> <4905bb76@solutions.advantagedatabase.com>
Subject: Re: 6610 errors since upgrading to version 9
Date: Thu, 30 Oct 2008 11:47:23 -0400
Lines: 19
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.5512
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
X-RFC2646: Format=Flowed; Response
NNTP-Posting-Host: 207.35.108.169
Message-ID: <4909d571@solutions.advantagedatabase.com>
X-Trace: 30 Oct 2008 09:40:33 -0700, 207.35.108.169
Path: solutions.advantagedatabase.com!solutions.advantagedatabase.com!207.35.108.169
Xref: solutions.advantagedatabase.com Advantage.Networking:822
Article PK: 1132241

We're experiencing the same problem with ADS9 Linux Server on SUSE9/OES.
Users on W2000/XP are getting 6610 and the errors 7020 logged in the
ads_err.adt relates to those same users.

However our clients are still with v8.1 dlls. We did not update those since
everything worked fine in our tests.


"Bill Seven" <bill_nospam@include.com> a ?crit dans le message de news:
4905bb76@solutions.advantagedatabase.com...

> Hi Rodger,
>
> Did Mark's suggestions solve your errors? We have had a similar situation
> with many 6610 errors popping up on XP clients connected to Windows 2003
> server. I'm also trying Mark's suggestions to see if they help.
>
> Bill


Mark Wilkins Posted on 2008-10-30 19:30:48.0Z
From: "Mark Wilkins" <mark@no.email>
Newsgroups: Advantage.Networking
References: <48f4be04@solutions.advantagedatabase.com> <48f62e9d@solutions.advantagedatabase.com> <48f63192@solutions.advantagedatabase.com> <4905bb76@solutions.advantagedatabase.com> <4909d571@solutions.advantagedatabase.com>
Subject: Re: 6610 errors since upgrading to version 9
Date: Thu, 30 Oct 2008 13:30:48 -0600
Lines: 32
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.3138
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
X-RFC2646: Format=Flowed; Response
NNTP-Posting-Host: 10.24.38.228
Message-ID: <490a09ea@solutions.advantagedatabase.com>
X-Trace: 30 Oct 2008 13:24:26 -0700, 10.24.38.228
Path: solutions.advantagedatabase.com!solutions.advantagedatabase.com!10.24.38.228
Xref: solutions.advantagedatabase.com Advantage.Networking:823
Article PK: 1132242

Hi,

What connection type are you using? Is it 2 (ADS_REMOTE_SERVER) or 4
(ADS_AIS_SERVER)?

Mark Wilkins
Advantage R&D

"evaded" <not@set.yet> wrote in message
news:4909d571@solutions.advantagedatabase.com...
> We're experiencing the same problem with ADS9 Linux Server on SUSE9/OES.
> Users on W2000/XP are getting 6610 and the errors 7020 logged in the
> ads_err.adt relates to those same users.
>
> However our clients are still with v8.1 dlls. We did not update those
> since everything worked fine in our tests.
>
>
> "Bill Seven" <bill_nospam@include.com> a ?crit dans le message de news:
> 4905bb76@solutions.advantagedatabase.com...
>> Hi Rodger,
>>
>> Did Mark's suggestions solve your errors? We have had a similar
>> situation with many 6610 errors popping up on XP clients connected to
>> Windows 2003 server. I'm also trying Mark's suggestions to see if they
>> help.
>>
>> Bill
>
>


evaded Posted on 2008-10-31 20:39:21.0Z
From: "evaded" <not@set.yet>
Newsgroups: Advantage.Networking
References: <48f4be04@solutions.advantagedatabase.com> <48f62e9d@solutions.advantagedatabase.com> <48f63192@solutions.advantagedatabase.com> <4905bb76@solutions.advantagedatabase.com> <4909d571@solutions.advantagedatabase.com> <490a09ea@solutions.advantagedatabase.com>
Subject: Re: 6610 errors since upgrading to version 9
Date: Fri, 31 Oct 2008 16:39:21 -0400
Lines: 15
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.5512
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
X-RFC2646: Format=Flowed; Response
NNTP-Posting-Host: 207.35.108.169
Message-ID: <490b6b5d@solutions.advantagedatabase.com>
X-Trace: 31 Oct 2008 14:32:29 -0700, 207.35.108.169
Path: solutions.advantagedatabase.com!solutions.advantagedatabase.com!207.35.108.169
Xref: solutions.advantagedatabase.com Advantage.Networking:824
Article PK: 1132243

Its configured at 7 for everyone, but i believe it's using REMOTE_SERVER
(Says so in Data Architect when we open a table)


"Mark Wilkins" <mark@no.email> a ?crit dans le message de news:
490a09ea@solutions.advantagedatabase.com...

> Hi,
>
> What connection type are you using? Is it 2 (ADS_REMOTE_SERVER) or 4
> (ADS_AIS_SERVER)?
>
> Mark Wilkins
> Advantage R&D


Mark Wilkins Posted on 2008-11-03 17:23:59.0Z
From: "Mark Wilkins" <mark@no.email>
Newsgroups: Advantage.Networking
References: <48f4be04@solutions.advantagedatabase.com> <48f62e9d@solutions.advantagedatabase.com> <48f63192@solutions.advantagedatabase.com> <4905bb76@solutions.advantagedatabase.com> <4909d571@solutions.advantagedatabase.com> <490a09ea@solutions.advantagedatabase.com> <490b6b5d@solutions.advantagedatabase.com>
Subject: Re: 6610 errors since upgrading to version 9
Date: Mon, 3 Nov 2008 10:23:59 -0700
Lines: 30
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.3138
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
X-RFC2646: Format=Flowed; Response
NNTP-Posting-Host: 10.24.38.228
Message-ID: <490f3231@solutions.advantagedatabase.com>
X-Trace: 3 Nov 2008 10:17:37 -0700, 10.24.38.228
Path: solutions.advantagedatabase.com!solutions.advantagedatabase.com!10.24.38.228
Xref: solutions.advantagedatabase.com Advantage.Networking:825
Article PK: 1132244

Hi,

Can you possibly send me the ads_err.* files that show the 7020 error? I'm
not sure it will help, but maybe I'll see something that helps shed some
light on this. If you can, send them to advantage@ianywhere.com (attn:
Mark Wilkins).

Thanks,
Mark Wilkins
Advantage R&D

"evaded" <not@set.yet> wrote in message
news:490b6b5d@solutions.advantagedatabase.com...
> Its configured at 7 for everyone, but i believe it's using REMOTE_SERVER
> (Says so in Data Architect when we open a table)
>
>
> "Mark Wilkins" <mark@no.email> a ?crit dans le message de news:
> 490a09ea@solutions.advantagedatabase.com...
>> Hi,
>>
>> What connection type are you using? Is it 2 (ADS_REMOTE_SERVER) or 4
>> (ADS_AIS_SERVER)?
>>
>> Mark Wilkins
>> Advantage R&D
>
>


Mark Wilkins Posted on 2008-11-04 23:07:58.0Z
From: "Mark Wilkins" <mark@no.email>
Newsgroups: Advantage.Networking
References: <48f4be04@solutions.advantagedatabase.com>
Subject: Re: 6610 errors since upgrading to version 9
Date: Tue, 4 Nov 2008 16:07:58 -0700
Lines: 53
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.3138
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
X-RFC2646: Format=Flowed; Response
NNTP-Posting-Host: 10.24.38.228
Message-ID: <4910d44f@solutions.advantagedatabase.com>
X-Trace: 4 Nov 2008 16:01:35 -0700, 10.24.38.228
Path: solutions.advantagedatabase.com!solutions.advantagedatabase.com!10.24.38.228
Xref: solutions.advantagedatabase.com Advantage.Networking:826
Article PK: 1132245

Hi,

In version 8.10.0.26, the default timeout values were lowered. There is a
timeout value for "Internet" clients (ADS_AIS_SERVER) and a separate one for
typical (ADS_REMOTE_SERVER) connections. The default timeout was changed
from 10 minutes for Internet clients and 4 minutes for other remote clients
down to 2 minutes for both types. I mentioned in an earlier post that the
Internet timeout had been changed, but I had completely forgotten that the
regular timeout also was changed. It could be that this is the cause of the
6610 errors.

When a client is idle (not actively communicating with the server), it sends
keepalive packets to the server to let it know it still exists. If the
server does not hear from a client within the timeout period, it disconnects
the client and logs a 7020 entry in the ads_err log file. The keepalive
packet interval is 1/4th of the timeout period. Thus, if the timeout is 2
minutes, the client will send a keepalive packet every 30 seconds. The
timeout countdown at the server is reset every time it receive any packet
from a client (keepalive or normal communication), so only 1 out of 4
keepalive packets needs to succeed in reaching the server. Generally, we
have seen that the increased frequency of the keepalive packets results in
better connectivity. However, if the network connection is completely
inoperable (e.g., maybe a router stops working) for over 2 minutes, then the
2 minute client timeout would result in a 7020 error while the original 4
minute timeout would retain the connection.

If this describes your situation, you can increase the timeout values. The
configuration parameter names are CLIENT_TIMEOUT and
INTERNET_CLIENT_TIMEOUT. If you are running Advantage Database Server for
Windows, you can set it in the configuration utility (ads_cfg.exe) under the
communications tab.

Mark Wilkins
Advantage R&D

<rodgerv@nospam.calsense.com> wrote in message
news:48f4be04@solutions.advantagedatabase.com...
>I have a 10 user ADS server with a Delphi service client running on 8
>computers and I seem to be having 6610 error issues with 2 of my computers.
>One of them is an XP computer that used to work until upgrading the server
>to ADS version 9. Now every day in the afternoon this computer reports a
>6610 error. Also I have a brand new Vista computer that was put on to the
>network at the same time the ADS was upgraded to version 9. It seems to
>report 6610 errors more frequently than the other computer. I have looked
>through the knowledge base but nothing has worked so far.
>
> Any ideas?
>
> Thanks in advance,
>
> Rodger Van Kirk


evaded Posted on 2008-11-05 16:34:16.0Z
From: "evaded" <not@set.yet>
Newsgroups: Advantage.Networking
References: <48f4be04@solutions.advantagedatabase.com> <4910d44f@solutions.advantagedatabase.com>
Subject: Re: 6610 errors since upgrading to version 9
Date: Wed, 5 Nov 2008 11:34:16 -0500
Lines: 234
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_000B_01C93F3A.6F5A6D20"
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.5512
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
NNTP-Posting-Host: 207.35.108.169
Message-ID: <4911c965@solutions.advantagedatabase.com>
X-Trace: 5 Nov 2008 09:27:17 -0700, 207.35.108.169
Path: solutions.advantagedatabase.com!solutions.advantagedatabase.com!207.35.108.169
Xref: solutions.advantagedatabase.com Advantage.Networking:828
Article PK: 1132247

When we upgraded from 8.1 to 9.0 we noticed that the timeout value had been changed to 120, but we put back the original value of 240 in an attempt to minimize any side effects.
 
We're using a Cisco Catalyst as a backbone, so I checked the statistics on the switch and there are no collisions nor packet dropped and the latency is good ( < 1ms) for every client.
We were able to reproduce the error once with USE_TCP_IP=0 in the client's ads.ini file, so for now we're going to set the value to 1 for every user.
 
Mark or Raymond, could you check if there was a change with the USE_TCP_IP setting between v8 and v9?
I am under the assumption that in v8, only the key (without a value) was needed in the ads.ini file to get the client to use tcp/ip, and that now with v9 we must specify "=1" for it to work. I can't remember where we got this information but we did deploy v8 with "USE_TCP_IP=" in the ads.ini of our users (no 0 or 1 after the equal sign) and it worked flawlessly since then (~18 months).
 
 
 
"Raymond Kwong"
> In version 8.10.0.26 (and in 9.x), the default timeout value value was reduced from 4 minutes to 2 minutes.  A lower
> timeout makes the client send keepalive packets more often, so the change should not result in this behavior.  However,
> if the customer has a poor network that has outages lasting over 2 minutes (but less than 4 minutes), then this change
> would definitely result in the behavior you are seeing.  If this is possible please change it back by adding the following to
> the configuration file (ads.conf).
>
> CLIENT_TIMEOUT=240
"Mark Wilkins"
> Hi,
>
> In version 8.10.0.26, the default timeout values were lowered.  There is a
> timeout value for "Internet" clients (ADS_AIS_SERVER) and a separate one for
> typical (ADS_REMOTE_SERVER) connections.  The default timeout was changed
> from 10 minutes for Internet clients and 4 minutes for other remote clients
> down to 2 minutes for both types.  I mentioned in an earlier post that the
> Internet timeout had been changed, but I had completely forgotten that the
> regular timeout also was changed.  It could be that this is the cause of the
> 6610 errors.
>
> When a client is idle (not actively communicating with the server), it sends
> keepalive packets to the server to let it know it still exists.  If the
> server does not hear from a client within the timeout period, it disconnects
> the client and logs a 7020 entry in the ads_err log file.  The keepalive
> packet interval is 1/4th of the timeout period.  Thus, if the timeout is 2
> minutes, the client will send a keepalive packet every 30 seconds.  The
> timeout countdown at the server is reset every time it receive any packet
> from a client (keepalive or normal communication), so only 1 out of 4
> keepalive packets needs to succeed in reaching the server.  Generally, we
> have seen that the increased frequency of the keepalive packets results in
> better connectivity.  However, if the network connection is completely
> inoperable (e.g., maybe a router stops working) for over 2 minutes, then the
> 2 minute client timeout would result in a 7020 error while the original 4
> minute timeout would retain the connection.
>
> If this describes your situation, you can increase the timeout values.  The
> configuration parameter names are CLIENT_TIMEOUT and
> INTERNET_CLIENT_TIMEOUT.  If you are running Advantage Database Server for
> Windows, you can set it in the configuration utility (ads_cfg.exe) under the
> communications tab.
>
> Mark Wilkins
> Advantage R&D
>


Mark Wilkins Posted on 2008-11-05 21:16:36.0Z
From: "Mark Wilkins" <mark@no.email>
Newsgroups: Advantage.Networking
References: <48f4be04@solutions.advantagedatabase.com> <4910d44f@solutions.advantagedatabase.com> <4911c965@solutions.advantagedatabase.com>
Subject: Re: 6610 errors since upgrading to version 9
Date: Wed, 5 Nov 2008 14:16:36 -0700
Lines: 168
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0016_01C93F51.1C9AFCF0"
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.3138
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
NNTP-Posting-Host: 10.24.38.228
Message-ID: <49120bb5@solutions.advantagedatabase.com>
X-Trace: 5 Nov 2008 14:10:13 -0700, 10.24.38.228
Path: solutions.advantagedatabase.com!solutions.advantagedatabase.com!10.24.38.228
Xref: solutions.advantagedatabase.com Advantage.Networking:830
Article PK: 1132250

Hi,
 
I looked at the code, and I cannot see that there has been any change in how that setting is read or used.  If there is no value specified for USE_TCP_IP, it defaults to zero (FALSE).  Also, I think you mentioned that you are still using 8.x clients.  The USE_TCP_IP setting is purely a client-side configuration value, so even if it changed in 9.x, you would have to be using the 9.x client to see the change.
 
The error logs you provided (thank you) show that the 7020 errors existed with both 8.x and 9.x.  They average per day does increase some after the 9.x upgrade.  If the 7020 errors are resulting in 6610 errors at the client, then it seems the 8.x server should have been causing 6610 errors as well.  So I'm still rather puzzled.  If someone "turns off" his client PC (or otherwise abnormally terminates the application), then that will likely result in the 7020 being logged when the server detects the situation.  So maybe that is the explanation for the certain level of 7020 entries with 8.x, and the additional ones with 9.x are due to the server incorrectly logging out still-connected clients. 
 
I don't know how feasible it would be for you, but if you could gather a network sniff (e.g., using Wireshark) on the server side of the Cisco switch, we could look at it and maybe deduce what is happening.  It would need to include the traffic of at least one client that received the 6610.  So it could result in rather large file.  But I think it might help.

Mark Wilkins
Advantage R&D
 
"evaded" <not@set.yet> wrote in message news:4911c965@solutions.advantagedatabase.com...
When we upgraded from 8.1 to 9.0 we noticed that the timeout value had been changed to 120, but we put back the original value of 240 in an attempt to minimize any side effects.
 
We're using a Cisco Catalyst as a backbone, so I checked the statistics on the switch and there are no collisions nor packet dropped and the latency is good ( < 1ms) for every client.
We were able to reproduce the error once with USE_TCP_IP=0 in the client's ads.ini file, so for now we're going to set the value to 1 for every user.
 
Mark or Raymond, could you check if there was a change with the USE_TCP_IP setting between v8 and v9?
I am under the assumption that in v8, only the key (without a value) was needed in the ads.ini file to get the client to use tcp/ip, and that now with v9 we must specify "=1" for it to work. I can't remember where we got this information but we did deploy v8 with "USE_TCP_IP=" in the ads.ini of our users (no 0 or 1 after the equal sign) and it worked flawlessly since then (~18 months).
 


Mark Wilkins Posted on 2008-11-07 16:18:34.0Z
From: "Mark Wilkins" <mark@no.email>
Newsgroups: Advantage.Networking
References: <48f4be04@solutions.advantagedatabase.com> <4910d44f@solutions.advantagedatabase.com> <4911c965@solutions.advantagedatabase.com>
Subject: Re: 6610 errors since upgrading to version 9
Date: Fri, 7 Nov 2008 09:18:34 -0700
Lines: 98
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_005D_01C940B9.CF39AA00"
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.3138
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
NNTP-Posting-Host: 10.24.38.228
Message-ID: <491468da@solutions.advantagedatabase.com>
X-Trace: 7 Nov 2008 09:12:10 -0700, 10.24.38.228
Path: solutions.advantagedatabase.com!solutions.advantagedatabase.com!10.24.38.228
Xref: solutions.advantagedatabase.com Advantage.Networking:831
Article PK: 1132251

Hi,
 
An issue similar to this was posted on the General newsgroup and the customer found that setting the USE_SEMAPHORE_FILES configuration value to 0 fixed the problem.  Are you using semaphore files to maintain connections?  If so, then it is probably the same issue.  Using TCP/IP connections would eliminate the problem because TCP/IP does not use semaphore files.  If you have that setting turned on (it is available in the ads_cfg utility under the Communications tab), it is probably best to turn it off; that should eliminate the problem regardless of the USE_TCP_IP setting at the client.

Mark Wilkins
Advantage R&D
"evaded" <not@set.yet> wrote in message news:4911c965@solutions.advantagedatabase.com...
When we upgraded from 8.1 to 9.0 we noticed that the timeout value had been changed to 120, but we put back the original value of 240 in an attempt to minimize any side effects.
 
We're using a Cisco Catalyst as a backbone, so I checked the statistics on the switch and there are no collisions nor packet dropped and the latency is good ( < 1ms) for every client.
We were able to reproduce the error once with USE_TCP_IP=0 in the client's ads.ini file, so for now we're going to set the value to 1 for every user.


evaded Posted on 2008-11-13 21:19:06.0Z
From: "evaded" <not@set.yet>
Newsgroups: Advantage.Networking
References: <48f4be04@solutions.advantagedatabase.com> <4910d44f@solutions.advantagedatabase.com> <4911c965@solutions.advantagedatabase.com> <491468da@solutions.advantagedatabase.com>
Subject: Re: 6610 errors since upgrading to version 9
Date: Thu, 13 Nov 2008 16:19:06 -0500
Lines: 15
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.5512
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
X-RFC2646: Format=Flowed; Original
NNTP-Posting-Host: 207.35.108.169
Message-ID: <491c981a@solutions.advantagedatabase.com>
X-Trace: 13 Nov 2008 14:11:54 -0700, 207.35.108.169
Path: solutions.advantagedatabase.com!solutions.advantagedatabase.com!207.35.108.169
Xref: solutions.advantagedatabase.com Advantage.Networking:832
Article PK: 1132249

I never saw this option before so my guess is we don't use it.

Last week we deployed USE_TCP_IP=1 company-wide and, except for one user,
we've been pretty much error free since then(some 7020 are still logged but
users seem unaffected).

I followed your advice and sniffed the traffic between client and server
with wireshark. We discovered that for this user, one specific application
was communicating with UDP, even with USE_TCP_IP=1 in the ads.ini; that's
when we discovered this application was using advantage dlls v8.0 (instead
of 8.1). We updated the dll on this workstation and everything is OK now,
but it seems that UDP communication between client and server is broken in
some way...


Mark Wilkins Posted on 2008-11-14 00:10:40.0Z
From: "Mark Wilkins" <mark@no.email>
Newsgroups: Advantage.Networking
References: <48f4be04@solutions.advantagedatabase.com> <4910d44f@solutions.advantagedatabase.com> <4911c965@solutions.advantagedatabase.com> <491468da@solutions.advantagedatabase.com> <491c981a@solutions.advantagedatabase.com>
Subject: Re: 6610 errors since upgrading to version 9
Date: Thu, 13 Nov 2008 17:10:40 -0700
Lines: 30
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.3138
X-RFC2646: Format=Flowed; Response
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
NNTP-Posting-Host: 10.24.38.228
Message-ID: <491cc07f@solutions.advantagedatabase.com>
X-Trace: 13 Nov 2008 17:04:15 -0700, 10.24.38.228
Path: solutions.advantagedatabase.com!solutions.advantagedatabase.com!10.24.38.228
Xref: solutions.advantagedatabase.com Advantage.Networking:833
Article PK: 1132252

Thank you for reporting back with the results of this.

If you still have the network trace and could send it to us (e,.g., if it
does not contain proprietary information), I might be able to learn
something from it. If it is small enough, you could mail it to
advantage@ianywhere.com (attn: Mark Wilkins). If semaphore files are being
used for some reason, I might be able to tell from that network trace.

Mark Wilkins
Advantage R&D

"evaded" <not@set.yet> wrote in message
news:491c981a@solutions.advantagedatabase.com...
>I never saw this option before so my guess is we don't use it.
>
> Last week we deployed USE_TCP_IP=1 company-wide and, except for one user,
> we've been pretty much error free since then(some 7020 are still logged
> but users seem unaffected).
>
> I followed your advice and sniffed the traffic between client and server
> with wireshark. We discovered that for this user, one specific application
> was communicating with UDP, even with USE_TCP_IP=1 in the ads.ini; that's
> when we discovered this application was using advantage dlls v8.0 (instead
> of 8.1). We updated the dll on this workstation and everything is OK now,
> but it seems that UDP communication between client and server is broken in
> some way...
>


solo Posted on 2010-07-22 08:55:06.0Z
From: solo@rietumu.lv
Subject: Re: 6610 errors since upgrading to version 9
Newsgroups: Advantage.Networking
MIME-Version: 1.0
References: <48f4be04@solutions.advantagedatabase.com> <4910d44f@solutions.advantagedatabase.com> <4911c965@solutions.advantagedatabase.com> <491468da@solutions.advantagedatabase.com> <491c981a@solutions.advantagedatabase.com> <491cc07f@solutions.advantagedatabase.com>
X-Newsreader: Lotus Notes Release 8.5.1 FP3 May 24, 2010
X-MIMETrack: Serialize by Notes Client on Serge Golubev/RBTG/Rietumu Banka(Release 8.5.1 FP3|May 24, 2010) at 22.07.2010 10:57:58
Content-Type: multipart/mixed; boundary="=_mixed 002BC29AC2257768_="
NNTP-Posting-Host: 194.153.171.5
Message-ID: <4c47f95a@solutions.advantagedatabase.com>
Date: 22 Jul 2010 01:55:06 -0700
X-Trace: 22 Jul 2010 01:55:06 -0700, 194.153.171.5
Lines: 120
Path: solutions.advantagedatabase.com!194.153.171.5
Xref: solutions.advantagedatabase.com Advantage.Networking:941
Article PK: 1132351

Hello Mark,

we have the same problems like this with using adsdosip.exe (for DOS CA-Clipper applications) utility and UDP/IP and windows ADS clients. By unknown reason all of them at the same several times a day loosing connection with ADS server with error code 6610. And this message at the same time follows with 7020 errors from all this clients in ads_err.adt. Playing with timeouts was unhelpful.

Changing of usage UDP/IP to TCP/IP (USE_TCP_IP=1, USE_UDP_IP=0) for windows clients, it seems, solved this problem, but adsdosip hase strange behavior.

First of all, I want to get some background information. We using ADS under Novell Netware beginning from ADS v 4.
Actually in production we using ADS 8.10.0.38, but it sometimes crushes together with Netware server.
We planning to migrate from Netware 6.5 (Novell OES 2) to SUSE Linux (Novell OES 2 linux part) ant to new version of ADS.
Actually we testing version 10.0.0.3 of ADS under SUSE Linux 10 SP3 (Novell OES 2 SP 2,  uname -a: Linux linads 2.6.16.60-0.66.1-smp #1 SMP Fri May 28 12:10:21 UTC 2010 x86_64 x86_64 x86_64 GNU/Linux)

As I told earlie, problem with windows application (tested with Advantage data architect 10) was solved, but ADSDOSIP utility hase strange behavior.
We have installed adsdosip version 7.0 and axcws32.dll version 7.0.0.0 (taken from it's versioninfo record). With this combination of software, parameters USE_TCP_IP and USE_UDP_IP are ignored and adsdosip connecting to ads server using UDP/IP protocol.
But, if I changing axcws32.dll to newer version (tested with 8.10.0.38 and 10.0.0.3) and USE_TCP_IP = 1 (when  USE_UDP_IP=1 all woking, except described earlie 6610/7020 errors) adsdosip can't establish connection to ADS. When Clipper application trying to open database, adsdosip sends sevaral TCP packets ( dump attached) and session stops and clipper application hanging. This trying seems in ads_err.adt as 2 error records with Error_code values 7139 and 7149.

Maybe you khow how to fix it?