It really looks like this is an 'ALF' jukebox ... an alien life form because so far you only know what you have done.

What does 'moved location' mean ? - Did you physically move the hardware or did you make a host transfer ?

Has the hardware changed at all ? - SCSI drivers, tape drivers etc. ?

The OS seems to be W2K3 but which NW version do you run ?

Is the Windows RSM service disabled ? - Has it re-enabled again ?

If all these basics have been verified, i think it is easier and faster to delete and reconfigure the jukebox. Or let it NW detect it itself.

Moved locations as in the physical building, the company moved locations locally and the servers are now stored offsite, The hard ware has not changed and the NW Version is 7.5.2 and yes the RSM is disabled.

So what does "inquire" report? - does it see the robot and all drives as before?

Verify the SCSI addresses with your configuration.

Reading the inquire command it seems like it is just the connection, or am I missing something? It shows it reads the tape drives, just not the Juke.

I did the inquire command and this is what it said:

H:\>inquire

scsidev@0.0.0:HL-DT-STCDRW/DVD GCC4244B101|CD-ROM

scsidev@2.0.0:DELL    PERC 5/i        1.00|Disk

                                           WWNN=60013720662FFA000C6DFCE53773D421

scsidev@2.64.0:  RAID   DummyDevice    0001|Unknown Device Type

scsidev@3.0.0:IBM     ULTRIUM-TD3     93G0|Tape, \\.\Tape0

                                           S/N: 1210154483

                                           ATNN=IBM     ULTRIUM-TD3     1210154483

                                           WWNN=500308C099952000

                                           WWPN=500308C099952001

                                           PORT=00000001

scsidev@3.1.0:IBM     ULTRIUM-TD3     93G0|Tape, \\.\Tape1

                                           S/N: 1210366255

                                           ATNN=IBM     ULTRIUM-TD3     1210366255

                                           WWNN=500308C099952004

                                           WWPN=500308C099952005

                                           PORT=00000001

scsidev@4.0.0:DGC     RAID 5          0219|Disk

                                           S/N: FCNPR061300136

                                           WWNN=6006016083D21800702FFEBCECB4DE11

                                           PORT=00000002

scsidev@4.0.1:DGC     RAID 5          0219|Disk

                                           S/N: FCNPR061300136

                                           WWNN=6006016083D218001CED4DB0EAB4DE11

                                           PORT=00000002

scsidev@4.1.0:DGC     RAID 5          0220|Disk

                                           S/N: FCNPR062301112

                                           WWNN=6006016052841801AA1304E50C26DE11

                                           PORT=00000003

scsidev@4.2.0:DGC     RAID 5          0220|Disk

                                           S/N: FCNPR062301112

                                           WWNN=6006016052841801AA1304E50C26DE11

                                           PORT=00000002

H:\>

H:\>jbverify -j

14866:jbverify:

Jbverify is running on host alcbackup01, Windows Server 2003 5.2

14918:jbverify:

Processing jukebox devices...

14920:jbverify:

Processing jukebox ALCJUKE:

16024:jbverify: Unable to open SJI device scsidev@3.2.1. Check device, connections and drivers.

39078:jbverify: SYSTEM error: No such file or directory

39077:jbverify: error, Cannot initialize jukebox! Driver may not be loaded!

14926:jbverify:

Failed while processing jukebox ALCJUKE on alcbackup01

14929:jbverify:

Finished processing jukebox devices.

**********************************************************************

                 Summary report of jbverify

                 ======= ====== == ========

Hostname   Device Handle    Blocksize  Jukebox  Drv No. Status

--------   -------------    ---------  -------  ------- ------

alcbackup01 Unknown          N/A        ALCJUKE  N/A     Fail

**********************************************************************

14938:jbverify:

Exiting jbverify with failures.

NW's 'INQUIRE' command uses the SCSI INQUIRE command.

In general, it 'pings' each possible SCSI and see whether the target answers. Then it uses additional information to get the details like type and vendor. That's the brief description.

As it turns out, you see the drives but not the robot (if it should be connected to the same computer). Here is ours:

scsidev@nn.0.0:GRAU    ITL-5000l       1.7 |Autochanger (Jukebox)

  ....

So check the connectivity issues and make sure that you see the hardware via the OS. Then rerun inquire before you proceed with anything else.

Thank you for the input Bingo and I think you got it right. It has to be the connection. I just hung up the phone talking to the Co-lo IT department that we are using to store or servers and they noticed one of the connections is not online, so this has to be the issue. I will update when I get back from going to the data center.

This is a Windows server - there is nothing to be set.

If INQUIRE sees the jukebox, simply detect it (Devices > your_server > Scan for Devices).

Once it is visible here, select it and open the menu with a right mouse-click.

Then select Configure All Libraries or Re-configure Library.

sizer2,

How do I do the following?

LD_LIBRARY_PATH variable needs to be set to include the non-default lib directory prior to NetWorker started up.

After much wire connection chasing, everything seems to be connected properly. Still having the same issue.