Troubleshooting; Server Fails To Start - Sybase Adaptive Server Configuration Manual

Troubleshooting

sybase.com - being responsible for all IPv4 networking applications
v6.sybase.com - being responsible for all IPv6 networking applications
Troubleshooting

Server fails to start

00:00000:00002:2003/09/22 12:37:23.63 kernel
ether, port 4559, filter NONE
00:00000:00002:2003/09/22 12:37:23.65 kernel
use
00:00000:00002:2003/09/22 12:37:23.68 server Error: 1602, Severity: 18, State:
66
Before starting Adaptive Server for IPv6-aware operations, make sure that
your infrastructure is correctly set up. Once your operating system is correctly
configured, an IPv6
connection handler
Configuring and enabling the IPv6
additional DCL entry. A single Adaptive Server configuration can typically
carry up to 32
connection handler
For example if you have a Site-local setup with two domains administrated
under the nameserver setup:
The DCL entry for Adaptive Server to start named "SYBASE" on the host
"revival" for port 17100 would typically look like:
SYBASE
master tcp ether revival.sybase.com 17100
query tcp ether revival.sybase.com 17100
master tcp ether revival.v6.sybase.com 17100
query tcp ether revival.v6.sybase.com 17100
In the above example, when Adaptive Server is started with IPv6-awareness it
creates two
connection handlers
Clients connection requests, and the other listens on port 17100 for incoming
IPv6 Clients connection requests.
This section describes how to correct some common situations that may cause
a server to not start.
If a server fails to start with the following message, the port number specified
in the interfaces file may be in use:
can be configured and enabled.
connection handler
assignments within the DCL.
. One listens on port 17100 for incoming IPv4
network name SERV_CORPNET, type
ninit: bind, Address already in
Adaptive Server Enterprise
requires adding an