Data Set Currently In Use Errors In The Error Log; Problems Restoring Trustees; Smdr Errors; Miscellaneous Errors - Novell SERVER CONSOLIDATION MIGRATION TOOLKIT 1.2 - ADMINISTRATION GUIDE 09-2007 Administration Manual

12.2.2 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.2.3 Problems Restoring Trustees

If you see the error An unknown error has occurred. (Source Server: SRV1
Path: 'SYS:SYSTEM\NUW30\TRUSTEE.REF' Error: '1' Function:
'fopen (OpenTrusteeReference)' when migrating from NetWare 5.1 to NetWare
6.5 SP6, make sure you have disabled file caching in the Novell Client. For more information,
see Section 3.1, "Meeting the Workstation Requirements," on page
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
"Migration Step 2: Edit Configuration Files," on page
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.3 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 on-screen 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
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.4 Miscellaneous Errors

This section identifies other errors that might be encountered when using the NetWare Migration
Wizard.
programs are loaded on your servers.
TM
27.
Section 11.6,
103.
Troubleshooting Server Migrations 113