You are viewing limited content. For full access, please sign in.

Question

Question

Web Access Character Limit

asked on October 18, 2017 Show version history

We have a client that is now noticing an error in Web Access stating that

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

This is something that only happens in Web Access, not in the windows client and we need to know if there's a way around this or some setting we can change? 

We looked and the docs we found have a path and filename length of 252 characters.  Looking for advice on how to get around this, thanks.

0 0

Replies

replied on October 18, 2017

This is a generic error, when are they encountering it? What version of Web Access are they using?

0 0
replied on October 18, 2017

This error happens when opening a document in Web Access, and only when they choose "Edit" not "View" (These are Excel and Word docs).  It seems the Error message is very descriptive and is stating that the path or name is too long, and it is indeed past the limits stated in the error.  But we're looking for a way around this, or a reason why there's a limit on path lengths in web access of 248 characters, when in the client it's i think 1023?

Their Web Access version is: 10.2.1.362

0 0
replied on October 19, 2017 Show version history

This is more likely a bug in Web Access than an intentional limitation.  It is probably attempting to save a copy of your document to the local disk, and it's the Windows OS that is enforcing a path limit, rather than the Laserfiche server.

Can you confirm that you see this error in a dialog put up from within the Office application, and not from Web Access itself?

0 0
replied on October 20, 2017

So digging further i have found why some things work and not others, and it is a difference in behavior between the full client and Web Access and the error message comes from Web Access but it refers to a Windows API Function that's failing (NormalizePath).  The full client when opening an office doc will save the temporary file to C:\Users\UserName\AppData\Local\Temp\#\Docname Truncated to 74 Chars_EntryID\TruncatedDocName

So it looks like the full client has a built in function to truncate the temporary file name when it's longer that 74 characters.

Web Access stores an office document in 2 different places depending on whether you choose "View" or "Edit".  We noticed a difference in behavior between the two options only because the docname was slightly above the characters limit.  When choosing "View" it stores it in

C:\Users\UserName\AppData\Local\Temp\#\SomeGUID\Docname

When Edit is chosen it stores it under

C:\Users\UserName\Documents\My Laserfiche Documents\Docname\Docname

And webaccess to does not auto truncate the path or filename if it's longer than 74 characters as the Windows Client Does and the windows function NormalizePath that the office integration uses seems to be limited in the size the path can be.  

 

So now i understand what's happening a little better, can this be filed as a Bug for the Web Client?  If Laserfiche allows document names of 255 characters, i would imagine there shouldn't be any scenario's where a user can't access an electronic file because the name is somewhere close to that.  Any thoughts on this?  I understand we can't change the windows function, but it seems the fix has already been built into the Windows Client, can it get added to the Web Client?

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.