Fatal Errors

When an operation fails, an error response will be provided. This includes an error code and a text message. The <response> element will contain the three elements:

• A <result> element containing the EPP error code. The codes used by our EPP server are described here.
  
• A <resData> element containing a <namespace:failData> element. The <failData> elements are described below.
• A <trID> element.

<domain:failData> element

The <domain:failData> element contains the following two sub-elements:

• A <domain:name> element giving the domain name concerned.
• A <domain:reason> element giving the reason for rejection of the request. This contains an automaton error message and contains an automaton error code (different to the EPP error code).
  

<account:failData> element

The <account:failData> element will be returned when <account:info> and <account:update> requests fail and will contain the following two sub-elements:

• An <account:roid> element giving the account concerned.
• An <account:reason> element giving the reason for rejection of the request. This contains an automaton error message and contains an automaton error code (different to the EPP error code).
  

<contact:failData> element

The <contact:failData> element will be returned when <contact:info> and <contact:update> requests fail and will contain the following two sub-elements:

• A <contact:roid> element giving the contact concerned.
• A <contact:reason> element giving the reason for rejection of the request. This contains an automaton error message and contains an automaton error code (different to the EPP error code).
  

<ns:failData> element

The <ns:failData> element will be returned when <ns:info> and <ns:update> requests fail and will contain the following two sub-elements:

• A <ns:roid> element giving the contact concerned.
• A <ns:reason> element giving the reason for rejection of the request. This contains an automaton error message and contains an automaton error code (different to the EPP error code).

Example of an error message

    <?xml version="1.0" encoding="UTF-8" standalone="no"?>
    <epp xmlns="urn:ietf:params:xml:ns:epp-1.0"
          xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
          xsi:schemaLocation="http://www.nominet.org.uk/epp/xml/epp-1.0 epp-1.0.xsd">
      <response>
        <result code="2201">
          <msg>Authorization error</msg>
        </result>
        <resData>
          <domain:failData
            xmlns:domain="http://www.nominet.org.uk/epp/xml/nom-domain-1.0"
            xsi:schemaLocation="http://www.nominet.org.uk/epp/xml/nom-domain-1.0
            nom-domain-1.0.xsd">
            <domain:name>example.co.uk</domain:name>
            <domain:reason>V013 The account name field cannot be modified</domain:reason>
          </domain:failData>
        </resData>
        <trID>
          <clTRID>EPP-XYZ-84535</clTRID>
        </trID>
      </response>
    </epp>

Warnings

Warnings are given if a non-fatal error occurred. Warning messages can be appended to successful operations. Even though your operation is successful a non-fatal error means there is an issue that could prevent you from performing future operations. In addition to the other content the <response> element will contain an <extension> element before the <trID> element containing one of four possible <warning> elements described below.

<domain:warning> element

The <domain:warning> element describes the error that has occurred and will contain the automaton error code.

<account:warning> element

The <account:warning> element will be returned when there has been a non-fatal error while processing an <account:info> or <account:update> request and will contain the automaton non-fatal error message.

<contact:warning> element

The <contact:warning> element will be returned when there has been a non-fatal error while processing an <contact:info> or <contact:update> request and will contain the automaton non-fatal error message.

<ns:warning> element

The <ns:warning> element will be returned when there has been a non-fatal error while processing an <ns:info> or <ns:update> request and will contain the automaton non-fatal error message.

Example of a warning message

    <?xml version="1.0" encoding="UTF-8" standalone="no"?>
    <epp xmlns="urn:ietf:params:xml:ns:epp-1.0"
          xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
          xsi:schemaLocation="http://www.nominet.org.uk/epp/xml/epp-1.0 epp-1.0.xsd">
      <response>
        <result code="1000">
          <msg>Command completed successfully</msg>
        </result>
        <resData>
          <domain:creData
            xmlns:domain="http://www.nominet.org.uk/epp/xml/nom-domain-1.0"
            xmlns:account="http://www.nominet.org.uk/epp/xml/nom-account-1.0"
            xmlns:contact="http://www.nominet.org.uk/epp/xml/nom-contact-1.0"
            xmlns:ns="http://www.nominet.org.uk/epp/xml/nom-ns-1.0"
            xsi:schemaLocation="http://www.nominet.org.uk/epp/xml/nom-domain-1.0
            nom-domain-1.0.xsd">
            <domain:name>example.co.uk</domain:name>
            <domain:account>
              <account:creData>
                <account:roid>100167-UK</account:roid>
                <account:name>New Multimedia</account:name>
                <account:contact type="admin" order="1">
                  <contact:creData>
                    <contact:roid>C100283-UK</contact:roid>
                    <contact:name>Nick Smith</contact:name>
                  </contact:creData>
                </account:contact>
                <account:contact type="admin" order="2">
                  <contact:creData>
                    <contact:roid>C100284-UK</contact:roid>
                    <contact:name>James Smith</contact:name>
                  </contact:creData>
                </account:contact>
                <account:contact type="admin" order="3">
                  <contact:creData>
                    <contact:roid>C100285-UK</contact:roid>
                    <contact:name>Mr Smith</contact:name>
                  </contact:creData>
                </account:contact>
              </account:creData>
            </domain:account>
            <domain:ns>
              <ns:creData>
                <ns:roid>NS100160-UK</ns:roid>
                <ns:name>ns1.bb.co.uk</ns:name>
                <ns:crDate>2008-07-09T16:09:33</ns:crDate>
              </ns:creData>
              <ns:creData>
                <ns:roid>NS100161-UK</ns:roid>
                <ns:name>ns0.bb.co.uk</ns:name>
                <ns:crDate>2008-07-09T16:09:33</ns:crDate>
              </ns:creData>
            </domain:ns>
            <domain:crDate>2008-05-09T14:11:18</domain:crDate>
            <domain:exDate>2010-05-09T14:11:18</domain:exDate>
          </domain:creData>
        </resData>
        <extension>
          <domain:warning
          xmlns:domain="http://www.nominet.org.uk/epp/xml/nom-domain-1.0"
          xsi:schemaLocation="http://www.nominet.org.uk/epp/xml/nom-domain-1.0
          nom-domain-1.0.xsd">
            You are within 20% of your credit limit. The calculation takes into
    account your current outstanding balance, plus any new registrations and    
    renewals which have been made during the current month.
    If you anticipate that you will exceed your current credit limit before you
    make your next payment, please contact your Credit Controller to place an amount
    of money on your account or to pay any overdue invoices. This will avoid
    the suspension of your tag(s).
          </domain:warning>
        </extension>
        <trID>
          <clTRID>EPP-XYZ-84535</clTRID>
          <svTRID>100605</svTRID>
        </trID>
      </response>
    </epp>