Error Dynamics 365 into Snowflake

  • 220Views
  • Last Post 14 November 2022
0
votes
Gabriel Longarai posted this 11 November 2022

The package below is sourced from CRM Dynamics 365 and loaded into Snowflake.

 

What is the cause of this error?

Package: https://app.skyvia.com/#/76069/packages/193361/debug

Run Id: 112450541

Date: Nov 11, 2022 5:17:09 PM

 

Object error Hide details

The content type text/html; charset=utf-8 of the response message does not match the content type of the binding (text/xml; charset=utf-8). If using a custom encoder, be sure that the IsContentTypeSupported method is implemented properly. The first 1024 bytes of the response were: '<!DOCTYPE HTML> <html> <head> <script type='text/javascript'>var LoadStartTime = new Date().getTime();</script> <script type='text/javascript'>APPLICATION_FULL_VERSION = '9.2.22104.170';</script> <script type='text/javascript'> var isKeyPressed=false; var headElement = document.getElementsByTagName('head')[0]; var style_element = document.createElement('style'); style_element.id = 'focusStyle'; var focusCss = ':focus{outline:2px dashed !important; outline-offset: 1px !important;}::-moz-focus-inner{border:0;}'; var removefocusCss = ':focus{outline:0}::-moz-focus-inner{border:0;}'; document.addEventListener('keydown', function(e) { isKeyPressed=true; // This class breaks drag/drop keyboard accessibility in the dashboard editor, so temporarily remove it. if (window.location.href.indexOf('dashboardEditor.aspx') > -1) { var target = e && e.target; if (target && target.classList && target.classList.contains('keyboardFocusClass')) { targ'.

 

 

0
votes
Yevheniia Bilotserkovska posted this 14 November 2022

Hello Gabriel.

Thank you for contacting us.

Error 'The type text/html; charset=utf-8 the response message does not match the content type of the binding (text/xml; charset=utf-8). ' was returned by Snowflake.

We assume it was due to a Binding mismatch between the client and service configuration. Please check your service configuration if this error appears again.

Looks like it was a temporary problem as we can see currently your runs are successful.

Could you please clarify if the issue still persists or not?

We are looking forward to hearing from you.

Best regards,

Yevheniia Bilotserkovska.

Close