PCo not sending files

[Former Member]

Hi

We have PCo v15 running on a remote PC.  It uses FileMonitor Agent to send log files to MII, and then renames the file to avoid sending it again.

This has suddenly stopped working, though the Agent Instance still reports as running fine.  The connections to MII have been checked and also seem fine.

There are no errors in the error log, just a warning - "The maximum number of dispatch threads configured exceeds 60% of the total threads available"

We have tried all the usual rebooting and restarting PCo, but with no joy.

Does anyone have any ideas?

Just let me know if you need any further info.

Regards

Nick

[former_member196557 · Accepted solution]

Hi Nick,

1. what SP and Patch level for PCo 15?
2. Please describe the situation in more detail:
   1. Are there any Error or Warning messages in the Agent Instance Log
   2. Is the monitored folder local to PCo or on a Remote PC?
   3. Are there files in the FileMonitor monitored directory that match the mask for the file name that remain in the directory and are NOT picked up by PCo?
   4. For FileMonitor Agent folder access:
      1. Do you have a user defined on the Authentication tab
      2. What are the permission settings for the Folder and the Folder Share?
   5. In the FileMonitor Agent Settings tab, are either of the following check boxes checked:
      1. Notify Only If File Is Unlocked
      2. ignore Unavailability of UNC Folders?
3. From the PCo Server, can you open the shared folder from File Explorer and see contents?

Regards, Steve

[Former Member · Accepted solution]

Hi

The File Unlocked thing was checked, so I unchecked it and it all started working again!

Thanks for your time

regards

Nick

[former_member196557 · Accepted solution]

Hi Nick,

You really need to find out why the file was left locked in the first place.  With the 'Notify Only If File Is Unlocked' box unchecked, you could possible receive incomplete content from the file, especially if it is a large file. Also, if the file is locked, you likely cannot rename/move/delete the file either, and it may get processed over and over again until it is unlocked.

Regards, Steve

[Former Member · Accepted solution]

Hi

The way it seems to work is when we pass a job to the machine, it creates a log file for that job.  Each operation is written to this log file, but between writing operations the file is not locked, so PCo has no idea whether the job is finished or not, and just sends the file across, and renames it.

The m/c doesn't care, it just creates a new log file and carries on.

As you can imagine, the danger of errors, duplicated entries and data spread across several files is quite significant, so my transaction in MII already deals with all these scenarios

So switching off this locking check may cause more errors, but the transaction expects these, and should deal with them.

Thanks for all your help

Nick