Skip to main content
Solved

Renamed FMW but log file name still old one when called from Workspace Runner

tim_wood
Contributor
Forum|alt.badge.img+8

I created some Workspaces and call them using Workspace Runners in a parent Workspace. As part of refining my overall process, I have renamed the Workspaces. However when I run the parent Workspace, the translation log for the child Workspaces has the old name of the child FMW.

I've tried doing File > Save as on the child FMWs, and adding new Workspace Runners to the parent Workspace rather than updating the existing ones. I can't see the log file names specified anyway so why isn't FME creating the logs with the same name as the FMW?

Best answer by redgeographics

It seems to be that if you rename the .fmw file through Windows Explorer it will continue to log to the old logfile (this also happens if you run it directly from FME Workbench rather than through a WorkspaceRunner, so I suspect the WorkspaceRunner has nothing to do with this issue). When I did a File -> Save As it then used the new name for the log file.

I think it's best to send this in to Safe's support (either directly or through your local partner). In the meantime, there is a Log File setting in the Workspace Parameters, by default it's not set and it uses the same filename as your workspace was saved as. If you want to be absolutely certain of where your log files end up and how they're named, this is the setting to change.

View original
Did this help you find an answer to your question?
This post is closed to further activity.
It may be a question with a best answer, an implemented idea, or just a post needing no comment.
If you have a follow-up or related question, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.

3 replies

redgeographics
Celebrity
Forum|alt.badge.img+50
  • redgeographicsCelebrity
  • Celebrity
  • Best Answer
  • November 1, 2016

It seems to be that if you rename the .fmw file through Windows Explorer it will continue to log to the old logfile (this also happens if you run it directly from FME Workbench rather than through a WorkspaceRunner, so I suspect the WorkspaceRunner has nothing to do with this issue). When I did a File -> Save As it then used the new name for the log file.

I think it's best to send this in to Safe's support (either directly or through your local partner). In the meantime, there is a Log File setting in the Workspace Parameters, by default it's not set and it uses the same filename as your workspace was saved as. If you want to be absolutely certain of where your log files end up and how they're named, this is the setting to change.

tim_wood
Contributor
Forum|alt.badge.img+8
  • tim_woodContributor
  • Author
  • Contributor
  • November 1, 2016
redgeographics wrote:

It seems to be that if you rename the .fmw file through Windows Explorer it will continue to log to the old logfile (this also happens if you run it directly from FME Workbench rather than through a WorkspaceRunner, so I suspect the WorkspaceRunner has nothing to do with this issue). When I did a File -> Save As it then used the new name for the log file.

I think it's best to send this in to Safe's support (either directly or through your local partner). In the meantime, there is a Log File setting in the Workspace Parameters, by default it's not set and it uses the same filename as your workspace was saved as. If you want to be absolutely certain of where your log files end up and how they're named, this is the setting to change.

I'm pretty sure I did File > Save as but I'll try it again. I can't be certain but my feeling is that the Workspace produces the correctly named log file when run stand alone, but the old name when run from the Workspace Runner.

 

 

tim_wood
Contributor
Forum|alt.badge.img+8
  • tim_woodContributor
  • Author
  • Contributor
  • November 1, 2016
redgeographics wrote:

It seems to be that if you rename the .fmw file through Windows Explorer it will continue to log to the old logfile (this also happens if you run it directly from FME Workbench rather than through a WorkspaceRunner, so I suspect the WorkspaceRunner has nothing to do with this issue). When I did a File -> Save As it then used the new name for the log file.

I think it's best to send this in to Safe's support (either directly or through your local partner). In the meantime, there is a Log File setting in the Workspace Parameters, by default it's not set and it uses the same filename as your workspace was saved as. If you want to be absolutely certain of where your log files end up and how they're named, this is the setting to change.

OK File > Save as is the answer. It seems I needed to do it twice to fix the problem, probably because I had renamed it in Windows Explorer at some point. So to get the correct log file for "MyWorkspaceA.fmw" I had to save it as "MyWorkspaceA2.fmw", then save that as "MyWorkspaceA.fmw".

 

Helpful Members This Week

Community Stats

31,345
Posts
118,893
Replies
38,962
Members

Latest FME

Terms & ConditionsCookie settings

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
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.