B
Bikini Browser
Hello everyone...
I'm trying to migrate files from a Windows SBS 2000 server to a Windows 2003
SBS R2 new server. The data drive is alone so I should be able to just copy
ALL the data from one drive to the other using Winwows Explorer. Both target
and destination drives are NTFS.
I am using the standard Windows Explorer, click-dragging folders from the
old data drive to the new 2003 Server's Hard Disk. Everything works as
expected except that every once in a while I get a message like "The
filename you specified is invalid or too long". and then the copying stops.
This usually happens in folders that are nested 3 to 5 levels "deep" ore
more in the folder tree.
Here is one example of a file name I found:
"Report on complience and internal control over financial reporting based on
an audit of financial statements performed in accordance with government
auditing standards.wpd"
I can't always shorten the file's name, because the users expect to find the
same file names on the new server. However when I change the file name for
some of the files they then copy OK.
This is very annoying since I have to "walk down the folder tree", find the
file, and rename (i.e., shorten the name) it, for every error. Since the
error also aborts further copying, I have to find these "landmines" one at a
time, or more specifically, one per copy session.
The "offending" finenames are typically 25 to 50 characters long, and
nowhere near the 255 character limit.
So here's my question:
Is there some parameter somewhere that need to set to avoid this error?
If the filenames are really too long, why did the system not complain about
them when I originally named the files on the System Hard Disk? (This is a
GOOD Question!)
Is the problem really one of too long a filename or an "invalid" name. If
the name was invalid, wouldn't the OS have complained when I originally
assigned the name to that file on the System Hard Disk. I've looked at the
"offending" filenames carefully, and none of the forbidden characters are
present. Also, there are no leading or trailing spaces in the "offending"
filenames.
Is there a Utility with Windows 2000 or Windows 2003 SBS Server that is
similar to SCANDISK on Win-9x OSes? If there was, I could use it to find
ALL offending filenames at once, instead of having to "walk the minefield".
Is there a better way to copy contents of a folder and all its subfolders
from the System Hard Disk to a Backup Drive, that would be less sensitive to
this "long file name error".
I look forward to you ideas....
Bikini Browser
I'm trying to migrate files from a Windows SBS 2000 server to a Windows 2003
SBS R2 new server. The data drive is alone so I should be able to just copy
ALL the data from one drive to the other using Winwows Explorer. Both target
and destination drives are NTFS.
I am using the standard Windows Explorer, click-dragging folders from the
old data drive to the new 2003 Server's Hard Disk. Everything works as
expected except that every once in a while I get a message like "The
filename you specified is invalid or too long". and then the copying stops.
This usually happens in folders that are nested 3 to 5 levels "deep" ore
more in the folder tree.
Here is one example of a file name I found:
"Report on complience and internal control over financial reporting based on
an audit of financial statements performed in accordance with government
auditing standards.wpd"
I can't always shorten the file's name, because the users expect to find the
same file names on the new server. However when I change the file name for
some of the files they then copy OK.
This is very annoying since I have to "walk down the folder tree", find the
file, and rename (i.e., shorten the name) it, for every error. Since the
error also aborts further copying, I have to find these "landmines" one at a
time, or more specifically, one per copy session.
The "offending" finenames are typically 25 to 50 characters long, and
nowhere near the 255 character limit.
So here's my question:
Is there some parameter somewhere that need to set to avoid this error?
If the filenames are really too long, why did the system not complain about
them when I originally named the files on the System Hard Disk? (This is a
GOOD Question!)
Is the problem really one of too long a filename or an "invalid" name. If
the name was invalid, wouldn't the OS have complained when I originally
assigned the name to that file on the System Hard Disk. I've looked at the
"offending" filenames carefully, and none of the forbidden characters are
present. Also, there are no leading or trailing spaces in the "offending"
filenames.
Is there a Utility with Windows 2000 or Windows 2003 SBS Server that is
similar to SCANDISK on Win-9x OSes? If there was, I could use it to find
ALL offending filenames at once, instead of having to "walk the minefield".
Is there a better way to copy contents of a folder and all its subfolders
from the System Hard Disk to a Backup Drive, that would be less sensitive to
this "long file name error".
I look forward to you ideas....
Bikini Browser