Main Page/Provisioning/AAPT DSL Provisioning Errors - Revision history

Dcowan at 05:59, 12 September 2018

2018-09-12T05:59:19Z

Rlusher at 06:19, 8 May 2017

2017-05-08T06:19:34Z

Tyates at 00:13, 10 December 2014

2014-12-10T00:13:49Z

Rlusher: /* Common List of errors and actions to take */

2014-11-18T22:18:34Z

‎Common List of errors and actions to take

Rlusher at 22:15, 18 November 2014

2014-11-18T22:15:18Z

Rlusher: /* Common List of errors and actions to take */

2014-11-18T22:13:32Z

‎Common List of errors and actions to take

Rlusher: /* Common List of errors and actions to take */

2014-11-12T04:38:30Z

‎Common List of errors and actions to take

Rlusher: /* Common List of errors and actions to take */

2014-11-12T04:30:42Z

‎Common List of errors and actions to take

Rlusher: /* Common List of errors and actions to take */

2014-06-20T07:48:24Z

‎Common List of errors and actions to take

Rlusher: /* Common List of errors and actions to take */

2014-06-20T07:46:50Z

‎Common List of errors and actions to take

@@ Line 95: / Line 95: @@
 * <b> Could not Find AAPT response object - was this service ordered via Cumulus? </b>.  This error occurs during cancellation.  If the service in Emersion has been manually activated during the course of provisioning, or was, for example, imported in an Active state, or was created via any other method other than normal provisioning, then this error will occur.  It occurs because when an order is submitted to AAPT, they send back a response with an Integration Reference ID.  If AAPT has not responded to us properly, or there was some other error, we don't get this ID.  If the service is manually activated, billing begins without the Reference ID in our system.  This same reference ID is used to cancel the service when talking to AAPT during cancellation stage.  Therefore if the ID is not there, cancellations won't work.  If you get this error and you need to cancel, you will have no choice but to finish the cancellation via manual provisioning.
