This is another of Windows NT's lovely quirks.
ADSM's limits are based upon the limits of the O/S or Filesystem.
Path Too Long Error Message When Exceeding MAX_PATH
The information in this article applies to:
* Microsoft Windows NT Workstation versions 3.51, 4.0
* Microsoft Windows NT Server versions 3.51, 4.0
SYMPTOMS
Windows 95 and Windows NT 4.0 clients can expand a server directory
structure beyond MAX_PATH (256 characters) by accessing a server share and
creating directories and files through the network.
As a result, a server running Windows NT 4.0 will return the following error
message if the server administrator tries to access these files or
directories locally on the server through Windows NT Explorer:
Can't access this folder.
Path is too long.
Attempting to create a new folder may return the following error:
Unable to create the folder '<name>'.
The filename or extension is too long.
A server running Windows NT 3.51 will show unexpected results in File
Manager such as a general protection fault (GP fault), WINFILE crash, or
display of nonexistent directories.
Several tools and programs may also show problems when working with this
directory structure that exceeds MAX_PATH.
CAUSE
Win32 programs are limited to a 256-character string size limit because of
the MAX_PATH variable. Software programs can work around this problem by
passing Win32 a path that is MAX_PATH or less. The real underlying path can
then be accessed independently of the real length of the path. In this way,
a program can access files or directories beyond MAX_PATH on the server.
RESOLUTION
To resolve problems when the directory structure exceeds MAX_PATH, use
either of the following methods:
* On the server that contains the long directory structure, access
these files and directories through a local redirection ("net use") of the
same share the network clients access across the network.
-or-
* In Windows NT Explorer, select the folder one level above the folder
that returns the error. Right-click the folder returning the error and
select Rename. Rename the folder to reduce the number of characters used in
the folder name.
STATUS
Microsoft is researching this problem and will post new information here in
the Microsoft Knowledge Base as it becomes available.
MORE INFORMATION
The problem described above could not be reproduced with NTBACKUP and files
and directories that were beyond the MAX_PATH limit could be backed up and
restored successfully.
Additional query words: User Interface explore
Keywords : kberrmsg kbui kbbug4.00 kbbug3.51 NTSrvWkst
Version : WinNT:3.51,4.0
Platform : winnt
Hardware : ALPHA PPC x86
Issue type : kbbug
Solution Type : kbnofix
-----Original Message-----
From: Dwight Cook [SMTP:decook AT AMOCO DOT COM]
Sent: Monday, June 07, 1999 3:28 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Maximum Length of path name
If you look into some of the API constant declarations you will
find
such things as the HLQ with length 255, LLQ length 255,
filespacename
64, filename 64 (or 255) anyway it works out to a MASSIVE
length for a
fully qualified name.
Well, 280 might be on the excessive side...
______________________________ Reply Separator
_________________________________
Subject: Maximum Length of path name
Author: pricerr (pricerr AT WESTINGHOUSE DOT COM) at unix,mime
Date: 6/7/99 3:23 PM
Is there a maximum length of path name for a file to be backed up
with ADSM.
I have an NT system that is failing consistently on a file. One
unusual
property of this file is that the path name is about 280 characters
long.
Configuration: AIX Server 3.1.2.1, NT Client 3.1.0.3.
Bob Price
Systems Management Specialists
(Westinghouse Account)
4350 Northern Pike
Monroeville, PA 15146-2886
Email: pricerr AT westinghouse DOT com
Voice: (412) 374-3247, (WIN) 284-3247
FAX: (412) 374-3470, (WIN) 284-3470
|
