So true in did not count the file name length, and it is well under the support length. The only other thing I would look at is to map on to the server and look at this file and the other files in this directory to make sure tsm is reporting the full filename in the log and that its not a file before or after causing it!
-----Original Message----- From: Rob Schroeder [mailto:[EMAIL PROTECTED]] Sent: Friday, 16 November 2001 2:00 AM To: [EMAIL PROTECTED] Subject: Re: file name length error The only issue that I have with this response is that the path and file name that I am having trouble with is 230 characters. That should be well enough under the 255 character limit. I will try the USEUNICODEFILENAMES parameter anyhow. Rob Schroeder Famous Footwear "BURDEN,Anthony" <[EMAIL PROTECTED]>@VM.MARIST.EDU> on 11/14/2001 05:55:17 PM Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] cc: Subject: Re: file name length error I hope this might help. After reading Andy's last reply I did some searching (thanks Andy for your nice reply to my last statement that I made which was wrong on my part).I found that I was out of date on this info. I run TSM client versions 3.1.08 and TSM 4.1.12, both of these clients continue to backup data when a long file name is found, but I got confused because the 3.1.08 client did not handle a directory + filename longer then 259 characters, where with the version you are running and the Ver 4 client I am running the directory + filename length is as follows.. But you must run with USEUNICODEFILENAMES YES, unless you have Mac volumes!! The maximum length of the file name itself (not including the directory in which it resides), is 255 characters. The maximum length of the directory path in which the file resides (not including the file itself) can not exceed 1,024 characters. The maximum length of any component within a directory path can not exceed 255 characters "Component" refers to a part of a structure as delimited by the backslash \ character. To illustrate: Given a path of the form x:\comp1\comp2\comp3\ Each component "compx" can not exceed 255 255 characters in length. Likewise, "filename" can not exceed 255 characters in length. In addition, the "x:\comp1\comp2\comp3" can not exceed 1,024 these limits are not supported. anthony -----Original Message----- From: Rob Schroeder [mailto:[EMAIL PROTECTED]] Sent: Thursday, 15 November 2001 8:07 AM To: [EMAIL PROTECTED] Subject: file name length error Here is the error I am seeing in my TSM error log for a Win2000 client running 4.1.3 to a Win2000 server running TSM server 4.1.4.1 11/14/2001 02:51:33 ANS1228E Sending of object '\\ffdata01\d$\Data\IS\Projects\P2915002 Aldon ACMS (Phase II)\p2915001 Software Configuration Management - Acquire and Install Aldon\document\Java classes that didnt parse\com\famousfootwear\systems\retail\forms\personal\boundary' failed 11/14/2001 02:51:35 ANS4018E Error processing '\\ffdata01\d$': file name too long 11/14/2001 02:51:35 ANS1512E Scheduled event 'DATA01' failed. Return code = 4. What is the maximum file length name that is supported in TSM? Also, according to the messages book,this file should get skipped and the backup should continue...however my backup failed. Has anyone seen this? Rob Schroeder Famous Footwear Notice: The information contained in this e-mail message and any attached files may be confidential information, and may also be the subject of legal professional privilege. If you are not the intended recipient any use, disclosure or copying of this e-mail is unauthorised. If you have received this e-mail in error, please notify the sender immediately by reply e-mail and delete all copies of this transmission together with any attachments. Notice: The information contained in this e-mail message and any attached files may be confidential information, and may also be the subject of legal professional privilege. If you are not the intended recipient any use, disclosure or copying of this e-mail is unauthorised. If you have received this e-mail in error, please notify the sender immediately by reply e-mail and delete all copies of this transmission together with any attachments.
