MSAG record does not exist for a change. An attempt was made to change a record that does not exist in the MSAG.

Transcription

1 Code Description Non-numeric character in telephone number. This includes any spaces or alpha characters in 002N the NPA, NNX, or TN fields of the telephone number. This is considered a data error. Non-numeric character in main telephone number. This includes any space or alpha 003N characters in the NPA, NNX, or TN fields of the main number. This is considered a data error. Illegal class of service. The class of service must be a digit from 0 to 9 or values A through Z 009N defined in class_service table.. 010N Illegal type of service. The type of service must be a single digit from 0 to 5. Attempted an illegal main number default. An attempt was made to default part of a main number that already had a distinct component. Blank fields in the main telephone number 011N will be populated with the same value as the telephone number. But a field cannot be defaulted if some earlier part of the main number has already been specified. (Example: leaving the main NNX field blank after specifying an NPA.) This is considered a data error. 012N Non-numeric character in the customer code. The customer code must be all numeric. Leading spaces are allowed. This is considered a data error 264 Invalid RESELLER ID in incoming CRIS file 265 DB RECON unable to correct soft errors, because TN record is unlocked. 266 Nonnumeric in Customer Code or Blank Customer Code in CRIS TN. 267 Nonnumeric in TN or Main TN number or Blank TN/Main TN in CRIS TN. 268 TN record in incoming CRIS file has an invalid date. DB RECON comparison utility encountered the following conditions: 269 1) 2 or more errors encountered, where at least of them was a hard error (soft errors not fixed in this case) 2) 5 or more soft errors encountered (soft errors not fixed in this case) 270 FR/DBMS TN record is newer than CRIS TN record 271 Incoming TN record in CRIS file has bad location field 272 FR/DBMS TN and CRIS TN records' pilots numbers differ and DBMS is a sub line 273 FR/DBMS TN shows reseller and CRIS tn does not 274 Incoming TN record in CRIS file, is newer than today's date 275 FR/DBMS TN record exists, but no appropriate record in incoming CRIS TN file 276 CRIS Location overflow indicator set. 277 CRIS location field overflow. 278 FR/DBMS missing supplemental data record. 279 CRIS shows Resellers and FR/DBMS does not. 280 CRIS record exists; FR/DBMS record does not. 281 FR/DBMS and CRIS Resellers differ. 282 CRIS has invalid type of service. 285 Duplicate TN records received from CRIS 286 FR/DBMS and CRIS pilot TNs differ. 287 CRIS shows address as SLA and FR/DBMS does not. 288 FR/DBMS shows address as SLA and CRIS does not. 289 Addresses differ and SLA flags match. 290 FR/DBMS and CRIS classes of service differ. 291 FR/DBMS and CRIS customer names differ. 292 FR/DBMS and CRIS customer codes differ. 293 FR/DBMS and CRIS foreign exchange indicators differ. 294 CRIS record has no address or badly formatted address. 295 FR/DBMS and CRIS location information differ. 298 FR/DBMS and CRIS publish flags differ or CRIS doesn't have. 299 CRIS record has no foreign exchange indication. 302 MSAG range overlap on an insert or change. The attempted insert or change operation would result in overlapping street ranges in the MSAG. 303 MSAG record does not exist for a change. An attempt was made to change a record that does not exist in the MSAG. E911 Error Codes Page 1 of 13 10/25/2004

