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 With Win7-64 but Suceeds on Advantage Restart

4 posts in Networking Last posting was on 2012-05-24 14:16:57.0Z
John Pierce Posted on 2012-05-15 17:23:12.0Z
From: "John Pierce" <john@medicompal.com>
Newsgroups: Advantage.Networking
Subject: 6420 With Win7-64 but Suceeds on Advantage Restart
Date: Tue, 15 May 2012 12:23:12 -0500
Lines: 3
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
Importance: Normal
X-Newsreader: Microsoft Windows Live Mail 15.4.3538.513
X-MimeOLE: Produced By Microsoft MimeOLE V15.4.3538.513
NNTP-Posting-Host: 98.71.73.126
Message-ID: <4fb290b0$1@solutions.advantagedatabase.com>
X-Trace: 15 May 2012 10:21:52 -0700, 98.71.73.126
Path: solutions.advantagedatabase.com
Xref: solutions.advantagedatabase.com Advantage.Networking:1001
Article PK: 1132411

I've had my share of 6420 problems in the past and always solved them with
firewall adjustments or an ads.ini file, but this one eludes me.
This client has Advantage 10.0 running on a Windows 7 Pro 64-bit machine
used as the server in a network with all clients also running Windows 7 pro
64-bit. All machines are Static IP and each has 'Enable NetBIOS over TCP/IP'
selected under the WINS tab of Advanced TCP/IP settings. For testing Windows
Firewall is DISABLED on all machines. Network discovery is ENABLED on all
machines with security set to 128 bit. File sharing is enabled and every
client can access the 'server's' shared folders with full file privileges
without fail. DHCP is administered by a netopia router with AT&T firewalls
enabled on the wan. The DHCP range is outside the static range. Pinholes are
open for remote users.

Whenever the 'server' is restarted (even if clients are restarted) ALL
clients fail to connect with error 6420. It doesn't matter how long you
wait. This occurs whether or not the client has an ads.ini file present in
the Windows folder (the only ads.ini file on machine). It also does not
matter if windows firewall is on or off on the server and the workstations.
However, EVERYTHING works perfectly without an ads.ini file and with Windows
firewall enabled - IF - the Advantage Database Server is Stopped and
Restarted on the 'server'.

So, as an overview. After the 'server' is restarted someone MUST stop and
restart the Advantage Database Server Service using the Configuration
Manager to allow clients to connect. Once this is done ALL clients instantly
connect and work fine until the 'server' is restarted again.
My only thought is that it seems as if Advantage is not binding to the IP or
port correctly upon boot-up. The configuration is set to 0(default) for
each. The 'server' is an Intel P7 machine that boots on ssd drives to the
login screen in about 12 seconds. Any ideas why the Advantage Server must be
restarted for connections to work?


Mark Wilkins Posted on 2012-05-16 23:42:10.0Z
From: "Mark Wilkins" <a@b.c>
Newsgroups: Advantage.Networking
References: <4fb290b0$1@solutions.advantagedatabase.com>
In-Reply-To: <4fb290b0$1@solutions.advantagedatabase.com>
Subject: Re: 6420 With Win7-64 but Suceeds on Advantage Restart
Date: Wed, 16 May 2012 17:42:10 -0600
Lines: 2
Organization: Sybase
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
Importance: Normal
X-Newsreader: Microsoft Windows Live Mail 14.0.8089.726
X-MimeOLE: Produced By Microsoft MimeOLE V14.0.8089.726
NNTP-Posting-Host: 10.6.193.219
Message-ID: <4fb43b05$1@solutions.advantagedatabase.com>
X-Trace: 16 May 2012 16:40:53 -0700, 10.6.193.219
Path: solutions.advantagedatabase.com
Xref: solutions.advantagedatabase.com Advantage.Networking:1002
Article PK: 1132412

Hi John,

It sounds as if the Advantage service is starting before the various
networking components are available. If this is true, there would likely be
some 8000 class errors in the error log (ads_err.*).

You might verify that the service dependencies are in there. In the control
panel under the services, right click on "Advantage Database Server", choose
properties, and look at the dependencies tab. It should show "Server" and
"Workstation". Assuming that those are in there, you might try adding a
couple more. It requires editing a registry key:

HKLM\SYSTEM\CurrentControlSet\services\Advantage\DependOnService

That key should currently contain "LanmanWorkstation" and "LanmanServer",
which are the two previously mentioned dependencies.

Add "Tcpip" and "Afd", which are "TCP/IP Protocol Driver" and "Ancillary
Function Driver for Winsock". I'm not sure it will help because I would
think those would already be started by one of the other dependencies ...
but maybe it would change the load order.

Mark Wilkins
Advantage R&D

