Skip to main content
Question

Failed writing received data to disk/application

  • July 16, 2018
  • 2 replies
  • 159 views
fmeuser_gc
Contributor
Forum|alt.badge.img+9

I get this error when using HTTPCaller for generating .CSV file. It is fully authenticated as the call goes through and has status code of 200.

Failed writing received data to disk/application

HTTPCaller_2(HTTPFactory): HTTP transfer summary - status code: 200, download size: '6950 bytes'

ERROR |HTTPCaller_3(HTTPFactory): HTTP/FTP transfer error: 'Failed writing received data to disk/application'

2018-07-16 14:29:06| 1.2| 0.0|ERROR |HTTPCaller_3(HTTPFactory): Please ensure that your network connection is properly set up

2018-07-16 14:29:06| 1.2| 0.0|ERROR |HTTPCaller_3(HTTPFactory): No proxy settings have been entered. If you require a proxy to access external URLs, please ensure the appropriate information has been entered.

Please advise. Thank You

@takashi, @david_r

Yash K
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.

2 replies

danilo_fme
Celebrity
Forum|alt.badge.img+52
  • danilo_fmeCelebrity
  • Celebrity
  • July 18, 2018

Hi @fmeuser_gc

 

Could you send us your link to make test?

Thanks,

Danilo

 

Partner Solutial Brazil - www.solutial.com.br
laurawatsafe
Safer
Forum|alt.badge.img+13

This same issue was raised via support recently, so I thought I'd post a potential workaround for this here (below this explanation):

The error was happening due to a malformed response coming back from the endpoint being accessed in the HTTPCaller. The response included the following header:

  • Content-Encoding: UTF-8

This wasn't really a proper use of this header, as it should be used to indicate any compression used in the response. The character set is given in the Content-Type header:

  • Content-Type: application/json; charset=UTF-8

So this issue was actually a problem with the server that was sending the response.

 

Workaround

In the HTTPCaller, add a custom header “Accept-Encoding” with no value. This will turn off the automatic decoding of the response.

Community Stats

32,154
Posts
122,047
Replies
39,812
Members

Latest FME

Terms & ConditionsCookie settingsAccessibility statement
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.