topic Re: CIM - Suddenly E000001 - Test account only in Integration and Testing

CIM - ASP/VBScript - Sudden E000001 with no change to Util.asp

Julie — Tue, 29 Jun 2010 07:30:44 GMT

It's probably just late and so I'm not seeing something, but the code that generates my XML statement didn't change and the util.asp file with the send command didn't change, nothing on my server changed, but I'm suddenly getting an error. (Obviously, something must have changed somehow, because it's not working. lol):

Here's what the feedback looks like:

API URL: https://apitest.authorize.net/xml/v1/request.api

Raw request:
<?xml version="1.0" encoding="utf-8"?>
<createCustomerProfileRequest xmlns="AnetApi/xml/v1/schema/AnetApiSchema.xsd">
   <merchantAuthentication>
      <name>xxxxxxxxxx</name
      <transactionKey>xxxxxxxxxxxxxxxx</transactionKey> 
    </merchantAuthentication>
    <profile> 
       <merchantCustomerId>272518</merchantCustomerId>
    </profile>
</createCustomerProfileRequest>

Raw response: 
<?xml version="1.0" encoding="utf-8"?>
<createCustomerProfileResponse xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="AnetApi/xml/v1/schema/AnetApiSchema.xsd">
<messages>
    <resultCode>
        Error
    </resultCode>
    <message>
        <code>
           E00001
        </code>
        <text>
            An error occurred during processing. Please try again.
        </text>
    </message>
</messages>
<customerPaymentProfileIdList />
<customerShippingAddressIdList />
<validationDirectResponseList />
</createCustomerProfileResponse>

It takes a long time to get the error back - feels like a time out, almost. I rebooted my server, and it didn't help.

Earlier today in another part of the system (the part that retrieves a list of customer credit cards) I suddenly started getting the error "The download of the specified resource has failed", and again, it with no changes to the code. Seriously - one second it loaded fine, the next second it did not. I fixed that with a suggestion from a post here (change Set objHTTP = Server.CreateObject("MSXML2.ServerXMLHTTP")" to
Set objHTTP = Server.CreateObject("Microsoft.XMLHTTP")...included that here in case someone is searching for that error), but that didn't work for this other problem.

I'm lost.

It must be something obvious, but I'm just not seeing it.

Any clues?

Thanks so much,

Julie

Re: CIM - Suddenly E000001 - Test account only

Julie — Tue, 29 Jun 2010 09:44:27 GMT

More information:

I had tried about everything...I normally work on a password protected development site, so I moved it over to live website to see if that would help. Live has a server certificate, and I tried both HTTP and HTTPS, and nothing helped.

I created a stripped down file with just the call to authorize.net, grabbed just the 2 routines I needed from util.asp (sendAPIRequest and MerchantAuthentication), so the file was as small as possible and still got the error.

Finally, I switched to api.authorize.net instead of apitest.authorize.net with the appropriate login information, and it worked quickly and perfectly.

So I edited the original files (the full page and the utlity file) to use the api.authorize.net...and again, it worked perfectly.

For testing I desperately need to use the test account.

Any ideas?

Thanks,

Julie

Re: CIM - Suddenly E000001 - Test account only

moklett — Tue, 29 Jun 2010 10:24:09 GMT

I am seeing a similar issue (error E00001 returning after about 30 seconds), so I suspect an issue with the test server.

Re: CIM - Suddenly E000001 - Test account only

Julie — Tue, 29 Jun 2010 10:29:43 GMT

Boy if one more person could confirm that, I'd go to bed. lol. It's 3:30AM here, and I've been beating on this for hours now.

Re: CIM - Suddenly E000001 - Test account only

moklett — Tue, 29 Jun 2010 10:37:32 GMT

I have automated tests that once passed, and now fail, with no changes. So I can almost guarantee its not you.

Re: CIM - Suddenly E000001 - Test account only

Julie — Tue, 29 Jun 2010 10:40:04 GMT

You're my hero. It's bedtime. :)

Re: CIM - Suddenly E000001 - Test account only

moklett — Tue, 29 Jun 2010 10:41:03 GMT

And if you need any more confirmation, try creating a CIM payment profile via the UI at https://test.authorize.net. It doesn't work there either.

Re: CIM - Suddenly E000001 - Test account only

