260 Characters in length error, PLEASE HELP!!!

260 Characters in length error, PLEASE HELP!!!

Post by acoo » Tue, 27 Apr 2004 22:06:14

hy am I getting this error in my webservice?? I am making a call to this
webservice and passing in a string of XML and it bombs. Now when I run the
webservice and paste in the exact same XML it runs fine, what the heck is
going on and what path is it taking about. Error and XML are below:

ERROR ---------------------------------------------------------

An unhandled exception of type 'System.Web.Services.Protocols.SoapException'
occurred in system.web.services.dll

Additional information: System.Web.Services.Protocols.SoapException: Server
was unable to process request. ---> System.IO.PathTooLongException: The path
is too long after being fully qualified. Make sure path is less than 260
at System.IO.Path.nGetFullPathHelper(String path, Char[]
invalidPathChars, Char[] whitespaceChars, Char directorySeparator, Char
altDirectorySeparator, Char volumeSeparator, Boolean fullCheck, String&
at System.IO.Path.GetFullPathInternal(String path)
at System.IO.Path.GetFullPath(String path)
at System.Xml.XmlResolver.ResolveUri(Uri baseUri, String relativeUri)
at System.Xml.XmlTextReader..ctor(String url, XmlNameTable nt)
at System.Xml.XmlDocument.Load(String filename)
at ICRMService.FindAction(String document)
at ICRMService.PutXMLDocument(String document)
--- End of inner exception stack trace ---

XML ---------------------------------------------------------


- <objectxml>
- <account>
<accountcategorycode name="name_1">1</accountcategorycode>
<accountclassificationcode name="name_1">1</accountclassificationcode>
<accountratingcode name="name_1">1</accountratingcode>
<address1_addresstypecode name="name_1">1</address1_addresstypecode>
<address1_freighttermscode name="name_1">1</address1_freighttermscode>

1. file name length must not exceed 260 characters...

2. Handling paths of length > 260 in Tcl on Windows

As the subject suggests, I need to be able to handle long pathnames on
Windows, ones that (although they exceed Explorer's hard limit of 255)
may be nearly-arbitrary in length.

This MSDN article mentions the issue:

Basically, right now it looks like the normalized filenames in the Tcl
file libraries are normalized as "<drive>:/<path... >" whereas for this
functionality to work, at the very least, the file and I/O commands
would also have to accept "\\?\<drive>:\<path...>

Is there a workaround for this? I can't be the first person who has
needed this functionality...

3. get around limitation of the URL-path of 260 characters

4. "Limit Profile Size" -Can I go beyond 260 characters in "Directory exclusions"?

5. WSS (2003) - Problem with too many levels within folders in doc library (260 character limit)

6. file search for long file names (> 260 characters)

7. The full path must be less than 260 characters

8. 260 character of Url limiation in SharePoint

9. Can we break the 260 character ceiling ?

10. Why still a 260 character path limit ?

11. How move a sharepoint file when new address is >260 characters?

12. Using VBA to export to excel - error on over 260 rows

13. Help ! Problem with a 260 ST !!!

14. [34-longterm 225/260] futex: Fix errors in nested key ref-counting

15. Update 260 ST....Need help...