Disk Utility (10.5.6) error: File name too long

Hello, here is one for you all...
I am in the midst of creating a new "build image" so I can start deploying Leopard.
Before I upgraded the build to 10.5.6 I was able to create a disk image of this build machine.
After updating it to 10.5.6 and all of the current Apple updates I am no long able to create a disk image.
I keep getting an error several minutes into the imaging process that says +"*File name too long".*+
I've run permission repair on the disk and Disk Warrior with still no luck. I've also used different machines and a boot FireWire drive to make he image and still have had no luck. I can use CCC to clone my Master build to another machine but I need to be able to make an image of it.
Thanks in advance for any help.

Bear in mind that in Unix, a file name includes the path, so if you have a very deep file or perhaps some kind of infinite recursive link, that might cause the problem, since that would make the file name very long indeed.
This may not be the problem you are having, but it just came to my mind when I read your post

Similar Messages

Consolidating Library Error: File Name Too Long, But What File?

I am trying to consolidate my library to put all my music (very unorganized) in one spot so I can back it all up. When I try to consolidate, it takes a second to prepare, then immediately brings up an error window saying "Copying Music Failed. The file name was invalid or too long."
How do I fix this? I really would like to back up my music!

Hi, ZeroGravity107.
This can be a tricky problem to figure out since iTunes doesn't specify what file name is "invalid or too long" and there's no documentation on what determines if a file name is "invalid or too long".
We had one user report that he was able to use his/her keen eyesight to note the last file that appeared before the error message appeared and it turned out that file was the cause of his/her trouble.
If your eyesight isn't that keen, I'd suggest concentrating on the file name being too long possibility.
The entire directory path leading to the file is considered part of the file name so, as an example, iTunes' default settings might place a particular file at C:\Documents and Settings\ user name \My Documents\My Music\iTunes\iTunes Music\artist folder\album folder\whatever.m4a.
Is the directory path leading to your consolidated location much longer than that?
polydorus has suggested a way to look over your file names: Assuming your music is currently in the default location, make your way there with Windows Explorer and select List in the View menu menu and see if anything stands out as being unusual.

JAXB: Error compiling classes generated by xjc (file name too long)

Hi friends,
I am trying to compile classes that are generated by using XJC tool on xsd file. The compilation fails with following message.
buildxsdmodel:
    [javac] Compiling 794 source files to /home/uchamad/working/teleworker/ejb/build/classes
    [javac] /home/uchamad/working/teleworker/ejb/build/tmpsrc/uk/co/novatel/teleworker/model/wlr/bulksearch
results/impl/ApplicationInformationTypeImpl.java:58372: error while writing
uk.co.novatel.teleworker.model.wlr.bulksearchresults.impl.ApplicationInformationTypeImpl.XMLRequestID
TypeImpl.SearchOrderResultsTypeImpl.SearchTypeDetailTypeImpl.OrderTypeImpl.OrderDetailsTypeImpl.
OrderLinesTypeImpl.NumberPortingTypeImpl.OLODetailsTypeImpl.NumberLocationTypeImpl.OLOMainP
STN1AddressTypeImpl.Unmarshaller: /home/uchamad/working/teleworker/ejb/build/classes/uk/co/novatel
/teleworker/model/wlr/bulksearchresults/impl/ApplicationInformationTypeImpl$XMLRequestIDTypeImpl$S
earchOrderResultsTypeImpl$SearchTypeDetailTypeImpl$OrderTypeImpl$OrderDetailsTypeImpl$OrderLin
esTypeImpl$NumberPortingTypeImpl$OLODetailsTypeImpl$NumberLocationTypeImpl$OLOMainPSTN1A
ddressTypeImpl$Unmarshaller.class (File name too long)
    [javac]                                             public class Unmarshaller
    [javac]                                                    ^
    [javac] 1 error