"John Pierce" <john@medicompal.com> wrote in message
news:4fb290b0$1@solutions.advantagedatabase.com...
> I've had my share of 6420 problems in the past and always solved them with
> firewall adjustments or an ads.ini file, but this one eludes me.
> This client has Advantage 10.0 running on a Windows 7 Pro 64-bit machine
> used as the server in a network with all clients also running Windows 7
> pro 64-bit. All machines are Static IP and each has 'Enable NetBIOS over
> TCP/IP' selected under the WINS tab of Advanced TCP/IP settings. For
> testing Windows Firewall is DISABLED on all machines. Network discovery is
> ENABLED on all machines with security set to 128 bit. File sharing is
> enabled and every client can access the 'server's' shared folders with
> full file privileges without fail. DHCP is administered by a netopia
> router with AT&T firewalls enabled on the wan. The DHCP range is outside
> the static range. Pinholes are open for remote users.
>
> Whenever the 'server' is restarted (even if clients are restarted) ALL
> clients fail to connect with error 6420. It doesn't matter how long you
> wait. This occurs whether or not the client has an ads.ini file present in
> the Windows folder (the only ads.ini file on machine). It also does not
> matter if windows firewall is on or off on the server and the
> workstations.
> However, EVERYTHING works perfectly without an ads.ini file and with
> Windows firewall enabled - IF - the Advantage Database Server is Stopped
> and Restarted on the 'server'.
>
> So, as an overview. After the 'server' is restarted someone MUST stop and
> restart the Advantage Database Server Service using the Configuration
> Manager to allow clients to connect. Once this is done ALL clients
> instantly connect and work fine until the 'server' is restarted again.
> My only thought is that it seems as if Advantage is not binding to the IP
> or port correctly upon boot-up. The configuration is set to 0(default) for
> each. The 'server' is an Intel P7 machine that boots on ssd drives to the
> login screen in about 12 seconds. Any ideas why the Advantage Server must
> be restarted for connections to work?
>


John Pierce Posted on 2012-05-23 22:05:03.0Z
From: "John Pierce" <john@medicompal.com>
Newsgroups: Advantage.Networking
References: <4fb290b0$1@solutions.advantagedatabase.com> <4fb43b05$1@solutions.advantagedatabase.com>
In-Reply-To: <4fb43b05$1@solutions.advantagedatabase.com>
Subject: Re: 6420 With Win7-64 but Suceeds on Advantage Restart
Date: Wed, 23 May 2012 17:05:03 -0500
Lines: 1
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
Importance: Normal
X-Newsreader: Microsoft Windows Live Mail 15.4.3538.513
X-MimeOLE: Produced By Microsoft MimeOLE V15.4.3538.513
NNTP-Posting-Host: 98.71.84.249
Message-ID: <4fbd5ea8@solutions.advantagedatabase.com>
X-Trace: 23 May 2012 15:03:20 -0700, 98.71.84.249
Path: solutions.advantagedatabase.com
Xref: solutions.advantagedatabase.com Advantage.Networking:1003
Article PK: 1132413

Thanks Mark,
I tried adding the Tcpip and Afd to the registry but you were right it did
not change anything. However, thinking about the load order I changed the
Advantage Database Server 'Service Startup type' to: 'Automatic (Delayed
Start)'. This seems to have the desired effect. Immediately after a server
restart Advantage database access is denied with error 6420 BUT,
approximately two minutes after server startup, connections to the advantage
database are processed with no errors returned. I tested this several times
and the results were consistent. Interestingly, the error log contained no
(0) recorded errors for the period of time while I checked all of this,
although it did contain various errors from the past including a few 8000
class errors.
As a summary: Changing the Advantage Database Service Startup type to
Automatic (Delayed Start) seems to have resolved the issue for the client.
Windows Firewall is now active on all machines, and none are using an
ads.ini file. Network response is superb.

Thanks for your help.


Mark Wilkins Posted on 2012-05-24 14:16:57.0Z
From: "Mark Wilkins" <a@b.c>
Newsgroups: Advantage.Networking
References: <4fb290b0$1@solutions.advantagedatabase.com> <4fb43b05$1@solutions.advantagedatabase.com> <4fbd5ea8@solutions.advantagedatabase.com>
In-Reply-To: <4fbd5ea8@solutions.advantagedatabase.com>
Subject: Re: 6420 With Win7-64 but Suceeds on Advantage Restart
Date: Thu, 24 May 2012 08:16:57 -0600
Lines: 1
Organization: Sybase
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
Importance: Normal
X-Newsreader: Microsoft Windows Live Mail 14.0.8089.726
X-MimeOLE: Produced By Microsoft MimeOLE V14.0.8089.726
NNTP-Posting-Host: 10.6.193.219
Message-ID: <4fbe4273$1@solutions.advantagedatabase.com>
X-Trace: 24 May 2012 07:15:15 -0700, 10.6.193.219
Path: solutions.advantagedatabase.com
Xref: solutions.advantagedatabase.com Advantage.Networking:1004
Article PK: 1132414

Hi John,

Thank you for providing this information. It may well be useful to someone
else in the future. I have never looked at the delayed start option, so I
just now searched around a bit out of curiosity. It sounds as if that 2
minute delay can be changed if needed. It is mentioned in a comment to one
of the answers here. I did not try it out, though.

http://superuser.com/questions/285653/what-does-delayed-start-do-in-startup-type-for-a-windows-service

Thanks,
Mark Wilkins
Advantage R&D

"John Pierce" <john@medicompal.com> wrote in message
news:4fbd5ea8@solutions.advantagedatabase.com...
> Thanks Mark,
> I tried adding the Tcpip and Afd to the registry but you were right it did
> not change anything. However, thinking about the load order I changed the
> Advantage Database Server 'Service Startup type' to: 'Automatic (Delayed
> Start)'. This seems to have the desired effect. Immediately after a server
> restart Advantage database access is denied with error 6420 BUT,
> approximately two minutes after server startup, connections to the
> advantage database are processed with no errors returned. I tested this
> several times and the results were consistent. Interestingly, the error
> log contained no (0) recorded errors for the period of time while I
> checked all of this, although it did contain various errors from the past
> including a few 8000 class errors.
> As a summary: Changing the Advantage Database Service Startup type to
> Automatic (Delayed Start) seems to have resolved the issue for the client.
> Windows Firewall is now active on all machines, and none are using an
> ads.ini file. Network response is superb.
>
> Thanks for your help.
>
>