NIO CommKit Host Interface Installation and System Administration Manual

B-12
Troubleshooting Guide
Outgoing Call Error Messages
dkdial ... Dialer error
Explanation The call could not be completed due to an error detected
by an old autodialer.
dkdial ... Dialstring too long
Explanation The call was denied because the length of the dialstring
was larger than the network maximum.
dkdial ... Directory Assistance
Explanation The user has requested directory assistance.
dkdial ... Dkserver: Call on a busy device or call collision, try again.
Explanation The call could not be accepted, because the host device is
busy or because the incoming call collided with an
outgoing call. A busy device is one that is being cleaned
up from a prior call or a device that is held open by some
lingering process.
You may also see this error message on an incoming call
from a
DESTINATION prompt displayed as error code
136.
dkdial ... Dkserver: Can’t chroot. Call System Administrator
Explanation The call could not be completed, because the remote
server could not change root to the home directory of the
caller on the remote host.
You may also see this error message on an incoming call
from a
DESTINATION prompt displayed as error code
134.
dkdial ... Dkserver: Can’t open line. Call System Administrator
Explanation The call could not be completed, because the remote host
interface server could not open the data switch special
device file needed to accept the call. See dkdevs(1M).
If you are using the dk command and this error occurs, it