 |
IMA Error Messages
October 20, 2008
Contact: imadocs@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 |
| D |
|
|
DACT must be D when LACT
is D and DDQTY is 1 |
|
|
DACT must be D, I, or
Z when LACT is Z and DDQTY is 1 |
|
|
DACT must be I or Z when
LACT is I and DDQTY is 1 |
|
|
DACT must be N when LACT
is N and DDQTY is 1 |
|
|
DACT must be O or Z when
LACT is O and DDQTY is 1 |
|
|
DATED has a bad length. Length must
be 10. |
|
|
DATED is mandatory and
must be filled. |
|
|
DATED <SPEC_DATE>
is not a date |
|
|
DATED should not succeed
<SPEC_DATE> |
|
|
dbFetchSpareLoop unable
to complete transaction. Please try later. |
|
|
DDALO prohibited when
DDASN is not populated |
|
|
DDANO required when DDAPR
or DDASF is populated |
|
|
DDASF prohibited when
DDANO is not populated |
|
|
DDASN required when DDASD,
DDATH, or DDASS is populated |
|
|
DDD is mandatory and
must be filled. |
|
|
DDD must equal Current
Date |
|
|
DDDO cannot be less than
or equal to the DDD. |
The date in the DDDO field must be later than the date
in the DDD field. |
|
DDDO cannot equal the
DDD |
|
|
DDDO cannot exceed 30
days from the DDD. |
The date in the DDDO field must be no more than 30 days
later than the date in the DDD field. |
|
DDDO must be greater
than DDD. |
The date in the DDDO field must be later than the date
in the DDD field. |
|
DDQTY must match the
number of occurrences of Delivery Address sections |
|
|
DEPT must be alphanumeric.
DEPT must be a minimum of four characters. |
DEPT must be 4-6 letters and/or numbers. |
|
Derived Call Forwarding
Busy USOC <requested USOC> unavailable for NM bus--use hunting
(plus Call Forwarding DA if needed). |
|
| DFDT invalid format, only
HHMM (Military Time) or 'XX' is valid |
In the DFDT field, either enter the time in 24-hour format
(0001–2359) or enter XX for an outside move for business or government
accounts |
|
DFDT required when ACT
is <> and CHC is Y |
|
|
DFDT required when ACT
is V or Z |
|
|
DFDT required when CHC
is Y and ACT is C |
|
|
DIRNAME required when
NSTN is populated |
|
|
DIRNAME required when
RTY first char is F |
|
|
DISCNBR required when
REFNUM is populated |
|
| Disconnect listing AN <###-###-####>
request already exists. |
|
|
Display message in the
format it is returned from FnS. |
You specified an LSO that is valid in two or more wire centers.
Contact the service center and have the meet point
validated by the service representative. |
| DL form is not allowed without <ProductFormName> form. |
|
|
DLIS: Error connecting
to server |
|
|
DNUM prohibited when
DISCNBR is not populated |
|
|
DOI must be 0 when STYC
is SH, SL, or CH |
|
|
DOI must be 1 or 2 when
STYC is SI |
|
|
DOI must be 1 thru 7
when STYC is CI |
|
|
DOI must not be 0 when
LTXTY is ITX |
|
|
DOI required when ACT
is N |
|
|
DOI required when LACT
is not Z or D |
|
|
DPA must be numeric.DPA
too long--<length of dpa value> vs 3.DPA must be greater
than 0. |
Make sure that DPA is 1 to 999. |
|
DQTY (0) must be equal
to or greater than the number of Disconnect Sections (1). |
|
|
DRC or FAXNO required
when RTR is D |
|
|
DSGCON required when
RTR is D |
|
|
DSGTELNO is required
when RTR is D and ACT is one of "NDVCTM" |
|
|
DSPTCH must be blank
or N when CHC is B |
|
|
DSPTCH must equal Y or
N when ACT is <ACT>. |
The DSPTCH field can't be left blank. Select Y
if a dispatch is required or N if it's not required. |
|
DSPTCH not allowed when
product is "UL" and activity is "<>" |
|
|
DSPTCH not allowed with
product= “UL” and activity= “X” [where X is N, T, M, D, or C] |
The DSPTCH field must be left blank (neither Y
nor N) for the product and activity you selected. (Qwest
automatically arranges for dispatch if it is required.)
Make sure that you have selected the product and
activity you want. If you have, make sure that the DSPTCH
field is blank. |
| DSPTCH not valid with product and activity selected. |
|
|
Due date change not
allowed. LSRs already submitted for appointment. |
|
|
Duplicate HTN values
may not exist for same HTQTY |
|
| E |
|
|
EAN should not match
AN |
|
|
EASNUM must be Y when
ECATEG or EWORD is populated |
|
|
ECATEG or EWORD must
be populated when EASNUM is Y |
|
|
ECCKT is mandatory and
must be filled. |
|
| ECCKT is prohibited for LNA
of N. |
If you selected N - New in the LNA field,
the ECCKT field must be left blank. |
|
ECCKT required when ACT
is C |
|
|
ECCKT required when ACT
is D, C, T or M |
|
|
Either LSR ID or CCNA
and PON must be provided. |
|
|
E-Mail or Fax is required |
|
|
English USOC descriptions
are not available for this account. |
IMA doesn't provide descriptions of the USOCs in CSRs for the Central
Region. |
|
Error during MP Validation
- POTS SPLITTER <> not found |
|
|
Error during MP Validation
- Specified device <> not available to <> |
|
|
Error in communicating
with the server. IMA unavailable to process request at this time. |
|
|
Error opening socket |
|
|
Error processing request |
|
|
Error Processing Request
OSS Gateway: No data returned NO DATA RETURNED |
The USOC you specified is invalid for the NPA, NXX, state, and type of
service you specified. |
|
Error reading xml response
from socket |
|
|
ERROR: No Response from
Business Process Layer. Try again. |
|
|
Errors on 'Address Information'
tab: |
|
|
Errors on 'Admin' tab: |
|
|
Errors on 'Contact' tab: |
|
|
Errors on 'Control' tab: |
|
|
Errors on 'DL' tab: |
|
|
Errors on 'Initiator'
tab: |
|
|
Errors on 'Instruction'
tab: |
|
|
Errors on 'Service' tab: |
|
|
EUMI field contains multiple
different values, cannot determine action |
You need to fill in the EUMI field the same way on every
Location tab you use. |
|
EUMI must be Y or N |
For the product and the activity you selected, the EUMI
field can't be left blank.
Select Y if your customer is moving
or N if they’re not moving. |
|
EUMI required when ACT
is V |
|
|
EV2 Invalid when FA
is N. Use FVJ, FBJ, FDJ Instead. |
|
|
EVB Invalid when FA
is N. Use FVJ, FBJ, FDJ Instead. |
|
|
EVD Invalid when FA
is N. Use FVJ, FBJ, FDJ Instead. |
|
|
EVF Invalid when FA
is N. Use FVJ, FBJ, FDJ Instead. |
|
|
EVK Invalid when FA
is N. Use FVJ, FBJ, FDJ Instead. |
|
|
EVO Invalid when FA
is N. Use FVJ, FBJ, FDJ Instead. |
|
|
EXP prohibited when ACT
is D or W |
|
|
EXP prohibited when
CHC is B |
|
| F |
|
|
FA must be empty for
products ALSP/DLSP when ACT is N/D/V/Z/C and LNA is X/W/P/Y/L. |
|
|
FA must be N or D when
LNA is D |
|
|
FA must be N when LNA
is N |
|
|
FA must be N, C, D or
T when LNA is C |
|
|
FA must be N, C, D or
T when LNA is T |
|
|
FA of "C" ('Change
From') must be used in conjunction with FA of "T" ('Change To') |
|
|
FA required when ACT
is V or Z and LNA is V, N or D |
|
|
FA required when LNA
is V |
|
|
Fac. Type is mandatory
and must be filled. |
|
|
Facility does not meet
availability requirements. |
Correct the CFA value and try again. |
|
FAXNO prohibited when
DRC is populated |
|
|
FAXNO prohibited when
DSGCON is not populated |
|
|
FAXNO required when RTR
is D and DRC is not populated |
|
|
FBDL listing already
exists - must submit listing request on separate FBDL LSR |
You can't submit a UBL LSR with directory listed for the TN you specified
when there is an FBDL standalone on LSS for that TN. |
|
FBI - AN, BILLNM, SANO,
SASN, CITY, STATE and ZIP required when FBI is D |
|
|
FCUDSL: Error connecting
to server |
|
| Feature(s) and Blocking value(s) XXXX not available for this end-user line in specified switch. |
|
|
FEATURE <requested
Hunting USOC> Not Valid when ACT is V or Z and LSR HTQTY is 0 |
If the activity is V or Z and the HTQTY field is zero,
then the Feature field (on the Resale form) must not
be populated with the Hunting USOC. The following are valid Hunting FID
values: HTG, HSO, HSHPT, HSHPG, HCKPG, EH6, HSHHP, EH8, EH9, P89, PHY,
BRA, EHC, EHD, MUMHT, NZQ, NZQPG, NZS, NZSPG, NZT, NZTPG, N2D, N2DPG,
HDT, HDTPG, H6U, H6UPG, SE3PN, SE3PG, BRR, A9AEX, MB1, HSGPH, HSGPN.
Verify that the feature value is not populated
with any of the values listed (Hunting USOC) if the activity is V or Z
and HTQTY field is zero. |
|
Feature Details Section
required when ACT is N, C or T |
|
|
Feature Details Section
required when ACT is V or Z and LNA is V, N or D |
|
|
Feature Details Section
required when LNA is V |
|
|
FEATURE must contain
a Contract USOC when MIL is populated. |
The FEATURE field must have a contract USOC because the
MIL field is populated. |
|
FEATURE required when FA is populated |
|
|
Feature <>
requires one of the following USOCs: <list of USOCs> |
To add the indicated feature to an account, you must also add one of the
USOCs listed in the error message.
|
|
Feature <>
requires one of the following USOCs:
<first list of USOCs> and requires
one of the following USOCs: <second list of USOCs> |
To add the indicated feature to an account, you must also add one of the
USOCs from each of the two lists in the error message. |
| Feature value <>
is invalid for <product> when ACT is <> |
|
| Feature value <>
is invalid for <product> when REQTYP is <>
and ACT is <> |
|
|
Feature value XRS is
invalid for UNE_P_CENTREX_21 when ACT is B |
|
|
Feature Verification
not allowed. A trouble report already exists. |
Feature Verification does not work for a TN with an open trouble report.
Verify that entries are correct. Wait until
trouble report is closed and try again.. |
|
Feature with FA of C
must be present with feature of FA of T. |
If you select C in the FA field, you
also need to select T and then select a corresponding
USOC in the FEATURES field. |
|
Feature with FA of C
must have related feature with FA of T for <>. |
If you select C in the FA field, you
also need to select T and then select a corresponding
USOC in the FEATURES field. |
|
Feature with FA of T
must be present with feature of FA of C |
If you select T in the FA field, you
also need to select C and then select a corresponding USOC in the FEATURES
field. |
|
Feature with FA of T
must have related feature with FA of C for <>. |
If you select T in the FA field, you
also need to select C and then select a corresponding USOC in the FEATURES
field. |
|
Feature(s) <list
of USOCs> not available for this end-user line in specified switch
|
If the requested USOCs are FDJ, FVJ, or FBJ and the derived USOCs for
these are not available in the switch, then XXXX is the series
of requested USOC(s) containing both the requested USOC and the derived
USOC in parentheses ().
XXXX varies under either of the following conditions:
-- If the requested feature(USOC) is not available
in the switch, then XXXX is the requested USOC in the feature field
of the Order form.
-- If more than one requested USOC(s) is not available
in the switch, XXXX is the string of concatenated requested USOCs separated
by delimiters ',' (commas). |
|
Features on account are
not compatible with requested features |
You can't add an LEF on the account because there is a WTN freeze on the
account. |
|
Fetch TOI USOC failed
() |
|
|
Fetch UBL/EICT USOCs
failed () |
|
|
FID 'TN' required when
FID 'MCFI' is entered on the FEATURE DETAIL field |
|
| First character of ALI code
must be alpha |
|
| First character of NSTN may not be a space |
|
|
First digit of TOS must
be 4 when PSP |
|
|
FIRSTUNIT required when
CABNM or LASTUNIT is populated |
|
| FOC must contain at least
one order |
|
| Form/Section required for
Reject Reason. |
|
|
Full AN not provided
and no corresponding preorder attempt |
Verify AN or make PreOrder TN reservation attempt |
|
Full AN required on LSR
form admin section when EUMI is Y |
|
| G |
|
|
Gift billing on this
account requires separate authorization. |
A service request for conversion (ACT = W, V, or Z) of an account participating
in a Gift Billing Group relationship is rejected.
Discontinue the Gift Billing Relationship before
submitting a service request for conversion. If there is a pending Service
Order that discontinues Gift Billing, you may successfully submit this
request by checking the pending Service Order flag. |
| H |
|
|
HA must be N when ACT
is <activity type> |
|
|
HA must be N, C or D
when ACT is C |
|
|
HA required when HTQTY
is greater than zero |
|
|
HICABCONN is mandatory
and must be filled. |
|
|
HID must be an alpha
when HNTYP is 2, 3, 7, 16, or 17 |
|
|
HID must be blank when
HA is N |
|
|
HID must be numeric when
HNTYP is 4, 6, 13, 14, or 15 |
|
|
HID required when HA
is <HA values> |
|
|
HIPOTSSPLIT is mandatory
and must be filled. |
|
|
HLA must be N when HA
is N |
|
|
HLA required when Hunt
Detail Section is populated |
|
|
HNSTN required when STYC
is SI and HTN is not populated |
|
|
HNTYP required when HA
is populated |
|
|
HS required when doi
is greater than zero |
|
|
HTN not allowed when
STYC is not SI |
|
|
HTN required when STYC
is SI and HNSTN is not populated |
|
|
HTN value must be present
in the HTSEQ field when HLA is N or E |
|
|
HTN value must not be
present in the HTSEQ field when HLA is D |
|
|
HTQTY field must be greater
than 0 on the LSR when the Line Activity (LNA) of V, D, or X is requested
on an existing line that is part of a hunt sequence. |
|
|
HTSEQ field may not be
populated when HA is E |
|
|
HTSEQ prohibited when
HA is E. |
|
|
HTSEQ required when ACT
is N, V, Z, C or T and HA is N or C |
|
|
HTSEQ required when ACT
is N, V, Z, C or T and HA is N, C or V |
|
|
Hunt Detail Section must
be populated when HA is N or C |
|
|
Hunting Functionality
is supported only when HNTYP is <> |
|
|
Hunting Functionality
is supported only when HTSEQ format is valid |
|
Last Update: October 20, 2008 |
|