Answers.Body: <p>Answering (2) only here.</p>
  
  <p>CiviCRM's payment processor logs vary in their location based on the CMS in use. These logfiles include a unique string per site, as the logfiles are  located within the webroot and a hard to guess filename offers some defense against attackers viewing debug output.</p>
  
  <p>This is documented @ -</p>
  
  <ul>
  <li><a href="https://wiki.civicrm.org/confluence/display/CRMDOC/Debugging+for+developers#Debuggingfordevelopers-Logfiles" rel="nofollow">https://wiki.civicrm.org/confluence/display/CRMDOC/Debugging+for+developers#Debuggingfordevelopers-Logfiles</a></li>
  <li><a href="https://wiki.civicrm.org/confluence/display/CRMDOC/CMS+Standard+Directories+and+File+locations" rel="nofollow">https://wiki.civicrm.org/confluence/display/CRMDOC/CMS+Standard+Directories+and+File+locations</a> </li>
  </ul>
  
  <h2>WordPress</h2>
  
  <p>4.6 and below: <code>wp-content/plugins/files/civicrm/ConfigAndLog/CiviCRM.HARDTOGUESS.log</code>
  4.7 and above: <code>wp-content/uploads/civicrm/ConfigAndLog/CiviCRM.HARDTOGUESS.log</code></p>
  
  <h2>Joomla</h2>
  
  <p><code>media/com_civicrm/ConfigAndLog/CiviCRM.HARDTOGUESS.log</code> (<a href="https://wiki.civicrm.org/confluence/display/CRMDOC/Debugging+for+developers#Debuggingfordevelopers-Logfiles" rel="nofollow">1</a>) or
  <code>media/civicrm/ConfigAndLog/CiviCRM.HARDTOGUESS.log</code> (<a href="https://wiki.civicrm.org/confluence/display/CRMDOC/CMS+Standard+Directories+and+File+locations" rel="nofollow">2</a>)</p>
  
  <h2>Drupal</h2>
  
  <p><code>sites/&lt;sitedir&gt;/files/civicrm/ConfigAndLog/CiviCRM.HARDTOGUESS.log</code></p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-06-16T21:18:50.343Z
Answers.Text: I don't think the web-accessible logfiles are great even with the current protections applied, and I'm working to provide better options in [CRM-13639](https://issues.civicrm.org/jira/browse/CRM-13639).
Answers.UserDisplayName: Chris Burgess
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-06-16T22:20:23.937Z
Answers.Text: Thank you! Follow up question: If this log shows only email related errors and nothing about the payment processor that is acting up, what would you take from that information?
Answers.UserDisplayName: naomisl
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-06-17T00:12:43.907Z
Answers.Text: I'd check if the Authorize.NET payment processor logs to a separate file; next I'd track down the location of that error message (capitalisation of **V**erification may make the location distinctive?) and debug what specific inputs aren't matching, leading to a validation failure.
Answers.UserDisplayName: Chris Burgess
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-08-10T05:13:41.810Z
Answers.Text: Correction for Joomla: ```~/media/civicrm/ConfigAndLog/```
Answers.UserDisplayName: BruceW
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-08-10T11:00:13.073Z
Answers.Text: Thanks BruceW! Looks like [Debugging for Developers](https://wiki.civicrm.org/confluence/display/CRMDOC/Debugging+for+developers#Debuggingfordevelopers-Logfiles) and [CMS Standard directories](https://wiki.civicrm.org/confluence/display/CRMDOC/CMS+Standard+Directories+and+File+locations#CMSStandardDirectoriesandFilelocations-Joomla!) differ re Joomla! locations, hope someone who uses Joomla can check and correct the wiki docs. Updated the above to mention both for now, let me know if I should trim it down again.
Answers.UserDisplayName: Chris Burgess
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-06-16T21:18:31.780Z
Answers.LastActivityDate: 2016-08-10T11:01:42.823Z
Answers.LastEditDate: 2016-08-10T11:01:42.823Z
Answers.UserDisplayName: Chris Burgess
Body: <p>I have the same issue that <a href="https://civicrm.stackexchange.com/questions/7383/payment-processor-error-message-9003-md5-verification-failed-after-upgrade">this person did</a>, though I'm updated to 4.6.10 The issue is that when submitting payments, I get the 9003 error code, which says "MD5 Verification failed."  I've reset the MD5 code from both sides, and am confident that they match. It's possible that my issue could be solved with the answer that I linked, but I don't know enough to apply it. It's also possible that Authorize.net tech support could help me, but they won't do anything without the log and I'm unsure where it lives. So...</p>
  
  <p>1) Do you know how to fix this error?</p>
  
  <p>Or failing that,</p>
  
  <p>2) Where are CiviCRM's payment processor logs? </p>
  
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2016-06-16T20:52:33.007Z
Comments.Text: Can you please edit your question and correct the version number (4.10) which you've reported? There isn't (yet) such a CiviCRM version, and an accurate answer will be more likely with an accurate question.
Comments.UserDisplayName: Chris Burgess
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2016-06-16T20:55:59.787Z
Comments.Text: Good catch! Edited.
Comments.UserDisplayName: naomisl
Tags: <payment-processor><error><authorize.net><logging>
Title: Payment Processor Error 9003, and logging
ThreadText: # Payment Processor Error 9003, and logging
  
  (Asked by: username_0 on 2016-06-15)
  
  I have the same issue that [this person did](https://civicrm.stackexchange.com/questions/7383/payment-processor-error-message-9003-md5-verification-failed-after-upgrade), though I'm updated to 4.6.10 The issue is that when submitting payments, I get the 9003 error code, which says "MD5 Verification failed." I've reset the MD5 code from both sides, and am confident that they match. It's possible that my issue could be solved with the answer that I linked, but I don't know enough to apply it. It's also possible that Authorize.net tech support could help me, but they won't do anything without the log and I'm unsure where it lives. So...
  
  1) Do you know how to fix this error?
  
  Or failing that,
  
  2) Where are CiviCRM's payment processor logs?
  
  **Tags:** payment-processor, error, authorize.net, logging
  
  > **Comments:**
  > **username_1**: Can you please edit your question and correct the version number (4.10) which you've reported? There isn't (yet) such a CiviCRM version, and an accurate answer will be more likely with an accurate question.  
  > **username_0**: Good catch! Edited.  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2016-06-16. Score: 2 | Accepted answer
  
  Answering (2) only here.
  
  CiviCRM's payment processor logs vary in their location based on the CMS in use. These logfiles include a unique string per site, as the logfiles are located within the webroot and a hard to guess filename offers some defense against attackers viewing debug output.
  
  This is documented @ -
  
  * <https://wiki.civicrm.org/confluence/display/CRMDOC/Debugging+for+developers#Debuggingfordevelopers-Logfiles>
  * <https://wiki.civicrm.org/confluence/display/CRMDOC/CMS+Standard+Directories+and+File+locations>
  
  ## WordPress
  
  4.6 and below: `wp-content/plugins/files/civicrm/ConfigAndLog/CiviCRM.HARDTOGUESS.log`
  4.7 and above: `wp-content/uploads/civicrm/ConfigAndLog/CiviCRM.HARDTOGUESS.log`
  
  ## Joomla
  
  `media/com_civicrm/ConfigAndLog/CiviCRM.HARDTOGUESS.log` ([1](https://wiki.civicrm.org/confluence/display/CRMDOC/Debugging+for+developers#Debuggingfordevelopers-Logfiles)) or
  `media/civicrm/ConfigAndLog/CiviCRM.HARDTOGUESS.log` ([2](https://wiki.civicrm.org/confluence/display/CRMDOC/CMS+Standard+Directories+and+File+locations))
  
  ## Drupal
  
  `sites/<sitedir>/files/civicrm/ConfigAndLog/CiviCRM.HARDTOGUESS.log`
  
  > **Comments:**
  > **username_1**: I don't think the web-accessible logfiles are great even with the current protections applied, and I'm working to provide better options in [CRM-13639](https://issues.civicrm.org/jira/browse/CRM-13639).  
  > **username_0**: Thank you! Follow up question: If this log shows only email related errors and nothing about the payment processor that is acting up, what would you take from that information?  
  > **username_1**: I'd check if the Authorize.NET payment processor logs to a separate file; next I'd track down the location of that error message (capitalisation of **V**erification may make the location distinctive?) and debug what specific inputs aren't matching, leading to a validation failure.  
  > **username_2**: Correction for Joomla: ```~/media/civicrm/ConfigAndLog/```  
  > **username_1**: Thanks username_2! Looks like [Debugging for Developers](https://wiki.civicrm.org/confluence/display/CRMDOC/Debugging+for+developers#Debuggingfordevelopers-Logfiles) and [CMS Standard directories](https://wiki.civicrm.org/confluence/display/CRMDOC/CMS+Standard+Directories+and+File+locations#CMSStandardDirectoriesandFilelocations-Joomla!) differ re Joomla! locations, hope someone who uses Joomla can check and correct the wiki docs. Updated the above to mention both for now, let me know if I should trim it down again.  
  
  ---
  
  