We analyzed the directory causing the error and also got a very helpful
hint from IBM.
The problem was caused by a too long file/pathname. A user put a file
into a shared directory and made use of the maximum possible pathlength
(255 chars).
In the real NTFS on the disk there is a path that leads to the shared
directory. Together with these additional characters the real pathname
was much longer than seen by the user's machine, which caused the error.
After renaming the file ADSM now completes without error.

Both microsoft's implementation as well as the behaviour of ADSM should
get fixed to make invalid filenames impossible and to not crash when
such a filename occurs...

Regards,
Michael
--
Michael H. Bartl
Michael H. Bartl
ADAC e.V. (Rechenzentrum, Produktionsplanung und Organisation)
Tel.: (089) 7676-4063, Fax: (089) 7676-8161
EMail: Michael.Bartl AT Zentrale.ADAC DOT de
>