Skip to main content
Question

ImageFetcher on FME server

  • September 11, 2013
  • 3 replies
  • 65 views

Forum|alt.badge.img
Hi!

 

Im working on a PDF cartographic output application running on FME server.

 

 

Recnetly I encountered the workspace is not flawless as it used to be. It seems around 1/3 of all executions will result in error similar to:

 

 

PNG reader: Failed to open the dataset 'C:\\Users\\SAFME2~1\\AppData\\Local\\Temp\\ImageFetcher_21378914917511_5860'. Please ensure source data is valid and correct reader is selected

 

 

This is a Imagefetcher. Used to get a WMS - PNG-image.

 

Error is at 1.8 seconds, so it cant be a timeout.

 

Pasting the WMS URL in browser works fine.

 

Using the same imagefetchers and URL in other .fmw-files  on the server works fine.

 

Downloading and running the workspace on desktop with same identical settings as on the crash works fine.

 

 

Im out of ideas. Should I clean the server up somehow? Any input most welcome.

 

Thank you!

 

 

 

 

 

 

 

This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, 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

david_r
Celebrity
  • September 12, 2013
Hi,

 

 

the first thing I would check would be that the user running the FME Server instance has sufficient rights on the harddisk.

 

 

Consider temporarily giving the user Administrator rights or running FME Server as a local Administrator on the server to see if the problem goes away. If it does go away, the error is most probably due to insufficient rights.

 

 

David

Forum|alt.badge.img
  • Author
  • September 12, 2013
Hi David

 

It is runned by the guest account, and its working 2 of 3 times meaning there must be sufficient rights..

 


Forum|alt.badge.img
  • Author
  • September 12, 2013
Problem solved. Caused ofcourse not by FME but by instable WMS-server..