Article ID: 114736, created on Sep 10, 2012, last review on Apr 15, 2017

  • Applies to:
  • Operations Automation 6.0
  • Operations Automation 5.5
  • Operations Automation 5.4
  • Business Automation

Symptoms

There is a domain order that cannot be successfully processed - it is stuck in Provisioning, Long Running Operation or Failed status.

As a Provider, I performed a required operation directly on the registrar side (registered, transfered, or renewed a domain), verified the correct information using WHOIS and now I need to complete an order in Business Automation (BA).

Cause

Domain order processing in BA may fail for several reasons: a changed registrar API, network connectivity problems between BA and the registrar, missing required parameters, and more.

A domain may be registered/transferred/canceled manually on the registrar side and, after that, it is necessary to mark the corresponding operation as completed in BA, i.e., to mark the corresponding sales/renewal/cancellation order as Completed.

Resolution

The requested operation can be performed using the BA Domain Conflict Resolver. A feature has been implemented in BA 5.1 with the main purpose of completing a failed domain operation (registration, transfer, renewal, or cancellation) manually, where all required actions were completed on the registrar side.

Important! Only use the Domain Conflict Resolver in BA if you are completely sure that all required operations on the registrar side have been completed. It does not send any requests to the registrar, only sets the correct statuses to the related BA objects (domain, order, subscription).

Follow the steps below to complete a domain order:

  • BA 5.4: Operation Director > Sales Manager > Customers Orders > Order ID

    BA 5.5 and later: Home > Operations > Orders > Order ID

  • Switch to the Provisioning Items tab
  • Click on the failed domain item in the Subscription ID column
  • Switch to the Service Props tab
  • Enter the reason for the manual operation in the Comment field
  • Click either the Complete Operation Manually or the Mark Operation as Failed button as shown in the screenshot below:

Your text to link here...

  • Resubmit an order for provisioning if it has been in Failed status.

Note: The button Mark Operation as Failed may be absent from the Domain Conflict Resolver screen, depending on the domain order type and status.

Restrictions

If there are other items than the domain itself in the order, Domain Conflict Resolver will not work (no statuses will change when you click "Complete Operation Manually"). This is a known bug with the ID #PBA-45759, which was corrected in BA 5.5.4. If you need to complete an order manually and your BA version is below 5.5.4, please contact Odin Technical Support for assistance.

Search Words

register domain

OrderItemID=15049; SubscrID=1004481; ServiceName=misal.fi; IssuedSuccessfully=1; DomainOperation=90; Message=Domain is successfully transferred.

minsi.se

domain transfered renewal email hosting

An order stay in "provisionning" status

DNS Zone update was failed.

domain stuck in long running operation

failed orders

domain renewal failing

manual domain provisioning

failed task

sadsad

order failed

Domain Status Prepared

cancelation order

DNS Zone update was failed

update zone dns

complete order

domain issue

фэйлится ордер

domain status info

registrar

Email hosting without domain subscription

Domain registration request accepted by registrar. Domain status:Checking Registration Status. DNS Zone update was failed. Domain Status: Registered, Notifying

provisioning failed cancellation orders

Failed to get APS resource id. aps node is not found

stuck in provisioo

test

stuck in long running operation

order issue

provisioning

Domains stuck in "Renewing" status despite cancelled Renewal Order

Stuck on provisioning status

domain transfered renewal

manual completion

domain tranfered to another registrar

Table Gate Link doesn't contain row

Domain name cannot be renewed

Failed to provision new domain

failed downgrade order PBA

adfaffqw

[23:06] José Ramírez García: <<< no hay "que sibirlo a parallels, hay que subirlo a akky.mx le agreg"s este pedacito de log por fa [16-07-11 23:04:40.784 RDBMS RQ238649 INF] Execute [0x7f52d02311e0]: 3952705 [16-07-11 23:04:40.785 RDBMS RQ238649 DBG] F"etch [0x7f52d02311e0]: 3952705, 20, 20, 1688796, ""-1, 1468296218, 0, 'Checked status of registration in r"egistrar. It is in progress. Domain status:Checking Registration Status. Objeto no existe<4 time(s) called.">', 'RESPONSE: <?xml version="1.0" encoding=""UTF-8" standalone="no"?><epp xmlns="urn:ietf:params:xml:ns:epp-1.0"><greeting><svID>epp-2.mx.app-sf.nic.net.mx</svID><svDate>2016-07-12T04:03:40.2Z</svDate><svcMenu><version>1.0</version><lang>es</lang><lang>en</lang><objURI>urn:ietf:params:xml:ns:contact-1.0</objURI><objURI>urn:ietf:params:xml:ns:host-1.0</objURI><objURI>urn:ietf:params:xml:ns:domain-1.0</objURI><svcExtension><extURI>http://www.nic.mx/nicmx-msg-1.0</extURI><extURI>http://www.nic.mx/nicmx-res-1.0</extURI><ex

cannot renew customer

cancel domain subscr cancel order failed

sales order stuck domain plugi for registrar opensrs

provisioning email account

long running operation

issue with domain transfer between subscriptions

Unable

order provisioning fails

Manual provisioning of domain can't be completed

failed

domain renewal

domain transfered

Domain is not being canceled manually - can not mark it as complete with manual cancelation. Domain Status is Canceled.

cname

domain stuck in long running

post upgrade PBA 6.0.1 - all orders stuck on status provisioning

domain name

domain transfer failed

aps node is not found

order

long running

FTP access

Table Gate Link doesn't contain row with id 2387879

cancellation order

DNS update was failed

Domian stuck

-

domain transfer completed in opensrs but failing in BA

provisioning failure

logicboxes .org transfer

transfer

orders

email hosting without active domain subscription

caea8340e2d186a540518d08602aa065 198398b282069eaf2d94a6af87dcb3ff 5356b422f65bdad1c3e9edca5d74a1ae 5b048d9bddf8048a00aba7e0bdadef37 2554725ed606193dd9bbce21365bed4e ac82ce33439a9c1feec4ff4f2f638899 e12cea1d47a3125d335d68e6d4e15e07 956c448bddc7e1f3585373687602379f 6f1456866eed87488c0f02b298a741c0

Email subscription for changes to this article
Save as PDF