moklett — Tue, 29 Jun 2010 18:57:13 GMT

@Julie, tech team is aware of this issue. Follow results over here: http://community.developer.authorize.net/t5/Integration-and-Testing/Can-t-destroy-CIM-profile-in-test-mode/m-p/3769#M3446

Re: CIM - Suddenly E000001 - Test account only

Michelle — Wed, 30 Jun 2010 18:31:13 GMT

Hey everyone,

It's true...we're having issues with CIM on the test server. Once we know more on when it will be fixed, we'll update this post. Sorry for the problems!! :smileysad:

Thanks,

Michelle

Developer Community Manager

Re: CIM - Suddenly E000001 - Test account only

ramontayag — Mon, 01 Aug 2011 07:36:28 GMT

I'm getting this problem too. And, I can't create one on the website either. Are there any problems?

Re: CIM - Suddenly E000001 - Test account only

proof1 — Mon, 01 Aug 2011 13:37:41 GMT

We started experiencing this last night aroun d 8pm EST. We can't use existing CIM profiles or create new ones with either the API or the website.

Re: CIM - Suddenly E000001 - Test account only

missbossy — Fri, 04 Nov 2011 18:02:31 GMT

Can you verify what the actual timeout time is? I've heard both 10 seconds and 30 seconds.

Thank you!!!

Re: CIM - Suddenly E000001 - Test account only

Trevor — Mon, 07 Nov 2011 23:04:43 GMT

What timeout in particular are you referring to? The timeout mentioned in this thread was an internal timeout within the Authorize.Net test system and is not something that you should need to account for.

Re: CIM - Suddenly E000001 - Test account only

TJPride — Tue, 08 Nov 2011 01:51:32 GMT

Not sure on that, but it'd be useful to know, for instance, how long to wait when processing multiple charges in sequence. If no response comes back in 10 seconds, is it never going to come back? How about 30 seconds? How about when creating or updating a profile?

Re: CIM - Suddenly E000001 - Test account only

Trevor — Mon, 14 Nov 2011 23:42:05 GMT

Internally, we time out a transaction after approximately 2 minutes. However, the average transaction time within our system is well under 2 seconds and the possible sets of circumstances that would be required for it to get anywhere near that limit are extremely limited. It is also worth mentioning that I can't guarantee that we wont' change that limit in the future without notice.

The other main factor in a transaction time lifespan would be the communication timeout for when we send you the transaction results. The timeout for that communication for most API connections is 30 seconds. Again, there are limited situations where it could take that long. If we fail to resolve a connection to you or the connection is interrupted, we give up immediately. It would only hit 30 seconds if it is taking a very long time just to establish a connection.

Re: CIM - Suddenly E000001 - Test account only

TJPride — Tue, 15 Nov 2011 07:55:30 GMT

Hmm. Would it be safe to, for instance, have a process time out on our end after 10 seconds, then retry with the same information, and if it gets back a duplicate transaction error, assume that it went through? What about relay response? Do we need to set the timeout on that to 2 minutes just to be safe?

Re: CIM - Suddenly E000001 - Test account only

Trevor — Thu, 17 Nov 2011 22:54:08 GMT

It should almost always be safe to have a transaction time out after 10 seconds, but it's probably better to put it to at least 20. I actually have personally never seen a transaction take more than 10 seconds, but it does occur very infrequently. If the transaction takes over 20 seconds, it is a very good bet that the transaction has failed or that the response failed. However, it is not safe to assume that a transaction went through if you get a duplicate transaction response. This would confirm that the transaction was processed, but it very well might have been declined.

Relay response is an asynchronous process. The customer always must leave your system and then come back, so generally I wouldn't expect a strict transaction timeout to be set on your side at all. The customer session might time out, but that is usually outside the scope of the transaction lifespan.

Re: CIM - Suddenly E000001 - Test account only

TJPride — Fri, 18 Nov 2011 10:14:28 GMT

I'm talking about the page that you use in ARB to receive the transaction info when payments process through automatically. Not sure if the correct term for that is relay response or callback or what.

Re: CIM - Suddenly E000001 - Test account only

missbossy — Mon, 05 Dec 2011 19:51:16 GMT

Should I specify a timeout in the

getHostedProfilePageRequest?

Thanks,

Monique