2 307 MSAG record does not exist on a delete. An attempt was made to delete a record that does not exist in the MSAG. 310 Valid ESN/Community or county mismatch. The current ESN and community or county combination does not appear in the Valid ESN/Community or county_esn table. Only one record specified for a split or combine. Split and combine are intended to work on 311 multiple MSAG records in one operation, and only one record was specified. If the intent was to shorten or extend a range, a change operation should be performed. Split, join, or change would leave unsupported tn records. The attempted operation would 312 leave tn records with no underlying MSAG record. This can be due to gaps in street ranges, the shrinking of street ranges, or the changing of the odd/even flag. ESN greater than 999 while PDP is a target system. The PDP ALI/DMS systems have a 313 limitation that the ESN can only be 3 characters long. As long as a PDP system is still being updated by the FR/DBMS, no ESNs greater than 999 can be used. 314 Low house number is greater than the high house number. In order to form a valid range, the low house number must be less than the high house number. 320 Illegal odd/even indicator value. The odd/even flag can only have the values (O)dd, (E)ven, or (B)oth. 321 Community name field not populated. During bulk loads, the community name must be specified on every MSAG record. 323 Non-numeric character in ESN or blank ESN. The ESN must be all numeric and must have a value greater than zero. 324 Illegal function of change. During a MSAG bulk load, the only valid function of change is (I)nsert. 325 Range overlap on an AKA record. The AKA you are attempting to associate with this MSAG record overlaps with an AKA associated with this or another SAG record. Range overlap on an AKA record associated with a MSAG change. The MSAG record you are 331 trying to change has an AKA record associated with it which will overlap with an AKA record associated with another MSAG record if the change is made. No ALI ID defined. This is an error related to the ARCS feature package. Every MSAG record 353 in an ARCS database must have an ALI ID defined for its combination of PSAP-ID, state, and exchange. No configuration defined for ALI ID. This is an error related to the ARCS feature package. The 354 MSAG record has an ALI ID defined, but this ALI ID is missing a configuration file definition. No router id defined. This is an error related to the ARCS feature package. Every MSAG 355 record in an ARCS database must have a valid router id defined. The router ID is defined by a combination of the PSAP ID and state. 356 Switch type missing for router ID. This error is part of the ARCS feature package. The MSAG record has a router ID assigned, but this router ID is missing a switch type definition. MSAG RECORD NOT OWNED BY YOUR COMPANY. YOU ARE RUNNING A RESTRICTED 360 CLERK INTERFACE AND THE MSAG RECORD YOU ARE ATTEMPTING TO OPERATE ON IS NOT OWNED BY YOUR COMPANY. MSAG RECORDS NOT OWNED BY YOUR COMPANY CAN BE VIEWED BUT NOT CHANGED IN ANY WAY. 601 A translation for the given NPANNX was not found in the NPANNX to ESSID table. The received R record contained an illegal function of change. The valid functions of change 602 for R records are Change (C), Delete (D), X-Delete (X), Insert (I), Unlock (U), and Migrate (M). 603 The donor system is not authorized to modify the R record. The receiving system does not recognize the donor system as owning the existing record. 604 The R record is missing one or more mandatory data elements. The FOC, CTN, ESN, CPF, and ASI data elements are mandatory. 605 A donor system has sent an R record for a CTN that already exists in the receiving system's database. 606 The receiving system is unable to validate the ASI value. 607 The receiving system is unable to validate the ESN value. 608 The received R record contains a CPF value that is unknown to the receiving system. 609 The received R record contained only one coordinate data element (e.g., either XCD or YCD). E911 Error Codes Page 2 of 13 10/25/2004

3 613 An attempt was made to delete a record that does not exist in the database. 614 The received R record is attempting to migrate an existing R record that has not been unlocked. 615 The receiving system has received an R record for a CTN that is managed by another donor system. 616 The received R record is attempting to change an unlocked R record. 617 The received R record is attempting to delete an unlocked R record. 618 The received R record is attempting to insert an unlocked R record. 620 The received R record is attempting to unlock an existing non-r record. 621 The received R record is attempting to unlock an unlocked R record. 622 The received R record is attempting to unlock a nonexistent R record. 623 The received R record is attempting to migrate an existing non-r record that has not been unlocked. 624 The received R record is attempting to insert an unlocked non-r record. 625 The received R record is attempting to change an unlocked non-r record. 626 The received R record is attempting to delete an existing full TN record. 627 The received R record needs to be resent. 628 The received R record needed to be resent, but a resend could not be performed because the max resend count was exceeded. 629 The received R record contains an invalid MAPID. 630 The received R record contains a different CPF value than the current R-record. 650 The received R record verification data elements do not agree with the sent R-record data elements. 651 An RTR file was not received in the allowed time frame for a previously sent dar file. 652 A pilot or subsidiary TN exists for the received R record. 653 The received R(M) was queued for later processing (awaiting unlock). This is an informational error. 654 Either the remote ali id for the received R record has not been configured or the NPANNX_ALI pair table does not contain an entry for this record (if multi-ali is turned on). 661 The incoming R record file is incomplete - it does not contain a valid trailer. 662 The incoming R record file does not contain a valid header. 663 The incoming R record file contains a cycle number that is out of sequence. 664 The incoming R record file contains a mismatch between the actual record count and the count specified in the trailer. 665 The incoming R record file contains one or more records with an invalid record type. 700N 701M 702N 703N 704N 705N 706N 707N Illegal function of change. The valid functions of change for telephone number records are (I)nsert, (C)hange, (D)elete, (P)ilot Delete, (T)ransfer, and (F)inal. This is considered a data error. No MSAG record found. No MSAG record was found for this address. This includes cases where the street name does not exist in the MSAG and where the street exists, but the ranges do not cover the current address. This error code replaces the error codes 701 and 709 from the PDP DMS system. Record already exists on insert. An attempt was made to insert a telephone number that already exists.. Main record not found. An attempt was made to insert or change a subsidiary whose main telephone number does not exist in the database. Record does not exist on delete. Telephone number record doesn't exist on a delete. An attempt was made to delete a telephone number record which does not exist in the database. Record does not exist on a pilot delete. An attempt was made to perform a pilot delete on a main telephone number that does not exist in the database. Service order error field is populated. The service order error field is populated with some nonspace character(s). The meaning of this error field is implementation specific. Subsidiary customer code mismatch. An attempt was made to insert a subsidiary with a different customer code than its main telephone number record. E911 Error Codes Page 3 of 13 10/25/2004

