EDC Processing slow - Exclusive Access Error 1

[ClayTaco]

One of my sites is claiming that cards are processing slowly so they're consistently turning processing off. I'm worried about customers catching on and losing money to bogus cards.
Checking through the Aloha EDC log I'm seeing some "Failed to open req file with exclusive access" errors with several different transaction files.
These files do eventually get processed successfully.

Has anyone run into this error before?
Does this error have anything to do with processing slowly? I figured it was just a connection issue till I saw this in the logs.
It sounds like the error is caused by multiple connections trying to get read/ write access. Could the error by tied to FOH switching masters?
Any thoughts on narrowing down the issue?

 

[AlohaRoss]

I have had the same issue the past few weeks with Link(RBS). NCR tried telling us it was related to network card. However I was not able to process cards on a virtual mahcine with same edc settings. Tracert was showing it could not find the tptrans gateway. Calling RBS they suggested changing from port 6660 to 6661. NCR.local has to do. It was not something the enterprise level was allowed to do. And before everyone says it in the EDC.INI, its not. its a DLL that has to be changed for the port change. It is not like visanet setup where its as simple as adding PORT=6661.

If you are not with Link(RBS) then just ignore everything I just typed.

AlohaRoss

http://www.needaholahelp.com

3rd Party support

 

[ClayTaco]

The site is using Heartland as their processor. I'll have to give them a call and see if there are any changes I should make to the configuration.
I'm thinking that it wouldn't be a processor issue since the error is inconsistent. I'd expect the processor to always fail if the configuration was wrong.
Ross, was your site unable process any cards or was the error only happening occasionally?

 

[AlohaRoss]

unable to process. I would put them in spooling for an hour and then take them out and the transactions would go through. Sometimes just restating the service fixed the issue. still not 100%.

AlohaRoss

http://www.needaholahelp.com

3rd Party support

 

[ClayTaco]

Sounds about right.
Thanks for the quick response, time to give the processor a call......

 

[AlohaRoss]

Heartland is one of the better processors just remember to edit edc.ini file correct


6.2 and older use
host not IPhost

Heartland
IPHost=sslprod.secureexchange.net
IPport=22342


-For Aloha 5.3, version 5.3.1 through 5.3.26 should process to Exchange using dial up only. Merchants wanting to
process using IP should use version 5.3.27 or higher because of issues found with earlier versions of Aloha’s IP
functionality which were fixed beginning with version 5.3.27.
-For versions 6.3 or lower on Exchange, if parameter sheet Ip address is
IPHost=httpsprod.secureexchange.net, then you must add the following line to the edc.ini USEHTTPS=1 for high
speed processing to work.
-For versions 6.3 or higher or 7.0 or higher on Exchange if parameter sheet Ip address is
IPHost=sslprod.secureexchange.net then you must make sure that the edc.ini does NOT have usehttps=1 and
you must add IPport=22342 to the edc.ini


AlohaRoss

http://www.needaholahelp.com

3rd Party support