Question

Import Agent fails to monitor network folder but does not log errors

Import Agent Version 10

Updated April 13, 2021

asked on April 12, 2021 • Show version history

I've been unable to get Import Agent to monitor a network folder. There are no new events in the log viewer.

Here are some pertinent facts

I'm running IA version 10.4.0.170. I specified the network location with "\\servername\folder" syntax, not with a mapped drive letter
I have successfully imported from network locations in the past.
I restarted the service multiple times.
I restarted the server once.
I changed the profile to use my own admin account to make sure it had the permissions it needed.
I tried changing the schedule so that instead of importing continuously, it was scheduled to start importing at a time about 2 minutes in the future.
With all the above experimentation, IA never deleted the files from the monitored folder (as I had configured it to do) and it never created files in Laserfiche. It also never logged any error events.
I made a copy of the profile that didn't work. I told that copied profile to import from a folder on the C: drive of the server hosting IA. That profile works.

Questions:

Is there anything I should check that I might have forgotten?
Are there any known defects in IA 10.4.0.170 that would produce this kind of behavior?
If so, are there any fixes or workarounds for the problem?

0 0

Answer

SELECTED ANSWER

replied on April 13, 2021

Does the service account that Import Agent runs as in services.msc, have access to the network folder?

3 0

replied on April 13, 2021

That was it! I was hyperfocused on the identity specified in the profile, not realizing that the identity of the service account itself was the one that would be used to retrieve and delete the files--which makes sense on reflection.

Thank you for your reply!

2 0

Replies

replied on April 12, 2021

Assuming this is Windows, if your folder path is formatted the same as your example then it could just be because you used forward slashes instead of backslashes.

UNC paths for Windows should be \\servername\folder with backslashes.

Other than that, you mentioned you've imported from other network locations before, so the first thing to look for is what is different between the working and non-working profiles.

1 0

replied on April 13, 2021

Thank you for the reply. Unfortunately, the mistake was in my typing of the question. I'll correct it. Best wishes!

0 0

You are not allowed to follow up in this post.

Question

Question

Import Agent fails to monitor network folder but does not log errors

Answer

Replies

Sign in to reply to this post.