New post
Question
· Feb 17, 2020

File.InboundAdapter archives files missing or 0kb

#Interoperability #Ensemble

Hi: 

I'm new to Cache and intersystems. 

We have a live production solution that uses a file inbound adapter to collect pdf documents off a fileshare. This fileshare is accessed by many services and access is controlled to the files by AD.

A problem we are seeing is that documents either are attempted to be processed with a filesize of 0kb or more often a file gets processed that in the next buisness process then cannot be moved to a working directory and the file does not appear in the archive from the file inbound adapter. It appears like the same file gets picked up by a later session but we have no way of knowing if it is the same doc or not. 

We had some errors previously that was corrected by changing the confirm complete to writeable.

 

Does anyone have any ideas? The file adapter isn't notifying us of the problem archiving the files. 

Discussion (2)1
Log in or sign up to continue
Vic Sun · Feb 17, 2020

Are you using an Archive Path or Work Path?

When you look at the Visual Trace does it give you any more ideas for where issues could be cropping up?

Can you elaborate on this: "It appears like the same file gets picked up by a later session but we have no way of knowing if it is the same doc or not."

Do you mean that the file is sometimes picked up but with a reported filesize of 0kb? What business process is attempting to move the file to a working directory?

What were the errors that you had previously? If Ensemble is having trouble picking up the file it may be a fileshare availability issue.

This is likely not going to be easy to troubleshoot through this forum, I'd recommend reaching out to the WRC to investigate.

0 0
Mark O'Reilly · Feb 18, 2020

Hi:

The file gets automatically archived using the archive path. It gets passed to a bp which then validates the filename and then copies the document to a working directory before it converts the document to a tiff file. It fails as it tries to copy the file to the working directory. 

I do assume it is a fileshare availability/network issue but it is something we need contigency for to minimise manual intervention. 

Have logged to WRC. 

Mark

0 0