When performing a file migration, the following warnings and errors are received in the FileMigration__DateTimeStamp.log:
* Warning * [12:12:57:073] Cannot copy file \\?\UNC\GWISE1\SYS\users\username\trash\old\BindView\Scheduled Reports\Sarbanes Oxley\Very Long PathName\Very Long PathName\Very Long PathName\Netware\file server disk Very Long FileName.pdf; error code is 123.
* Error * [12:12:57:083] Cannot get the ACL on folder \\?\UNC\GWISE1\SYS\users\username\trash\old\BindView\Scheduled Reports\Sarbanes Oxley\Very Long PathName\Very Long PathName\Very Long PathName\Netware\file server disk Very Long FileName.pdf. Error code is 2.
Folders or files that end up with a path longer than 260 characters on the target Windows server can be migrated; however, there are no known commercial tools that allow users to view these folders and files with long path names.
For more information, refer to <http://support.microsoft.com/kb/210631/en-us>.
Folders or files with a path already longer than 260 characters on the source Netware server cannot be accessed by NDS Migrator and therefore cannot be copied.
This limitation still exists even if the target platform is Windows 2012. Source path cannot exceed 260 characters, while the target has to be less than or equal to 4k. The source path limitation comes from the NDS API we use to open the file handle, hence unfortunately we cannot access longer paths.