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

Question

Question

Getting IAError Using Import Agent

asked on February 25

Hello,

We have been using Import Agent for quite some time now.  Just recently, we started getting an IAError in the folder when scanning to Laserfiche.  Our Copier machine is uploading the files to a folder on a server and I can see the PDF arrive, but when it tries to process, it moves it to an IAError folder and uploads a blank page to the Repository.

Anyone have experience with something like this?

Nothing has changed in the past few weeks other than did MS Updates on the server last week.

Thank you for your help!

0 0

Answer

SELECTED ANSWER
replied on February 26

What's the version of Import Agent? The issue may occur on RepositoryAccess 10.4.2 or before. Recommend to upgrade to Import Agent 11.

0 0
replied on February 26

I updated the Import Agent to Version 11 from 10.4 and it worked.

 

Thank you!

0 0

Replies

replied on February 25

If you open the Windows Event Viewer on the machine hosting Import Agent, it should have logs with more information about the errors.

Event Viewer > Applications and Services > Laserfiche > ImportAgent > Service > Admin

0 0
replied on February 25

I am looking at the log and see that it says "The process cannot access the file because it is being used by another process:"

StackTrace at Laserfiche.ImportAgent.Library.Helpers.GetLastErrorAndThrowIfFailed(String extra)

This mean anything?

replied on February 25

Sorry, was looking at the wrong log file.  

this is what it says:

There was an error running the profile (Name) while importing the file (Received bad response from the server)

Error Code: 0

StackTrace: at Laserfiche.RepositoryAccess.EntryLock.ParselLockResponse(httpResponse response)

 

0 0
replied on February 25

That's an odd one. Seems like something is locking the entry. Do you have any workflows set to run based on the Entry Created event?

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

Sign in to reply to this post.