Difference between revisions of "Main Page/Provisioning/AAPT DSL Provisioning Errors"
From Emersion
(→Common AAPT DSL Provisioning Errors and how to handle them) |
(→Common AAPT DSL Provisioning Errors and how to handle them) |
||
| Line 8: | Line 8: | ||
[[File:Cumulus_-_Customers_-_Customer_List_-_Provisioning_Logs.jpg]] | [[File:Cumulus_-_Customers_-_Customer_List_-_Provisioning_Logs.jpg]] | ||
| + | |||
| + | |||
| + | == Common List of errors and actions to take == | ||
* <b> FrontierLinkService_enquireService - Request failed, message was: 0 > File (FrontierLinkService_enquireService_beceeeb3a915faa95a05ff726bf6ff98.log) </b> | * <b> FrontierLinkService_enquireService - Request failed, message was: 0 > File (FrontierLinkService_enquireService_beceeeb3a915faa95a05ff726bf6ff98.log) </b> | ||
Revision as of 10:36, 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
- FrontierLinkService_enquireService - Request failed, message was: 0 > File (FrontierLinkService_enquireService_beceeeb3a915faa95a05ff726bf6ff98.log)
