Skip to main content
Question

The wrong log file gets updated


fmenco
Contributor
Forum|alt.badge.img+5

I run a workbench automatically through task scheduler. I've recently renamed this workbench (let's call the old one workbenchA, and the new on workbenchB). I have also updated the task. However, whenever this workbench runs through the taskscheduler, the logfile that gets created or updated is the one referring to the old name (so workbenchA.log). It does run workbenchB and says it as well in the workbenchA.log, but just sticks to the old filename when it comes to logging.

I've already emptied my user temp folder. I've also now renamed workbenchA. But it still does it. It's like something is stuck in cache memory somewhere, but I don't know where to look. Also, when I manually start the workbenchB it does create a logfile with the correct name.

 

I Have FME Desktop version 2019.

6 replies

ebygomm
Influencer
Forum|alt.badge.img+31
  • Influencer
  • February 27, 2020

Is there a logfile set in the workspace parameters?

 


fmenco
Contributor
Forum|alt.badge.img+5
  • Author
  • Contributor
  • February 27, 2020
ebygomm wrote:

Is there a logfile set in the workspace parameters?

 

I just checked and no there's no logfile set in the workspace parameters.


virtualcitymatt
Celebrity
Forum|alt.badge.img+34

I would try clearing the task from the scheduler and then resetting it up again (if you haven't tried that yet)


  • February 27, 2020

The problem lies in the renaming issue.

FME Stores the Workspace name when it's saves the workspace. That name is by default used for the logfile name.

Try SaveAs instead of renaming the FMW file.

 


fmenco
Contributor
Forum|alt.badge.img+5
  • Author
  • Contributor
  • February 28, 2020
tibor wrote:

The problem lies in the renaming issue.

FME Stores the Workspace name when it's saves the workspace. That name is by default used for the logfile name.

Try SaveAs instead of renaming the FMW file.

 

Yes, this did the trick! Thank you!


fmenco
Contributor
Forum|alt.badge.img+5
  • Author
  • Contributor
  • February 28, 2020
virtualcitymatt wrote:

I would try clearing the task from the scheduler and then resetting it up again (if you haven't tried that yet)

Yes, I tried this. The issue was the renaming itself (see answer above) :-)… Thank you


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings