|
Shon Smith
|
May 11, 2017 at 8:26 am
I am receiveing the following error when a payment is processed.
The following errors have occurred:
The stored data for session ee_ssn_a35cc0f430f9528feae8c7965f65c93d failed to pass a hash check and therefore appears to be invalid.
EE_Session – _retrieve_session_data – 533
The following Exception was thrown in /var/www/nwforums.com/wp-content/plugins/event-espresso-core-reg/core/db_models/EEM_Base.model.php on line 2204:
this is in production.
Thanks
|
|
Josh
|
May 11, 2017 at 10:50 am
Hi Shon,
Do you know if there’s any caching happening on the website?
|
|
Shon Smith
|
May 11, 2017 at 10:56 am
HI Josh,
None that I know of?
|
|
Josh
|
May 11, 2017 at 11:06 am
Does you host run server side caching?
This error:
The stored data for session ee_ssn_a35cc0f430f9528feae8c7965f65c93d failed to pass a hash check and therefore appears to be invalid.
usually means EE is receiving cached data.
You can try disabling the hash check to see if another error is shown using:
add_filter('FHEE__EE_Session___perform_session_id_hash_check', '__return_false');
to a functions plugin and activate it.
However if data is being served from a cache on the server you’ll likely see other problems.
|
|
Shon Smith
|
May 11, 2017 at 11:11 am
Hi Josh, I just ran another transaction through with my own card and it worked fine. The only difference was a promotional discount of 50% for the one that is not working. I will try the above code and see if there is any other errors.
Thanks
|
|
Shon Smith
|
May 11, 2017 at 11:18 am
Added the code above and re-ran the process with wp-debug on. this is what I got.
The following errors have occurred:
The following Exception was thrown in /var/www/nwforums.com/wp-content/plugins/event-espresso-core-reg/core/db_models/EEM_Base.model.php on line 2204:
WPDB Error occurred, but no error message was logged by wpdb! The wpdb method called was “insert” and the arguments were “array ( 0 => ‘wp_esp_log’, 1 => array ( ‘LOG_time’ => ‘2017-05-11 17:16:12’, ‘OBJ_ID’ => ‘597’, ‘OBJ_type’ => ‘Payment’, ‘LOG_type’ => ‘gateway’, ‘LOG_message’ => ‘a:1:{s:31:”Payeezy sale request Parameters”;a:12:{s:10:”gateway_id”;s:9:”111111-01″;s:16:”transaction_type”;s:2:”00″;s:6:”amount”;s:6:”525.00″;s:13:”currency_code”;s:3:”USD”;s:14:”ecommerce_flag”;s:1:”7″;s:12:”reference_no”;s:8:”kbt9$ToD”;s:15:”cardholder_name”;s:10:”Shon Smith”;s:16:”cvd_presence_ind”;s:1:”1″;s:16:”credit_card_type”;s:16:”American Express”;s:12:”client_email”;s:12:”XXXX@uic.edu”;s:7:”address”;a:8:{s:8:”address1″;s:22:”130 Somwhere #1907″;s:8:”address2″;s:0:””;s:4:”city”;s:7:”XXXXXX”;s:5:”state”;s:2:”IL”;s:3:”zip”;s:5:”60602″;s:12:”country_code”;s:2:”US”;s:12:”phone_number”;s:14:”xxx-xxx-xxxx ?”;s:10:”phone_type”;s:1:”W”;}s:18:”partial_redemption”;i:0;}}’, ‘LOG_wp_user’ => 0, ), 2 => array ( 0 => ‘%s’, 1 => ‘%s’, 2 => ‘%s’, 3 => ‘%s’, 4 => ‘%s’, 5 => ‘%d’, ), )”
EE_SPCO_Reg_Step_Payment_Options – _handle_payment_processor_exception – 2134
I have x out some of the content for obvious reasons.
THanks
Shon
|
|
Josh
|
May 11, 2017 at 11:43 am
Hi Shon,
A possible reason for the errors you’re seeing is if the database is using some different collations, and so the characters being sent to the database aren’t what Event Espresso is seeing come out of it. You mentioned that the error is happening on production, can I assume that there’s also a staging server? If so, do the two servers use the same collation for their databases?
|
|
Shon Smith
|
May 11, 2017 at 11:47 am
Hi Josh
Yes they do. I have not touched the collation since initial configuration, so I don’t think that is it. Also, I entered a separate event transaction and it worked fine, just not this one? Not sure what is unique about this one except for the promotion.
Thanks
|
|
Josh
|
May 11, 2017 at 1:14 pm
One guess is if there’s something within the promotion’s description or other field like an emoji or something it could affect things. You can go to Event Espresso > Payment Methods > Logs, then check the log entries for that Transaction. There you can check the Payeezy sale request Response.
|
