Message Help 1500-2299

ERROR	DESCRIPTION	PROBABLE CAUSE	CORRECTIVE ACTION

ERROR	DESCRIPTION	PROBABLE CAUSE	CORRECTIVE ACTION
1500 ERROR: NMFS Person Name is invalid
1501 ERROR: NMFS Person Name is too long
1502 ERROR: IFQ Permit Holder Name is required
1503 ERROR: IFQ Permit Holder Name is invalid
1504 ERROR: IFQ Permit Holder Name is too long
1505 ERROR: IFQ Permit Class is required
1506 ERROR: IFQ Permit Class CLASS is invalid where: CLASS is The one character IFQ permit class code.
1507 ERROR: IFQ Permit Class is too long
1508 ERROR: Agency Stat Area is required
1509 ERROR: Agency Stat Area STAT_AREA is invalid where: STAT_AREA is The ADF&G Statistical Area identifier.
1510 ERROR: UNIT_OF_EFFORT must be greater than zero where: UNIT_OF_EFFORT is The unit of measurement for effort for the gear type, such as number of pot lifts for pot gear.
1511 ERROR: UNIT_OF_EFFORT cannot be greater than MAX where: UNIT_OF_EFFORT is The unit of measurement for effort for the gear type, such as number of pot lifts for pot gear. MAX is The maximum number.
1512 ERROR: UNIT_OF_EFFORT is required where: UNIT_OF_EFFORT is The unit of measurement for effort for the gear type, such as number of pot lifts for pot gear.
1513 ERROR: UNIT_OF_EFFORT must be numeric where: UNIT_OF_EFFORT is The unit of measurement for effort for the gear type, such as number of pot lifts for pot gear.
1514 ERROR: All Agency Stat Area Worksheet Lines but one need percent entered
1515 ERROR: Species CODE is not a valid crab IFQ species where: CODE is The numeric disposition code, indicating what is being done with the catch.	For crab IFQ reporting five species are valid: Red King crab, Blue King crab, Golden King crab, Opilio snow crab, and Bairdi tanner crab. No other crab species can be entered for IFQ reports.	The species entered is not a crab species, or it is not a species that is managed under an IFQ program.	Enter the correct species code.
1516 ERROR: NMFS RAM IFQ System communications error: MSG where: MSG is The Java Exception message.	When IFQ reports are submitted on the eLandings system the reports are sent to the NMFS RAM IFQ system and the transaction results are returned so that IFQ receipts can be printed. This message results if the NMFS RAM IFQ system experiences problems or the communications link between the eLanding System and the NMFS RAM IFQ system is unable to handle the transactions properly.	Technical communication problems between component parts of the eLandings system. More specifically, network problems between the eLandings system and the NMFS IFQ system, or issues with firewalls, proxies, web services configurations, or Oracle packages called by web services.	Contact eLandings support to resolve the problem and/or NMFS Enforcement to complete a manual IFQ landing report. In some cases the system problem can be resolved and the IFQ report can be submitted like normal. In other cases manual IFQ landing reports must be made by phone to the NMFS Enforcement Data Technicians.
1517 ERROR: Estimated weights are not allowed on final reports	Itemized catch line weights may be entered as estimated weights in certain cases when vessels are unloaded by the catch is not weight until processing. Initial landing reports may have estimated weights, but they must be reentered as scale weights before the landing report can be submitted as a final landing report.	At least one itemized catch line has its weight modifier field set to indicate that the weight for the item is estimated rather than a scale weight. Alternately, you entered scale weights for the itemized catch lines, but forgot to reset the weight modifier.	Enter scale weights for all itemized catch line items, and reset the weight modifier to blank.
1518 ERROR: Unsubmitted IFQ reports are not allowed on final Landing Reports	You were trying to submit a final report for a landing and it had unsubmitted IFQ reports.	The landing report had issues with IFQ reporting and the IFQ reports were submitted as manual landings over the phone with the NMFS Data Technicians. Alternately, the landing report has been submitted, the IFQ reports are ready to submit, and you were trying to submit the report as a final landing report before you submitted the IFQ reports.	Submit the IFQ reports if IFQ reporting has not been done via a manual landing. If a manual landing has been done with NMFS Enforcement then remove all unsubmitted IFQ reports. Use the 'Edit IFQ Reports' page to access the IFQ Reports entry page and then 'Remove Unsubmitted Reports'.
1519 ERROR: Batch Year is required	The batch year is required data and must be entered.	Batch data was being added to a landing report and no batch year was provided.	Enter a valid batch year. Alternately, set default batch information before saving landing report information.
1520 ERROR: Batch Year YEAR is invalid where: YEAR is The earliest year allowed to be entered.	The batch year entered is not valid.	The batch year is not numeric, is a year in the future, or is too long ago in the past.	Enter a valid batch year. Alternately, set default batch information before saving landing report information.
1521 ERROR: Batch Office Code is required	The batch office code is required data, and must be entered. Office codes are ADF&G office codes.	Batch data was being added to a landing report and no office code was provided.	Enter a valid office code. Alternately, set default batch information before saving landing report information.
1522 ERROR: Batch Office Code CODE is invalid where: CODE is The numeric disposition code, indicating what is being done with the catch.	The office code entered is not valid.	The office code entered is not numeric, is zero or less, or is greater than 99.	Enter a valid office code. Alternately, set default batch information before saving landing report information.
1523 ERROR: Amount is required	The paper fish ticket line item amount was required, and was not provided.	Amount was not entered.	Enter an amount.
1524 ERROR: Amount must be numeric	The paper fish ticket line item amount was not numeric.	Amount was entered with non-digit data. Amount must be a number. It can include decimal points.	Enter a numeric amount.
1525 ERROR: Amount cannot be negative
1526 ERROR: Amount is too large
1527 ERROR: Agency Stat Area AREA not in effect for date DATE where: AREA is The IPHC Regulatory Area. DATE is The date entered for the announcement.	The statistical area was not valid at the time the report was made. The date of the report is the date of landing for landing reports. For production reports it is the report date.
1528 ERROR: Vehicle License Number should not be entered for OP_TYPE operations where: OP_TYPE is The name of the operation type.	A vehicle license number are only used for Buying Station operations.	A vehicle license number was entered for an operation that is not a buying station.	Remove the vehicle license number from the operation data. If the operation is a new operation and it is a buying station change its type to Buying Station.
1529 ERROR: UNIT_OF_EFFORT cannot be entered if no stat area is entered where: UNIT_OF_EFFORT is The unit of measurement for effort for the gear type, such as number of pot lifts for pot gear.	Effort information must be reported by statistical area. Effort, such as pot lifts for crab, has no meaning with out the provided statistical area.	Effort was entered for the report line, but no statistical area was entered.	Remove the effort entered or enter a statistical area.
1530 ERROR: UNIT_OF_EFFORT cannot be entered, STAT_AREA is entered in Stat Area Worksheet where: UNIT_OF_EFFORT is The unit of measurement for effort for the gear type, such as number of pot lifts for pot gear. STAT_AREA is The ADF&G Statistical Area identifier.
1531 ERROR: Agency UNIT_OF_EFFORT cannot be entered if no stat area is entered where: UNIT_OF_EFFORT is The unit of measurement for effort for the gear type, such as number of pot lifts for pot gear.
1532 ERROR: Agency UNIT_OF_EFFORT cannot be entered, STAT_AREA is entered in agency Stat Area Worksheet where: UNIT_OF_EFFORT is The unit of measurement for effort for the gear type, such as number of pot lifts for pot gear. STAT_AREA is The ADF&G Statistical Area identifier.
1533 ERROR: Lookup ID is required
1534 ERROR: Lookup ID LOOKUP_ID is invalid where: LOOKUP_ID is The message lookup ID number
1535 ERROR: Species Code SPECIES_CODE cannot be used in Production Reports where: SPECIES_CODE is The numeric species code.	The species code entered is not setup to be used on production reports.	You entered a line on a production report with for a species that is a valid species, but that is not eligible for production reports. The species code may have been mistyped.	Enter the correct species code or remove the line for the species code from the report.
1536 ERROR: Product Code PRODUCT_CODE cannot be used in Production Reports where: PRODUCT_CODE is The product code.	The product code entered is not setup to be used on production reports.	You entered a line on a production report with for a product code that is a valid code but that is not eligible for production reports. The product code may have been mistyped.	Enter the correct product code or remove the line for the product code from the report.
1537 ERROR: Comment Code COMMENT_CODE is not valid with Condition Code CONDITION_CODE where: COMMENT_CODE is The comment type identifier. CONDITION_CODE is The numeric condition code.
1538 ERROR: Comment Code COMMENT_CODE is not valid with Disposition Code DISPOSITION_CODE where: COMMENT_CODE is The comment type identifier. DISPOSITION_CODE is The numeric disposition code, indicating what is being done with the catch.
1539 ERROR: Comment Code COMMENT_CODE is not valid with Species Code SPECIES_CODE where: COMMENT_CODE is The comment type identifier. SPECIES_CODE is The numeric species code.
1540 ERROR: Comment Text is required
1541 ERROR: User USER_ID is not authorized to view Production Report REPORT_ID where: USER_ID is The eLandings system user ID. REPORT_ID is The eLandings landing report ID
1542 ERROR: Statistical Area STAT_AREA is entered with UNITS on multiple lines for the same species and Fish Ticket where: STAT_AREA is The ADF&G Statistical Area identifier. UNITS is The unit for counting the number of animals in the catch, such as fish or crab.	On the itemized catch lines, effort is not always a required field. If there is effort information, please report it as the system allows. For some disposition codes, you will not enter effort, if there are multiple line items with the same species code, stat area, and fish ticket.	Effort was entered for multiple line items with the same species code, stat area, and fish ticket. The convention is enter the effort for the sold items (i.e. disposition of 60) and do not enter effort for the personal use items (i.e. disposition 95).	Review effort information for all line items, make corrections as necessary. Leave all dispositions blank for a line items with the same species code, stat area, and fish ticket except for one, usually the sold item.
1543 ERROR: IFQ Reports not allowed on reports with confiscated catch
1544 WARNING: SPECIES overages should not be retained for bait where: SPECIES is The species code.
1545 WARNING: Some of the search criteria specified cannot be used to search for unsubmitted reports, so unsubmitted reports will not be filtered by this criteria.	The system does not allow unsubmitted reports to be filtered by fish ticket number or port code, so unsubmitted reports will be displayed with this criteria; however, other criteria can be entered to filter these unsubmitted reports. Reports with a status other than unsubmitted will be filtered by this criteria.	This warning is generated when a fish ticket number or a port code is entered.	No action is necessary for this warning. If you can not find the report you are searching for, enter more criteria to narrow your results.
1546 ERROR: Product Type PROD_TYPE is not allowed for Product Code PROD_CODE where: PROD_TYPE is The product type, either P for primary or A for ancillary. PROD_CODE is The product code.	The Product Types: primary designated product (P) or ancillary secondary product (A) must be compatible with the Product Code. For example: Product Type 'P' is valid with Product Code '23 - filets, skinless/bone' because filets are a primary product. Product Type 'A' is valid with Product Code '16 - heads only' because heads are an ancillary product. Some products like '14 - roe only' can have a Product Type of 'P' or 'A'.	An invalid combination of Product Type and Product Code was input.	Review the Product Type and Product Code and correct one or the other so they are compatible.
1547 ERROR: UNITS are required for statistical area STAT_AREA where: UNITS is The unit for counting the number of animals in the catch, such as fish or crab. STAT_AREA is The ADF&G Statistical Area identifier.
1548 ERROR: UNITS are required for agency statistical area STAT_AREA where: UNITS is The unit for counting the number of animals in the catch, such as fish or crab. STAT_AREA is The ADF&G Statistical Area identifier.
1549 ERROR: Agency override statistical area STAT_AREA is entered with UNITS on multiple lines for the same species where: STAT_AREA is The ADF&G Statistical Area identifier. UNITS is The unit for counting the number of animals in the catch, such as fish or crab.
1550 ERROR: Percent add up to more than 100 percent
1551 ERROR: Percent do not add up to 100 percent
1552 ERROR: All lines must have percent entered
1553 ERROR: Weights add up to more than itemized catch line weight
1554 ERROR: Weights do not add up to itemized catch line weight
1555 ERROR: All lines must have weight entered
1556 ERROR: Pre-printed ticket TICKET_NUMBER is invalid where: TICKET_NUMBER is The pre-printed ticket number.	The system expects a pre-printed fish ticket number in the form of a leading letter with two digits, a space, and six more following digits. Examples of this are G03 394820, A99 999999, and Z00 000000. The letter is associated with the type of report, the following two digits are the year of the landing report, and the last two digits is a sequential number.	The pre-printed fish ticket number entered is not in the correct format.	Verify the fish ticket number, and enter the value in the correct format.
1557 ERROR: No CFEC Permits found that match search criteria
1558 ERROR: No Vessels found that match search criteria
1559 ERROR: CFEC permit holder name is required
1560 ERROR: CFEC permit holder name cannot be longer than MAX_SIZE characters where: MAX_SIZE is The maximum number of characters that can be stored in the database for the field.
1561 ERROR: CFEC serial number is required
1562 ERROR: CFEC serial number SERIAL_NUMBER is invalid where: SERIAL_NUMBER is The serial number on the CFEC permit
1563 ERROR: Vessel name is required
1564 ERROR: Vessel name cannot be longer than MAX_SIZE characters where: MAX_SIZE is The maximum number of characters that can be stored in the database for the field.
1565 ERROR: Search criteria must be entered	Search criteria is required to perform a search on this panel.	The search criteria was omitted.	Enter search criteria and try again.
1566 ERROR: Search returned too many records to display. Refine search criteria to limit results
1567 ERROR: No data found that match search criteria	No information was found.	The search criteria does not match any information in the database.	Verify the search criteria used and try again or try different criteria.
1568 ERROR: Message ID MSG_ID is invalid where: MSG_ID is The unique message identifier.
1569 ERROR: Message ID is required
1570 ERROR: Message severity is required
1571 ERROR: Message severity SEVERITY is invalid where: SEVERITY is The message severity, S for System Error, E for error, W for warning, or I for information
1572 ERROR: Message text is required
1573 ERROR: Message description is too long
1574 ERROR: Message probable causes is too long
1575 ERROR: Message corrective action is too long
1576 ERROR: Message substitution tag is required
1577 ERROR: Message substitution tag is too long
1578 ERROR: Message substitution tag TAG is invalid where: TAG is The substitution tag that will be replace in the message data with the actual value
1579 ERROR: Message substitution tag description is require
1580 ERROR: Message substitution tag description is too long
1581 ERROR: Message text is too long
1582 ERROR: Message probable causes is required
1583 ERROR: Message corrective action is required