The compiler is complaining about the file name being too long. This is happening because the java classes when generated from XSD contains deep nesting of inner classes. So when it comes to compile the .class name file is too long for the operating system.
I am trying this on unix box.
I wonder if there is a way to configure XJC so that it does not produce inner classes but instead keep them out.
Any help would be appreciated.
many thanks
Usmangani

Flattening your schema definition will flatten the output files, too -- that will probably be nice for coding as well since you wont have to use class names such as SomeTypeNestedInAnotherTypeThatHasYetAnotherType. Instead of having all of the elements defined directly within the enclosing root element, define logical chunks at the top level and incorporate them in the definition of real root element of your documents by reference.

File name too long cannot copy (cont'd)

This is a continuation of the post started September 01, 2009, with the last post on
October 17, 2011 named File name too long cannot copy
Since this is an ongoing unsolved issue, and the thread was locked, it continues here.
It is ever so easy to create a long file/path using explorer.exe as will be shown below.
What needs to be solved is, what is an easy way (no, not by listing out all the files in a directory to a text file and counting characters), perhaps using a shell extension, to find out which files in a directory and it's subdirectories will be (or were)
too long to copy, (and then perhaps even copying those over either intact or renamed)?
Maflagulator said:
I'm running the 7100 build...enjoying it except for one big thing:
While attempting to copy 402gb from my main storage volume onto a spare 500gb drive (for the purpose of changing to a new RAID array) I've come across something that I would expect a Windows 98 OS to give me.
It tells me that a file has TOO LONG of a file name, then provides with two unhelpful options: SKIP or CANCEL
I never had XP give me an issue like this at all, so what gives? And while some specific files did have long file names (such as for songs, etc.) it had 7 issues with folders stating that their name was too long, but in fact they were not since they were
titled '07-06-07' for the date that I dumped the audio files in them. However, they may have contained FILES with long file names though.
Anyone else get this same situation? Perhaps the RTM version does not do this? Can anyone verify this regarding their install of the RC or the RTM?
It made it through 400gb out of the 402gb transfer.
I'm just happy to see that it doesn't spazz out about an issue like this until it has done all the other transfers that it can do because it saves the issues it has with files until the very end. In XP it would spazz about it the moment it came across it
causing the transfer process to halt.
Since long path/file names can so easily be created on Win7, it might be useful to see a typical way this happens, which might then give clues how to work with them.
In Windows Vista, we learnt from:
File names and file name extensions: frequently asked questions that:
Windows usually limits file names to 260 characters. But the file name must actually be shorter than that, since the complete path (such as C:\Program Files\filename.txt) is included in this character count.
In Windows 7, we are told here:
File names and file name extensions: frequently asked questions that:
It depends on the length of the complete path to the file (such as C:\Program Files\filename.txt). Windows limits a single path to 260 characters. This is why you might occasionally get an error when copying a file with a very long file name to a location
that has a longer path than the file's original location.
From the Windows Dev Center - Desktop, we read about Maximum Path Length Limitation here:
Naming Files, Paths, and Namespaces
This helps us understand why a folder can be a maximum of 244 characters, from the defined 260 length of MAX_PATH as follows:
260 minus C:\ (3) minus <NUL> (1) = 256
256 minus 8.3 file name (12) = 244
We also learn there that: The Windows API has many functions that also have Unicode versions to permit an extended-length path for a maximum total path length of 32,767 characters.
And we read the claim that: The shell and the file system have different requirements. It is possible to create a path with the Windows API that the shell user interface is not be able to interpret properly.
There is also a comment below this document that reads: In a previous iteration of this document, it is mentioned that The Unicode versions of several functions permit a maximum path length of approximately 32,000 characters composed of components up to
255 characters in length. This information is now gone.
So we are in a position where the file system and Windows API can create long path/flies that the shell cannot handle.
But then we need to be able to handle it, so a little exploration might lead to a better understanding of how to do this.
For most tasks being performed on long folder/files, Windows 7 and other Windows programs balk when the Path+Filename length > 260
Let's create a long path/file.
Create a folder called A at the root of a Drive.
Create a sub-folder of A called: B
Create a sub-folder of B called: C
Make a FILE in sub-folder C called (no spaces or break, one long continuous string): 123456789A123456789B123456789C123456789D123456789E123456789F123456789G123456789H123456789I123456789J 123456789K123456789L123456789M123456789N123456789O123456789P123456789Q123456789R123456789S123456789T
123456789U123456789V123456789W123456789X123456.txt
Rename sub-folder C to the string (no spaces or break, one long continuous string) (The actual directory created will be slightly shorter than this full length): 123456789A123456789B123456789C123456789D123456789E123456789F123456789G123456789H123456789I123456789J
123456789K123456789L123456789M123456789N123456789O123456789P123456789Q123456789R123456789S123456789T 123456789U123456789V123456789W123456789X123456789Y123456789Z
Rename sub-folder B to the same full string above. (The actual directory created will be slightly shorter than this full length but 2 characters longer than the step above.)
Rename folder A to that same full original string. (Again the actual directory created will be slightly shorter than this full length but 2 characters longer than the step above.)
You now have the lovely file placed at (the breaks are just so it fits into the screen):
C:\123456789A123456789B123456789C123456789D123456789E123456789F123456789G123456789H123456789I123456789J 123456789K123456789L123456789M123456789N123456789O123456789P123456789Q123456789R123456789S123456789T 123456789U123456789V123456789W123456789X1234\ 123456789A123456789B123456789C123456789D123456789E123456789F123456789G123456789H123456789I123456789J
123456789K123456789L123456789M123456789N123456789O123456789P123456789Q123456789R123456789S123456789T 123456789U123456789V123456789W123456789X12\ 123456789A123456789B123456789C123456789D123456789E123456789F123456789G123456789H123456789I123456789J 123456789K123456789L123456789M123456789N123456789O123456789P123456789Q123456789R123456789S123456789T
123456789U123456789V123456789W123456789X\ 123456789A123456789B123456789C123456789D123456789E123456789F123456789G123456789H123456789I123456789J 123456789K123456789L123456789M123456789N123456789O123456789P123456789Q123456789R123456789S123456789T 123456789U123456789V123456789W123456789X123456.txt
You have a folder length of over 700 and a file length of over 250 for a total of over 950
However you will notice that each folder, when created, could only be a maximum of 247 charachters including the path (example C:\ , & C:\A , & C:\A\B
This only applies backwards, that is up the path. It did not matter what was further down the path.
Now, you can't easily access or rename the file, but you can rename the folders easily.
For best results, start renaming from the top of the Tree, working down the subfolders, because renaming from down up will limit you, and in fact won't work if the folder lengths are too long.
So how might knowing this help us?
Well, to copy this long_file from the C:\ drive to the D:\ drive, and keeping the path structure, this should work:
Note the name of the top folder. Rename it to something very short, say: A (Make sure C:\A does not exist)
Note the name of the 2nd folder. Rename it to something very short, say: B (Make sure C:\A\B does not exist)
Note the name of the 3rd folder. Rename it to something very short, say: C (Make sure C:\A\B\C does not exist)
Make sure D:\A does not exist - then copy the A folder on disk C: to disk D: (which gives you D:\A\B\C\long_file
Rename D:\A\B\C to D:\A\B\Original_3rd_Folder_name
Rename D:\A\B to D:\A\B\Original_2nd_Folder_name
Rename D:\A to D:\Original_top_Folder_name
Rename C:\A\B\C back to their original names, in this same reverse order starting with C, then B, then A
Note: If using Explorer, at some points you might have to press the F5 refresh key.
This is of course how you might copy such long path/files without using the other more "easy" techniques for the "normal" everyday user like:
sharing a sub-folder
using the commandline to assign a drive letter by means of SUBST
using AddConnectionunder VB to assign a drive letter to a path
using the "\\?\" prefix to a path string to tell the Windows APIs to disable all string parsing and to send the string that follows it straight to the file system
and so on.
See how simple Windows can be for Dummies!
But then, how can we know that files to be copied exceed this MAX_PATH? Or also after a copy has taken place, know exactly which files that have NOT been copied because of exceeding the MAX_PATH limit, and then a procedure to copy these either by renaming
them, or by copying them intact as they are?
There have been suggestions to use
LongPathTool, but this does not have a facility to check a series of folders and tell you which files are going to be caught by the error when copying. So once a copy has taken place using Windows 7, one does not know which files did not get copied, and
where exactly they are located.
Neither does the free
Old Path Scanner do that. It can only check for overly long directory paths, but misses out when the directory path is within limits, but adding in the file name puts it out of bounds.
So, as shown above, it is ever so easy to create a long file/path using explorer.exe
So, what then is an easy way (no, not by listing out all the files in a directory to a text file and counting characters), perhaps using a shell extension, to find out which files in a directory and it's subdirectories will be (or were) too long to copy,
(and then perhaps even copying those over either intact or renamed)?

This is a not a "solution" ....but a "work around": a low tech fix....for error message "your file name is too long to be copied, deleted, renamed, moved" :
1.   problem is this: the "file name" has a limit on number of characters.....the sum of characters really includes the entire path name; you gotta shorten it first (i.e, if the total number of characters in the file name + Path name are over the
limit, the error appears). The deeper your file folder sub levels are, the more this problem will come up, especially when you copy to a subfolder of a subfolder/subfolder of another path ...adds to character limit)
2. How do you know which combined file names + path names are too long if you are in the middle of a copy operation and this error pops up? Some files copied but the "long files error message" says "skip" or "cancel" ... but not which
files are the "too long" ones. If you hit "skip" or "cancel" the "too long" files are left behind...but are mixed in with non-offender "good" "short name" files.   Sorting thru 1000s of "good" files to find a few "bad" ones manually is impractical.
3.   Here's how you sort out the "bad" from the "good":
4.    Let's say you want to copy a folder ..."Football" ...that has five layers of subfolders; each subfolder contains numerous files:
C:/1 Football / 2 teams/ 3 players/ 4 stats/ 5 injuriessidelineplayerstoolong
       There are five levels root "1 football" with subfolders 2, 3, 4 and lastly "5 injuries"
5.    Use "cut" and "paste" (for example to backup all five levels to a new backup folder):
       select "1 football" ....cut....select target folder....paste
       ("cut" command means as the files are copied to the target destination, the file is deleted from the source location)
      Hint: avoid "cut" and "paste" to a target folder that is itself a sub/sub/sub folder ...that compounds the "characters over the limit" problem ...because the characters in the sub/sub/sub folder are included in the "file name
character limit"...instead "paste" to a C:/ root directory.
       Suppose in the middle of this operation...error pops up: "5 files have file names that are too long" Skip or cancel?
       select "skip" ...and let operation finish
6.    Now go back and look at the source location: since the software allows only the "good" "short name" files to be copied (and because you "skipped" the "bad" "Long name" files so they are not copied or deleted) ...all that remains
in the source location are the "bad" "long name files" (because "good" ones were deleted from the source location after the "cut" operation...the bad ones stick out like a sore thumb.
7.   You will find ....all that remains in source folders are: the "bad" "too long" files; in this example the "bad" file is in level 5:
      C:/ 1 football / 2 teams /3 players /4 stats /5 injuriessidelineplayerstoolong
8.   select folder 5 injuriessidelineplayerstoolong (that's right...select folder, not file) gotta rename the folder first.
9. hit F2 rename folder..folder name highlighted...delete some of the letters in the folder name:
       like this:   5 injuriessidelineplayers ....you should delete 'toolong'....from the folder name
10. then go into folder 5....and do the same operation ...with the too long file name:
        hit F2 rename file....file name hightlighted...delete some of the letters
           like this: injuriessidelineplayers.....you should delete 'toolong' from the file name
11. Now..."cut and paste" the renamed file to the target backup folder.
The Error message will pop up again if you missed any "bad" files....for example, it will indicate "5 files too long" ....then repeat process 5 times until you fix all of them
12.    Finally, copy the target destination files back to the source location (when you are certain all source location file folder locations are empty)
Of course, this "makeshift" solution would not be necessary if MSFT would fix the problem...

"Maximum number of application files exceeded or file names too long"...help!!!

Hi there…
I am trying to create a game for my mobile.
The “problem” is that I have more than 500 swfs that I want to pack using the Adobe Mobile Packager. And I am getting this error:
“Maximum number of application files exceeded or file names too long”
How could I solve this problem?
Thanks everyone!
Cheers.
Leo.

500?? What are there so many files?
The problem is that the CAB format only allows for 300 files maximum, so there's nothing that we can do about that I'm afraid.
Mark
www.flashmobileblog.com

Receiving ERROR meassage when trying to copy..file name too long.

Hello.
There is an error code number, but didn't write it down...will do so, if no-one can answer this question at the minute. I am not at the Mac at the moment, so this post is pre-emptive.
Problem:
If I try to copy over a folder with photoshop images onto another drive, the copy is incomplete due to the name/s of the files being too long, apparently.
The error message says something to the effect: 'the names are too long can't complete copy'.
The file names are about 10-12 [at most]characters in length.
Please advise
Chris

If the drive is formatted HFS then you are limited to 32 characters on a file name. If it is formatted HFS + then you can have file names as long as 255 characters. I am not familiar withi the format you say the drive is formatted in so I can't speak to it.
If you are receiving -50 errors that can indicate a file name that is too long OR an illegal character in the filename regardless of its length.
If you are actually using 10.3.8 as your profile states then that may be part of the problem. Many of these problems existed in 10.3.X but were fixed in 10.4
I remember that 10.3.8 had issues copying to external drives when there were more than a certain number of characters in a filename. I don't remember the number but for some reason 10 or 12 is what comes to mind. It caused me many problems when I would try and copy files to a Zip disk that I used to have. Since I updated to 10.4 those issues have never occured again.
Since you know what folder the problematic files are in why not just open the folder and try to copy files one at a time. When you get to the one(s) that is a problem, change the file name to something shorter.
A better solution would be to update to 10.4 but with 10.5 coming out sometime in the Spring of 2007 this may not be the time.

Importing iTunes library from a Mac to PC--File name too long error.....

Hi...
Hope someone can help. Ive been forced to use a PC at work (Win7) and am trying to install my 84 gig library from my Macbook Pro to the PC. During the course of the import, i get an error stating that a file is too long, and then the whole process aborts....any suggestions?
thanks in advance!
yp

Log into the migrated account, find the content, choose Go to Folder from the Finder's Go menu, provide /Users/Shared/ as the path, drag it there, and access it from the new account.
(100256)

HT4790 My Mac OS Lion 10.7 FileVaulted HD does not boot, prohibitory sign, stop sign appears some minutes after boot starts. Disk Utility repair shows four error messages: Unable to bootstrap transaction group 2517: inconsistent crosscheck (the same with

My Mac OS Lion 10.7 FileVaulted HD does not boot, prohibitory sign, stop sign appears some minutes after boot starts. Disk Utility repair shows four error messages:
Unable to bootstrap transaction group 2517: inconsistent crosscheck
No valid commit checkpoint found
The volume xxxxxxxxxxxxxx(here it shows physical volume number) was found corrupt and can not be repaired.
Problems were encountered during repair of the partition map
Error: Storage system verify or repair failed.
(the same with 2518, 2519 and 2520 transaction group)
I suppose it is serious bug in Mac OS Lion managing FileVault and wonder what the help could be?

Most likely culprit is your Lacie drives which are notorious for flaky power supplies which cause just the sort of erratic behaviour that you describe. Have had similar issues myself. Lacie has been good about replacing my power converter-- twice. If you have seven of them, good luck finding the bad one or more. Like I said, the behaviour is erratic. Sometimes it'll work sometimes not. I can't comment on Samsung drives because I've never used them and have never heard anything about them. Same with Softraid. Why not just use Disk Utility. Sounds like you're ready for an external hardware raid. This will be much faster, much more reliable, and may even be cheaper than seven firewire drives. Check out G Tech, and Maxx Digital for starters.
Best of luck
Terry

How can I burn a disk of photos with a modified file name?

After importing photos from scan device, I use Photos > Batch > Change to rename files. When burning a disk the changed file names do not transfer with the image but use the original file name. How can I burn a disk of photos with the modified file name?
This is what I have done so far with no success.
Drag selected photos from Event to Burn Folder where the file names were changed. Burn folder lists file with original file name.
Drag albums to Burn Folder with the same result.
In Filer I am able to change the iPhoto Library > Master > Date > Filename and then drag to burn disk folder and see the changed name but this is a single file exercise without a view of the file's image, but to use the new file name in iPhoto events I have to repeat the naming convention.

File > Export.
In the resulting dialogue note the "Name" section. Choose to use the Title as Filename.
Regards
TD

Need assistance with my Porsche Design LaCie Time Capsule... It is not operating at all.. I have ran the diagnostic via the Disk Utility and under the error reading it runs the repair and then says it not about to repair what do I do... Thanks

Need assistance with my Porsche Design LaCie Time Capsule... It is not operating at all.. I have ran the diagnostic via the Disk Utility and under the error reading it runs the repair and then says it not about to repair what do I do... Thanks

LaCie doesnt make ANYTHING. It contains a Seagate 3.5" 5400RPM HD.
Check the HD on another computer, if nothing, your SATA bridge is fried, or the HD (very unlikely since its a Seagate inside)
Youd have to crack open the HD, remove the SATA bridge cart thats plugged into the HD and put the HD into an enclosure or a HD dock to get the data
those external HD use a 50 cent SATA bridge famous for failing. The curse of all the good HD externals is the junk 3rd party SATA bridges attached to them that crash and burn.
Sata bridge:

Catalog file names to long

after upgrading from 10g to 11g
I see how to restore the repository from backup..
but how do I restore the catalog from backup..
If I try to copy from a backup to the SH catalog folder I get a bunch of file name to long errors, do you want to skip this file..
(this is on windows)

bryannew wrote:
Hi all,
I am working on a mix project for a band and am having issues with one song.
The song has previously been mixed in Logic and I am working from a "Save copy as " version - do not have access to original source files.
In the provided audio folder all audio files are named "The code 24 bit export -" followed by the name of the instrument (e.g. bass, Keys etc.).
When I open the song/session Logic asks for me to point it to the folder containing audio files "The code 24 bit export - #643"
Unfortunately... you are in a world of trouble and pain.
The numbers in the file name refer to the -original- disk geometry (block location) the files were recorded on. Once moved they lose that relationship with the project file and you are s--- out of luck.
There was a time when Logic would've tried to load the project anyway and your audio files would be an amalgam of whatever was at the disk location, a file might have bits and pieces of vocal, guitar, noise..etc...etc.
Without the original disk you have to rebuild.
I guess the long file name limitation has been corrected in version 9.1.
pancenter-

File communication channel issue : object name too long

Hi Experts,
My requirement is to place the successful files in folder and un-successful files in one folder after processing.
we used parameterized mapping to achieve this requirement.
I'm facing below issues, please help me to resolve.
" An error occurred while connecting to the FTP server. The FTP server returned the following error message: 'com.sap.aii.adapter.file.ftp.FTPEx: 501 Unexpected reply codeSpecified object name too long, limit is 10 characters: $Filepath_Su.'. For details, contact your FTP server vendor.
As per my understanding it is not taking the path specified,because of length issue.
Please send me your valuable inputs and help me.
Thanks in advance for your help.
Regards
Bhargava Krishna

Hello,
By loking ur error description, it's quite evident that it's a FTP sever issue?
Sometime on FTP server, there is a check which is enabled to limit the length of file names, and i think the same has been recently implemented on ur FTP server. So instead of changing ur config, check with ur FTP admin.
Tested the same after tweaking existing FTP server settings.
Thanks
Amit Srivastava

Framemaker uses $filename for short file name, can we edit this to change appearance? We do not want the short file name of long filename to include the .fm extension can this be removed or modified to make this happen?

Framemaker uses <$filename> for short file name, can we edit this to change appearance? We do not want the short file name of long filename to include the .fm extension can this be removed or modified to make this happen? In compiling our books it would be helpful to not have this extension appear as it then requires us to create extra files without them.

See: System Variables

File path too long when collecting??...

Hi all,
REALLY hope someone has some wisdom on this! I've searched forums and the web and not yet found an answer....
I've got a MASSIVE project on an external drive that's on the way out, so I want to collect the project that's on it to another new healthy drive. The current file structure leaves alot to be desired (several years of updating the same project and splitting it into managable portions then importing them back together several times, files still on there that aren't in use in AE anymore but have been kept 'incase we need them again later', etc...you can imagine the mess!)
SO, I'm getting the 'file path too long' error when trying to collect it. Now, I could manually go through every folder and sub folder and tidy things up within AE - this would days about a week I reckon! - but I'll do it if that's the only way. What I'm wondering is this: -
A) is the problem AE is having with the deep structure *WITHIN* ae project, or with the actual folders/files on the disk itself?
B) if I tidy it up in AE only will that fix it?
C) is there an easier way to do this rather than manually going through everything and looking for the offenders???
Thanks guys,
Jim.

GULP....so I have to reorganise my assets OUTSIDE of AE and then relink it all WITHIN AE afterwards?? With 3 x 430GB projects and thousands of assets that is going to take a looooooooonng time.
What I don't understand (or like) is how AE will let you get this far without any warning and still operate/save, etc but then when you come to collect is goes 'urr urrrr, computer says no'.
Is there really no way of automating some of this then? I mean even a script that highlighted items in the project that are over the maximum path length would save a hell of a lot of manual searching and counting.
Thanks for your replies guys but.....AAAARRGGHH!!!!!

Client-error-request-value-too-long

What is this error???? I am trying to add an Epson 1280 printer and I get this error. I have the most current driver and not sure why this isn't working.

My flatmate had this "client-error-request-value-too-long" problem with her (powerpc) powerbook. Nearly everything I tried didn't work:
1) Reinstalling drivers
2) Permissions repair
3) Resetting print system using Fixamac's Printer Setup Repair Utility
4) Updating from 10.4.10 to 10.4.11
5) Using the command line to try and recreate the directory: /var/spool/cups/tmp (which told me it already existed)
6) Using Transmit (with show invisible files turned on) to browse to /var/spool/cups/ and try and recreate the tmp folder
On the last point I couldn't change anything about the /var/spool/cups/ directory because the permissions were corrupted in some way. It keep telling me tmp already existed but I couldn't see it.
In the end what did work was enabling and logging in as root, browsing to /var/spool/ using Transmit and deleting the cups folder and then recreating. It took a few tries to delete too, but in the end I managed to remove it.
Of course I wouldn't actually recommend this. I'm no Unix geek so god knows what I might have broken in the process, so I'm going to reinstall her system with the Archive and Install options when I get a chance, which is what I'd recommend doing in the first place to anyone having this problem.

Disk Utility (10.5.6) error: File name too long

Similar Messages

Maybe you are looking for