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

no
vd
ocx
(E
NU)
9 Decem
ber
200
5
Troubleshooting Server Migrations 109
• If Migration Wizard encounters filenames with a total path length of more than 256 bytes, the
file copy stops. You might need to reorganize the data on your source server if your path
lengths are longer than 256 bytes.
12.5 Data Set Currently In Use Errors in the Error
Log
If you see
NWSMTS error: Data set is currently in use and cannot be
accessed
errors in the error log file after the migration, it means the specified files were open
during the file copy and were not migrated. You can expect to see these errors for files such as
sys:_swap_.mem
and others that are always open. These errors are mainly informational.
12.6 SMDR Errors
Sometimes the SMDR program that is running on the destination server can’t make a connection to
the source server. To correct this problem, try one or more of the following:
• Unbind the protocol you are not using from the destination server. For example, if you are
using IP for the migration but IPX is bound on the destination server, unbind the IPX protocol
on the destination server during the migration.
• If Migration Wizard can’t load the appropriate tsa.nlm on your destination server, manually
load it from the destination server console and following the onscreen instructions. Or, enter
smdr new
at the server console to re-create the SMDR object.
• Load
smdr.nlm
at the destination server console and then enter
smdr new
at the destination
server console to solve SMS problems.
• Make sure the latest NLM
TM
programs are loaded on your servers.
Migration Wizard automatically copies the required NLM programs to the source and
destination servers. To verify that you have the latest NLM programs loaded, check the files in
the
NetWare Migration Wizard\products\nw3x
directory. You might need to load
TSA312 manually.
• Check your primary connections. Right-click the N icon, then select NetWare Connections .
Make sure the destination tree and server are marked as Primary.
• Reboot the source server.
12.7 Restoring Trustees
• If the trustees fail to restore and you get a 0xfffffffb error, this means that you did not modify
your server’s IP address in all the necessary places. For more information, see Section 11.5,
“Migration Step 2: Edit Configuration Files,” on page 101 .
• If you need to restore trustees, you can click the Finish NDS/eDir Migration button in the
Migration Wizard, or select Restore Trustees on the toolbar.
12.8 Nuwagent.nlm Load Errors
Nuwagent.nlm
is the NLM program that Migration Wizard uses to do much of its work. If you
get errors that the
nuwagent.nlm
won’t load, try the following:
• Manually load
nuwagent.nlm
at the server console.