Difference between revisions of "Main Page/Provisioning/AAPT DSL Provisioning Errors"
From Emersion
(→Common AAPT DSL Provisioning Errors and how to handle them) |
(→Common List of errors and actions to take) |
||
| Line 12: | Line 12: | ||
== Common List of errors and actions to take == | == Common List of errors and actions to take == | ||
| + | * <b> Succesfully enquired on status of service provisioning for 0738222248, the provisioning is still in a pending state. </b> While a service is provisioning, you'll see this message appear about 4 to 5 times a day. If the last log states this and it has been sometime since the polling request, contact Emersion Support. Provide the "Service ID", the "Service Identifier", the Account Number and a screenshot. | ||
| − | * <b> FrontierLinkService_enquireService - Request failed, message was: 0 > File (FrontierLinkService_enquireService_beceeeb3a915faa95a05ff726bf6ff98.log) </b> | + | * <b> 'FrontierLinkService_enquireService - Request failed, message was: Service Not Found - Service Number = 0296295729> File (FrontierLinkService_enquireService_2aba476c0d7f80c4bbfe292b3663db31.log)' </b>. A fairly common error. this means the order was submitted to AAPT, but they have subsequently withdrawn the error. Before taking any action, you need to find out why. |
| + | [[File:AAPT_Frontier_Screenshot.jpg]] | ||
| + | |||
| + | |||
| + | |||
| + | * <b> FrontierLinkService_enquireService - Request failed, message was: 0 > File (FrontierLinkService_enquireService_beceeeb3a915faa95a05ff726bf6ff98.log) </b>. This is an AAPT generated error. You can click the Retry Provisioning button as pictured in the screenshot above. If this button is not available, navigate to manual provisioning and "halt" provisioning, then click retry provisioning. | ||
| + | |||
| + | *<b> FrontierLinkService_newService - Request failed, message was: Unknown name value for enum class com.aapt.qualification.domain.ParameterKey: TELSTRA_DA_MLL_E_PARAMETER_KEY | ||
| + | > File (FrontierLinkService_newService_b5ea414f7de80da815a78ea66bb4d5e1.log) </b>. If this error is received, contact Emersion. | ||
Revision as of 10:45, 21 May 2014
Common AAPT DSL Provisioning Errors and how to handle them
This page describes common errors that may occur whilst attempting to provision DSL service for Broadband Connect L2, or Broadband Connect L3 service types. In all cases, if a service is still preactive your first reaction should not be go to manual provisioning straight away. You should navigate to the provisioning logs to investigate what is going on. The provisioning logs can be found against the service subscription as pictured.
Common List of errors and actions to take
- Succesfully enquired on status of service provisioning for 0738222248, the provisioning is still in a pending state. While a service is provisioning, you'll see this message appear about 4 to 5 times a day. If the last log states this and it has been sometime since the polling request, contact Emersion Support. Provide the "Service ID", the "Service Identifier", the Account Number and a screenshot.
- 'FrontierLinkService_enquireService - Request failed, message was: Service Not Found - Service Number = 0296295729> File (FrontierLinkService_enquireService_2aba476c0d7f80c4bbfe292b3663db31.log)' . A fairly common error. this means the order was submitted to AAPT, but they have subsequently withdrawn the error. Before taking any action, you need to find out why.
- FrontierLinkService_enquireService - Request failed, message was: 0 > File (FrontierLinkService_enquireService_beceeeb3a915faa95a05ff726bf6ff98.log) . This is an AAPT generated error. You can click the Retry Provisioning button as pictured in the screenshot above. If this button is not available, navigate to manual provisioning and "halt" provisioning, then click retry provisioning.
- FrontierLinkService_newService - Request failed, message was: Unknown name value for enum class com.aapt.qualification.domain.ParameterKey: TELSTRA_DA_MLL_E_PARAMETER_KEY
> File (FrontierLinkService_newService_b5ea414f7de80da815a78ea66bb4d5e1.log) . If this error is received, contact Emersion.
