cancel
Showing results for 
Search instead for 
Did you mean: 

CIM Timeout Issue as of 11 PM EST

I am experiencing a timeout issue on CIM as of 11 PM EST. Our last successful transaction and payment profile was created at 10:55 PM EST. Profile response, shipping address response, and payment profile response all looked normal and time for API call was 2 seconds max. However, on our next transaction at 11:41 PM EST, I am receiving time out errors as follows:

 

[2014-09-19 03:33:57][----Request----]
MASKED
----CURL ERROR----
Operation timed out after 45000 milliseconds with 0 bytes received

[2014-09-19 03:34:42][----Response----]

[ Time Taken for the API CALL : 45seconds ]


[2014-09-19 03:34:42][----Request----]
MASKED
----CURL ERROR----
Operation timed out after 45000 milliseconds with 0 bytes received

[2014-09-19 03:35:27][----Response----]

[ Time Taken for the API CALL : 45seconds ]


[2014-09-19 03:37:20][----Request----]
MASKED
[2014-09-19 03:37:58][----Response----]
<?xml version="1.0" encoding="utf-8"?><updateCustomerProfileResponse xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" ><messages><resultCode>Error</resultCode><message><code>E00014</code><text>Customer Profile ID is required.</text></message></messages></updateCustomerProfileResponse>
[ Time Taken for the API CALL : 38seconds ]


[1411097878]:Error Creating Customer profile 23454: Error: Error
Message: Customer Profile ID is required.
E00014
[2014-09-19 03:39:41][----Request----]
MASKED
----CURL ERROR----
Operation timed out after 45000 milliseconds with 0 bytes received

[2014-09-19 03:40:26][----Response----]

[ Time Taken for the API CALL : 45seconds ]


[2014-09-19 03:40:26][----Request----]
MASKED
[2014-09-19 03:41:09][----Response----]
<?xml version="1.0" encoding="utf-8"?><ErrorResponse xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" ><messages><resultCode>Error</resultCode><message><code>E00003</code><text>The element 'profileTransAuthCapture' in namespace 'AnetApi/xml/v1/schema/AnetApiSchema.xsd' has invalid child element 'order' in namespace 'AnetApi/xml/v1/schema/AnetApiSchema.xsd'. List of possible elements expected: 'lineItems, customerProfileId' in namespace 'AnetApi/xml/v1/schema/AnetApiSchema.xsd'.</text></message></messages></ErrorResponse>
[ Time Taken for the API CALL : 43seconds ]

 

 

The same errors occurred for 2 other users under different IP addresses, as well as several of my own tests. Our system has been working solidly for weeks now, and I have not uploaded any changes in over 2 weeks. Is anyone else experiencing this CIM timeout issue?

jmagaro88
Contributor
22 REPLIES 22

I suspect it will be ignored like the three other CIM outages I have recorded this summer (7/8, 7/28, 8/19, and now 9/18). Remember when their integration with First Data broke in July 2013 and they said we should all call our banks? That was a good one.

npiasecki
Regular Contributor

this is happening again to me.

From Customer Support:

 

"I am sorry, we were not provided with any specifics on what caused this issue. There will not be a root cause analysis posted regarding this issue. However, I can pass you feedback on regarding this issue and that you would like to request this information if it happens in the future. "

 

I have recorded CIM going down on these dates in 2014:

 

  • June 2nd
  • July 8th
  • July 28th
  • August 19th
  • September 18th

I have requested a root cause analysis and a status page each time. I simply give up.

npiasecki
Regular Contributor