Answers.Body: <p>This has been fixed. My hosting company migrated my site to another server which could communicate with eWay and it is now working. </p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-12-01T22:12:03.443Z
Answers.Text: ideally you would 'accept' your own answer and help close this off
Answers.UserDisplayName: petednz - fuzion
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-09-06T21:49:22.170Z
Answers.LastActivityDate: 2016-09-06T21:49:22.170Z
Answers.UserDisplayName: Garry Hyman
Body: <p>eWay Payment Processor error 9001 on Contact's Contribution page.</p>
  
  <p>Setup new eWay account works fine with Xero, however, with CiviCrm (4.7.10) when used with a Contact's Contribution page I get a "9001 error. Connection to payment gateway failed - no data found". Have tried the delivered eWay processor and also Chris Chincilla's V1.2 and I get the same behaviour.</p>
  
  <p>Have checked the setup many times and it is correct. Have deleted the payment processor and then re-added it. No change.</p>
  
  <p>Can anybody help me or point me in he right direction please? </p>
  
Tags: <wordpress><payment-processor><eway>
Title: eWay Payment Processor error 9001 on contribution - help please
ThreadText: # eWay Payment Processor error 9001 on contribution - help please
  
  (Asked by: username_0 on 2016-09-05)
  
  eWay Payment Processor error 9001 on Contact's Contribution page.
  
  Setup new eWay account works fine with Xero, however, with CiviCrm (4.7.10) when used with a Contact's Contribution page I get a "9001 error. Connection to payment gateway failed - no data found". Have tried the delivered eWay processor and also Chris Chincilla's V1.2 and I get the same behaviour.
  
  Have checked the setup many times and it is correct. Have deleted the payment processor and then re-added it. No change.
  
  Can anybody help me or point me in he right direction please?
  
  **Tags:** wordpress, payment-processor, eway
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_0 on 2016-09-06. Score: 2 | Accepted answer
  
  This has been fixed. My hosting company migrated my site to another server which could communicate with eWay and it is now working.
  
  > **Comments:**
  > **username_1**: ideally you would 'accept' your own answer and help close this off  
  
  ---
  
  