Migration Wizard step 4 option greyed out or not available

(Last modified: 28Jul2003)

This document (10085486) is provided subject to the disclaimer at the end of this document.

symptom

Migration Wizard fails in step 4

Special commands from the Migration Wizard not copied into the AUTOEXEC.NCF on the Destination server.

fact

Novell NetWare 5.1

Novell Directory Services 8

Novell Migration Wizard 6.0

fix

There are two possible solutions:

Option 1. When you go into the Migration Wizard and then select to continue the last or saved project and you see the step 4 button greyed out, you can click on VIEW at the top of the screen, then click on SHOW ALL BUTTONS, and you should be able to continue. If this does not work proceed to option 2 (below).

Option 2. If the Source server has been shut down and it's Directory Services database has been locked, and if the Destination server has taken on the identity of the old (source) server, and if it's temporary Directory Services Database has been removed, then you can manually finish step 4 by doing the following:

1. If coming from NDS 8.x, the wizard copies the backup directory $HWNDS.BAK to the destination SYS:SYSTEM\$HWNDS.BAK. Then, in NWCONFIG on the new server hardware, you will choose "Restore local NDS information after hardware upgrade." It will ask you where to restore from. Because SYS:\SYSTEM is the default directory for creating the backup directory, it will not restore from this directory. To resolve this problem, move the $HWNDS.BAK directory (and 00000000.$HW file inside) to a path other than SYS:\SYSTEM\$HWNDS.BAK\ such as SYS:$HWNDS.BAK\, you can use NETBASIC, JCMD, OR CPQFM (Compaq File Manager) utilities to perform the creation of the new directory and the file copy. Now when NWCONFIG asks where to restore from, you would type in the path to the directory you created, in this example; SYS:$HWNDS.BAK\ . The restore should complete without error.

2. Now restore the trustees according to what ever utility you used to backup the trustees, such as TRUSTBAR.NLM, TBACK, etc. If the trustee restore fails, you can try again, but if it is not successful, then you will need to recreate them manually because we cannot restore them like we can a Directory Services Database.

3. Once the trustees have been restored, you need to re-backlink the server with the following commands:

SET DSTRACE=ON
SET DSTRACE=NODEBUG
SET DSTRACE=+BLINK
SET DSTRACE=*B

When you see the message "Finished checking backlinks succeeded" or "Finished Reference Check", it has finished the re-backlinking process.

4. LOAD DSREPAIR -A | Advanced Options | Check Volume Objects and trustees. Authenticate as ADMIN or ADMIN equivalent. This will begin the check. If it comes back with errors (top right hand corner) hit the ESC key and run the check again, and the errors should now be at zero (if not you may run it again). Once the number of errors returned are zero then you may escape from this option.

5. You may want to verify that there have been no special commands put into the *AUTOEXEC.NCF by the Migration Utility. if they exisit, remove them and save the new AUTOEXEC.NCF.

6. You may want to verify the health of the server by running an NDS Health Check according to TID #10060600 .

*Note: Some of the typical reasons we see migrations fail include the following:

Problems with IP being bound and not IPX only.

Special database migration commands not being placed in the Destination server's AUTOEXEC.NCF

Problems with connectivity between the workstation and the Destination server.

Full NDS Health Check not run on the Source server prior to the migration.

document

Document Title:	Migration Wizard step 4 option greyed out or not available
Document ID:	10085486
Solution ID:	NOVL91281
Creation Date:	25Jul2003
Modified Date:	28Jul2003
Novell Product Class:	NetWare

disclaimer

The Origin of this information may be internal or external to Novell. Novell makes all reasonable efforts to verify this information. However, the information provided in this document is for your information only. Novell makes no explicit or implied claims to the validity of this information.
Any trademarks referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information.