You have to realize I am not here to be yelled at. I know my post came after you posted the information but I did not know it at the time since I was busy trying to find information for you.

When sending in the enabler codes - did you use the new system's information or the old system?

Found this on SunSolve: may or may not help you.
This Legato Technical Bulletin (modified for Sun customers) describes
how to move Solstice Backup from one server to another one.

==============================================================================
I. Move Solstice Backup ( SBU ) from old server to new:

1. Using Solstice Backup, perform a full backup of all the filesystems
on the old NetWorker server.

2. Stop the SBU daemons on the old server, using the
" /etc/init.d/networker stop " or " nsr_shutdown -a " command.

3. Copy the entire /nsr directory tree from the old server to the new
server. To do this, make a tar tape of the /nsr directory and reload
it on the new server by running tar xvf. If /nsr is a symbolic link
on the old server (which it probably is) make sure that the new server
has the appropriate /nsr symbolic link.

* Note: SBU 5.0.1 and earlier releases permitted symbolic links under
/nsr. This was useful if you wanted to link an index to
another file system because of insufficient space on the
current file system.

SBU 5.1 does not permit the utilization of symbolic links
under /nsr because of security issues...

If you need to link out indexes to other file systems, use
the "index path" field under "client setup; view details"
window...

4. Shut down your old server, and disconnect all the backup devices.

5. Shut down the new machine, add the hardware devices to the new server.
Restart both machines by running boot -r so that devices get properly
configured. Start up the old machine first, then the new one.

6. Using the SBU CD, install the Solstice Backup software on the new
server using pkgadd commands. During each pkgadd session, answer "no"
when prompted to start daemons after installation. Install the Sun
packages in this order:
SUNWsbuc, SUNWsbun (5.x only), SUNWsbus1, SUNWsbus2, and SUNWsbum

* If the new server's hosts name is different than the old server's
hosts name then perform the following operations on the new server:

a. Shutdown the daemons with: " /etc/init.d/networker stop "

b. Confirm nsr daemons have stopped: " ps -ef | grep nsr "

c. cd /nsr/index

d. rmdir new-hostname

e. Rename the old index directory to the new server hostname:

" mv old-hostname new-hostname "

* Note, PRIOR to starting up the daemons install required patches:

Call Sun if you cannot find this patch on the web or ftp site.

a. If the new server has Solstice Backup 5.0.1, then install
patch 105658-xx ( rev -06 or higher; do not use -04 ).

b. If the new server has Solstice Backup 5.1, then install
patch 106408-xx ( rev -04 or higher for Sparc systems )
106454-xx ( rev -01 or higher for x86 systems )


7. If you installed patch 105658-xx (for 5.0.1), the daemons should have
started up automatically. Else, start the daemons manually by running:
/etc/init.d/networker start

8. When daemons are started for the first time on the new server, you should
see messages similar to these:

NetWorker Server: (notice) started
NetWorker Registration: (notice) invalid auth codes detected.
The auth codes for the following licenses enablers are now invalid.
The cause may be that you moved the NetWorker server to a new computer.
You must re-register these enablers within 15 days to obtain new codes.
License enabler #xxxxxx-xxxxxx-xxxxxx (NetWorker Advanced/10)


==============================================================================
II. Verify operation of the new Solstice Backup server:

1. Verify that all the clients are included in the scheduled backups.

2. Use the Recover window to make sure all the client indexes are visible
and therefore `recoverable.'

3. Back up the indexes on the new server by entering in: saveindex -l full
at the system prompt. (Or, if you prefer, perform a full backup of the
new server as soon as possible.)

==============================================================================
III. Obtain Enabler Codes for your new Solstice Backup server.

1. Open the Registration window by selecting the Registration command in
the Administration pull-down menu of the Main window.

2. Select Tabular from the View pull-down menu to display the tabular view
of the window.

3. Select Print from the File pull-down menu and enter a print command to
send a copy of the Registration window to a printer.

4. FAX this printout along with your name, company, and telephone number
to Sun Licensing Center and request that your enabler codes be
transferred. FAX number for Sun Licensing Center is 1-317-364-7220
( their email address is license@sun.com )
Sun will then send you new enabler codes (replacing the old ones)

Another section:

Installing a 4mm Autoloader with Networker software 8 May 1995

Description Top

(Reference the Installation and Maintenance manual received with the
Networker product along with the Sun Release Notes.)

USER MUST HAVE THE ADVANCED NETWORKER SERVER PACKAGE LICENSE. (Jukebox license
is optional, depending on how the device will beused.)

Note: If user needs to use addresses for the installation (depending on the
age of the drivers):

The controller is a "0" (zero) for the first one.
The target unit number is always a "1" (one) - this is hard-coded.

(ctlr=0, tape(unit)=1)

If it asks for the "type", use 'ARC Diamondback.'

If software is not already installed, do so:

Do the pkgadd of the Networker server package. DO NOT START the daemons at
the end of the installation script.

(Be sure to apply patch number 1019 55 for version 4.0.2 of the Networker
software to get the current drivers fro the jukebox devices.)

Follow the installation instructions for the jukebox devices with the
following:

If applying patch number 101955, 'deinstall' the Networker driver, a nd install
the patched driver:

1) cd /usr/lib/nsr/sjidriver
2) ./deinstall
3) apply the patch
4) cd /usr/lib/nsr/sjidriver
5) ./install

Initially, set up the device with switch 2 in the off position:
facing the front of the unit, with the carriage open, there is a small rubber
cover on the top-right-rear of the carriage. Under this cover is a 4-pole
switch pack. Normally, switch 2 is ON. Turn it OFF; power cycle the device for
this switch change to take effect.

6) shutdown the system
7) boot -r

(Use of jukebox device name is used below. User may need to test using normal
tape device name like /dev/rmt/0bn).When the system is back up, check for
the device:

7) pscinfo -c INQUIRY /dev/sjid1u1

This should return information about the device.

Load tapes into slots , and initialize the device.

8) pscinfo -i /dev/sjid1u1

Enter the following to be sure that the system returns info about tapes

9) pscinfo -e /dev/sjid1u1

If all of the above works correctly, proceed. If not, there is an installation
problem - start again.


NOW TEST THE DEVICE CONNECTION:

Load tapes into slots 1 and 4 only. Run jbexercise:

10) jbexercise -c /dev/sjid1u1

This should pass. If it does not, there is a device problem.

Start the daemonsup, if they are not running at this time:

nsrd

Run the enablers for the jukebox, if user has a jukebox module license.

11) jbm_enabler (select ARC-Diamondback if needed here)

IF the Networker software has not been enabled yet, do so now:

12) nsrcap -v -c <enabler-code-lowercase>

Are there multiple interfaces on the new system?

no just one interface. i am not shifting servers.
the new installation is an entirely different server on a different network

NB: i wasnt yelling at you. i appreciate all the help i am getting from you.

__________________
Simbo Adeyemi ( Miss)
m.c.s.e.
m.c.p.
c.c.n.a.

I have looked on SunSolve and Legato but can not find your exact error. I don't know if you care to try but I posted the site for Legato.

Two options:
If you purchased support call SUN. They should help you if you bought the drive.

Or -
Wait to see if someone else may know the answer.