-* <b>  Request failed, message was: cvc-pattern-valid: Value '0407xxxxxx' is not facet-valid with respect to pattern '((0)[2,3,7,8][0-9]{8})|((13)\d{4})|((1300|1800)\d{6})' for type 'LandLineTelephoneNumber'</b>.  For more information regarding this error, click on the following link. [http://wiki.emersion.com.au/wiki/index.php/Provisioning/AAPT_Error_Landline_Telephone_Number Provisioning Error Landline Telephone Number]
+* <b>  Request failed, message was: cvc-pattern-valid: Value '0407xxxxxx' is not facet-valid with respect to pattern '((0)[2,3,7,8][0-9]{8})|((13)\d{4})|((1300|1800)\d{6})' for type 'LandLineTelephoneNumber'</b>.  For more information regarding this error, click on the following link. [http://wiki.emersion.com/wiki/index.php/Provisioning/AAPT_Error_Landline_Telephone_Number Provisioning Error Landline Telephone Number]
 * <b>  FrontierLinkV2Service_enquireService - Request failed, message was: java.lang.OutOfMemoryError: Java heap space; nested exception is: java.lang.OutOfMemoryError: Java heap space - java.lang.OutOfMemoryError: Java heap space; nested exception is: java.lang.OutOfMemoryError: </b>  This is an error at AAPT's end.  If provisioning has halted, you can click retry provisioning which should reinitiate polling.  If you cannot retry, or repolling doesn't start again within a few hours, contact Emersion.

← Older revision		Revision as of 06:19, 8 May 2017
Line 104:		Line 104:

	*<b> FrontierLinkV2Service_newService - Request failed, message was: cvc-datatype-valid.1.2.1: is not a valid value for integer. - org.xml.sax.SAXParseException: cvc-datatype-valid.1.2.1 </b> This means that we have tried to send either a phone number, or a LocationID to AAPT to provision a service, however the service identifier against the subscription is not in the correct format, and cannot correctly represent a service identifier or phone number. If this error is received you should abort the subscription and reallocate the subscription with a correctly formatted service identifier (this will be required anyway to get a valid SQ result). If for whatever reason the service is already active in FrontierWeb, you should use manual provisioning to complete provisioning.		*<b> FrontierLinkV2Service_newService - Request failed, message was: cvc-datatype-valid.1.2.1: is not a valid value for integer. - org.xml.sax.SAXParseException: cvc-datatype-valid.1.2.1 </b> This means that we have tried to send either a phone number, or a LocationID to AAPT to provision a service, however the service identifier against the subscription is not in the correct format, and cannot correctly represent a service identifier or phone number. If this error is received you should abort the subscription and reallocate the subscription with a correctly formatted service identifier (this will be required anyway to get a valid SQ result). If for whatever reason the service is already active in FrontierWeb, you should use manual provisioning to complete provisioning.
		+
		+	* <b> FrontierLinkV2Service_newService - Request failed, message was: cvc-pattern-valid: Value '09111222' is not facet-valid with respect to pattern '((0\|[+]61)[2,3,4,7,8]\d{8})\|((1300\|1800)\d{6})\|((13)\d{4})\|((\+)\d)' for type 'AustralianTelephoneNumber'. - org.xml.sax.SAXParseException: cvc-pattern-valid: Value '09111222' is not facet-valid with respect to pattern '((0\|[+]61)[2,3,4,7,8]\d{8})\|((1300\|1800)\d{6})\|((13)\d{4})\|((\+)\d)' for type 'AustralianTelephoneNumber'. > File (FrontierLinkV2Service_newService_dd119256e9809239d66fa0fa95312485.log) </b>. Fix the phone number on the primary/billing contact and add the area code and retry provisioning.

← Older revision		Revision as of 00:13, 10 December 2014
Line 1:		Line 1:
−		+	{{DISPLAYTITLE:AAPT DSL and NBN Provisioning Errors}}
	== Common AAPT DSL and NBN Provisioning Errors and how to handle them ==		== Common AAPT DSL and NBN Provisioning Errors and how to handle them ==

@@ Line 81: / Line 81: @@
 * Access Method NBN/ Access Type NFAS
-<i> These attributes are set on the buy service plan at the top of the plan hierachy as pictured. </i>
+<i> These attributes are set on the buy service plan at the top of the plan hierachy as pictured. </i>. If you encounter this error you need to fix your plan, abort the service subscription and reallocate.
 [[File:2014-11-19_09_12_06-Cumulus_-_Packages_and_Plans_-_Management_-_Properties.png]]

@@ Line 81: / Line 81: @@
 * Access Method NBN/ Access Type NFAS
-These attributes are set on the buy service plan at the top of the plan hierachy as pictured.
+<i> These attributes are set on the buy service plan at the top of the plan hierachy as pictured. </i>
 [[File:2014-11-19_09_12_06-Cumulus_-_Packages_and_Plans_-_Management_-_Properties.png]]

← Older revision		Revision as of 22:13, 18 November 2014
Line 70:		Line 70:

	* The attributes from the Service Qualification must match the attributes against the plan chosen. If they do not the order will surely fail. If this is the case you should abort the subscription and reallocate, ensuring that the plan chosen has attributes that match the Service Qualification. If the Plan matches the SQ, and these kinds of errors are still received, contact Emersion and we will help facilitate communications with FrontierLink Support.		* The attributes from the Service Qualification must match the attributes against the plan chosen. If they do not the order will surely fail. If this is the case you should abort the subscription and reallocate, ensuring that the plan chosen has attributes that match the Service Qualification. If the Plan matches the SQ, and these kinds of errors are still received, contact Emersion and we will help facilitate communications with FrontierLink Support.
		+
		+	* <b> FrontierLinkService_newService - Request failed, message was: Error submitting order. - Access Type 'DSL-L2' can only be specified for Access Method 'Telstra L2IG'. </b>. You have configured your plan incorrectly. Certain access types can only be used together with certain access methods. Current AAPT rules permit the following:
		+
		+	* Access Method AAPT ADSL2+/ Access Type SSS
		+
		+	* Access Method iiNet ADSL2+/ Access Type SSS
		+
		+	* Access Method Telstra L2IG / Access Type DSL-L2
		+
		+	* Access Method NBN/ Access Type NFAS
		+
		+	These attributes are set on the buy service plan at the top of the plan hierachy as pictured.
		+
		+	[[File:2014-11-19_09_12_06-Cumulus_-_Packages_and_Plans_-_Management_-_Properties.png]]
		+
		+	<br />
		+	<br />
		+

	* <b> FrontierLinkService_newService - Request failed, message was: In Flight Order validation failed - A pending service order exists </b>. This error typically occurs when there was an issue with provisioning, and provisioning was resubmitted under the assumption that the order was never acknowledged by AAPT. In this case you will likely need to use manual provisioning to activate the order, once the service is marked as active in FrontierWeb.		* <b> FrontierLinkService_newService - Request failed, message was: In Flight Order validation failed - A pending service order exists </b>. This error typically occurs when there was an issue with provisioning, and provisioning was resubmitted under the assumption that the order was never acknowledged by AAPT. In this case you will likely need to use manual provisioning to activate the order, once the service is marked as active in FrontierWeb.

@@ Line 50: / Line 50: @@
 * <b> FrontierLinkService_newService - Request failed, message was: Error submitting order. - DSL Transfer Date must be in the past, and no more than 30 days in the past.</b>  You have set the Churn Authority date in the order to be either in the future, or more than 30 days in the past from when the order was submitted.  Check to see if the order is not already active in Frontier.  If it is, you will have to manually provision.  If it is not, you may abort the subscription and reallocate.
-* <b> FrontierLinkService_enquireService - Request failed, message was: Could not connect to host - 0 .</b>. This is a general networking error. It usually means the AAPT went down.  You can click retry provisioning.  If this error repeatedly reappears Contact Emersion with Service ID, the Service Identifier, the Account ID, and a screenshot.
+* <b> FrontierLinkService_enquireService - Request failed, message was: Could not connect to host - 0 .</b>. This is a general networking error. It usually means the AAPT went down.  You can click retry provisioning which in most cases will move things along.  If this error repeatedly reappears Contact Emersion with Service ID, the Service Identifier, the Account ID, and a screenshot.
 * <b> FrontierLinkService_newService - Request failed, message was: Error submitting order as the access speed is not available. - Access speed = Up to 20Mbps/1Mbps, did not pass for this orders access method. </b>.

← Older revision		Revision as of 07:48, 20 June 2014
Line 85:		Line 85:
	* <b> FrontierLinkV2Service_enquireService - Request failed, message was: Service Not Found - Multiple services found based on specified criteria - Services found: xxxx, xxxxx </b>. There are multiple orders in FrontierWeb for the same service service identifier/location identifier. Even if one is withdrawn and one is complete, AAPT will continue to return two results, preventing auto - activation in Emersion. You will need to manually provision to step around this.		* <b> FrontierLinkV2Service_enquireService - Request failed, message was: Service Not Found - Multiple services found based on specified criteria - Services found: xxxx, xxxxx </b>. There are multiple orders in FrontierWeb for the same service service identifier/location identifier. Even if one is withdrawn and one is complete, AAPT will continue to return two results, preventing auto - activation in Emersion. You will need to manually provision to step around this.

−	* <b> FrontierLinkV2Service_newService - Request failed, message was: cvc-datatype-valid.1.2.1: '' is not a valid value for 'integer'. - org.xml.sax.SAXParseException: cvc-datatype-valid.1.2.1: </b>. This means that we have tried to send either a phone number, or a LocationID to AAPT to provision a service, however the service identifier against the subscription is not in the correct format, and cannot correctly represent a service identifier or phone number. If this error is received you should abort the subscription and reallocate the subscription with a correctly formatted service identifier (this will be required anyway to get a valid SQ result). If for whatever reason the service is already active in FrontierWeb, you should use manual provisioning to complete provisioning.	+	*<b> FrontierLinkV2Service_newService - Request failed, message was: cvc-datatype-valid.1.2.1: is not a valid value for integer. - org.xml.sax.SAXParseException: cvc-datatype-valid.1.2.1 </b> This means that we have tried to send either a phone number, or a LocationID to AAPT to provision a service, however the service identifier against the subscription is not in the correct format, and cannot correctly represent a service identifier or phone number. If this error is received you should abort the subscription and reallocate the subscription with a correctly formatted service identifier (this will be required anyway to get a valid SQ result). If for whatever reason the service is already active in FrontierWeb, you should use manual provisioning to complete provisioning.

← Older revision		Revision as of 07:46, 20 June 2014
Line 84:		Line 84:

	* <b> FrontierLinkV2Service_enquireService - Request failed, message was: Service Not Found - Multiple services found based on specified criteria - Services found: xxxx, xxxxx </b>. There are multiple orders in FrontierWeb for the same service service identifier/location identifier. Even if one is withdrawn and one is complete, AAPT will continue to return two results, preventing auto - activation in Emersion. You will need to manually provision to step around this.		* <b> FrontierLinkV2Service_enquireService - Request failed, message was: Service Not Found - Multiple services found based on specified criteria - Services found: xxxx, xxxxx </b>. There are multiple orders in FrontierWeb for the same service service identifier/location identifier. Even if one is withdrawn and one is complete, AAPT will continue to return two results, preventing auto - activation in Emersion. You will need to manually provision to step around this.
		+
		+	* <b> FrontierLinkV2Service_newService - Request failed, message was: cvc-datatype-valid.1.2.1: '' is not a valid value for 'integer'. - org.xml.sax.SAXParseException: cvc-datatype-valid.1.2.1: </b>. This means that we have tried to send either a phone number, or a LocationID to AAPT to provision a service, however the service identifier against the subscription is not in the correct format, and cannot correctly represent a service identifier or phone number. If this error is received you should abort the subscription and reallocate the subscription with a correctly formatted service identifier (this will be required anyway to get a valid SQ result). If for whatever reason the service is already active in FrontierWeb, you should use manual provisioning to complete provisioning.