4 709M 710N 711N 712N 720N 721N 723N 724N 725N 732M 737M 738N 739N 740N 741N 742M 743N 744N 745N TN has no supporting MSAG record. An MSAG delete was performed that left this telephone number with no underlying MSAG record. Customer codes do not match on a change. The customer code on a change to a telephone number record does not match the customer code of the existing record. Customer codes do not match on a delete. The customer code on a delete or pilot delete operation does not match the customer code of the record to be deleted. Record does not exist on change. An attempt was made to change a telephone number record which does not exist in the database. NPA to NPD translation not found. The NPD translation for the current NPA does not exist in the NPA to NPD translation table. Type of service is a foreign exchange. The number belongs to a foreign exchange, i.e. the type of service is a 2 or 5. NPANNX to ESSID translation not found. The translation for the given NPANNX was not found in the NPANNX to ESSID translation table. Non-numeric character in ESN or blank ESN. The ESN must be all numeric and must have a value greater than zero Service order error field shows and error - this error code is valid only on PDP DMS only. This error code should only appear on error records that have been transitioned from a PDP DMS. Multiple MSAG record exchange matches found. An attempt to insert or change a record with no community name was made. While trying to query the MSAG to match based on the address and exchange, multiple records were found. Exchange matching failed to find a unique MSAG record. The MSAG was queried using the address and community name with the exchange matching feature turned on. Multiple address and community name matches were found and the exchange was used to try and find a unique MSAG record. There were no MSAG records found with the same address, community and exchange Attempted to change a main number to a subsidiary line. The record in error is currently a main number with subsidiaries in the database. The attempted change would make this number into a subsidiary of another line. This would leave the original subsidiaries without a valid main number. Street names do not match on a delete. The street name in the delete record does not match the street name in the database. If a delete record has a street name present, it must match the street name of the record in the database. The street name is not a required field on a delete. Delete attempted on a number with subsidiaries. A function of change "D" was attempted on a phone number which has subsidiaries. A function of change "P" must be used to delete the main with all of its subsidiaries or all of the subsidiaries must be deleted before attempting to delete the main. Main number is already a subsidiary line. An attempt was made to insert a subsidiary whose main number is already a subsidiary to another line. This would leave this number without a valid main number. Routing table entry not found for a subsidiary. A subsidiary line was inserted with the same address as the main and the main's ESN was assigned from the routing table. While trying to inherit the main's ESN, the routing table entry was not found. Function of change (F)inal would result in a pilot delete. A (F)inal transaction was attempted that would result in the delete of an entire pilot -subsidiary group. This action must be accomplished with a (P)ilot Delete record. (P)ilot Delete attempted on a subsidiary line. A (P)ilot Delete can not be performed on a subsidiary line. If the intent was to delete the entire pilot-subsidiary group, a (P)ilot Delete should be performed on the main number. If the intent was to delete the subsidiary line only, a (D)elete should be performed on the subsidiary line. Function of change (FOC) other than (I)nsert attempted during an initial load. During an initial load, no function of change other than (I)nsert is allowed. This error can also occur if a function of change of P is passed in a service order record on a system where the Pilot Processing Disable feature key is enabled. E911 Error Codes Page 4 of 13 10/25/2004

5 746N 747N 748N 749N 750N 751M 752M 753N 754N 755N 756N 757N 758N 759M 760M 761L 762L 763L 764L NPANNX to ALI-ID relationship is missing. Every NPANNX must have an entry in the NPANNX to ALIID table to specify which ALI system should be updated. Record already exists in another database. This telephone record already exists on the system, but in another database. Telco PS TN Range Violation: A telco service order record, or a record from the TN or ERROR screen in the clerk interface, has a telephone number that is in a range assigned to a private switch. This is an illegal operation for the service order processor or any FR/DBMS user except an FR/DBMS Administrator. Private Switch TN Range Violation: A service order record from a private switch has a telephone number that does not fall in one of the telephone number ranges granted to that private switch. Invalid Private Switch Range: A service order record from a private switch contains a telephone number that is in a range assigned to some other private switch. The PSAP ID in the MSAG record covering this TN has changed. The PSAP ID currently assigned to this TN was assigned from the MSAG Bypass table by a TN bypass. Either remove the record from the MSAG Bypass table or delete the error codes. The ESN in the MSAG record covering this TN has changed. The ESN currently assigned to this TN record was assigned from the MSAG Bypass table. Either change the ESN in the MSAG Bypass table or delete this error record. No ALI ID defined. This is an error related to the ARCS feature package. Every telephone number in an ARCS database must have an ALI ID defined for its combination of PSAP-IDid, state, and exchange. No configuration defined for ali id. This is an error related to the ARCS feature package. The telephone number record has an ali id defined, but this ALI ID is missing a configuration file definition. No Router ID defined. This is an error related to the ARCS feature package. Every telephone record in an ARCS database must have a valid Router ID defined. The Router ID is defined by a combination of the PSAP ID and state. Switch type missing for Router ID. This error is part of the ARCS feature package. The telephone number record has a Router ID assigned, but this Router ID is missing a switch type definition. No NPANNX to ALIPAIR relationship defined. This error code is associated with the Multi-ALI Pair Update Feature Package. The NPANNX of the TN record is not associated with an ALI pair. The association with an ALI pair tells the DBMS which ALI pair to update. No ESSID to ALIPAIR relationship defined. This error code is associated with the Multi-ALI Pair Update Feature Package and a switch served by an ALISA. The ESSID of the TN record is for a type E switch which is a 5E served by an ALISA. The ESSID, however, has not been associated with an ALI pair. Exact exchange match not found. Exchange matching is turned on and this Tn record has matched against a single MSAG record, but the exchange value in the TN record does not match the exchange value in the MSAG. Unsupported TN on MSAG Bypass. There is no underlying MSAG record for this TN record. Therefore, when the Bypass record was deleted this TN record became unsupported. Please enter a new MSAG or MSAG Bypass which will support these records and then correct the errors. Unlock attempted on an unlocked TN (same Company ID). This TN has already been unlocked by the same Company ID as is in the new service order record. In effect, this is a duplicate unlock request. Unlock attempted on an unlocked TN (different Company ID). This means that two different Companies have tried to unlock the same TN record. One of these Companies is in error. Further investigation as to which Company actually owns this record should be pursued. Migrate attempted on a locked TN. In order for an "M" or migrate function of change service order to process correctly, a "U" or unlock service order must have been previously processed successfully. Insert attempted on a TN that is unlocked. Once a TN record has been successfully unlocked, the only valid function of change is "M" or migrate. E911 Error Codes Page 5 of 13 10/25/2004

