Error when running domainsync with Enom

[vivaciti]

We have just started to get an error when running our domainsync cron.

We only get this error for domains registered with Enom the error is: Error: An invalid command was specified

 

We raised a ticket and was given a reply: We have recently became aware of this happening and the "An invalid command was specified" error is being returned by eNom.

The error is coming from Enom as we are sending information according to their API document so you will need to raise this with Enom (cheers WHMCS, I could here the noise that buck sounded while being passed around the floor) anyhow I have raised a ticket with Enom, but does anyone else have any ideas?

[Kelly]

I was having the same issue and got the same response from WHMCS support. I called Enom and they informed me that they were having issues on their end since yesterday and that it was fixed about 2 hours ago. I have tested and confirmed that the syncs are now working.

[WHMCS John]

Hi,

I first noticed the error at about midnight BST on 14/04/2016. The latest update I have from eNom support on the matter is:

 

I have submitted this issue to our Network Operations team for further investigation.

 

I appreciate your patience and will get back to you as soon as possible. In the meantime, if you have any additional questions about this matter, please feel free to update this ticket.

 

I'll be sure to update this thread once I receive confirmation of a fix from eNom.

[WHMCS John]

Hi,

I've just heard back from eNom support confirming the issue is resolved:

 

Thank you for your patience.

 

Our development staff reported that this issue was resolved on 2016-04-14 at 07:14 (GMT-. We are sorry for the inconvenience.

 

I hope this has resolved this issue to your satisfaction. If you have any additional questions about this matter, please feel free to update this ticket.

 

Because WHMCS communicates with so many external services, there is a reliance on the APIs operating as documented.