frequent_export_errors

frequent_export_errors

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
frequent_export_errors [2020/05/13 17:24]
franz
frequent_export_errors [2020/06/16 16:46]
amil
Line 13: Line 13:
 === HTTP response status code 401 === === HTTP response status code 401 ===
  
-  * Check if there is an user defined in the FINDOLOGIC ​customer-account.+  * Check if there is an user defined in the Findologic ​customer-account.
   * If there is an user defined, check if the credentials are correct.   * If there is an user defined, check if the credentials are correct.
   * If there are no credentials defined, try if the Export URL can be opened within the browser. If not, configure the correct username and password.   * If there are no credentials defined, try if the Export URL can be opened within the browser. If not, configure the correct username and password.
-  * If the URL can be opened within the browser, contact the FINDOLOGIC ​[[support@findologic.com|support@findologic.com]].+  * If the URL can be opened within the browser, contact the Findologic ​[[support@findologic.com|support@findologic.com]].
  
 \\  \\ 
Line 22: Line 22:
 === HTTP response status code 403 === === HTTP response status code 403 ===
  
-  * Check if there is an user configured in the FINDOLOGIC ​customer-account.+  * Check if there is an user configured in the Findologic ​customer-account.
   * Try to open the Export URL in the browser. If there is an username set, use those credentials to log in.   * Try to open the Export URL in the browser. If there is an username set, use those credentials to log in.
-  * If the Export URL is reachable from the browser, the FINDOLOGIC ​server might be black listed. Check those configurations or contact the FINDOLOGIC ​[[support@findologic.com|support@findologic.com]].+  * If the Export URL is reachable from the browser, the Findologic ​server might be black listed. Check those configurations or contact the Findologic ​[[support@findologic.com|support@findologic.com]].
   * If the page cannot be opened, the defined user has not the required permissions. Please set these permissions accordingly.   * If the page cannot be opened, the defined user has not the required permissions. Please set these permissions accordingly.
   * If Cloudflare is used the Browser Integrity Check has to be disabled for the export. A description on how to do disable the Browser Integriy Check can be found [[docs.findologic.com/​doku.php?​id=frequent_export_errors#​cloudflare_and_the_findologic_import|here]].   * If Cloudflare is used the Browser Integrity Check has to be disabled for the export. A description on how to do disable the Browser Integriy Check can be found [[docs.findologic.com/​doku.php?​id=frequent_export_errors#​cloudflare_and_the_findologic_import|here]].
Line 69: Line 69:
 === Validation issue(s) === === Validation issue(s) ===
  
-This means, that the exported XML is not valid against our [[https://​github.com/​FINDOLOGIC/​xml-export/​blob/​master/​src/​main/​resources/​findologic.xsd|schema]]. Please see the import log in the FINDOLOGIC ​customer account for more details about the validation issue. For more information,​ see also our documentation regarding the [[xml_export_documentation:​xml_format|XML export format]] or contact our [[support@findologic.com|support@findologic.com]].+This means, that the exported XML is not valid against our [[https://​github.com/​FINDOLOGIC/​xml-export/​blob/​master/​src/​main/​resources/​findologic.xsd|schema]]. Please see the import log in the Findologic ​customer account for more details about the validation issue. For more information,​ see also our documentation regarding the [[xml_export_documentation:​xml_format|XML export format]] or contact our [[support@findologic.com|support@findologic.com]].
  
 \\  \\ 
Line 75: Line 75:
 === Could not reach API method for... === === Could not reach API method for... ===
  
-This is a failure which can only happen in Plentymarkets shops. It shows that one or more of the REST-API calls can not be reached. Please add the needed permissions for the FINDOLOGIC ​user. See [[https://​docs.findologic.com/​doku.php?​id=integration_documentation:​plentymarkets_ceres_plugin:​rest_export|our documentation]] for more details regarding the REST exporter.+This is a failure which can only happen in Plentymarkets shops. It shows that one or more of the REST-API calls can not be reached. Please add the needed permissions for the Findologic ​user. See [[https://​docs.findologic.com/​doku.php?​id=integration_documentation:​plentymarkets_ceres_plugin:​rest_export|our documentation]] for more details regarding the REST exporter.
  
 \\  \\ 
Line 81: Line 81:
 === Import Failed: Unable to lock instance === === Import Failed: Unable to lock instance ===
  
-A manual import was started while an automatic import-process was already running. Automatic import will continue anyway, so wait for the end of the automatic import and restart your manual import afterwards if needed. If this issue persists, please contact our support.+A manual import was started while an automatic import-process was already running. Automatic import will continue anyway, so wait for the end of the automatic import and restart your manual import afterwards if needed. If this issue persists, please contact our [[support@findologic.com|support@findologic.com]].
  
 \\  \\ 
Line 87: Line 87:
 === Cloudflare and the Findologic import === === Cloudflare and the Findologic import ===
  
-If you are using Cloudflare the user-agent ​FINDOLOGIC ​is blocked by default. This will cause the export to fail. The Cloudflare feature that is blocking the user-agent, is the Browser Integrity Check. ​+If you are using Cloudflare the user-agent ​Findologic ​is blocked by default. This will cause the export to fail. The Cloudflare feature that is blocking the user-agent, is the Browser Integrity Check. ​
 There are two ways to disable the Browser Integrity Check in the Cloudflare Backend. There are two ways to disable the Browser Integrity Check in the Cloudflare Backend.