Article ID: 122396, created on Jul 18, 2014, last review on Jul 18, 2014

  • Applies to:
  • Business Automation

Symptoms

Attempt to set the lock on the domain registered with DistributeIT fails:

"Failed to set Registrar Lock"

In the DISTRIBUTEIT.log there is a response like that:

Response content: ERR: 614, Parameter value policy error
    Results of "ERR: 614, Parameter value policy error" parse:
    status: false
    rawPrefix: 
    prefix: 
    message: 614, Parameter value policy error
    errorCode: 614
    errorMessage: Error code not defined
    errorDescription:  Parameter value policy error
"setLock" NOT SUCCEEDED**!**

Cause

You can check the domain status with whois and see that the domain is already locked at the registrar side, therefore lock operation cannot be completed. PBA displays incorrect lock status because of the bug #PBA-57758 ("Domain Registrar Lock status is not set correctly for new DistributeIT domains").

Resolution

Either manually unlock the domain at the registrar side or set the domain as locked in the PBA database (so actual lock status will be displayed for the domain).

Search Words

Registrar lock status out of sync

Failed to set registrar lock

198398b282069eaf2d94a6af87dcb3ff caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07

Email subscription for changes to this article
Save as PDF