Problem
After installing SCO ARCserve/Open on the system, when selecting the Device Management option from the ARCserve menu, the following popup error message is displayed:
Failed to contact ARCserve Tape Server. Please wait for retry.
This message continues to display and the only option is:
Quit Device Management Solution
This error is a result of the tapesvr daemon not starting. The
normal output of the astatus command should look similar to this:tapesvr 596 598 dbserver 591 593 asod 600 aprocess
The output of interest is the line that reads "tapesvr 596 598". This output indicates that the tapesvr started, one PID is assigned to the ARCserve/Open process and the other PID is associated with the configured tape drive on the system (additional configured tape drives would each have their own tapesvr PID).
The output of the astatus command, where the error message is displayed, would look similar to this:
tapesvr
dbserver 591 593
asod 600
aprocessThis output shows that no tapesvr process has started on the system.
There are several steps to take to resolve this problem.
STEP 1Verify that the hardware is set up correctly. Follow these steps
to verify that all of the hardware has been checked:|-------------------------|--------------------------------------------|
| I've installed SCO | Make sure that all cards, cables, |
| ARCserve/Open, but I'm | and devices are connected properly. |
| having trouble seeing my| If you installed a new card in your |
| tape drive(s). | system before installing SCO |
| | ARCserve/Open, make sure it is |
| | seated properly in its slot. If |
| | that does not work, try putting the |
| | card in a different slot. |
| | |
| | Type astatus to see if the SCO |
| | ARCserve/Open tapesvr daemon is |
| | running. |
| | |
| | If you have multiple host adapter |
| | cards installed in your system, |
| | make sure your drive is connected |
| | to the first one. |
| | |
| | Make sure your SCSI bus is |
| | terminated properly. There must be |
| | two sets of terminating resistors, |
| | one at the beginning of the chain |
| | and one at the end. If you only |
| | have one drive connected to your |
| | machine, then you have two devices |
| | on the SCSI bus; the host adapter |
| | card and the tape drive. Both the |
| | host adapter card and the tape |
| | drive should be terminated. |
| | |
| | Make sure each SCSI device in the |
| | chain has a unique ID. If you have |
| | two tape drives attached to the |
| | SCSI bus, each with a SCSI ID of 2, |
| | chances are neither device will |
| | work. Set each drive to a unique |
| | SCSI ID. |
| | |
| | Make sure all the tape drives are |
| | turned on. Sometimes if you forget |
| | to turn on one device in a chain, |
| | the others will behave erratically. |
| | |
| | Make sure the jumper settings on |
| | your adapter board are correct. |
| | Check the documentation that came |
| | with the board to make sure the |
| | jumpers are set correctly for use |
| | with your hardware. |
| | |
| | Replace the cables you are using |
| | with ones you know are good. If |
| | the problem goes away, you |
| | had a bad cable. |
|-------------------------|--------------------------------------------|This and additional troubleshooting material can be found in the SCO ARCserve/Open Release and Installation Notes in the Troubleshooting section.
This material can be accessed from the SCO Desktop Help function by following these steps:
1. Select the Help icon from the desktop.
2. Select the Navigate option from the top bar menu.
3. Select the Search option from the pull down menu.
4. Select the Specified Books option.5. Select SCO ARCserve/Open from Cheyenne Documentation set.
6. Select "seeing" (without the quotes) as the search word.
7. Select the Troubleshooting hypertext link.This should ensure that the hardware configuration is correct.
STEP 2Check the kernel resources required by ARCserve/Open. This is
contained in the IT database which can be accessed online through
SCO's BBS or web server. See the following article:TA100084This should ensure that the basic kernel parameters are correct.
STEP 3Check the inter-process communication facilities of the system with
the ipcs(ADM) command. This should produce an output similar to
the following:IPC status from /dev/kmem as of Thu Nov 21 14:02:22 1996
T ID KEY MODE OWNER GROUP
Message Queues:
q 100 0x012a7d9a --rw-rw-rw- root ARCserve
q 101 0x022a7d9a -Rrw-rw-rw- root ARCserve
q 102 0x012a0309 --rw-rw-rw- root ARCserve
q 103 0x022a0309 -Rrw-rw-rw- root ARCserve
Shared Memory:
m 200 0x012a08ce --rw-rw-rw- root ARCserve
m 201 0x012a08cf -Crw-rw-rw- root ARCserve
m 202 0x102a7d9a --rw-rw-rw- root ARCserve
m 103 0x000018e5 --rw-rw-rw- root sys
m 4 0x4c2aac06 --rw-rw-r-- lanman sys
Semaphores:
s 20 0x012a087c --ra-ra-ra- root ARCserve
s 21 0x012a08d0 --ra-ra-ra- root ARCserve
s 22 0x012a08d3 --ra-ra-ra- root ARCserve
s 23 0x102a7d9a --ra-ra-ra- root ARCserve
s 4 0x002ac03f --ra------- root sys
s 5 0x000018e5 --ra-ra-ra- root sysIf there are no ARCserve entries, then the Message Queues in the
kernel need to be increased. Using configure(ADM), select option
13, Message Queues, and set the values to the following minimums:MSGMAP 512
MSGMAX 8192
MSGMNB 8192
MSGSEG 1024Upon completion of these 3 steps, ARCserve/Open should now be able to open the tape drives.