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

Question

Question

ImportEDoc error - The file exists

SDK
asked on January 15, 2018

On one server we are getting an error when trying to import any electronic file using the LF API.

Laserfiche.RepositoryAccess.MultiStatusException: The file exists [-2147024816]
  at Laserfiche.RepositoryAccess.EntryInfo.Save()
  at Laserfiche.DocumentServices.DocumentImporter.ImportEDoc(...)

At this point we have already created a new DocumentInfo object, set the Template and fields, and saved the DocumentInfo object.  After this error the empty LF Document will remain in the LF Client.

The Laserfiche Client has no problems when adding files and neither does the LF Outlook 2010 Add-In.  There are a couple of other posts about this error from a couple of years ago (the server is still using LF 9.2).  The posts all mention clearing out various temp folders which we have tried.  

0 0

Answer

SELECTED ANSWER
replied on February 1, 2018

This was related to the user not having the correct rights on the Volume.  We were able to import successfully with a different Volume.

0 0

Replies

replied on March 25, 2019

I received this same error. Turned out after a database restore the volume had files which were not represented in the database. I deleted the extra files because it was a test region and then I could save again from Laserfiche Forms.

1 0
replied on January 15, 2018

Check if you have multiple LF volumes that share the same path, in which case two different documents would point to the same file on disk.

0 0
replied on January 16, 2018

Hi Robert,

 

The volumes all have different paths in this case. Also if this was a volume related issue, I'm assuming you would see the same error when importing through the client or office integration? Both the client and Office Integration can import without issue, this seems something specifically related to the API.

 

Cheers!

0 0
replied on January 16, 2018

This bug sounds familiar to me but I can't find a corresponding bug report in our system. I think there is a good chance it has been fixed in the LF server since 9.2. 

Alternatively, if you open a support case we can get process monitor/LFS trace/LFSO logs to help diagnose the problem.

0 0
SELECTED ANSWER
replied on February 1, 2018

This was related to the user not having the correct rights on the Volume.  We were able to import successfully with a different Volume.

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

Sign in to reply to this post.