2 Intern

 • 

2K Posts

January 31st, 2008 01:00

I think you should involve EMC Support for this. For NW 732, they had a patch for a similar message. They claimed NW 733 & & 7.4 allready had them covered. Even if you get this message, jbconfig would configure the library and it actually works fine.

4 Operator

 • 

14.4K Posts

January 31st, 2008 11:00

3 days ago I configured one MSL5000 with SDLT600 no problems using 7.4SP1 under x64 win2k3 (using jbconfig).

GUI is right - you do not get serial numbers thus autoconfig won't work. jbconfig should, but it seems as it can't talk to library. Try sjirdtag 4.0.0 to see if you get an answer as that should also open scsi device port for communication.

3 Posts

January 31st, 2008 23:00

Thanks for help. I found out that this library (Compaq MSL5026) is only compatible with Networker on Windows 32 Bit Systems. My System is x64 and so it is not compatible. Now we think to install Windows Server 2003 32Bit Edition.

3 Posts

January 31st, 2008 23:00

Here is output of sjirdtag:

C:\Documents and Settings\Administrator>sjirdtag scsidev@4.0.0
In update_scsi_bus_map: open_bus invalid on nadapters = 6
scsidev@4.0.0: Unknown error

C:\Documents and Settings\Administrator>

4 Operator

 • 

14.4K Posts

January 31st, 2008 23:00

As I said, mine was x64 too and it works fine - so issue is somewhere else. Have you tried sjirdtag command?

4 Operator

 • 

14.4K Posts

February 1st, 2008 00:00

And that's exactly why jbconfig is failing too. Why is now beyond my pot of ideas. I had an issue like that, but in my case RSM was enabled. You said you had disable it already so... You must also make sure no library driver is installed or any other program/driver that would mess around (take over control) of library. sjirdtag is using SJI protocol to communicate directly with library (so no NW here) and it shows here that you can't have access to it from that host (it is visible, but communication path is broken or taken exclusively by something else).

22 Posts

November 21st, 2017 02:00

Hrvoje

(it is visible, but communication path is broken or taken exclusively by something else).

I have the same problem what is the solution ?

22 Posts

November 21st, 2017 06:00

Yes with networker 9 LTO6 juckbox I have the same behavior. I try to configure the library it says : cannot be autoconfigured it maybe claimed by another device.

Then: problem communicating with library because no serial number returned.

I can see the juckbox by inquire cmd. But with jbconfig it fails to be configured : SCSI command mode_sense failed.

I don't know what is the issue

Regards

Get Outlook for Android

2.4K Posts

November 21st, 2017 06:00

For a 9 year old thread - do you have the exact configuration?

A bit more details would be helpful as there is not only one possible solution.

BTW - there are in fact (virtual) tape libraries which cannot be configured automatically.

In these cases, does a manual configuration (jbconfig) work at all?

1 Message

March 22nd, 2022 19:00

hi,did you solve this?I got same error.

2.4K Posts

March 23rd, 2022 01:00

I wonder whether this is 'exactly' the same situation. Do not forget that 14 years have passed since the last message. So, despite the hardware most likely the OS and the NW versions are different, too.

The tape drives must be supported by the OS or a vendor-specific driver. NW only controls the jukebox. And do not forget that you must run jbconfig at the node which controls the library.

 

No Events found!

Top