Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Weird Settling Issue

Status
Not open for further replies.

alohaakamai3

IS-IT--Management
Aug 11, 2006
482
US
Aloha EDC v5.3.16

Haven't seent this one before.

Go to settle a batch, and you'll get an error message saying "there are no transaction to settle with selected processors".

There are two processors, Visanet and Alohanet. The cards are assigned to their appropriate processors.

If you look at the settings for visanet under processors, you won't see the visa net config screen... you will see the Alohanet configuration screen for both Visanet and Alohanet.

The temporary workaround (and the most significant insight to the problem that I can offer): If you delete Alohanet from the Processors, it will settle just fine.

It's almost as if Alohanet is "taking over" all of the processors when it's added to list. Don't know when or how this started, but I think this definitely qualifies as a bug. Planning on doing a point upgrade, but can anyone think of a reason why this is happening?

Thanks!
 
If it were me, I would rename the edc.ini, restart edc and put in the processors again, using the blank edc.ini.

But that's just me!!!

Adam
 
That's not a horrible idea. I've already done the basics (unreg/re-reg, start/stop services, etc). I am thinking only something a little more extreme... like upgrading or starting from scratch... is going to fix this. More suggestions are welcome though.
 
I've had weird things like this happen with edc and starting with a blank edc.ini worked. I've looked through the point release documents and I haven't seen anything regarding this. Just seems that the file got corrupt.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top