eNom Renewal Error: Error: Access Control Violation - Name Locking not allowed

[ScottN]

I've had this problem for a few weeks now: When a customer has recently edited their WHOIS contacts on a .ORG domain... then tries to renew the domain (or auto-renew processes), the renewal fails and I receive the following error via email from WHMCS:

 

Error: Access Control Violation - Name Locking not allowed

 

Of course, WHMCS is just sending us the error it receives from eNom. When I log into eNom, I can see that the domain in question is, indeed, under the 60 day transfer lock period.

 

My theory is that WHMCS is trying to set some additional variables, in addition to requesting renewal, and eNom is blocking the entire request due to something being sent that violates the 60 day lock in place.

 

I opened tickets with both eNom and WHMCS and both point the finger at the other and, specifically, WHMCS says my theory is not possible. WHMCS has asked me to enable full debug but since it can take days and days between these errors, I'm worried about the effects of doing debug like that.

 

Of note: I'm still on v 6.3.1, but I plan to move to 7.1 in the next day or so. Since nobody else is reporting this error in the forums (or tickets) I am hopeful that upgrading will magically resolve this error.

 

I'll keep you posted.

 

- Scott

[ScottN]

I realized that I can duplicate this simply by clicking "Renew" inside WHMCS, so I enabled debug and tried it, and sure enough, the error happens simply when issuing the "extend" command via the API. I would tend to agree with WHMCS on this one, that this is an eNom issue. I've updated my case with them, and gave them the following debug output:

 

COMMAND

extend

 

REQUEST

uid=*******&pw=************&tld=org&sld=redacted&NumYears=1&command=extend&Engine=WHMCS6.3&

 

RESPONSE

;URL Interface

;Machine is SJL0VWAPI02

;Encoding Type is utf-8

Command=EXTEND

APIType=API

Language=eng

ErrCount=1

Err1=Access Control Violation - Name Locking not allowed

ResponseCount=1

ResponseNumber1=406379

ResponseString1=Authentication error; policy violation; Access Control Violation - Access Control Lock

MinPeriod=1

MaxPeriod=10

Server=SJL0VWAPI02

Site=

IsLockable=True

IsRealTimeTLD=True

TimeDifference=+07.00

ExecTime=0.000

Done=true

TrackingKey=028a25ca-dba7-4396-921d-8628f7c3afe9

RequestDateTime=1/31/2017 2:34:51 PM

[ScottN]

For closure, eNom says they have fixed the issue causing this problem. Their response makes it seem like it was unique to my account, but perhaps if someone else out there has this same issue, it will help you to identify the solution:

 

I have updated the controls for your domains so that the requests will process correctly. Since your account is the only one affected, it appears to have been caused by the name locking being disabled (unable to change the lock status), even though this is not directly related to the command that you were running. There was nothing on the account to indicate why name locking was disabled, so I have reverted it to "enabled" which is the default.

 

That being said, if you see this or any similar issues after the update, please provide the domains names and full API commands, and I'll get it over to our API engineers for in-depth analysis.