CenturyLink Spirit of Service
Qwest.com | About Qwest  
Products and Services Customer Service Manage My Account
Cable (MSOs) | ILECs/ICOs | IXCs| International | ISPs/ESPs | National Service Resellers | Wireless | View All Products & Services
Wholesale: Operation Support Systems  
Operation
Support Systems
OSS Overview
OSS Production Support
ASR Ordering Systems
BDT Differences List
CEMR
Directory Listings
IMA XML
IMA GUI
IMA Error Messages
MEDIACC-EBTA
Online Dispute Management
PIC/LPIC Verification
Qwest Control
Qwest IP Network Statistics
Q.pricer
Regional Subscription System (RSS) for IXCs
IMA Error Messages
April 10, 2006

Contact: itdocs@qwest.com

Use this table to find explanations of error messages in IMA. Most of the error messages tell you what you need to do. For some of the more difficult error messages, however, the table expands on what has gone wrong and what you need to do next.

To find an error message, search for the first word in the error message (including words such as "an" and "the"). If the error message begins with a variable—for example, <activity type> or XXXX—search for the next word in the error message.

Click on any letter below to jump to the section containing the error message you want to look up.



Error message

Explanation or solution

I Back to Top

i.  MIL must be a 3-digit numeric.
ii.  MIL must be greater than 0.
iii. MIL must be alphanumeric.

MIL must always be a number greater than 0. In the Central Region, it must be one to three digits (1 to 999). In the Western Region it must be three digits (001 to 999).

If <USOC identifier> USOC is supplied then following FID(s) <list of FID identifiers> should be floated. Please correct and resubmit

The LSR has an incorrect combination of USOC and FID values.

Replace the incorrect USOC or FID and try again to submit the LSR.

If LSR.ACT is T, LACT should equal N or Z

 

If removing one of the following <the number of USOCs> USOCs: <a list of master USOCs> must also remove <N2W or NWT>

If you remove master USOCs from a residential account, you must also remove the N2W or NWT USOC.

If the First Directory Listing’s RTY is LML and the LACT is O, the Second Directory Listing must be the corresponding RTY of LML with an LACT of I.  
IMA cannot identify the state. Check the NPA_NXX you entered and correct it if necessary.
If the NPA_NXX is correct, select the USOC from the feature list.
IMA doesn’t recognize the NPA-NXX you entered. Check the NPA-NXX and correct it if necessary. If the NPA-NXX is correct, select the USOC from the FEATURE list or try again later.

IMA is not able to find CFA data for <>

 

IMA not able to retrieve the following CFAs: <the CABNM value> <the FIRST UNIT value> to <the LAST UNIT value>

The CFA information you selected is unavailable.(The message appears for each row that IMA was not able to retrieve.)

IMA unable to retrieve all CFA data requested. Please request the remaining data from <the FIRST UNIT value> to <the LAST UNIT value>

IMA couldn't retrieve all the CFA units in the range you specified. Enter a larger value for the FIRST UNIT and/or a smaller value for the LAST UNIT so as to define a smaller range.

IMP TEL NO cannot be populated when pager is populated.

 

IMP TEL NO is mandatory when IMPCON is populated.

 

IMPCON required when ACT is C

 

IMPCON required when ACT is N, V, C, T or M

 

IMPCONPAGER / IMPCONTELNO required (not both) when IMPCON is populated

 

IMPCONTELNO required when IMPCON is populated and ACT is V or Z for LNP

 

In "From" date, invalid date value, 'mm', 'dd', and 'yyyy' must be digits

 

In "From" date, invalid day of month - must be 01 to 30

 

In "From" date, invalid month of year - must be 01 to 12

 

In "To" date, invalid date value, 'mm', 'dd', and 'yyyy' must be digits

 

In "To" date, invalid day of month - must be 01 to 30

 

In "To" date, invalid month of year - must be 01 to 12

 

INIT is mandatory and must be filled.

 

INQ FASG FAILED: L400-050: THE REQUESTED FACILITY ADDRESS CANNOT BE FOUND. CHECK YOUR INPUT

 

Installation type invalid

You aren't authorized to order this type of installation.

Order an installation that you are authorized to order. (Refer to your contract for authorized USOCs.)