6 765L 766L 767L 768L 769L 770L 771L 772L 773L 774N 775M 776M 777M 778M 779M 780M 781L 782N 783N 784N 785N Change attempted on a TN that is unlocked. Once a TN record has been successfully unlocked, the only valid function of change is "M" or migrate. Delete attempted on a TN that is unlocked. Once a TN record has been successfully unlocked, the only valid function of change is "M" or migrate. Company IDs do not match on a change. The TN record that you are trying to change is assigned to a different Company ID. This record needs to be unlocked by the original Company and a migrate order processed by the new Company. Only after the migrate order has been successfully processed can change orders be applied. Company IDs do not match on a delete. The TN record that you are trying to delete is assigned to a different Company ID. This record needs to be unlocked by the original Company and a migrate order processed by the new Company. Only after the migrate order has been successfully processed can delete orders be applied. Clerical and ERROR record Company IDs do not match. The Company ID(s) associated with the clerical user do not match the Company ID of the ERROR record. Either an additional Company ID needs to be assigned to the clerical user, or a different clerical user with the appropriate Company ID should process this record. Clerical and TN record Company IDs do not match. The Company ID(s) associated with the clerical user do not match the Company ID of the TN record. Either an additional Company ID needs to be assigned to the clerical user, or a different clerical user with the appropriate Company ID should process this record. Unlock attempted on a nonexistent TN. The TN record that you are attempting to unlock does not exist. Company IDs do not match on an unlock. Only the Company ID associated with the TN record can unlock that TN record. Migrate attempted on a nonexistent TN. The TN record that you are trying to migrate does not exist Pre-Completion insert attempted on existing TN. Insert of a pre-completion record attempted when the original TN exists in the database. A County default MSAG record does not exist for this county. Insert a county default MSAG record from the MSAG screen to correct this problem. Street name not found in the map. Geocoding of the address could not be completed because the street name could not be found on the map server. Street range not found in the map. The specified street was found to exist in the map, but no records were found with an address range which contains the house number specified. Geocoding of the address could not be completed. Overlapping street range found in the map. More than one street segment was found in the map with an address range which contains the specified house number. Geocoding of the address could not be completed. Mismatch between the MSAG ESN and the MAP ESN. The ESN value retrieved from the MSAG did not match the ESN value retrieved from the MAP. Map Server is disabled. This address must be geocoded and cannot be processed until the Map Server is activated. Duplicate TN; insert attempted by another company Record already exists. An attempt was made to insert a telephone number that already exists and is owned by another company. Buffer size exceeded for TN data. One or more fields have exceeded their buffer size resulting in a truncation of data. Completion Date Error. The completion date of the TN in the currently stored FR/DBMS record is later than the completion date of the incoming transaction (later than or the same as for D and P foc's). Secondary address error Secondary Address Error. Signifies a problem with the SLA, such as an unknown SLA value, or an illegal operation for the specified SLA. Usually signifies an illegal address change for a pilot or one of its subsidiaries. Location Error. Signifies a problem with the location field or location flags, such as: unknown location flag value, unknown location label, illegal address/line location flag combinations, or an overflow in the location field when factoring in address element changes from a pilot to its subsidiary. E911 Error Codes Page 6 of 13 10/25/2004

7 786N Supplemental data error. Signifies that required supplemental data was not present in a transaction or not found for an existing record. 787N Invalid reseller ID - Invalid Reseller. The reseller is not defined in the LNP Company table. TN is managed by another database service provider. A service order or a manual operation 788N has been received for a CTN that is ma naged by another database service provider. Either ther ESN/ESSID appears in the r_owner table or the CPF does not match the existing R record. 790N Delete attempt on R-record. A delete service order attempted to delete an R-record. Migrate attempted on TN that exists in another database. Migrate attempted on an existing TN 791L located in the wrong database. The TN record that you are trying to migrate does not exist in the database named in the unlock record. Migrate attempt on locked TN; reprocess request already queued. Migrate-reprocess-queuesubmission attempted on a TN that has an existing queued Migrate waiting to be re- processed 792L by CLEC ALI mode 2. Only one queued Migrate can exist for a given TN at any time. CLEC ALI mode 2 must first reprocess this queued Migrate before any futher Migrates can be queued for reprocessing. 793N Assigned ESN exceeds maximum allowable range. ESN greater than maximum range. English Language Translation not found. The English language translation for the current 800 ESN/ESSID combination was not found. This is an informational error, therefore the operation was performed despite this error occurring. Subsidiary line unchanged. A change was made to this subsidiary line's main number. This is 819 an informational error. If the change should not be applied to the subsidiary line, this error record should be deleted. Subsidiary line unchanged. A change was made to this subsidiary line's main number. Either 820 the existing subline or the incoming pilot change contains line location data 821 Incoming pilot TN is 99. Subsidiary line on the same address as existing pilot TN has SLA YY. Location comment flag set on a change. An attempt was made to change a record which has 825 the location comment flag set. This is an informational error, therefore the record was processed but the location and telco comment fields remained unchanged. Location comment flag set on a Migrate to an external company. An attempt was made to 826 migrate a record which has the location comment flag set. This is an informational error, therefore the record was processed but the location and telco comment fields remained unchanged. Customer name field has changed on a private TN record. A customer name change has 827 occurred on a record that has been designated as having the customer_name displayed as PRIVATE CITIZEN at the PSAP. 828 A private TN record has been deleted. A delete of a record whose customer_name field was designated to be displayed as PRIVATE CITIZEN at the PSAP has just occurred. Location comment flag set on a delete. The Location comment flag was set on a deleted 833 record. This is an informational error, therefore the record was deleted despite this error occurring. This may result from a delete or pilot delete. In the case of a deleted subsidiary during a pilot delete the subsidiary's record will appear in the error table. A change to the MSAG has caused the PSAP ID to change in this record. This is an 850 informational error that can be used as a TAR change report. Two 850 errors will be generated, one with a "D" FOC containing the old PSAP ID and a second with an "I" FOC containing the new PSAP ID. The PSAP ID in the MSAG record covering this TN has changed. The PSAP ID currently 851 assigned to this TN record was assigned from the MSAG Bypass table by a TAR Bypass. The clerk must initiate an R-type service order and delete the error record. Migrate attempted on a TN that has not been unlocked. This is an informational error indicating that the TN record you are trying to migrate has not been unlocked by the donor Company yet. 863 This record will be reprocessed automatically and will become a 763 error if the unlock record has not been received by then. Street name not found in the map. Geocoding of the address could not be completed because 876 the street name could not be found on the map server. This is an informational error. The record was processed using data from the MSAG. E911 Error Codes Page 7 of 13 10/25/2004

8 Street range not found in the map. The specified street was found to exist in the map, but no records were found with an address range which contains the house number specified. Geocoding of the address could not be completed. This is an informational error. The record was processed using data from the MSAG. Overlapping street range found in the map. More than one street segment was found in the map with an address range which contains the specified house number. Geocoding of the address could not be completed. This is an informational error. The record was processed using data from the MSAG. Mismatch between the MSAG ESN and the MAP ESN. The ESN value retrieved from the MSAG did not match the ESN value retrieved from the MAP. This is an informational error only. The ESN used by the ALISA to route calls will be determined by the esn_source value in the map_enable table. Map Server is disabled. This address requires geocoding but cannot be processed until the Map Server is activated. This is an informational error. The record was processed using data from the MSAG. SLA/Primary address discrepency. A change was made to this subsidiary line resulting in the subline at SLA having the same address as the current main number at Primary. This is an informational error. The change has already been applied. 882 A CASP TN record already exists on an Insert. 883 There is no CASP TN record to Delete/Change/Migrate/Unlock. 884 A CASP TN record exists for a Verizon-owned TN Illegal character in the UNIX login. Ths UNIX Login must consist of a single word of lower case characters only! Attempted to use a word for a UNIX LOGIN that has already been used. Each user's UNIX LOGIN must be unique. The FR/DBMS system was intentionally designed to never allow the same UNIX LOGIN to be reused. Choose a different word for the UNIX LOGIN, or alter it slightly, say by changing mary to mary1. The user attempting to use this program is not a registered FR/DBMS user. Only users who have been added to the system using the FR/DBMS DEFINE -USER screen are allowed to access FR/DBMS. UNIX user whose login ids have been added using the UNIX interface are not considered registered FR/DBMS users and will not be allowed access. Login is disabled and cannot be updated. Once a FR/DBMS user's login is disabled, it is frozen for historical and legal reasons. It cannot be changed in any way, nor can it ever be reenabled or removed from the database. A PBX user cannot be updated. There are no fields associated with this type of user that can be changed. The only permissible operation on a PBX user is to disable the login. No matching record in the PSAP configuration table. An operation on a PSAP user requires that a record exist in the PSAP configuration table, and no record was found where the PSAP ID matches PSAP ID associated with this PSAP user. This is an internal data integrity error that should never occur. Call Intrado for assistance. MSAG Mail, Misroutes, and Supplemental Data turned off for this PSAP. An attempt was made to associate a user with a PSAP that has none of the end user features turned on. In order to have a valid user, at least one of these features must be activated. No matching record in the municipality configuration table. An operation on a municipality user requires that a record exist in the municipality configuration table, and no record was found where the municipality ID matches the municipality ID associated with this municipality user. This is an internal data integrity error that should never occur. Call Intrado for assistance. MSAG Mail, Misroutes, and Supplemental Data are all disabled for this municipality. An attempt was made to associate a user with a municipality that has all of the end user features disabled. At least one of these features must be enabled for a valid user. Maximum array size exceeded. An internal limit to the number of elements in an array has been exceed. This error is associated with an array being displayed in a window, and means that the program is not capable of displaying all the data available. It is not necessarily a fatal error, but should be brought to the attention of Intrado support. E911 Error Codes Page 8 of 13 10/25/2004

9 Fatal error installing or deleting a FR/DBMS user. This is an internal error that indicates the 1011 administration program was not able to install or delete a FR/DBMS user. Do not attempt to install or delete this or any other user until you refer this problem to Intrado support. A user cannot delete himself/herself. A FR/DBMS Administrator can delete any other user on the FR/DBMS system but himself/herself. This safeguard exists to prevent an administrator 1012 from inadvertently deleting himself, or from deleting the last administrator on the FR/DBMS system. Access denied to FR/DBMS user: wrong access level. An attempt has been made by 1013 FR/DBMS user to access a program outside their access level. For example, a user with "clerk" access level has attempted to access the administration program. The access is denied and a record of the denied access is made in the log file /dms/log/dms.log Service order format name must be unique. The service order format names must be unique. Change the name to a different word, or make some slight change to distinguish it. Service order format record length too short. The total record length for the service order 1015 format record must be at least as long as the sum of all the numbers in the LEN column on the RECORD FORMAT form. Boundary error in field. This error results when the position and length of a field defined in a service order format record overlaps onto another field in the same record. The RECORD 1016 FORMAT screen will display the names of the two fields involved in the boundary error, and will have positioned the cursor in the first of the suspect fields. The error can be corrected by changing the position or length of either fields. Maximum length of field exceeded. The value enter for the length of the current field exceeds 1017 the maximum size of this field in the FR/DBMS database. Enter a value less than or equal to the maximum length. Duplicate Service Order SOURCE NAME. An attempt was made to add a source with an 1018 identical name as an existing source. This name must be unique. Alter the name being entered in some way so that it is distinct from all existing names. Unknown FORMAT NAME. A FORMAT NAME cannot be associated with a Service Order 1019 source that has not been defined. Use the FR/DBMS System Administration, SERVICE - ORDER, Record-Format screen to define the Record-Format for FORMAT NAME first. ESSID not defined. The ESSID entered has not been defined in the ESSID-TYPE table. Use 1020 the ESSID-TYPE screen under CONFIG-SELECTIVE ROUTER to define a new ESSID/ESSTYPE relation No views defined. There are no views defined at this time, so the VIEW command is not currently valid Initial load has not been performed on ESSID. The switch specified has never been loaded, therefore, it is not possible to do a daily update. NPANNX not associated with ESSID. The hold group selected does not belong to the switch 1023 specified by the given ESSID. Check the CONFIG-SELECTIVE ROUTING-NPANNX/ESSID for the correct ESSID translation for this group Cannot reverse this function of change. Only records with a function of change (D)elete, (C)hange, (M)ain change, (P)ilot delete, (T)ransfer, or (F)inal can be reversed Cannot reverse delete, record already exists. The current delete audit trail record cannot be reversed since another record already exists. Cannot reverse record, newer audit available. The current audit record cannot be reversed 1026 since a change has been made to the record since the time of the current audit record. Only the last operation to any record can be reversed Can only mass reverse same function of change. A mass reversal of audit trails can only be done if all the records in the current list have the same function of change Cannot reverse audit record, record no longer exists. An attempt was made to reverse a change to a record that no longer exists in the database. Cannot reverse audit record, subsidiary newer than main. An attempt was made to reverse a 1029 change to a pilot number that would affect subsidiaries, and one or more subsidiaries have been altered since the time of the audit record This is a required field. Data MUST be entered for this field. E911 Error Codes Page 9 of 13 10/25/2004

10 Fatal internal error during TN audit archive. During the TN audit archive process, the tn_audit table was unloaded to a UNIX file and the contents of that file written out to tape. The tn_audit table was then dropped from the database to empty it and recover its disk space. Then, the 1031 /dms/bin/cdt program was executed to re-create the tn_audit table, however, this program has failed. To attempt to recover from this, login as the user DMS and from the directory /dms/bin run, CDT tn_audit, from the command line. If it fails again, record the sql error number and contact Intrado support for further assistance. Fatal internal error during MSAG audit archive. During the MSAG audit archive process, the msag_audit table was unloaded to a UNIX file and the contents of that file written out to tape. The msag_audit table was then dropped from the database to empty it and recover its disk 1032 space. Then, the /dms/bin/cdt program was executed to re-create the msag_audit table, however, this program has failed. To attempt to recover from this, login as the user DMS and from the directory/dms/bin run, CDT msag_audit, form the command line. If it fails again, record the sql error number and contact Intrado support for further assistance. Fatal internal error during selective router audit archive. During the selective router archive process, the sr_audit table was unloaded to a unix file and the contents of that file written out to tape. The sr_audit table was then dropped from the database to empty it and recover its disk 1033 space. Then, the /dms/bin/cdt program was executed to re-create the sr_audit table, however, this program has failed. To attempt to recover from this, login as the user DMS and from the directory /dms/bin run, CDT sr_audit, from the command line. If it fails again, record the sql error number and contact Intrado support for further assistance. Fatal internal error during SR sent audit archive. During the SR sent audit archive process, the sr_sent table was unloaded to a UNIX file and the contents of that file written out to tape. The sr_sent table was then dropped form the database to empty it and recover its disk space Then, the /dms/bin/cdt program was executed to re-create the sr_sent table, however, this program has failed. To attempt to recover from this, login as the user DMS and from the directory /dms/bin run, CDT sr_sent, from the command line. If it fails again, record the sql error number and contact Intrado support for further assistance A PS user cannot be updated. There are no fields associated with this type of user that can be changed. The only permissible operation on a PS user is to disable the login PAIRNAME NOT DEFINED. You can not assign an essid to a non-existent pairname. You must set up the pairname first NOT AN ALISA ESSID TYPE. This feature will only work with a type "E" (ALISA) ESSID type ESSID CAN BE ASSIGNED TO ONLY ONE PAIRNAME. An ESSID can be assigned to only one ALI pair TOO MANY ESSIDS FOR THIS PAIRNAME. You are over the configured limit for ESSIDs per pairname NO ALI Pair has been assigned for this ESSID. You must assign an ALI Pair to this ESSID before this feature will work NPA-NNX not in npannx to essid table. The NPANNX to ESSID relationship must be defined prior to using this feature. TN is already defined in the TN table. You can not use this feature to override an ESN for a 1042 TN record already in the TN database. This feature only works for records not yet in the TN table A Pure Group is defined which includes this TN. You can not override an existing pure group definition in this manner. Access denied to clerk or supervisor user, no company authorization in an LN P environment An attempt has been made by an FR/DBMS clerk or supervisor u ser to access the DBMS clerk interface. This user has no authority to access or change records for any company in an LNP environment. A record of the denied access is made in the log file /dms/log/dms.log. E911 Error Codes Page 10 of 13 10/25/2004

11 Fatal internal error during alisa audit archive. During the alisa audit archive process, the alisa_audit table was unloaded to a unix file and the cont ents of that file written out to tape. The alisa_audit table was then dropp ed from the database to empty it and recover its disk space. Then, the /dms/bin/cdt program was executed to re-create the alisa_audit table, however, t his program has failed. To attempt to recover from this, login as the user DMS and from the directory /dms/bin run, CDT alisa_audit, from the command line. If it fails again, record the sql error number and contact Intrado support for further assistance. Fatal internal error during ARCS SR audit archive. During the ARCS SR audit archive process, the arcs_sr_audit table was unloaded to a unix file and the contents of that file written out to tape. The arcs_sr_audit table was then dropped from the database to empty it and recover its disk space. Then, the /dms/bin/cdt program was executed to re-create the arcs_sr_audit table, however, this program has failed. To attempt to recover from this, login as the user DMS and from the directory /dms/bin run, CDT arcs_sr_audit, from the command line. If it fails again, record the sql error number and contact Intrado support for further assistance. Fatal internal error during ARCS SR sent archive. During the ARCS SR sent archive process, the arcs_sr_sent table was unloaded to a UNIX file and the contents of that file written out to tape. The arcs_sr_sent table was then dropped from the database to empty it and recover its disk space. Then, the /dms/bin/cdt program was executed to re-create the arcs_sr_sent table, however, this program has failed. To attempt to recover from this, login as the user dms and from the directory /dms/bin run, CDT arcs_sr_sent, from the command line. If it fails again, record the sql error number and contact Intrado support for further assistance. Fatal internal error during ARCS ALI audit archive. During the ARCS ALI audit archive process, the arcs_ali_audit table was unloaded to a unix file and the contents of that file written out to tape. The arcs_ali_audit table was then dropped from the database to empty it and recover its disk space. Then, the /dms/bin/cdt program was executed to re-create the arcs_ali_audit table, however, this program has failed. To attempt to recover from this, log in as the user DMS and from the directory /dms/bin run, CDT arcs_ali_audit, from the command line. If it fails again, record the sql error number and contact Intrado support for further assistance. Fatal internal error during UUCP ALI audit archive. During the UUCP ALI audit archive process, the uu_ali_audit table was unloaded to a unix file and the contents of that file written out to tape. The uu_ali_audit table was then dropped from the database to empty it and recover its disk space. Then, the /dms/bin/cdt program was executed to re-create the uu_ali_audit table, however, this program has failed. To attempt to recover from this, login as the user dms and from the directory /dms/bin run, CDT uu_ali_audit, from the command line. If it fails again, record the sql error number and contact Intrado support for further assistance. Fatal internal error during Private Citizen audit archive. During the Private Citizen audit archive process, the private_audit table was unloaded to a UNIX file and the contents of that file written out to tape. The private_audit table was then dropped from the database to empty it and recover its disk space. Then, the /dms/bin/cdt program was executed to re-create the private_audit table, however, this program has failed. To attempt to recover from this, login as the user dms and from the directory /dms/bin run, CDT private_audit, from the command line. If it fails again, record the sql error number and contact Intrado support for further assistance. Fatal internal error during Private SR audit archive. During the Private SR audit archive process, the priv_sr_audit table was unloaded to a UNIX file and the contents of that file written out to tape. The priv_sr_audit table was then dropped from the database to empty it and recover its disk space. Then, the /dms/bin/cdt program was executed to re-create the priv_sr_audit table, however, this program has failed. To attempt to recover from this, login as the user dms and from the directory /dms/bin run, CDT priv_sr_audit, from the command line. If it fails again, record the sql error number and contact Intrado support for further assistance. E911 Error Codes Page 11 of 13 10/25/2004

12 Fatal internal error during Private SR sent archive. During the Private SR sent process, the priv_sr_sent table was unloaded to a unix file and the con tents of that file written out to tape. The priv_sr_sent table was then dropped from the database to empty it and recover its disk 1052 space. Then, the /dms/bin/cdt program was executed to re-create the priv_sr_sent table, however, this program has failed. To attempt to recover from this, login as the user DMS and from the directory /dms/bin run, CDT priv_sr_sent, from the command line. If it fails again, record the sql error number and contact Intrado support for further assistance. Fatal internal error during Private ALI audit archive. During the Private ALI audit process, the priv_ali_audit table was unloaded to a unix file and the contents of that file written out to tape. The priv_ali_audit table was then dropped from the database to empty it and recover its disk 1053 space. Then, the /dms/bin/cdt program was executed to re-create the priv_ali_audit table, however, this program has failed. To attempt to recover from this, login as the user DMS and from the directory /dms/bin run, CDT priv_ali_audit, from the command line. If it fails again, record the sql error number and contact Intrado support for further assistance. During a FR/DBMS to CRIS database comparison, the telephone record is present in the 2000 service order database but not in the FR/DBMS database. The function of change for this error code is (I)nsert so that the record can be added to the FR/DBMS database, if desired During a service order to FR/DBMS database comparison, the customer name field did not match During a service order to FR/DBMS database comparison, the customer codes did not match. During a service order to FR/DBMS database comparison, the street addresses did not match This comparison includes the following fields: house number, house number suffix, prefix directional, street name, and suffix directional During a service order to FR/DBMS database comparison, the community names did not match During a service order to FR/DBMS database comparison, the class of service did not match During a service order to FR/DBMS database comparison, the type of service did not match During a service order to FR/DBMS database comparison, the main telephone numbers do not match During a service order to FR/DBMS database comparison, the location field does not match During a service order to FR/DBMS database comparison, a telephone number was found in the FR/DBMS database that was not present in the service order database A service order source name is required. This field is used to access all of the options for the service order processor Service order data file name is required. This field is necessary to determine what file should be used as input for the service order processor The default state name is a required field. This value will be used for any records that are processed without a state name value. An entry has been made to the PSAP configuration that does not allow any values to be displayed. This implies that the end user would not be able to see any data at all. Since this 2013 entry does not seem logical it is not allowed. If you do not want the end user to see any data turn off the appropriate feature, i.e. supplemental data, msag mail, or misroutes by setting those values to no. Otherwise at least one entry for the telephone record field should be set to yes. An entry has been made to the MUNI configuration that does not allow any values to be displayed. This implies that the end user is not allowed to see any data at all. Since this entry 2014 does not seem logical it is not allowed. If you do not want the end user to see any data at all turn off the appropriate feature, i.e. supplemental data, MSAG mail, or misroutes by setting these values to no. Otherwise at least one entry for the telephone record field should be set to yes No service order sources currently exist. At least one service order source must be defined before the service order processor can be run No records held for this ESSID. The ESSID chosen does not have any held records associated with it. E911 Error Codes Page 12 of 13 10/25/2004

13 No PSAP ID's were found in the ESN/ESSID assignment table. Use the user management menu for PSAP configuration to setup a PSAP and make sure there Is an ESN/ESSID assignment for each PSAP defined. If the PSAP is configured and an ESN/ESSID assignment exists and this error still occurs, call Intrado support. Illegal character in the user name field. The only characters allowed in this field are letters of the alphabet, spaces or the underscore character "_". Illegal character. Only the following characters are valid input: letter of the alphabet, number, underscore (_) or space ( ). Cannot reverse records from multiple databases. When you entered the History command, you selected a database. One or more of the records you are trying to reverse originated from a database other than the one you selected. Reselect your records and be sure the query by example is constructed in such a way as to include only records from the database you selected. Internal SQL error. An internal Informix SQL error has occurred during this operation. Additional information regarding this error has been placed in /dms/log/dms.log. Call your FR/DBMS administrator for further assistance. Database name is invalid. Database name does not match any name known to the system. Call you FR/DBMS administrator for further assistance. E911 Error Codes Page 13 of 13 10/25/2004