SIM no longer working after server reboot

d_james — Sat, 19 May 2012 22:18:40 GMT

After a hard server reboot, we're now getting x_response_reason_text = "This transaction cannot be accepted". I don't know the response reason code, because it's not being sent back to us with the other information. According to the SIM guide, it could be any of these:

3 97 This transaction cannot be accepted. Applicable only to SIM API. Fingerprints are
only valid for a short period of time. This
code indicates that the transaction fingerprint
has expired

.
3 98 This transaction cannot be accepted. Applicable only to SIM API. The transaction
fingerprint has already been used.

3 99 This transaction cannot be accepted. Applicable only to SIM API. The server-
generated fingerprint does not match the
merchant-specified fingerprint in the x_fp_
hash field.

3 103 This transaction cannot be accepted. A valid fingerprint, Transaction Key, or
password is required for this transaction.

I've verified that the fingerprint info is still being generated and submitted with the request; x_fp_sequence, x_fp_timestamp, x_fp_hash are being sent based off of a brand new transaction key, but still the same blank response from the gateway. We have Password-Required mode on.

Does this sound familiar?

Re: SIM no longer working after server reboot

RaynorC1emen7 — Mon, 21 May 2012 20:31:48 GMT

If you are getting (99) This transaction cannot be accepted. You shouldn't even see the credit card entry screen.

Did you check the server time?

topic SIM no longer working after server reboot in Integration and Testing

SIM no longer working after server reboot

Re: SIM no longer working after server reboot