Insufficient number of lines available for selected appointment (<# of lines>)

 

Internal Comment:  <> contains too many characters <number of characters> (max = 255).

 

Internet Access Problem – A problem occurred with System Permissions. RRRRR  RRRRR Check the policy file to ensure the following lines have been added: RRRRR  RRRRR permission java.util.PropertyPermission “javax.net.ss1.*”, ”read,write”; RRRRR  RRRRR permission java.util.PropertyPermission “user.home”, ”read”;

See the IMA Connection Guide.

<USOC> invalid when FA is N. Use FVJ, FBJ, FDJ instead.

 

Invalid ALI Code.

Validate the ALI code on the request against the CMD.

Invalid ALT IMPCON TEL NO. Valid value: xxx-xxx-xxxx or xxx-xxx-xxxx-xxxx, or without dashes (x is any number 0-9).

 

Invalid BTN.

Validate the BTN on the request against CMD.

Invalid CFA - CABNM required

 

Invalid CFA format; Consecutive Unit will Exceed 5 Digits.

Do not enter 99999 in the Unit Number for a four-wire unbundled loop.

Invalid CFN FID Detail format found. Valid CFN FID Detail format(s): /<CFN or CFNB or CFND> nnn nnn-nnnn

Enter FID detail format in the format specified in the error message.

Invalid characters in EWORD: Valid values are A through Y excluding Q, a through y excluding q, 0 through 9

 

Invalid CLLI

 

Invalid CMS ID for Account Number.

Validate the CMS ID on the request against CMD.

Invalid combination of MS, TOS, NC, and NCI

 

Invalid Common Block for Account Number.

Validate the common block ID (CB) on the request against CMD.

Invalid CVD

One or more of the numbers in the date you entered is invalid—for example, 2003/13/00. 

Invalid data was entered in the CFA and/or ACNA fields.

There are errors in one or more of the following fields: ACNA, LOCA, LOCZ,: CABNM, FIRST UNIT, and LAST UNIT. Check those fields, correct them where necessary, and try again.

Invalid Date, format should be in the form MM/DD/CCYY where 'MM' is month between 1 & 12 'DD' is date between 1 & 31 and 'CCYY' is 4 digit years

 

Invalid DPA Code - no name match.

Validate the DPA code on the request against CMD.

Invalid DSGCON EMAIL. Please enter a valid email address.

 

Invalid DSGCON FAX NO. Valid value: xxx-xxx-xxxx or xxx-xxx-xxxx-xxxx, or without dashes (x is any number 0-9).

 

Invalid DSGCON ZIP. Valid value: numbers.

 

Invalid FID and/or FID Data entered --/<invalid value>-- Please correct and resubmit.

For the product and activity you selected, the FID in the FEATURE DETAIL field is invalid.

Make sure that you have selected the product and activity you want. If you have, remove the FID or enter a new FID in the FEATURE DETAIL field on the Features tab. Follow the guidelines in the Qwest’s USOC/FID Finder and LSOG for the form in question.

Invalid HID Code.

Validate the HID on the request against CMD.

Invalid HTN format when HNTYP is 2, 3, 7, 16 or 17

 

Invalid HTSEQ format when HNTYP is 2, 3, 7, 16 or 17

 

Invalid IMPCON TEL NO. Valid value: xxx-xxx-xxxx or xxx-xxx-xxxx-xxxx, or without dashes (x is any number 0-9).

 

Invalid LOC Code - no address match.

Validate the LOC code on the request against CMD.

Invalid LPIC entered for <TN> for the wire center and Type of Service requested

The information in the LPIC field is invalid for the wire center and type of service you requested.

Re-enter the information in the LPIC field. Valid values are NONE, DFLT, or numeric codes other than 0000.

Invalid LSR ID: Should be a numeric value

 

Invalid MIL Code - no address match.

Validate the MIL code on the request against CMD.

Invalid MSS FID Detail format found.  Valid MSS FID Detail formats(s): /MSS *xxxxxx MSSGRP.xxxx, or /MSS *xxxxx MSSGRP.xxxx, or /MSS *xxxx MSSGRP.xxxx

Enter the feature detail in the format specified in the error message.

Invalid NC Code for unbundled product.

If Appointment NC CODE has an entry, it must exist on the IMA_PRODUCT_ NCCODES table for this product.

Use an NC code valid for the product (Unbundled Loop or Loop with Number Portability). See Tech Pub #77384 if further clarification is required. (http://www.qwest.com/techpub/)

Invalid NPA-NXX/State combination: <NPA-NXX/state>

There are errors in the NPA-NXX and/or the State you entered. Check that information, correct it where necessary, and try again.

Invalid PIC entered for <TN> for the wire center and Type of Service requested

You need to enter a valid value in the PIC field—NONE, DFLT, or four numbers other than 0000.

Invalid RCYC FID Detail format found <invalid format> Valid RCYC FID Detail format(s): /RCYC n

Enter FID detail format in the format specified in the error message.

Invalid SH1 FID Detail format found. Valid SH1 FID Detail formats(s): /SH1 nnn nnn-nnnn, or /SH1 nnn nnn-nnnn nn, or /SH1 nnn nnn-nnnn nnn

Enter FID detail format in the format specified in the error message.

Invalid TN for the End User

 

Invalid TN format <>

The format of the TN you added to the WTN list is invalid.

Re-enter the TN in the correct format: AAA-AAA-AAA-aaaa with ‘A’ requiring Alpha/ Numeric and ‘a’ Alpha/ Numeric optional

Invalid TOS for Unbundled Appointment <>

For unbundled appointments (TXTYP = “U”), the first character in the TOS field can't be 4 - PAL/Coin.

Invalid type of Number Portability requested

The central office you specified does not support this type of number portability.

Choose another type of Number Portability. If you chose INP, choose LNP. If you chose LNP, choose INP. If neither works, contact the IMA Help Desk.

Invalid user data

 

Invalid USOC supplied for Business account <>

 

Invalid USOC supplied for Residential account <>

 

Invalid USOC used in FEATURE <feature identifier>

 

Invalid USOCs - problems with Validity, Resellability, State or Contract: <list of invalid USOCs>

 

Invalid WO FID Detail format found. Valid WO FID Detail format(s): /WO nnn nnn-nnnn

Enter FID detail format in the format specified in the error message.

Invalid XLI Code - no address match <>

Validate the XLI code on the request against CMD

IPG could not be determined. Please verify CKR <NPA>-<NXX>-<XXXX>

 

<XXX> is not a valid FID.

Invalid FID entered in Feature Detail.

Enter a FID that's valid for your company and contract area.

IWJQ required when IWJK is populated

 

J Back to Top

JACKS not allowed when TXTYP is C

 

JS_ERR_112-1v:ZIPCODE translates into more than (1) SAGA

 

JS_ERR_112v:ZIPCODE could not be translated into a SAGA

 

L Back to Top

LACT cannot be D when RTY is LML

 

LACT cannot be N when LSR.ACT is V and RTY is LML

 

LACT cannot be N when RTY is LML unless LSR.ACT is N or T

 

LACT I or O has no corresponding DL form

 

LACT is mandatory and must be filled.

 

LACT must be I, O or Z when LSR.ACT is C or T and RTY is LML

 

LACT must be N when ACT is V and MI is C or D. See the FBDL User's Guide, chapter 3

LACT must be N when LSR.ACT is N

 

LACT must be N, D, I or O when LSR.ACT is C

 

LACT required

 

LALOC required when LASN is populated

 

LANO is required when LAPR or LASF is populated

 

LAPR prohibited when ADI is "O"

 

LASD prohibited when ADI is "O"

 

LASD prohibited when LASN is not populated

 

LASF prohibited when ADI is "O"

 

LASF prohibited when LANO is not populated

 

LASN is required when LASD, LATH, LASS, or LANO is populated

 

LASN is required when LASD, LATH, or LASS is populated

 

LASN prohibited when ADI is "O"

 

LASS prohibited when LASN is not populated

 

LASTUNIT required when CABNM or FIRSTUNIT is populated

 

LATH prohibited when ADI is "O"

 

LATH prohibited when LASN is not populated

 

LCC FID is required when feature is <feature identifier>

 

LCON required

 

LCON required when ACT is <activity type(s)>

 

LD1 must be populated when LV1 is populated

 

LD2 must be populated when LV2 is populated

 

LD3 must be populated when LV3 is populated

 

LEFV not available in this state

You are trying to add an LEF for an account in one of the states where LEF is not offered.

Line does not qualify for DSL.  Check Loop Qual Tool

If possible, remove the DSL feature and resubmit the request. Note: For Shared Loop service, you cannot remove the DSL feature, so you cannot resubmit the request.

Line has a bad length. Length must be at least 4.

 

Line is mandatory and must be filled.

 

Lines associated with LSR (<##>) exceed lines available for selected appointment (<# of lines>)

 

LINESHAREDTN required when ACT is C

 

Listing already exists for LTN<###-###-####>.  

 

 
Listing does not exist for AN<###-###-####>.  
Listing does not exist for LTN<###-###-####>.  

LNA is not applicable when ACT is <>

 

LNA must be <>

 

LNA must be <> when ACT is <>

Verify that LNA has one of the indicated values for the indicated values of ACT.

 

LNA must be C when ACT is C and primary location is impacted

 

LNA must be C when ACT is C and secondary location is impacted

 

LNA must be D or V when CHC is B

 

LNA must be N when ACT is T and secondary location is part of outside move

 

LNA must equal ACT

 

LNA required when ACT is <>

 

LNLN invalid - < LNLN > must be followed by an alpha character

 

LNLN is mandatory and must be filled.

 

LNLN may not start with a %, . or /

 

LOC must be a 4-digit numeric.LOC must be greater than 0.

Make sure that the LOC code is a four-digit number greater than 0.

LOCA Address Validation is not an EXACTMATCH

 

LOCA is mandatory and must be filled.

 

LOCABCONN is mandatory and must be filled.

 

Local Service Office has a bad length. Length must be 6.

 

Local Service Office is mandatory and must be filled.

You need to fill in the LSO (Local Service Office) field.

Location A has a bad length. Length must be at least 8.

 

Location A is mandatory and must be filled.

 

LOCATION ACCESS SECTION required (2 sections)

 

LOCATION ACCESS SECTIONs(<the number of location access sections>) must match LOCQTY(<the number of locations>)

 

Location Z has a bad length. Length must be at least 8.

 

LOCNUM in Secondary Location must have a matching LOCNUM in Secondary Location Service Details.

REQTYPE = KB and the Secondary Location Section of the RPL contains a LOCNUM and does not contain a corresponding LOCNUM entry in the Secondary Location Details Section.

Ensure the Secondary Location Section of the RPL contains a LOCNUM and contains a corresponding LOCNUM entry in the Secondary Location Details Section.

LOCNUM must be 1 when ACT is N

 

LOCNUMs must be unique across all address location sections.

Make sure that each address location has a unique LOCNUM.

LOCQTY must be 2

 

LOCQTY required when ACT is <activity type>

 

LOCZ Address Validation is not an EXACTMATCH

 

LOCZ is mandatory and must be filled.

 

Loop does not qualify for DSL speed requested

 

Loop does not qualify for Qwest DSL Service: Pair gain. The telephone number entered for the Qwest DSL service does not qualify at this time. If you would like to have the telephone number periodically re-qualified, ...


Loop Splitting is only valid on an UBL account with an NC code of LX-N or LXR-

 

LOPOTSSPLIT is mandatory and must be filled.

 

Low CABLE CONNECTION/ POTS SPLITTER <insert meet point> and/or Hi CABLE CONNECTION/POTS SPLITTER <insert meet point> do not exist (LO meet point or HI meet point do not exist)

Verify that Hi and/or Lo cable connection/POTS splitter are valid and try again.

LPIC required when ACT is <activity type(s)>

 

LPIC required when ACT is C and LNA is not C nor P

 

LQDB: Query failed(LQI could not get the primary npa/nxx for the loop.).

 

LQDB: Query failed. Unable to complete transaction.

 

LSCP is not allowed when ACT is B

 

LSO is mandatory and must be filled.

 

LSO not valid

Enter a primary or secondary LSO.

LSO required when ACT is W, V or C

 

LSO required when APTCON is not populated and LNA is N

 

LSO required when SCATEG is P or I

 

LSR already exists with the same CCNA|CC/PON.  VER and SUP must be populated.

Someone from your company has already submitted an LSR with the same PON. Assign a different PON. Or if you're submitting a supplemental LSR, assign a new VER.

LSR being processed. No saves or submissions allowed during processing activity.

You've tried to save or submit an LSR with the same PON as one that's already being processed. Check the PON and correct it if necessary. Or submit a supplemental LSR.

LSR contains non-override errors. Please correct and re-submit

 

LSR requested does not belong to <CCNA Value>

 

LSR requesting change to DSL, but no change to DSL USOC or MEGACENTNM

Change the DSL speed, contract interval length, or ISP.Then try again to submit the request:

LSR requests work on disconnected account.

You are trying to submit an LSR for an account that has been disconnected. Check the AN and correct it if necessary. If the AN you entered is correct, submit a new LSR for a new account.

LSR Search Criteria requires either a CORP ID/PON or an LSR ID.

 

LSR successfully saved to IMA with reject override. LSR requires manual handling.

 

LSR Requested does not belong to <CCNA Value> The LSR you requested does not belong to one of your owner CLECs.
LSR/BRC already exists with same CCNA/PON. For LSRs, if Supplemental is intended, VER and SUP must be populated. For BRCs, Supplementals are not allowed. Someone from your company has already submitted an LSR or BRC with the same PON. Assign a different PON. Or if you're submitting a supplemental LSR, assign a new VER.

LST required when ACT is V or C

 

LST required when TXTYP is C

 

LSTR:Unable to process request, no Letter of Authorization.

You need to obtain a letter of authorization for this request.

LTC required when LNA is T and ACT is T,V or Z

 

LTEXT required when DOI greater than zero and LALOC not populated

 

LTN has a bad length. Length must be 12.

 

LTN is mandatory and must be filled.

 

LTN must match LSR.AN when RTY = LML and LACT is I or Z

 

LTN prohibited when NSTN is populated

 

LTN required when RTY is LAL and NSTN is not populated

 

LTXTY required when DOI is greater than zero except when listing is an address indent

 

LTXTY required when LTEXT is populated

 

LTXTY required when LTEXT is populated unless LACT  equal to D or Z

 

LTY must not be 3 when RTY is LAC, LAM, LAU, LCM, LCR, LEM, LUL, LXL, or when first char of RTY is F

 

LTY must not be 3 when RTY is LAC, LCR, LAS, LAU, LXL or when first char of RTY is F

 

LV1 must be populated when LD1 is populated

 

LV2 must be populated when LD2 is populated

 

LV3 must be populated when LD3 is populated

 

M Back to Top

MANUALIND - REMARKS must be populated when MANUALIND is Y

 

MANUANIND must be Y when NPI is populate

 

Message[<message number>]=<> Fatal :: Gateway Error

IMA can't currently provide the information you requested. Try again later.

Message[<message number>]=CLR099I FIND COMPLETED THIS IS THE LAST DISTRIBUTION PAGE

No DLR is available for the circuit ID you specified.

Message[<message number>]=Communications failure (dac / rpc)

 

Message[<message number>]=ERROR: <>

 

Message[<message number>]=ExcSupportCsrLe gacyFatalError : File=[SupFnsInterface.cpp], Line#=[748] Received Error From FnsGateway (6.4.1.3) on message ResDupAccountList: E106 Account not found while resolving account on partial circ...

 

Message[<message number>]=FC error code: 20062 Valid PREMIS address - Address not in LFACS The requested address is in PREMIS - The request address is NOT in LFACS Issue service order with this address - Use correct remarks <ELLIPSE>

 

Message[<message number>]=INPUT ERROR(S):

 

Message[<message number>]=Invalid NPA NNX. The NPA NNX of the input TN must map to a wire center in PREMIS.

 

Message[<message number>]=Invalid unit range (firstUnit to lastUnit) expect (firstUnit <= lastUnit), received (101 to 23)

 

Message[<message number>]=Invalid unit range va<ELLIPSE>

 

Message[<message number>]=LSO not valid

 

Message[<message number>]=NO AVAILABLE NUMBERS SATISFY ALL THE VALID INPUT PARAMETERS.

 

Message[<message number>]=No exact street name/descriptive name matched in PREMIS. No partial match found.

 

Message[<message number>]=Screen (RDLOC) : Field (location->code->clliCode) : LOC504E FIND FAILED LOCATION CODE NOT FOUND

 

Message[<message number>]=Screen (RDLOC) : Field (location->code->clliCode) : Owner could not be established.

 

Message[<message number>]=TCB302I FIND DID NOT PROCESS LOGICAL ERROR RANGE ERROR - F1 GTR THAN F2

 

Message[<message number>]=THE QUANTITY OF NUMBERS SELECTED <quantity selected> DOES NOT MATCH THE QUANTITY REQUESTED <quantity requested> BECAUSE THERE WERE INSUFFICIENT AVAILABLE NUMBERS TO MEET THE REQUEST.

 

Message[<message number>]=TN not found.

 

Message[<message number>]=Verify Descriptive Address entry.

 

Message[<message number>]=WAS985E FIND FAILED CKT-ID NOT FOUND IN C1/INV

 

MI field indicates Full Conversion, but only a portion of the lines on the account have been entered

Select A or B in the MI field or enter all lines on the account.

MI field indicates Partial Conversion, but all lines on the account have been entered

Select C or D in the MI field or enter only a portion of the lines on the account.

MI must be C or D when ACT is W

Select C or D in the MI field, or use a value for the ACT field other than W.

MI required when ACT is <V or Z>

Select the appropriate value in the MI field.

Must have the current line level USOC with FA of ‘V’ or ‘T’.

Specify all line level USOCs.

Must have the current line level USOC with FA of V or T when ACT is V or Z, and LNA is V

 



Last Update: April 10, 2006

 

Legal Notices | Privacy | Wholesale Legal Notice
Careers at Qwest | Information for Disabled Customers with Disabilities | Servicio al Cliente en Español | Tariffs
Copyright © 2010 CenturyLink Inc. | All Rights Reserved