TOPIC:

We're running into a little problem that started mid day two days ago. There are two tasks in the import file process.  The first step is monitoring a folder that executes a script.  The problem is the file never gets detected. Our first step was to restart the TS where FH Server resides, then it works for a while.  I can also simply restart FH Server and it will work for a while.  They're both successful on 'server start' or 'file creation'.  I am using the absolute paths.  We think the problem is communication between the terminal server and the file server.  Our fix, we think, will be a script to restart FH Server twice a day to be sure we don't miss anything.  Any suggestions or guidance would be greatly appreciated.

Thanks, JD

Hi JD,

I guess this request is related to your previous question “ Execute | Trigger Task ”?

Related to this post please keep in mind that in case your trigger file already exist and you try to create a new file with output redirection like this
    Echo “trigger file” > C:\Temp\trigger.file

the event for file creation are not raised. In this case you have to enable also the option “Triggered by file modification”.

But in my point of view you just have to delete your trigger file after processing the task. For this just enable the option “Actions performed after execution – Delete file”, see screenshot below.

 

PS: If you really want to restart the server you can do this with the following two command lines, but this isn´t a good idea!

net stop "FlowHeater Server"
net start "FlowHeater Server"
 

Thanks for the response Robert.

The problem is not performing the task, the File Monitor is not seeing the new orders file.  I have tried numerous scenarios.  While I watch the monitored folder and the FH Server 'Logging'.  A new file appears and there's no log activity.  I can remove the new file, make a change to the monitored folder path, save it then change it back to the original path.  Put the file back in the monitored folder and the process works fine.  It's not every folder being monitored and it does not happen all the time to the same tasks.

I did try your suggestion and the same problem happened again.

We think the problem could be between the terminal server and the file server, the TS is newer with a newer OS. 
We're planning to upgrade the file server and move FH Server there.  But, we'll put that off until the seasonal push is over.

As always thanks for you support , I'll continue to watch. 
Your suggestions are always welcome.

JD

Hi JD,

I´ve made a few tests, including mapped network drives, UNC paths on different Windows Servers and on Linux NAS Samba shares as well. Every time FlowHeater Server works as expected.

Are you sure that your trigger file has been deleted after each run?

Did you tried enabling "Monitoring on file changes"?

Which FlowHeater Server version you are using?

May I ask you to try the latest version, perhaps the mentioned BETA Version ?

 

Thanks Robert,

Are you sure that your trigger file has been deleted after each run?
There is no trigger file at this stage.  New .csv order files come in through sftp to a 'Pending' folder for the customer. FH Server sees the file(s) 'file creation' and executes a command file that removes the headers and combines them to a .txt file, deletes the .csv file(s) and moves the .txt file to another folder 'ReadyToImport' where a second Task executes a blank command file (that does nothing) then sends an email notification.

Did you tried enabling "Monitoring on file changes"?
I have not.  Do you think it would help considering the structure above?

Which FlowHeater Server version you are using?
4.1.7

May I ask you to try the latest version, perhaps the mentioned BETA Version ?
At this point in the season, we don't make big changes, we're expecting an increase in production.
But I will when things slow down.

JD

Hi JD,

Ok, now it´s clear In case you move a file onto the same drive/volume no file created event will be raised. In this case you have to enable “Triggered by rename”, that’s all.

 

 

Sorry Robert, that did not work either.  I really don't think it's an issue or setting within FH Server, I think its the communication between our servers.  It's so random it has to be, I'm guessing. We only had one not work yesterday evening but started working this morning with no changes.

JD

Hi CD,

I´ve running some more huge Tests. I could reconstruct this behavior only in case the network connection is lost. In this case this network path are out of monitoring as long FlowHeater Server is restarted. In a further version I´ll implement a mechanisms that detects such broken network connection and restart the file monitoring for this connection.

Just for your information) Currently FlowHeater Server using a FileSystemWatcher API object, provided by the OS, to monitor the desired folder.

Workaround)
You could using a script that checks whether new files available in the network folder. If yes, just start the processing out of this script. The script can be scheduled every minutes.
 

Thanks for the followup Robert, that's exactly what we've been working on.  Look forward to the updated version.

JD