Help! XCACLS fails - Alternate solution

  • Thread starter Thread starter paul
  • Start date Start date
P

paul

Hello,
We have been using XCACLS to modify permissions on
Windows 2000 Servers and files systems that reside on unix
systems which has ntfs permissions on it. However we
noticed that even with the /Y /C options, many times
XCACLS fails to process certain directories which are
either too long and/or has some characters such as ,;-/
etc., The directories and files with such characters and
lengh exist. But XCACLS completely aborts inspite of
the /C, /Y options as soon as it encounters such long
directories and filenames.

This is the error:

"The filename, directory name, or volume label syntax is
incorrect."

and problem with filenames/directory names such as:
"DD1A DCTC Comparison Table for Internal Design
Verification (DD200, x16, 85C, -10C, 1."


After the above error, it just totally aborts.

There are several directories like this at different
levels. We couldn't possibly do this manually. Any
advise on what other sophisticated tools that we can use
and is fool proof. Or is there any other way we could
rectify this?
 
use "quotations" in your scripts
Hello,
We have been using XCACLS to modify permissions on
Windows 2000 Servers and files systems that reside on unix
systems which has ntfs permissions on it. However we
noticed that even with the /Y /C options, many times
XCACLS fails to process certain directories which are
either too long and/or has some characters such as ,;-/
etc., The directories and files with such characters and
lengh exist. But XCACLS completely aborts inspite of
the /C, /Y options as soon as it encounters such long
directories and filenames.

This is the error:

"The filename, directory name, or volume label syntax is
incorrect."

and problem with filenames/directory names such as:
"DD1A DCTC Comparison Table for Internal Design
Verification (DD200, x16, 85C, -10C, 1."


After the above error, it just totally aborts.

There are several directories like this at different
levels. We couldn't possibly do this manually. Any
advise on what other sophisticated tools that we can use
and is fool proof. Or is there any other way we could
rectify this?
 
Back
Top