Novell Server Consolidation and Migration Toolkit 1.1, Administration Manual, Page: 110 / 126

110 Novell Server Consolidation and Migration Toolkit Administration Guide
no
vd
ocx
(E
NU)
9 Decem
ber
200
5
• Enter
smdr new
at the destination server console. This re-creates the SMDR configuration
and allows
nuwagent.nlm
to load.
12.9 NICI Errors
If you are getting NICI errors when eDirectory is trying to load or when you are copying the NICI
files in Migration Wizard, this might mean that your NICI files are corrupt. To correct the problem,
follow these steps on the server that is getting NICI errors:
1 Copy the
*.nfk
file from NetWare 6.5 CD 1 (Operating System) to the server’s
sys:system
directory.
2 Rename the
*.nfk
file that you just copied to
nicifk
(this has no extension).
3
Go to the Novell Support Web site (http://support.novell.com/filefinder) and download
nrepair3.exe
.
4 Extract
nrepair3.exe
and locate
nrepair.nlm
.
5 Run
nrepair.nlm
on the server, clicking Yes at all the prompts.
6
Reboot the server.
7
Load
pki.nlm
on the server and verify that you are no longer getting NICI errors.
If you still see NICI errors, refer to TID #10025666 (http://support.novell.com/search/) in the Novell
Knowledgebase.
12.10 NMAS Error When Migrating from NetWare
5.1
When migrating from NetWare 5.1 Support Pack 7 with eDirectory 8 to NetWare 6.5 Support Pack 2
using Migration Wizard 8.0, NMAS
TM
might show a - 1660 (0xFFFFF984) error after completing
Step 3 (Start NDS
®
/eDirectory Migration) and rebooting the server and client.
This is the expected behavior because this is a new server that hasn’t been fully installed, so there
are no objects in the Security container, which means that NMAS (and other security products such
as NICI and PKI) have not been configured.
If you have Novell Client
TM
4.9 and later, you must disable the NMAS authentication. Right-click
the N icon, select Novell Client Properties > Advanced Login , then deselect the NMAS
Authentication option.
12.11 NDS/eDirectory Migration Failures
If the migration fails during the NDS/eDirectory Migration step, you need to restore the source and
destination servers to their original configuration before you can retry the NDS/eDirectory
migration. The instructions for restoring the servers to their original configurations are different
depending on when the migration of data failed.
If Begin NDS/eDir Migration (Step 3) failed and the destination server did not reboot and take on
the name and identity of the source server, complete the steps in
“Restore Source Server to Its
Original Configuration” on page 111 .