[FIXED] Problem with Enom Domain Syncronisation

[DimaK]

Today looks like Enom was down when Domain Syncronisation cron was started !

 

And we got big issues !

For EVERY domain "Next Due Date" and "Expiry Date" became 00/00/0000

and was created invoiced for ALL customers and were sent to all customers.

System tried to charge customer's credit cards automatically

(fortunately my gateway not active now...)

 

So please correct Enom Domain Syncronisation, if enom not show good date, then Don't change it in the WHMCS.

[chickendippers]

This happened with us but with the DirectI synchronisation. It was disastrous with numerous customers being charged.

[Redsign]

This happened to us a few days ago, but fortunately we caught it in time:

 

I recommend running the sync cron at a time you're going to be able to see the results before your actual cron kicks in.

 

That way you receive the sync email report, and if you notice anything strange there's a chance to rectify any problems before the main cron goes charging your clients.

 

This still needs to be addressed properly though.

 

Ben

[remcom]

The default fail is set to nothing. It really should have a backup for if it fails it stays the same instead of changing.

 

We didn't have this issue with failure. We did however have the invoice issue after we migrated a bunch of domains over and the invoice cron ran before the enom sync.