Skip to main content
Question

I set a temporary file location, FME_TEMP, for temp files but this has led to the Data Inspector not showing any data from the Inspector.

  • September 2, 2016
  • 9 replies
  • 60 views

Forum|alt.badge.img

I have set a temporary file location, using the instructions found here : https://knowledge.safe.com/articles/176/fme-temp-environment-variable.html

However, when I run a workspace with data going into an Inspector, the FME Data Inspector window opens, but no data is loaded in/displayed.

I can see data has gone into the FME Temp space fine, and writing to file works fine, it's just the Data Inspector.

Does anyone know how I can rectify this?

Thanks!

9 replies

erik_jan
Contributor
Forum|alt.badge.img+18
  • Contributor
  • September 2, 2016

This seems to be a case for support@safe.com


itay
Supporter
Forum|alt.badge.img+17
  • Supporter
  • September 2, 2016

Sometimes the data inspector gets stuck restarting it of the all machine can help


mark2atsafe
Safer
Forum|alt.badge.img+44
  • Safer
  • September 2, 2016
itay wrote:

Sometimes the data inspector gets stuck restarting it of the all machine can help

Yes, definitely if the Data Inspector and/or Workbench havn't been restarted since you changed the path.

 

 


mark2atsafe
Safer
Forum|alt.badge.img+44
  • Safer
  • September 2, 2016

Do you have the log window open in the Data Inspector? That might give us a clue about why it is having problems.


Forum|alt.badge.img
  • Author
  • September 5, 2016
mark2atsafe wrote:

Do you have the log window open in the Data Inspector? That might give us a clue about why it is having problems.

Hi Mark,

 

Yes I have restarted both (in fact I re-installed FME completely in case it had got stuck on something!).

 

All the log files say is: Log File: F:\\FME Temp\\FMEDataInspector\\logs\\fmedatainspector_2016-09-05T09-50-45.log

 

Is there anything else I can try?

 

Thanks

 


mark2atsafe
Safer
Forum|alt.badge.img+44
  • Safer
  • September 6, 2016
jess11 wrote:
Hi Mark,

 

Yes I have restarted both (in fact I re-installed FME completely in case it had got stuck on something!).

 

All the log files say is: Log File: F:\\FME Temp\\FMEDataInspector\\logs\\fmedatainspector_2016-09-05T09-50-45.log

 

Is there anything else I can try?

 

Thanks

 

What I'm looking for is that the Workbench log says "Storing feature(s) to FME feature store file" C:\\OneTempFolder\\inspector.ffs and the Data Inspector log says something like 'Couldn't find file D:\\AnotherTempFolder\\inspector.ffs' - because that will show whether the data is being written to the correct place (and the DI doesn't find it) or whether Workbench is writing it to the wrong location. And maybe the locations that are being used will reveal a clue as to why it's not working.

 


mark2atsafe
Safer
Forum|alt.badge.img+44
  • Safer
  • September 6, 2016

It shouldn't be an issue, but make sure the temp folder you are using has no spaces in its file/path names, and no special characters either. Like I said, it shouldn't be a problem, but it's one of those things to test for just to make sure.


Forum|alt.badge.img
  • Author
  • September 7, 2016
mark2atsafe wrote:

It shouldn't be an issue, but make sure the temp folder you are using has no spaces in its file/path names, and no special characters either. Like I said, it shouldn't be a problem, but it's one of those things to test for just to make sure.

 

Thanks Mark - I removed the space in the file name and this worked - I should have thought to check this. Thanks for all your help.

 


mark2atsafe
Safer
Forum|alt.badge.img+44
  • Safer
  • September 7, 2016
jess11 wrote:

 

Thanks Mark - I removed the space in the file name and this worked - I should have thought to check this. Thanks for all your help.

 

Yeah, not sure why I didn't think of it sooner. It's filed with the developers as PR#64578 and hopefully will be fixed before long.

 

 


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