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!!!!!

Similar Messages

Siteinfo.sol file path too long

Hopefully someone here can help with this problem. First, I'm
running Windows XP Pro. Every night I do an automatic backup of my
C: drive to an external hard drive (Maxtor) using Maxtor's backup
software, EMC Retrospect Express HD 2.0. However, the backup quits
when it tries to write a particular Flash file because the file
path is too long. The file at the end of the path is siteInfo.sol
and it is in a folder that is nested within 13 other folders. The
file path is:
C:/Documents and Settings/[my username]/Application
Data/Macromedia/Flash Player/#Shared
Objects/5WGFZ2N2/assets.cobalnitra.com/teams/repository/export/535/e93087b291004840/b0003 ba76d6c7/535e9308/7b291004840b0003ba76d6c7.swf
From the "teams" folder on down through the nesting, there
are no other files in any of the folders. The simplest solution
would be to delete the "teams" folder, and thus all of the folders
within it and the siteInfo.sol file, but I need to know if these
folders (from "teams" on down) and this file are necessary for the
operation of Flash Player. If they are, does anyone have another
solution? I could go into the backup program and manually designate
that every folder and file on my C: drive other than these be
backed up, but that's a pain. I would love to call Adobe technical
support, but there is no phone support for the free version of
Flash Player.
Thanks in advance for any help that anyone can provide.
Todd Serota

Todd,
This is a Flash Shared Object that was written to your
machine by cobalnitra.com. It's like a 'cookie' inside of Flash.
You can safely get rid of it, though you might lose perhaps some
saved game settings (or something saved by cobalnitra.com).
Basically if that site is something you use a lot and does
something important to you, then keep it. Otherwise you can delete
everything under the #Shared Objects folder.

Destination Path Too Long having this problem on desk top computer

Destination Path Too Long
when I try to move files from my desk top screen to my external hard drive or my internal hard drive I get this error message:
Path Too Long: The file name(s) would be too long for the destination folder. You can shorten the file name and try again, or try a location that has a shorter path.
These are files that I have previously moved from my internal hard drive on to my desk top [screen] computer, this error seems to pop up on my desk top not my lap top, both running windows
7. These files do not have long names, and I can not "skip" these files these are files that I have created for business or fun.
I am not a computer tech so if some one could instruct me what to do I would appreciate this.

