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

Question

Question

Issue with "export contents" and file path.

asked on July 30, 2014 Show version history

Hi,

 

I know this isn't exactly a Laserfiche-specific issue, but I'm looking for some options.  A client of ours was recently purchased by a larger corporation that uses a different document management system.  The new owners want to migrate all the information from Laserfiche to their other system.

 

The issue I'm running into is, when using the "export contents" tool, some of the file paths in Laserfiche exceed the 257(?) character limit for a file path in Windows.  The system is currently running on Windows XP.  Unfortunately, this client also does not have workflow to assist with this.  Is there an alternative way to export these files and retain the information provided by the folder structure itself?

 

Thanks,

Eric

0 0

Answer

SELECTED ANSWER
replied on July 30, 2014

If you're just exporting from the Client, there isn't much you can do. If you're exporting through the SDK, you could do something like export the files with unique names and write some sort of XML with the full path for them. Then you could rebuild the folder structure when you import into the other database.

 

You could also try going through SQL to get a list of documents with excessively long paths, but that might get complicated since you would have to rebuild the paths yourself going through the toc table.

0 0

Replies

replied on July 30, 2014

This is a Windows limitation.

0 0
replied on July 30, 2014

Yes, I understand that.  I'm just looking for some ideas on how to work around this limitation.  If I had workflow at my disposal I could potentially shorten the file paths, but that's not an option at this point.

0 0
SELECTED ANSWER
replied on July 30, 2014

If you're just exporting from the Client, there isn't much you can do. If you're exporting through the SDK, you could do something like export the files with unique names and write some sort of XML with the full path for them. Then you could rebuild the folder structure when you import into the other database.

 

You could also try going through SQL to get a list of documents with excessively long paths, but that might get complicated since you would have to rebuild the paths yourself going through the toc table.

0 0
replied on October 17, 2014

I have a similar situation

Is there a problem using File – Export – Folder Contents for a high number of exports? 
Is it expected behaviour for the LF client to error out if above 260 character total file path limit?
Do forward slashes or colons present a problem? 

Customer is exporting 20,000 to 100,000 PDF files yearly as part of their Vital Records program. 
They have repeatedly errored out when allowing this to run overnight using client 9.0.3.798. 
They have tested XP, Win7, Win8, on 32/64bit. 

Sample errors:

\Facilities & Land Management\Facilities Operation - History\ECOTrek Project\Ecotrek Holdings\Ecotrek Measure: K1 - Building Sub Metering (Electrical) Maintenance Manual\Ecotrek Measure: K1 - Building Sub Metering (Elec) Vol 6 of 6\864 + 867 - Wesbrook Building & Annex: I/O error in display engine. [6603:0x80070005]

Error creating file. [6411] 

Some file paths are definitely over 260 characters.

0 0
replied on October 17, 2014

I think this is the same issue I was having.  If the full path being created exceeds 260 characters (I think), then it will error out.  This is not an issue with Laserfiche itself, but a windows limitation.  As for special characters, by default Laserfiche will replace those with underscores if they're incompatible with windows folder/file names.

1 0
replied on August 1, 2014

Hi Eric, 

 

If your question has been answered, please let us know by clicking the "This answered my question" button on the response.

 

If you still need assistance with this matter, just update this thread. Thanks!

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

Sign in to reply to this post.