Hi,
the destination path is the full path you are copying to. In case of a library for example that would be (by default) c:\users\username\folder. The length of paths quickly adds up and may not exceed 255. Copying the file to a longer destination
path would render the file inaccesible in standard ways.
Consider to try copying the files to a shorter destination path (not to c:\folder\longfolder\subfolder\folder\ but to c:\x\for example). Please post back if that does not work either.
The foldername in your screenshot alone already has 40 about characters. Consider using shorter descriptive names for your folders. For example 'Bible scripts FB2010' only contains 22 characters and contains more or less the same info)
http://support.microsoft.com/kb/177665
If you still use large folderstructures to 'easily' track down your files, consider spending less time arranging files and using search more often. If I for example would need some file, I tap the windows key and start typing some part of the filename or
even it's contents or tags. Usually before I have typed afew characters, the startmenu shows exactly the document or picture I need. I' ve got about 4000 documents of all kinds stored in "my documents" only roughly spread over some folder like Letter,
Script, Work, House\*year*, Pay\*year*...Index your folders, use a bit of tagging and let the computer do the work!
Also, Windows does contain methods to access longer filepaths (see
http://social.technet.microsoft.com/Forums/en/winservergen/thread/cc7491ae-5039-4cf5-8347-d43f22389bb0) but these are not recommended for daily use as applications might fail handling files stored in such paths.
MCP/MCSA/MCTS/MCITP

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.

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...

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

Literal too long when 4000 chars

I get an error that literal too long when trying to insert a record to a clob or varchar2 field when the string is over 4000 chars.
How to resolve this problem. I'd like to be able to treat this insert the same as all other inserts rather than make a special case out of it so no special processing would be needed.
The application reads from an html form textarea and inserts the value of the text area along with the other fields of the form to a database.

Hi,
The maximum length of VARCHAR2 data is 4000 bytes.
You can't store more than 4000 bytes in varchar2 column.
CLOB can store upto 4GB of data.
You can check the LOB Datatype sample for details on how to insert data into CLOB.
The sample is located at
[url http://otn.oracle.com/sample_code/tech/java/sqlj_jdbc/files/advanced/LOBSample/LOBSample.java.html] LOB Datatype source
Check the loadSamples method which shows how to insert data into CLOB using empty_clob() method.
Hope this helps.
For furthur clarifications please post your question at
[url http://forums.oracle.com/forums/forum.jsp?forum=75]SQL and PL/SQL Forum
Regards,
Anupama
[url http://otn.oracle.com/sample_code/content.html]OTN Sample Code[url ]

Restore-DfsrPreservedFiles "Path Too Long" Error

I'm attempting to run this on a file server where all replicated folders live in the D:\data drive. I am not sure why I would get a "Path Too Long" error and the exception does not provide any clues as to what it doesn't like -- or if it does,
I am reading it wrong. Ideas anyone?
PS C:\Users\Administrator> Restore-DFSRPreservedFiles -Path "D:\data\DfsrPrivate\ConflictandDeletedManifest.xml" -Restor
eToPath "D:\backup\recovery\dfsrrecovery" -RestoreAlLVersions -CopyFiles -Force -verbose
VERBOSE: Loading preserved file manifest: "D:\data\DfsrPrivate\ConflictandDeletedManifest.xml"
VERBOSE: Restoring preserved files from manifest: "D:\data\DfsrPrivate\ConflictandDeletedManifest.xml"
Restore-DFSRPreservedFiles : The specified path, file name, or both are too long. The fully qualified file name must
be less than 260 characters, and the directory name must be less than 248 characters.
At line:1 char:1
+ Restore-DFSRPreservedFiles -Path "D:\data\DfsrPrivate\ConflictandDeletedManifest ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [Restore-DfsrPreservedFiles], PathTooLongException
+ FullyQualifiedErrorId : System.IO.PathTooLongException,Microsoft.DistributedFileSystemReplication.Commands.Resto
reDfsrPreservedFilesCommand

Hi Mark,
This has been already discussed here. Please refer the below thread.
https://social.technet.microsoft.com/Forums/windowsserver/en-US/14fc8393-d616-408f-abad-49a3ccb15585/windows-server-2012-r2-running-restoredfsrpreservedfiles-getting-path-file-name-or-both-are-too?forum=winserverfiles
Devaraj G | Technical solution architect

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.

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)

How can I download a 18 minute video I recorded from my iPad to either email or youtube or vimeo I keep getting the message the file is too long.

How can I transfer a 18 minute video I recorded on my iPad camera app to email/youtube or vimeo? I keep getting the message the file is too long do want to send clips?
Thanks

Youtube usually had an 8 minute length cap, which may be part of your issue. Also at 18 minutes that is probably a gig+ file size, which will also take a long time to upload and may be another part of the issue.
Edit it down as jim suggested. Or you may need to use something like dropbox, to get it off your ipad and onto a computer where might have more options to edit it down or size it down.
If it's just file size you can transcode it into a smaller file - a lower quality MP4 for example. If it's the length that's an issue for youtube, you'll need to break it up into a couple different files and upload part 1 and part 2

Error: "client-error-request-value-too-long" when trying to add printer

After installing the 10.4.9 Combo update, my HP 1350 All-in-One printer was not recognized. I reinstalled the driver, but now I can't add the printer. I get the error message "client-error-request-value-too-long" when trying to add the printer. Has anyone else experienced a similar problem.
Thanks in advance

Well, I tried all of that and I'm still getting the error message. I've also repaired disk permissions and run Disk Warrior. When I repaired disk permissions, many HP printer items showed up in the list.

"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

Source path too long :-Unable to delete mutiple number of folder and files from windows 2008 R2 file server

Hi Team,
we have a file server on windows server 2008 R2, I have copied some data from one server to another server using robocopy . I have checked access permission it seems okay no issues with access permission. but when i am trying to delete these folder i am
getting below error message
Error message:-
The source file name are larger than is supported by the file system.try moving to a location which has a shorter path name or try renaming to shortcut names before attempting this operations
Regards,
Triyambak
Regards, Triyambak

I have tried everything , but nothing help , getting same error
could any one help me regarding this.
Regards, Triyambak
I have not looked at the other thread mentioned, but usually when this ends up happening, There are several ways to go about it. One is to map a drive to the UNC path deeper into the folder structure.
So instead of C:\long\path\that\we\dont\want\files\in
You map a drive.. lets say M:\ to \\computer\c$\long\path\that\we\dont\want
Now, when you open Explorer to M:\ you've elimintated the length of the path down to M:\files\in which is completely usable.
The other way, is to shorten the names of everything. For example...
Folder structure like this:
Root
-----Folder1
-----Folder2
--------------Folder2A
-----Folder3
--------------Folder3A
Rename all the folders to shorten up the path. Rename Folder1 to '1' Rename Folder2 to '2', Rename folder3 to '3. Then try to delete. If it's still too long, go one folder deeper. Rename Folder2A to '1' and
Rename Folder3A to '1' and so on. Basically keep renaming everything to a single digit character and eventually you'll shrink the path down to where you can shift-delete everything remaining.
Hope that helps.
Brian / ChevyNovaLN

"PLS-00172: string literal too long" When Writing XML file into a Table

Hi.
I'm using DBMS_XMLStore to get a XML file into a db table. See the example below, I'm using that for my PL/SQL format. Problem is that because there're too many XML elements that I use in "xmldoc CLOB:= ...", I get "PLS-00172: string literal too long" error.
Can someone suggest a workaround?
THANKS!!!
DECLARE
insCtx DBMS_XMLStore.ctxType;
rows NUMBER;
xmldoc CLOB :=
'<ROWSET>
<ROW num="1">
<EMPNO>7369</EMPNO>
<SAL>1800</SAL>
<HIREDATE>27-AUG-1996</HIREDATE>
</ROW>
<ROW>
<EMPNO>2290</EMPNO>
<SAL>2000</SAL>
<HIREDATE>31-DEC-1992</HIREDATE>
</ROW>
</ROWSET>';
BEGIN
insCtx := DBMS_XMLStore.newContext('scott.emp'); -- get saved context
DBMS_XMLStore.clearUpdateColumnList(insCtx); -- clear the update settings
-- set the columns to be updated as a list of values
DBMS_XMLStore.setUpdateColumn(insCtx,'EMPNO');
DBMS_XMLStore.setUpdateColumn(insCtx,'SAL');
DBMS_XMLStore.setUpdatecolumn(insCtx,'HIREDATE');
-- Now insert the doc.
-- This will only insert into EMPNO, SAL and HIREDATE columns
rows := DBMS_XMLStore.insertXML(insCtx, xmlDoc);
-- Close the context
DBMS_XMLStore.closeContext(insCtx);
END;
/

You ask where am getting the XML doc. Well, am not
getting the doc itself.I either don't understand or I disagree. In your sample code, you're certainly creating an XML document-- your local variable "xmldoc" is an XML document.
DBMS_XMLSTORE package needs
to know the canonical format and that's what I
hardcoded. Again, I either don't understand or I disagree... DBMS_XMLStore more or less assumes the format of the XML document itself-- there's a ROWSET tag, a ROW tag, and a then whatever column tags you'd like. You can override what tag identifies a row, but the rest is pretty much assumed. Your calls to setUpdateColumn identifies what subset of column tags in the XML document you're interested in.
Later in code I use
DBMS_XMLStore.setUpdateColumn to specify which
columns are to be inserted.Agreed.
xmldoc CLOB :=
'<ROWSET>
<ROW num="1">
<KEY_OLD> Smoker </KEY_OLD>
<KEY_NEW> 3 </KEY_NEW>
<TRANSFORM> Specified </TRANSFORM>
<KEY_OLD> Smoker </KEY_OLD>
<VALUEOLD> -1 </VALUEOLD>
EW> -1 </VALUENEW>
<DESCRIPTION> NA </DESCRIPTION>
</ROW>
ROWSET>';This is your XML document. You almost certainly want to be reading this from the file system and/or have it passed in from another procedure. If you hard-code the XML document, you're limited to a 32k string literal, which is almost certainly causing the error you were reporting initially.
As am writing this I'm realizing that I'm doing this
wrong, because I do need to read the XML file from
the filesystem (but insert the columns
selectively)...What I need to come up with is a proc
that would grab the XML file and do inserts into a
relational table. The XML file will change in the
future and that means that all my 'canonical format'
code will be broken. How do I deal with anticipated
change? Do I need to define/create an XML schema in
10g if am just inserting into one relat. table from
one XML file?What does "The XML file will change in the future" mean? Are you saying that the structure of the XML document will change? Or that the data in the XML document would change? Your code should only need to change if the structure of the document changes, which should be exceptionally uncommon and would only be an issue if you're adding another column that you want to work with, which would necessitate code changes.
I found an article where the issue of changing XML
file is dealt by using a XSL file (that's where I'd
define the 'canonical format'), but am having a
problem with creating one, because the source XML is
screwed up in terms of the format:
it's not <x> blah </x>
<x2> blah </x2>
x2="blah" x3="blah> ...etc
Can you point me in the right direction, please?You can certainly use something like the DBMS_XSLProcessor package to transform whatever XML document you have into an XML document in an appropriate format for the XMLStore package and pass that transformed XML document into something like your sample procedure rather than defining the xmldoc local variable with a hard-coded document. Of course, you'd need to write appropriate XSL code to do the actual transform.
Justin

File path too long when collecting??...

Similar Messages

Maybe you are looking for