Message Help

1000 ERROR: Phone Number is required

Phone number is required information and must be entered.

The page, window, or web service requires Phone Number, and no data was provided.

Enter a phone number.

1001 ERROR: Phone Number must be in the format (xxx) xxx-xxxx

The phone number was entered in a format that was not recognized. This message can also be seen if the phone number is entered with letters in place of digits.

The phone number is stored in the format (aaa) eee-nnnn xxx... where aaa is the area code, eee is the exchange, nnnn is the number, and xxx... is the extension. Extension is optional. The system will accept the phone number in several commonly used formats, and will convert to the standard format. Valid entry format masks are (999) 999-9999, 999-999-9999, 999.999.9999, and (999)999-9999. The phone number does not match one of these valid formats.

Enter the phone number in the standard format, using digits.

1002 ERROR: Phone Number is too long

More than 32 characters were entered in the phone number field.

Phone numbers are limited to 32 characters, up to 15 for the formatted phone number and the rest for the extension. Too many characters were entered for the extension. This error can also occur if other data was entered in the phone number field.

Enter the phone number in the standard format, and limit the extension to the allowable number of characters.

1003 ERROR: Fax Number must be in the format (xxx) xxx-xxxx

The fax phone number was entered in a format that was not recognized. This message can also be seen if the fax phone number is entered with letters in place of digits.

The fax phone number is stored in the format (aaa) eee-nnnn xxx... where aaa is the area code, eee is the exchange, nnnn is the number, and xxx... is the extension. Extension is optional. The system will accept the fax phone number in several commonly used formats, and will convert to the standard format. Valid entry format masks are (999) 999-9999, 999-999-9999, 999.999.9999, and (999)999-9999. The fax phone number does not match one of these valid formats.

Enter the fax phone number in the standard format, using digits.

1004 ERROR: Fax Number is required

Fax phone number is required information and must be entered.

The page, window, or web service requires Fax phone number, and no data was provided.

Enter a fax phone number.

1005 ERROR: Fax Number is too long

More than 32 characters were entered in the fax phone number field.

Fax phone numbers are limited to 32 characters, up to 15 for the formatted phone number and the rest for the extension. Too many characters were entered for the extension. This error can also occur if other data was entered in the fax phone number field.

Enter the fax phone number in the standard format, and limit the extension to the allowable number of characters.

1008 ERROR: Email Address is invalid

Email address is not valid.

The Email address entered has invalid characters or is otherwise invalid.

Enter a valid email address.

1009 ERROR: Email Address is required

Email address is required information and must be entered.

The page, window, or web services requires Email address, and no data was provided.

Enter an email address.

1010 ERROR: Email Address is too long

More than 120 characters were entered in the email address field.

Too many characters were entered for the email address. This error can also occur if other data was entered in the email address field.

Check the email address to make sure it was entered correctly. If the email address has more than 120 characters check with your email provider customer service representative to see if a shorter alias can be used.

1011 ERROR: Email Address must be in the format uuuu@ssss.ddd

The email address was entered in a format that was not recognized.

Email addresses must contain a mail account name, followed by the @ sign, followed by a mail domain. The mail domain must contain at least one dot. The mail address entered did not conform to this format.

Check the email address to make sure it was entered correctly. Some internal mail systems do not require the @ sign and mail domain, or may have a mail domain without a dot. The eLandings system cannot use these email addresses. Check with your network administrator for an Internet email address to use.

1012 ERROR: Userid is required

UserID is required information and must be entered.

You were trying to login and did not provide your UserID, you were trying to create a new UserID and did not provide a value for the new ID, or you were requesting a password without entering the user ID.

Enter a UserID.

1013 ERROR: Userid cannot be all numbers

UserID cannot be all numbers.

You were trying to create a new UserID and entered a number for the new ID. Alternately, you were trying to login and misentered numeric data in the UserID field.

Enter a correct existing UserID to login, or enter a non-numeric UserId to create a new one.

1014 ERROR: Userid is already in the database

The UserID value you are trying to create for a new user is already in use for an existing user.

You were trying to create a new user account and the UserID value you entered is already used by another account.

Make sure you or someone else has not already requested an account for the user. Otherwise, choose a different UserID for the user.

1015 ERROR: Userid cannot be more than 40 characters

More than 40 characters were entered in the userid field.

Too many characters were entered for the UserID. This error can occur if other data is misentered in the UserID field.

Check the UserID to make sure it was correctly entered. If creating a new user choose a shorter UserID.

1016 ERROR:  PSW_TYPE Password is required where:  PSW_TYPE  is The type of password, either old or new, or blank.

Password is required information and must be entered.

You were trying to login and did not provide your password. Alternately, you were creating a new user account and did not provide a password.

Enter a password.

1017 ERROR:  PSW_TYPE Password must be at least  MIN_LEN  characters where:  MIN_LEN  is The minimum length of the field PSW_TYPE  is The type of password, either old or new, or blank.

Less than 6 characters were entered in the password field.

When trying to login, change a password, or create a new user account, you entered less than 6 characters in the password field.

Enter a valid password.

1018 ERROR:  PSW_TYPE Password cannot be longer than  MIN_LEN  characters where:  MIN_LEN  is The minimum length of the field PSW_TYPE  is The type of password, either old or new, or blank.

More than 16 characters were entered in the password field

When trying to login, change a password, or create a new user account, you entered more than 16 characters in the password field. You can also get this error if you misenter other data in the password field.

Enter a valid password.

1019 ERROR:  PSW_TYPE Password cannot be all numbers where:  PSW_TYPE  is The type of password, either old or new, or blank.

A password was entered that is all numeric digits. For security reasons, passwords cannot be numbers as these are too easy to guess by trial and error.

When trying to login, change a password, or create a new user account, you entered a password that was all numeric digits. You can also get this error if you misenter other data in the password field.

Enter a valid password.

1020 ERROR: User ID cannot be used as a part of Password

A password was entered that is the same as the UserID, or contains the UserID. For security reasons, this is not allowed, because it makes the password too easy to guess.

When trying to login, change a password, or create a new user account, you entered a password that was the same as the userid, or matched the userid with extra characters on the end or beginning.

Enter a valid password.

1021 ERROR: New password cannot be the same as old password

When changing a password, the new password and the old password were the same, so the password would not have changed.

When trying to change a password the value entered was the same as the old password.

Enter a new, valid password.

1022 ERROR: User Name is required

User name is required information and must be entered

You were trying to create or edit a user account and did not provide a name for the user.

Enter a name for the user. The name should be the person's name, not a company name.

1023 ERROR: User Name cannot be longer than 32 characters

More than 32 characters were entered in the user name field.

You were trying to create or edit a user account, and entered too much data in the user name field. You can also get this error if you misentered other data in the user name field

Enter the correct user name. It should be the person's name, not a company name. Abbreviate if necessary.

1024 ERROR: Agency name is required

Agency name is required information and must be entered.

You were trying to create an agency user account and did not provide the agency name.

Enter the correct agency abbrevation, such as ADFG, NMFS, or IPHC in the agency name field.

1025 ERROR: Agency  AGENCY_NAME  is not valid where:  AGENCY_NAME  is The agency abbreviation.

The agency name entered is not a recognized agency name.

Agency names are stored in the system code manager. The value you entered was not in the system's code set. 

Check that the agency name you entered was a correct agency abbreviation, such as ADFG, NMFS, or IPHC. If you have another agency name you believe should be valid check with eLandings system support.

1026 ERROR: Processor company name is required

The processor company name is required information, and must be entered.

You were trying to create or edit a user account and did not provide a company name for the user.

Enter a company name for the user. The processor company name should be the primary company where the user is an employee or hired contractor, even if they will be entering landing reports for multiple operations, as in the case of custom processing.

1027 ERROR: Processor company cannot be longer than 32 characters

More than 32 characters were entered in the processor company name field

When trying to create or edit a user account the processor name was too long. You can also get this error by misentering other data in the processor company name field.

Check that the processor company name is correct. Abbreviate if necessary.

1028 ERROR: Parent company name is required

The processor parent company name is required information, and must be entered.

You were trying to create or edit a user account and did not provide a parent company name for the user.

Enter a parent company name for the user. The parent company name should be the parent company of the primary company where the user is an employee or hired contractor, even if they will be entering landing reports for multiple operations, as in the case of custom processing.

1029 ERROR: Parent company cannot be longer than 32 characters

More than 32 characters were entered in the parent company name field

When trying to create or edit a user account the parent company name was too long. You can also get this error by misentering other data in the parent company name field.

Check that the parent company name is correct. Abbreviate if necessary.

1030 ERROR: City is required

City is required information and must be entered

You were trying to create or edit a user account and did not provide a city.

Enter the city.

1031 ERROR: City cannot be longer than 50 characters

More than 50 characters were entered in the city field

When trying to create or edit a user account the city was too long. You can also get this error by misentering other data in the city field.

Check the city name for the user is correct. Abbreviate if necessary.

1032 ERROR: State is required

State is required information and must be entered.

When trying to create or edit a user account and did not provide a state.

Enter the state.

1033 ERROR: State must be a two character state code

The state entered was not a valid two character State code.

When trying to create or edit a user account the state code was not valid. Typically this is because you entered more than the two character state abbreviation. You can also get this error by misentering other data in the state field.

Enter the correct two character abbrevation for the State.

1034 ERROR: Security question is required

The security question is required information, and must be entered.

The security question is used if the user forgets their password and must request it be reset by an agency user. For security reason, each user needs a security question and answer on file.

Enter a security question that the user will know the answer to, but that would be difficult for anyone else to answer.

1035 ERROR: Security question cannot be longer than 500 characters

More than 500 characters were entered in the security question field

When trying to create a user account the security question was too long.

Enter a shorter security question. The question should be one that the user will be unlikely to forget the answer to, but that anyone else would have a hard time answering correctly.

1036 ERROR: Secret answer is required

The secret answer is required information, and must be entered

The secret answer is used if the user forgets their password and must request it be reset by an agency user. It is the answer to the security question. For security reason, each user needs a security question and answer on file.

Enter the answer to the security question.

1037 ERROR: Secret answer cannot be longer than 500 characters

More than 500 characters were entered in the secret answer field

When trying to create a user account the secret answer was too long.

Enter a shorter secret answer, abbreviating if necessary. The security question that the secret answer answers should be one that the user will be unlikely to forget the answer to, but that anyone else would have a hard time answering correctly.

1038 ERROR: Port Code is required

The port code is required information and must be entered. Port codes are the ADF&G alphanumeric port codes. NMFS port codes and IFQ numeric port codes cannot be entered, the system will translate the entered ADF&G port code to the correct NMFS and IFQ values where needed.

Port code is required for most operations, all landing reports, and at-sea production reports.

Enter a valid three character ADF&G port code. The valid port codes can be looked up on the eLandings website.

1039 ERROR: Port Code  PORT_CODE  is invalid.  This must be the three letter alphabetic port code where:  PORT_CODE  is The ADF&G alphabetic port code.

The port code entered is not a valid ADF&G port code. Port codes are the ADF&G alphanumeric port codes. NMFS port codes and IFQ numeric port codes cannot be entered, the system will translate the entered ADF&G port code to the correct NMFS and IFQ values where needed.

The port codes are stored in the database. The value entered does not match any of the stored port codes.  

Enter a valid three character ADF&G port code. The valid port codes can be looked up on the eLandings website.

1040 ERROR: Vessel ADF&G Number is required

The ADF&G vessel number is required information and must be entered. ADF&G vessel numbers are five digit numbers issued by the Commercial Fisheries Entry Commission (CFEC).

Vessel ADF&G numbers are required for at-sea and tender operation setups, landing reports, and at-sea production reports.

Enter a valid ADF&G vessel number. Leading zeroes are not required, but may be entered.

1041 ERROR: ADF&G Vessel Number  VESSEL_NUM  is not valid where:  VESSEL_NUM  is The ADF&G Vessel number, issued by CFEC.

The ADF&G vessel number entered was not found in the database.

The vessel ADF&G numbers are stored in the database. They are issued by CFEC, and are updated daily. The vessel ADF&G number can be at most 5 characters.

Enter a valid ADF&G vessel number. Leading zeroes are not required, but may be entered. If you are sure the vessel number is the correct one for the vessel, contact eLandings system support.

1042 ERROR: Processor Code is required

The ADF&G processor code is required information and must be entered. ADF&G processor code is also know as the proc code, F-code, or Intent to Operate code. It is a five or six character identifier, where the first character is a letter, most commonly the letter F, followed by four numeric digits.

ADF&G processor code is required for landing reports, for shoreside plant production reports, and for the setup of most types of operations. 

Enter a valid ADF&G processor code.

1043 ERROR: Processor Code  PROC_CODE  is not valid where:  PROC_CODE  is The ADF&G Processor Code, also know as the F-code.

The ADF&G processor code entered was not found in the database. ADF&G processor code is also know as the proc code, F-code, or Intent to Operate code. It is a five or six character identifier, where the first character is a letter, most commonly the letter F, followed by four numeric digits.

The ADF&G processor codes are stored in the database. They are issued by ADF&G, and are updated daily. To be valid the proc code must be in the database.

Enter a valid ADF&G processor code. If you are sure the proc code you entered is correct, contact eLandings system support.

1044 ERROR: Security question is invalid

The security question is required information, and cannot contain special characters that are restricted due to scripting concerns.

The security question is used if the user forgets their password and must request it be reset by an agency user. For security reason, each user needs a security question and answer on file.

Enter a security question that the user will know the answer to, but that would be difficult for anyone else to answer. Do not use special characters.

1045 ERROR: Secret answer is invalid

The secret answer is required information, and cannot contain special characters that are restricted due to scripting concerns.

The secret answer is used if the user forgets their password and must request it be reset by an agency user. It is the answer to the security question. For security reason, each user needs a security question and answer on file.

Enter the answer to the security question, without using special characters.

1046 ERROR: Federal Permit Number is required

The Federal Permit number is required information for production reports and some landing reports. Federal Permit Numbers may be Federal Fisheries Permit numbers or Federal Processor Permit Numbers.

The Federal Permit number is require for some landing reports, for production reports, and for the setup of some types of operations

Enter a valid FFP or FPP number.

1047 ERROR: Federal Permit Number  FED_PROC_NUM  is not valid where:  FED_PROC_NUM  is The Federal Processor Permit Number.

The Federal Permit number is required information for production reports and some landing reports. Federal Permit Numbers may be Federal Fisheries Permit numbers or Federal Processor Permit Numbers. The Federal Permit Numbers are stored in the database and the entered number is compared to the database records.

The Federal Permit number entered was not found in the database.

Enter a valid FFP or FPP number.

1050 ERROR: Registered Buyer Number is required

Registered buyer number is required information and must be entered, if the species is either halibut or sablefish.  A default value is set by your user agreement registration, and if there is more than one registered buyer number number associated with your user agreement, select the correct one.

Registered buyer number number was switched to a blank value.

Verify that the registered buyer number number is set to the correct value, and select the correct value.

1051 ERROR: Registered Buyer Number  REG_BUYER_NUM  is not valid where:  REG_BUYER_NUM  is The NMFS Restricted Access Management Division registered buyer number for halibut and sablefish IFQ.

The registered buyer number entered was not found in the database.

The registered buyer number entered is not valid.  You may have mistyped the registered buyer number; or the permit was issued after the last database update (within the last few hours).

Verify your registered buyer number, and enter the correct value.  If this is unsuccessful, you may call NMFS Data Technicians: 1-800-304-4846, option 1.

1054 ERROR: Registered Crab Receiver Number is required

Registered crab receiver number is required information and must be entered for a crab landing report.  A default value is set by your user agreement registration, and if there is more than one registered crab receiver number associated with your user agreement, select the correct one.

Registered crab receiver number was switched to a blank value.

Verify that the registered crab receiver number is set to the correct value.  Select the correct value.

1055 ERROR: Registered Crab Receiver Number  RCR_NUM  is not valid where:  RCR_NUM  is The NMFS Restricted Access Management Division registered crab receiver number for crab IFQ.

The registered crab receiver number entered was not found in the database.

The registered crab receiver number entered is not valid.  You may have mistyped the registered crab receiver number; or the permit may have been issued after the last database update (within the last few hours).

Verify your registered crab receiver number, and enter the correct value.  If this is unsuccessful, you may call NMFS Data Technicians: 1-800-304-4846, option 1.

1059 ERROR: Landing report with no line items cannot be submitted

The system does not allow initial or final reports to be submitted without line item information.  Line item information includes stat areas, species codes, condition codes, weight, number of animals, pot lifts, and disposition codes;  number of animals and pot lifts are not always required or applicable.  When a sold disposition code is entered, line item information also includes size/grade, sold weight, and price per pound;  size/grade is not required.

There is no information for line items and submit an initial or final report was selected.

Verify line item information, and enter the correct values.

1060 ERROR: Trip Number is required

Trip number is required information and must be entered.  The system requires a whole numeric value between one and 10,000,000,000.

Trip number was not entered.

Verify the trip number, and enter the correct value.

1061 ERROR: Trip Number must be numeric

The system requires a whole numeric value between one and 10,000,000,000.

The trip number entered is not a whole numeric value between one and 10,000,000,000.

Verify the trip number, and enter the correct whole numeric value between one and 10,000,000,000.

1062 ERROR: Trip Number  TRIP_NUMBER  is invalid where:  TRIP_NUMBER  is The trip identifing number for the vessel.

The system requires a whole numeric value between one and 10,000,000,000.

The trip number entered is not a whole numeric value between one and 10,000,000,000.

Verify the trip number, and enter a whole numeric value between one and 10,000,000,000.

1063 ERROR: Report Type is required

1064 ERROR: Report Type  REPORT_TYPE  is invalid where:  REPORT_TYPE  is The landing report type such as C for Crab or G for groundfish.

1065 ERROR: Gear Code is required

The gear code is required information and must be entered.  Gear codes can be found on the eLandings website.

The gear code was not entered.

Verify the gear code, and enter the correct value.

1066 ERROR: Gear Code  GEAR_CODE  is not valid for crab where:  GEAR_CODE  is The numeric gear code.

The ADF&G gear code must be valid for crab if the report type is a Crab Landing Report.  Gear Codes can be looked up on the eLandings website.

The ADF&G gear code entered is not correct for the gear used, or the wrong landing report type was chosen.

Verify the ADF&G gear code, and enter the correct code.  Verify that the correct landing report type is being used.

1067 ERROR: Gear Code  GEAR_CODE  is not valid where:  GEAR_CODE  is The numeric gear code.

The ADF&G gear code entered was not found in the database.  The ADF&G gear code is a numeric value one or two digits long.  Leading zeroes are not required, but may be entered.  Gear codes can be found on the eLandings website.

The ADF&G gear codes are stored in the database.

Verify the gear code, and enter a valid ADF&G gear code.

1068 ERROR: Crew Size is required

Crew size is required information and must be entered.  The system expects a whole numeric value between one and 500.

The crew size was not entered.

Verify the crew size, and enter the correct value.

1069 ERROR: Crew Size must be a whole number

The system expects a whole numeric value between one and 500.

Data other than numbers have been entered in the crew size field.

Verify the crew size, and enter the correct value.

1070 ERROR: Crew Size cannot be less than one. Crew Size includes the skipper

The system expects a whole numeric value between one and 500.

The crew size entered is less than one.

Verify the crew size, and enter the correct value.

1071 ERROR: Crew Size cannot be greater than  MAX_SIZE  where:  MAX_SIZE  is The maximum number of characters that can be stored in the database for the field.

The system does not allow crew size to be greater than 500.  The system expects a whole numeric value between one and 500.

The crew size entered is greater than 500.

Verify the crew size, and enter a valid numeric value, between one and 500.  If you are sure of your crew size, contact eLandings support to resolve the problem.

1072 WARNING: Crew Size is greater than  MAX_SIZE . Is that right? where:  MAX_SIZE  is The maximum number of characters that can be stored in the database for the field.

This warning is generated when the crew size is between the maximum expected number of 99 and the maximum number of 500.  The system will let you continue when you select Save Ignoring Warnings.  This button only appears when no errors are generated with the warnings.

The Crew Size entered is between the maximum expected number of 99 and the maximum number of 500.

Verify that the Crew Size is correct, and if it is select Save Ignoring Warnings at the bottom of the website.  If the crew size is not correct, enter the correct crew size and select Save.

1073 ERROR: The number of Observers Onboard is required

The number of Observers Onboard is required information and must be entered.  The system expects a whole numeric value between zero and 20.

Number of Observers Onboard was not entered.

Verify the number of Observers Onboard, and enter the correct value.  If no observer was onboard, enter zero.

1074 ERROR: Observers Onboard must be a whole number

The system expects a whole numeric value between one and 20.

The observers onboard entered is not numeric.

Verify the observers onboard field, and enter the correct value.

1075 ERROR: Observers Onboard cannot be less than zero.

The system does not allow the number of observers onboard to be less than zero.

A negative number was entered, such as: -1, -5, and -20.

Verify the amount of observers onboard, and enter the correct value.

1076 ERROR: Observers Onboard cannot be greater than  MAX_SIZE  where:  MAX_SIZE  is The maximum number of characters that can be stored in the database for the field.

The system does not allow amount of observers onboard to be greater than 20.  The system expects a whole numeric value between one and 20.

The amount of observers onboard entered is greater than 20.

Verify the amount of observers onboard, and enter the correct value.  If you are sure of the amount of observers onboard, contact eLandings support to resolve the problem.

1077 WARNING: Observers Onboard is greater than  MAX_SIZE . Is that right? where:  MAX_SIZE  is The maximum number of characters that can be stored in the database for the field.

This warning is generated when the observers onboard is between the maximum expected number of three and the maximum number of 20.  The system will let you continue when you select Save Ignoring Warnings.  This button only appears when no errors are generated with the warnings.

The observers onboard entered is between the maximum expected number of three and the maximum number of 20.

Verify that the observers onboard is correct, and if it is select Save Ignoring Warnings at the bottom of the website.  If the observers onboard is not correct, enter the correct observers onboard and select Save.

1078 ERROR: Date Fishing Began is required

The date fishing began is required information and must be entered.

The date fishing began was not entered.

Verify the date fishing began, and enter the correct value.

1079 ERROR: Date Fishing Began is invalid

The system will accept the date in several commonly used formats, and will convert to the standard format.  The date fishing began field was not entered with one of the following formats:  mm/dd/yyyy, m/d/y, mmddyyyy, mm-dd-yyyy, m-d-y.

The date fishing began was entered in a format that was not recognized. This message can also be seen if the date fishing began is entered with letters in place of digits.

Verify the date fishing began, and enter the correct value.

1080 ERROR: Date Fishing Began requires four digit year

1081 ERROR: Date Fishing Began cannot be before this date in  YEAR  where:  YEAR  is The earliest year allowed to be entered.

The system restricts the date fishing began field from being dated more than six years in the past.

A date earlier than six years in the past has been entered in the date fishing began field.

Verify the date fishing began, and enter the correct value.

1082 ERROR: Date of Landing is required

The date of landing is required information and must be entered.

The date of landing field was not entered.

Verify the date of landing, and enter the correct value.

1083 ERROR: Date of Landing is invalid

The system will accept the date in several commonly used formats, and will convert to the standard format.  The date of landing field was not entered with one of the following formats:  mm/dd/yyyy, m/d/y, mmddyyyy, mm-dd-yyyy, m-d-y.

The date of landing was entered in a format that was not recognized.  This message can also be seen if the date of landing is entered with letters in place of digits.

Verify the date of landing, and enter the correct value.

1084 ERROR: Date of Landing cannot be in the future

The system does not allow a landing report to be completed before the date of landing.

A date that is in the future has been entered in the date of landing field.

Verify the date of landing, and enter the correct date.

1085 ERROR: Date of Landing requires four digit year

1086 ERROR: Date Fishing Began cannot be after Date of Landing

The system does not allow the date fishing began to be after the date of landing.

The date entered in the date fishing began field is after the date entered in the date of landing field.

Verify the date fishing began and the date of landing fields.  Enter the correct dates.

1087 ERROR: Time period between Date Fishing Began and Date of Landing cannot be more than 100 days

The system does not allow days fished to be greater than 100.  The system expects a whole numeric value between one and 100.

Days fished entered is greater than 100.

Verify the number of days fished, and enter the correct value.  If you are sure of your number of days fished, contact eLandings support to resolve the problem.

1088 WARNING: Time period between Date Fishing Began and Date of Landing is more than 60 days. Is that right?

This warning is generated when the number of days fished entered is between the maximum expected number of 60 and the maximum number of 100.  The system will let you continue when you select Save Ignoring Warnings.  This button only appears when no errors are generated with the warnings.

The number of days fished entered is between the maximum expected number of 60 and the maximum number of 100.

Verify that the number of days fished is correct, and if it is select Save Ignoring Warnings at the bottom of the website.  If the number of days fished is not correct, enter the correct days fished and select Save.

1089 ERROR: Days Fished must be a whole number

The system does not allow data other than numbers to be entered in the days fished field.

Data other than numbers have been entered in the days fished field.

Verify the days fished, and enter the correct value.

1090 ERROR: Days Fished is required

1091 ERROR: Days Fished cannot be less than one

The system does not allow the number of days fished to be less than 1.

A number less than 1 has been entered in the days fished field.

Verify the amount of days fished field, and enter the correct value.

1092 ERROR: Days Fished is more days than are between Date Fishing Began and Date of Landing

The system does not allow the number of days fished to be greater than the days between the date fishing began and the date of landing.

The days fished is greater than the days between the date fishing began and the date of landing.

Verify the days fished, date fishing began, and date of landing fields.  Enter the correct dates and correct number of days fished.

1093 ERROR: Nearest Bay or Headland is required

1094 ERROR: Nearest Bay or Headland cannot be longer than 50 characters

1095 WARNING: Nearest Bay or Headland should be text description, not GPS coordinates, numbers, or special characters

1096 ERROR: Owner Proc Code is required

The owner proc code is required information and must be entered.  ADF&G processor code is also know as the proc code, F-code, or Intent to Operate code. It is a five or six character identifier, where the first character is a letter, most commonly the letter F, followed by four numeric digits.

The owner proc Ccode was not entered.

Verify the owner proc code, and enter the correct value.

1097 ERROR: Owner Proc Code  OWNER_PROC_CODE  is not valid where:  OWNER_PROC_CODE  is The ADF&G Processor Code, also know as the F-code, of the person or company buying the catch.

The ADF&G processor code entered was not found in the database. ADF&G processor code is also know as the proc code, F-code, or Intent to Operate code. It is a five or six character identifier, where the first character is a letter, most commonly the letter F, followed by four numeric digits.

The owner processor code entered is not valid.

Verify the owner processor code, and enter the correct value.

1098 ERROR: Custom Processor Proc Code  PROCESSOR_PROC_CODE  is not valid where:  PROCESSOR_PROC_CODE  is The ADF&G Processor Code, also know as the F-code, of the company that is custom processing the catch.

The ADF&G processor code entered was not found in the database. ADF&G processor code is also know as the proc code, F-code, or Intent to Operate code. It is a five or six character identifier, where the first character is a letter, most commonly the letter F, followed by four numeric digits.

The custom processor code entered is not valid.

Verify the custom processor code, and enter the correct value.

1099 ERROR: Field Name is not valid

1100 ERROR: Discard Report Type Code  DISCARD_DESCRIPTION  is not valid where:  DISCARD_DESCRIPTION  is The discard report type

1101 ERROR: Permit Fishery is required

The CFEC fishery code is required information and must be entered.  Your CFEC fishery code is the first four or five digit code, in the fourth row, located on your CFEC permit card.

The CFEC fishery code was not entered.

Verify the CFEC fishery code on the CFEC permit card, and enter the correct code.

1102 ERROR: Permit Fishery  FISHERY  is invalid where:  FISHERY  is The CFEC fishery code that is on the CFEC permit card.

The CFEC fishery code entered was not found in the database.  Your CFEC fishery code is the first four or five digit code, in the fourth row, located on your CFEC permit card.

The CFEC fishery code entered on the CFEC Permit Worksheet is not valid.

Verify the CFEC fishery code on the CFEC permit card, and enter the correct code.

1103 ERROR: Permit Fishery  FISHERY  is not valid with gear type  GEAR_TYPE  where:  FISHERY  is The CFEC fishery code that is on the CFEC permit card. GEAR_TYPE  is The numeric gear code.

The CFEC fishery code does not match the gear type entered.  Your CFEC fishery code is the first four digit code, in the fourth row, located on your CFEC permit card.  Your issued CFEC permit card must be appropiate for the gear type.  Gear code can be looked up on the eLandings website.

The issued CFEC fishery code is not appropiate for the gear type entered, or the gear code entered is incorrect for your gear.

Verify the gear code, in the ADF&G Gear Code field, and enter the correct code.  Verify the CFEC fishery permit, on the CFEC permit card, and enter the correct code.

1104 ERROR: Permit Number is required

The permit number is required information and must be entered.  Your permit number is the second code, in the fourth row located on your CFEC permit card.  The permit number is a six digit code, followed by a single letter code.

The permit number was not entered.

Verify your issued permit number, on the CFEC permit card, and enter the correct value.

1105 ERROR: Permit Year Seq is required

The permit sequence code is required information and must be entered.  Your permit sequence code is located on your CFEC permit card as the first code, in the fifth row.  The permit sequence is a four digit code, followed by a single letter code.

The permit sequence code was not entered.

Verify the permit sequence code, and enter your issued permit sequence code on the CFEC Permit Worksheet.

1106 ERROR: CFEC Permit  CFEC_FISHERY   CFEC_PERMIT   CFEC_YEAR_SEQUENCE  not on file where:  CFEC_FISHERY  is The CFEC fishery code that is on the CFEC permit card. CFEC_PERMIT  is The CFEC permit number that is on the CFEC permit card. This is a 5 digit number followed by 1 letter. CFEC_YEAR_SEQUENCE  is The CFEC permit year and card issue sequence that is on the CFEC permit card. This field is a 2 digit year, a 2 digit issue sequence, followed by 1 letter.

The CFEC permit fishery, permit number, permit year and sequence number are required information and must be entered.  This information is located on the fourth and fifth row of the CFEC fishery permit card.

The permit information entered is not valid.

Verify the CFEC permit information by referencing the CFEC permit card.  Also reference Question 10, Frequently Asked Questions.  The FAQ's are located on the eLandings home page.  If you continue to experience problems enter the INTERIM VALUE (place holder) CFEC Permit - 9998 00098A 0000W.  Contact your local office of ADF&G, during business hours, for assistance.  The interim value must be replaced with a valid FEC permit within 72 hours.

1107 ERROR: Permit/Year Seq is invalid

The permit sequence code entered was not found in the database.  Your permit sequence code is located on your CFEC permit card as the first code, in the fifth row.  The permit sequence is a six digit code.

The permit Sequence code entered on the CFEC Permit Worksheet is not valid.

Verify the permit sequence code, and enter your issued permit sequence code on the CFEC Permit Worksheet.

1108 ERROR: Fishery/Permit is invalid

The CFEC fishery code does not match the permit number. Your CFEC fishery code and permit number are the first two codes, in the fourth row, located on your CFEC permit card.

The CFEC fishery code or the permit number entered is not correct.

Verify the CFEC fishery code and the permit number entered, on the CFEC Permit Worksheet.  Enter the correct codes.

1109 ERROR: Management Program  MANAGEMENT_PROGRAM  is not valid where:  MANAGEMENT_PROGRAM  is The management program that regulated the fishing.

The management program code for this fishery was not found in the database.  The management program identifies the fishery or fishery program that authorizes this harvest.

The management program code entered in the agency desktop application is not valid.

Reference the eLandings System Management Program codes to determine the correct management program, and enter the correct code.

1110 ERROR:  MANAGEMENT_PROGRAM  requires Management Program ID to be entered where:  MANAGEMENT_PROGRAM  is The management program that regulated the fishing.

The program ID is required information for management programs CDQ and AFA, and must be entered.  Valid program IDs can be looked up on the eLandings website.  See link: http://elandingstest.alaska.gov/elandings/MgmtProgLookup .

The management program code selected is incorrect, or the program ID was not entered.

Verify that the management program code correctly correspondes to the management program for this fishery, and if it is enter the correct program ID on the CFEC Permit worksheet.

1111 ERROR: Management Program ID  MANAGEMENT_PROGRAM_ID  is not valid where:  MANAGEMENT_PROGRAM_ID  is The fisher's identification number for the management program under which the fishing was conducted.

The program ID entered was not found in the database.  Valid program IDs can be looked up on the eLandings website.

The program ID entered on the CFEC Permit Worksheet is not valid.

Verify the management program ID.  Enter the correct management program ID on the CFEC Permit worksheet.

1112 ERROR: Management Program ID should not be entered for  MANAGEMENT_PROGRAM_ID  where:  MANAGEMENT_PROGRAM_ID  is The fisher's identification number for the management program under which the fishing was conducted.

The program ID is required information for management programs CDQ and AFA only; all other management programs do not require the program ID and it must not be entered.

The program ID field on the CFEC Permit Worksheet has a value entered.  A program ID is not needed for this management program.

Verify that the management program code is correct and if the program ID is required.  Delete the program ID, if it is not required.

1113 ERROR: Management Program is required if Management Program ID is input

1114 ERROR: Percent is required

1115 ERROR: Percent cannot be greater than 100

The system does not allow the percent entered to be greater than 100, on the Stat Area Worksheet.  The system will allow you to record pot lift effort with no catch, which is recorded as zero percent.

The percent field, on the Stat Area Worksheet, add up to more than 100 percent.

Verify the precent field, on the Stat Area Worksheet, has been entered correctly.  Adjust the percent field to be no more than 100.

1116 ERROR: Sequence Ticket must be less than 100000000

The system requires the sequence ticket number to be a number between one and 100,000.

The value entered is greater than 100,000.

Verify the sequence ticket nmber, and enter a value between one and 100,000.

1117 ERROR: Sequence Ticket must be numeric

The sequence ticket must be a whole numeric value between one and 100,000.

The sequence ticket is invalid.

Enter a whole numeric value between one and 100,000 for the sequence ticket.

1118 ERROR: NMFS ID  NMFS_ID , IFQ Permit  IFQ_PERMIT_NUMBER , Species  SPECIES_CODE  combination is entered multiple times where:  NMFS_ID  is The NMFS ID number for persons involved in IFQ fisheries. IFQ_PERMIT_NUMBER  is The NMFS Restricted Access Management Division IFQ permit number. SPECIES_CODE  is The numeric species code.

The IFQ permit and species code, on the IFQ Permit Worksheet, can match only once for each NMFS ID.

The IFQ permit and species code, on the IFQ Permit Worksheet, matches more than one time for a NMFS ID.

Verify the data entered on the IFQ Permit Worksheet is correct, and delete multiple entries of any combinations for each NMFS ID.

1119 ERROR: NMFS ID  NMFS_ID , IFQ Permit  IFQ_PERMIT_NUMBER , Species  SPECIES_CODE , IPQ Permit  IPQ_PERMIT_NUMBER  combination is entered multiple times where:  NMFS_ID  is The NMFS ID number for persons involved in IFQ fisheries. IFQ_PERMIT_NUMBER  is The NMFS Restricted Access Management Division IFQ permit number. SPECIES_CODE  is The numeric species code. IPQ_PERMIT_NUMBER  is The NMFS Restricted Access Management Division Processor quota share permit number.

The IFQ permit, species code, and the IPQ permit, on the IFQ Permit Worksheet, can match once for each CFEC permit holder's NMFS ID.

The IFQ permit, species code, and the IPQ permit, on the IFQ Permit Worksheet, matches more than one time for a CFEC permit holder's NMFS ID.

Verify the data entered on the IFQ Permit Worksheet is correct, and delete multiple entries of any combinations.

1120 ERROR: Species is required

When filling out the IFQ Permit Worksheet, the IFQ species code associated with the IFQ permit is required information and must be entered. Valid species codes can be referenced on the eLandings website.  See link: http://elandingstest.alaska.gov/elandings/SpeciesLookup .

The species code was not entered for a partially entered row on the IFQ Permit Worksheet.

Verify the species code, and enter the correct species code associated with the IFQ permit, on the IFQ Permit Worksheet.

1121 ERROR: Species Code  SPECIES_CODE  is not an IFQ species where:  SPECIES_CODE  is The numeric species code.

The species must be in the IFQ management program.  The species for the Rationalized Crab Fishery is limited to red king crab, golden king crab, blue king crab, baridi tanner crab, and Opilio Snow crab.  The IFQ groundfish are limited to halibut and sabelfish.  Valid Species codes can be looked up on the eLandings website.  See link: http://elandingstest.alaska.gov/elandings/SpeciesLookup .

A species code entered on the IFQ Permit Worksheet is not valid for the IFQ management program.

Verify the species code, on the IFQ Permit Worksheet, and enter the correct species code.

1122 ERROR: Species Code  SPECIES_CODE  is not valid where:  SPECIES_CODE  is The numeric species code.

The species code entered, on the IFQ Permit Worksheet, was not found in the database.  Valid species codes can be looked up on the eLandings website.

The species code entered on the IFQ Permit Worksheet is not valid.

Enter a valid species code on the IFQ Permit Worksheet.

1123 SYSTEM ERROR: HTTP call Post Data is required

The HTML5 web app called a server function that requires post data but did not provide it.

No post data was received for the call to the server.

Contact eLandings support to bring this to the attention of the developers.

1124 SYSTEM ERROR:  VAL  is not supported as input data where:  VAL  is The code value.

The HTML5 web app called a server function that requires post data with a data element that is not supported by the function.

An unsupported data element was received for the call to the server.

Contact eLandings support to bring this to the attention of the developers.

1125 ERROR: NMFS Person ID is required

The NMFS ID is required information and must be entered.  The NMFS ID corresponds with a CFEC permit, and is issued to invdividuals.  Each individual fishing and selling a product must enter their NMFS ID.

The NMFS ID, on the IFQ Permit Worksheet, was not entered.

Verify your NMFS ID, and enter the correct value, on the IFQ permit Worksheet.  If you do not have a NMFS ID, contact NMFS - RAM Division or the IFQ Data Clerks for instruction on how to complete the landing report.

1126 ERROR: NMFS Person ID  NMFS_ID  is not valid where:  NMFS_ID  is The NMFS ID number for persons involved in IFQ fisheries.

The NMFS ID entered was not found in the database.  The NMFS ID corresponds with a CFEC permit, and is issued to individuals.  Each individual fishing and selling a product must enter their NMFS ID.

The NMFS ID entered, on the IFQ Permit Worksheet, is not valid.

Verify your NMFS ID, on the IFQ Permit Worksheet, and enter the correct value.

1127 ERROR: IFQ Permit  IFQ_PERMIT_NUMBER  is not valid for NMFS Person ID  NMFS_ID  where:  IFQ_PERMIT_NUMBER  is The NMFS Restricted Access Management Division IFQ permit number. NMFS_ID  is The NMFS ID number for persons involved in IFQ fisheries.

The IFQ permit numbers must be valid for the given NMFS ID.

The IFQ permit numbers and the NMFS ID entered does not match in the database.

Verify the IFQ permit numbers and the NMFS ID.  Enter the correct IFQ permit numbers with the matching NMFS ID.

1128 ERROR: IFQ Permit  IFQ_PERMIT_NUMBER  is not valid for Species Code  SPECIES_CODE  where:  IFQ_PERMIT_NUMBER  is The NMFS Restricted Access Management Division IFQ permit number. SPECIES_CODE  is The numeric species code.

Each IFQ permit has a corresponding species code in the database.  Valid species codes can be looked up on the eLandings website.

The IFQ permits and the species codes do not match.

Verify that the IFQ permits and the species codes are correct and match.  Enter the matching IFQ permits and species codes.

1129 ERROR: IFQ Permit is required

When filling out the IFQ Permit Worksheet, the IFQ permit number is required information and must be entered.

The IFQ permit number was not entered for a partially filled out row on the IFQ Permit Worksheet

Verify the IFQ permit number, and enter the correct IFQ permit number, on the IFQ Permit Worksheet.

1130 ERROR: IFQ Permit  IFQ_PERMIT_NUMBER  is not valid where:  IFQ_PERMIT_NUMBER  is The NMFS Restricted Access Management Division IFQ permit number.

The IFQ permit number was not found in the database.

The IFQ permit number is not valid.  You may have mistyped the IFQ permit number; or the permit was issued after the last database update (within the last few hours).

Verify the IFQ permit number, and enter the correct value.  If this is unsuccessful, you may call NMFS Data Technicians: 1-800-304-4846, option 1.

1131 ERROR: IPQ Permit is required when using Class A IFQ permit

When using a class A IFQ permit, the IPQ permit number is required information and must be entered.

The IPQ permit number, for a class A IFQ permit, was not entered on the IFQ Permit Worksheet.

Verify the IPQ permit number, and enter the IPQ permit number, on the IFQ Permit Worksheet.

1132 ERROR: IFQ permit  IFQ_PERMIT_NUMBER  is not Class A.  IPQ Permit cannot be entered when not using Class A IFQ permit where:  IFQ_PERMIT_NUMBER  is The NMFS Restricted Access Management Division IFQ permit number.

When not using a class A IFQ permit, the IPQ permit number is not valid information and cannot be entered.  Class A IFQ permits require the IPQ permit number to be entered.

The IPQ permit number, for an IFQ permit that is not class A, was entered on the IFQ Permit Worksheet, or the wrong IFQ permit number was entered.

Verify that the IFQ permit number is correct and is not a class A IFQ permit.  If the IFQ permit number is not a class A IFQ permit, delete the IPQ permit number.

1133 ERROR: IPQ Permit  IPQ_PERMIT_NUMBER  is not valid with RCR Number  RCR_NUMBER  where:  IPQ_PERMIT_NUMBER  is The NMFS Restricted Access Management Division Processor quota share permit number. RCR_NUMBER  is The NMFS Restricted Access Management Division registered crab receiver number for crab IFQ.

The IPQ permit number must be valid for the given registered crab receiver number.

The IPQ permit number and the registered crab receiver number enetered does not match in the database.

Verify the IPQ permit number and the registered crab receiver number entered is correct.  Enter the correct IPQ permit number with the correct registered crab receiver number.

1135 ERROR: Pounds must be numeric and less than 1,000,000 pounds

The system does not allow data other than numeric, whole values to be entered in the pounds field.

Data other than whole numbers have been entered in the pounds field.

Verify the pounds field, and change it to a numeric, whole value.

1136 ERROR: Pounds of  POUNDS  is invalid where:  POUNDS  is The weight in pounds.

The system does not allow decimals, negative values, or values greater than 1,000,000 in the pounds field.

A decimal, negative value, or a value greater than 1,000,000 has been entered in the pounds field.

Verify the pounds field, and enter the correct whole, numeric value.  If you really have a weight over 1,000,000 pounds, contact the help desk for instructions on completeing the landing report.

1137 WARNING: IFQ Max-Out Pounds is more than 100,000. Is this correct?

This warning is generated when the max-out pounds field is greater than the expected number of 100,000.  The system will let you continue when you select Save Ignoring Warnings.  This button only appears when no errors are generated with the warnings.

The max-out pounds field entered is greater than the expected number of 100,000.

Verify that the pounds is correct, and if it is select Save Ignoring Warnings at the bottom of the website.  If the pounds are not correct, enter the correct pounds and select save.

1138 WARNING: Species codes  SPECIES_CODE1  and  SPECIES_CODE2  are separately permited by CFEC, and should not be reported on the same CFEC permit where:  SPECIES_CODE1  is The numeric species code. SPECIES_CODE2  is A different numeric species code.

The two species identified in the message need to be reported on separate CFEC permits.

Two species that need to be reported on separate CFEC permits were reported under the same CFEC permit.

Remove  one of the species and report it under a different CFEC permit.

1139 ERROR: At least one CFEC Permit must be input

The CFEC permit is required information and must be entered.  CFEC fishery, permit number, permit sequence, and management program are the minimum requirements to be entered, on the CFEC Permit Worksheet, in order to save the landing report.

The CFEC Permit Worksheet was left blank.

Enter the appropiate CFEC permit and management program, on the CFEC Permit Worksheet.  Enter other applicable information on the CFEC Permit Worksheet and IFQ Permit Worksheet.

1140 ERROR: CFEC Permit  CFEC_FISHERY   CFEC_PERMIT   CFEC_YEAR_SEQUENCE  is entered multiple times where:  CFEC_FISHERY  is The CFEC fishery code that is on the CFEC permit card. CFEC_PERMIT  is The CFEC permit number that is on the CFEC permit card. This is a 5 digit number followed by 1 letter. CFEC_YEAR_SEQUENCE  is The CFEC permit year and card issue sequence that is on the CFEC permit card. This field is a 2 digit year, a 2 digit issue sequence, followed by 1 letter.

The CFEC fishery number, permit number, and permit sequence number, on the CFEC Permit Worksheet, may be entered only once for each landing report.

The CFEC fishery number, permit number, and permit sequence number, on the CFEC Permit Worksheet, has been entered more than once for this landing report.

Verify the data entered on the CFEC Permit Worksheet is correct, and delete the extra entry of any combination.

1141 ERROR: Pounds to max-out permit can only be entered here if at least one other IFQ permit for the same species is available and has no pounds already allocated for max-out

The system does not allow the lbs. to max-out permit to be entered, if there is only one entry for that specific species, in the IFQ Permit Worksheet.  Also, the system does not allow Lbs. to max-out permit to be entered for all entries for the same species.  One permit must be available for balance of allocation.

Not all IFQ species permits can utilize max-out pounds.  For each IFQ species permit at least one permit must be availalbe for the balance of the allocation of pounds.

Delete max-out pounds from at least one IFQ species permits.

1142 ERROR: CFEC Permit worksheet percents add up to more than 100 percent

The system does not allow the total percent of the CFEC permits to add up to more than 100 percent, on the CFEC Permit Worksheet.

The percent fields, on the CFEC Permit Worksheet, add up to more than 100 percent.

Verify the precent fields, on the CFEC Permit Worksheet, have been entered correctly.  Adjust the percent fields to add up to no more than 100 percent.

1143 ERROR: CFEC Permit worksheet percents don't add up to 100 percent

The system does not allow the total percent of the CFEC permits to add up to less than 100 percent, on the CFEC Permit Worksheet, if data has been entered in all the percent fields.  The system does allow less than 100 percent to add up, if there is no data entered in one or more percent fields.

The percent fields, on the CFEC Permit Worksheet, add up to less than 100 percent.

Verify the precent fields, on the CFEC Permit Worksheet, have been entered correctly.  Adjust the percent fields to add up to no less than 100 percent.

1144 WARNING:  FLAG  is only valid for crab reports where:  FLAG  is The TRUE/FALSE value entered.

The flag is specific to crab.

The crab specific flag does not make sense for non-crab reports.

Reset the flag.

1145 ERROR: Stat Area is required

The system does not allow any lines, on the Stat Area Worksheet, to be entered without the stat area.

A stat area was not entered, on the Stat Area Worksheet.

Enter the correct stat area, on the Stat Area Worksheet.

1146 ERROR: Stat Area  STAT_AREA  is invalid where:  STAT_AREA  is The ADF&G Statistical Area identifier.

Valid statistical areas are stored in the database.  They are determined by ADF&G and the appropiate charts can be found at your local ADF&G office, or at http://www.cf.adfg.state.ak.us/geninfo/maps.php#shellfish .  Nation Marine Fisheries Service and the International Pacific Halibut Commission reporting area codes may not be used to substitute for the ADF&G statistical area codes.  A stat area code table, with the corresponding reporting areas, can be found on the eLanding website.  See link: http://elandingstest.alaska.gov/elandings/StatAreaLookup .

The stat area entered was not found in the database.

Verify that the stat area entered is valid.  Compare the stat area to the appropiate chart and enter the correct code.

1147 ERROR: Stat Area  STAT_AREA  is entered in agency stat area worksheet multiple times where:  STAT_AREA  is The ADF&G Statistical Area identifier.

The system does not allow the same stat area to be entered, into the Stat Area Worksheet, more than one time.

The same area has been entered into, the Stat Area Worksheet, more than one time.

Verify the state area, and enter the correct stat area, in the Stat Area Worksheet.  If all stat areas are correct, delete multiple entries.

1148 WARNING:  FLAG  is only valid for groundfish reports where:  FLAG  is The TRUE/FALSE value entered.

The flag is specific to groundfish.

The groundfish specific flag does not make sense for non-groundfish reports.

Reset the flag.

1149 ERROR: Agency Stat Area worksheet percents add up to more than 100 percent

The system does not allow the total percent of the Stat Areas to add up to more than 100 percent, on the Agency Stat Area Worksheet.

The percent fields, on the Agency Stat Area Worksheet, add up to more than 100 percent.

Verify the percent fields, on the Agency Stat Area Worksheet, have been entered correctly. Adjust the percent fields to add up to no more than 100 percent.

1150 ERROR: Agency Stat Area worksheet has no percent to give line without percent entered

1151 ERROR: Agency Stat Area worksheet percents don't add up to 100 percent

The system does not allow the total percent of the Stat Areas to add up to less than 100 percent, on the Agency Stat Area Worksheet.

The percent fields, on the Agency Stat Area Worksheet, add up to less than 100 percent.

Verify the percent fields, on the Agency Stat Area Worksheet, have been entered correctly. Adjust the percent fields to add up to no less than 100 percent.

1152 WARNING:  FLAG  is only valid for  TYPE  where:  FLAG  is The TRUE/FALSE value entered. TYPE  is The operation type code.

The flag is only used for specific situations.

The flag does not make sense for the current report.

Reset the flag.

1153 WARNING:  FLAG  is only valid for salmon reports where:  FLAG  is The TRUE/FALSE value entered.

The flag is specific to salmon.

The salmon specific flag does not make sense for non-salmon reports.

Reset the flag.

1154 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.

The system does not allow the number of Pot lifts to be less than 1.

A number less than 1 has been entered in the Pot Lifts field.

Verify the Pot Lifts fields, and enter the correct number of Pot Lifts.

1155 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.

The system does not allow pot lifts, on the Stat Area Worksheet, to be greater than 10,000.

Pot lifts entered is greater than 10,000.

Verify the pot lifts field and change the pot lifts to a numeric value, between one and 10,000.  If you are sure of the number of pot lifts, contact eLandings support to reslove the problem.

1156 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.

If you use the Stat Area Worksheet, you must complete the Pot Lifts field for each line that has a Stat Area.

May have neglected to complete the entire line.

Enter the number of pot lifts in the Pot Lifts field for the referred line in the error.

1157 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.

The system does not allow data other than numbers to be entered in the pot lifts field.

Data other than numbers have been entered in the pot lifts field.

Verify the pot lifts field and enter the correct number of lifts.

1158 ERROR: Stat Area  STAT_AREA  is entered in the Stat Area Worksheet multiple times where:  STAT_AREA  is The ADF&G Statistical Area identifier.

The system does not allow the same stat area to be entered, into the Stat Area Worksheet, more than one time.

The same area has been entered into, the Stat Area Worksheet, more than one time.

Verify the state area, and enter the correct stat area, in the Stat Area Worksheet.  If all stat areas are correct, delete multiple entries.

1159 ERROR: At least one of your Stat Area Worksheet lines requires a percent to be entered

The system does not allow more than one line with percent not entered, in the Stat Area Worksheet.  The system can calculate the remaining percent for one line.  The system will allow you to record pot lift effort with no catch, which is recorded as zero percent.

The percent was not entered on more than one line, in the Stat Area Worksheet.

Verify the percent fields are entered, and enter the correct percents.

1160 ERROR: Stat Area Worksheet percents add up to more than 100 percent

The system does not allow the total percent of the stat areas to add up to more than 100 percent, on the Stat Area Worksheet.  The system will allow you to record pot lift effort with no catch, which is recorded as zero percent.

The percent fields, on the Stat Area Worksheet, add up to more than 100 percent.

Verify the precent fields, on the Stat Area Worksheet, have been entered correctly.  Adjust the percent fields to add up to no more than 100 percent.

1161 ERROR: Stat Area Worksheet has no percent to give line without percent entered

The system does not allow any percent fields, on the Stat Area Worksheet, to remain empty when the other percent fields total 100.  If the other percent fields do not total 100, one percent field can remain empty and its value will be calculated.  The system will allow you to record pot lift effort with no catch, which is recorded as zero percent.

The percent fields, on the Stat Area Worksheet, total 100 with a remaining percent field that has not been entered.

Verify the precent fields, on the Stat Area Worksheet, have been entered correctly.  Enter the correct value in any remaining percent fields, and adjust the percent fields to add up to no more than 100 percent.  If you want to recrod pot lift effort with no catch, enter zero percent in the appropiate field.

1162 ERROR: Stat Area Worksheet percents don't add up to 100 percent

The system does not allow the total percent of the stat areas to add up to less than 100 percent, on the Stat Area Worksheet, if data has been entered in all the percent fields.  If the other percent fields do not total 100, one percent field can remain empty and its value will be calculated.  The system will allow you to record pot lift effort with no catch, which is recorded as zero percent.

The percent fields, on the Stat Area Worksheet, add up to less than 100 percent.

Verify the precent fields, on the Stat Area Worksheet, have been entered correctly.  Adjust the percent fields to add up to no less than 100 percent.

1163 ERROR: Stat Area is required for line, or use Stat Area Worksheet

The system does not allow a landing report to be completed without stat area information.  Stat area codes can be entered on the line item or entered on the Stat Area Worksheet, which is found by clicking the Edit Vessel, Permit, Location Information button, on the previous page.

Stat area code was not entered.

Verify stat area codes and enter them for the line, or enter them on the Stat Area Worksheet.

1164 ERROR: Fish Ticket must be assigned

The system requires the allocation of catch to individual CFEC permits.  The system does not allow a report with multiple CFEC permits to be submitted, when fish tickets are not allocated to line items.  The allocation permits button is located on the CFEC Permit Worksheet.

A request to submit the report was made, when line items have no fish tickets allocated.

Verify fish tickets with their corresponding line items, and allocate or select fish tickets for the line items.

1165 ERROR: Fish Ticket   FISH_TICKET_NUMBER  is not in CFEC Permit Worksheet where:  FISH_TICKET_NUMBER  is The ADF&G fish ticket id number.

Fish ticket number is required information and must be entered.

Fish ticket number has been deleted on the CFEC Permits tab, and it is still being used on another part of the landing report.

Verify the CFEC Permits information.  If it is correct, remove all data associated with a fish ticket number you are no longer using.  If you are missing a necessary fish ticket entry, reenter the information.  It might be possible to retrieve the information, if you close the landing report without saving (other changes will be lost).

1166 ERROR: Number of  UNIT_OF_EFFORT  is required for line, or use 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.

1167 ERROR: Price is required for IFQ Crab

The system requires the price, on all line items that have sold disposition codes, before an initial report or final report can be submitted

The price for a line item, that has a sold disposition code, has not been entered or has been deleted, when trying to submit an initial report or final report.

Verify the disposition code, and if it is correct, enter the price on the line item before you submit the report.  If the disposition code is not correct, enter the correct value and submit the report again.

1168 ERROR: Cannot change to non-sold disposition because the line has grading and pricing information

The system does not allow the disposition field to be changed to a non-sold disposition code, if the line has grading and pricing information.  The Add/Edit Grading and Pricing button is located on the previous page.  Disposition codes can be found on the eLandings website.

The disposition code was changed to a non-sold disposition after grading and pricing information for the line had been entered, on another page of the eLandings website.

Verify that the disposition code, grading, and pricing information is correct.  If the disposition code is correct, go to the grading and pricing information page and delete the sold weight and prices sold for that line.  If the disposition code is not correct, change the disposition code to the correct disposition.

1169 ERROR: Delivery Condition is required

The delivery condition code is required information and must be entered.  Valid delivery condition codes can be found on the eLandings website.

The delivery condition code was not entered.

Verify the delivery condition code, and enter the correct delivery condition code.

1170 ERROR: Delivery Condition  CONDITION_CODE  is not valid where:  CONDITION_CODE  is The numeric condition code.

The delivery condition code entered was not found in the database.  Valid delivery condition codes can be looked up on the eLandings website.

A delivery condition code entered is not valid.

Verify the delivery condition code, and enter the correct delivery condition code.

1171 ERROR: Delivery Condition  CONDITION_CODE  is not valid for species  SPECIES_CODE  where:  CONDITION_CODE  is The numeric condition code. SPECIES_CODE  is The numeric species code.

The system does not allow certain combinations of delivery condition codes and species codes.  These restricted combination of codes are not known to be neccissary for the current fisheries.

The combination of delivery condition code and species code entered do not match.

Verify the deliver condition code and species code entered.  Enter the correct codes.  If you codes are correct, contact eLandings support to resolve the problem or NMFS Enforcement to complete a manual IFQ landing report.

1172 ERROR: Delivery Condition for sold or personal use halibut must be 04 or 05

The system does not allow the disposition of sold or personal use halibut to be entered, if the delivery condition code entered is not gutted with head on (04) or headed and gutted (05).  Delivery condition codes and disposition codes can be looked up on the eLanding website.

The disposition code entered requires a delivery condition of gutted with head on or headed and gutted, which is 04 and 05, respectively.

Verify the delivery condition code, disposition code, and species code.  Enter the correct values.

1173 ERROR: Weight is required

The weight is required information and must be entered.

The weight field was not entered.

Verify the weight, and enter the correct value.

1174 ERROR: Weight must be numeric

The system does not allow fractions or data other than numbers to be entered for weight; however, the system does allow decimal values.

Data other than numbers have been entered in the lbs. field

Verify the weight, and enter the correct, numeric value.

1175 ERROR: Weight cannot be a negative number

The system does not allow the weight entered to be less than zero.  The system will allow a value of zero; however, the entire line will be deleted and then the report will be saved.  The system allows for decimal values.

A number less than zero has been entered in the lbs. field.

Verify the weight, and enter the correct value.

1176 ERROR: Weight must be less than 1,000,000,000 lbs.

The system does not allow the weight entered to be greater than 999,999,999.

The weight entered, in the lbs. field, is greater than 999,999,999.

Verify the weight, and enter the correct value.

1177 WARNING: Weight is greater than  MAX_EXPECTED_WEIGHT  lbs. Is this right? where:  MAX_EXPECTED_WEIGHT  is The maximum allowable weight.

This warning is generated when the weight entered is between the maximum expected lbs. (varies by species) and the maximum lbs. of 999,999,999.  The system will let you continue when you select Save Ignoring Warnings.  This button only appears when no errors are generated with the warnings.

The weight entered, in the lbs. field, is between the maximum expected (varies by species) and the maximum of 999,999,999.

Verify that the weight entered is correct, and if it is, select Save Ignoring Warnings at the bottom of the website.  If the weight is not correct, enter the correct weight and select Save.

1178 ERROR: Weight modifier  WEIGHT_MODIFIER  is invalid where:  WEIGHT_MODIFIER  is The flag that indicates a modification to the meaning of weight, such as estimated or includes ice and slime.

The system expects specific values for ice and slime and estimated weight modifiers.  These weight modifiers are the only allowable modifiers; however, a value is not required.  The ice and slime modifier can be entered as 'i/s' or simply '/', and estimated modifier can be entered as 'est'.

The weight modifier entered is not valid.

Verify the weight modifier, and enter 'i/s' or '/' for ice and slime, 'est' for estimated, or tab over this field if a weight modifier is not applicable.

1179 ERROR: Ice and Slime is only allowed for halibut and sablefish

The system does not allow the With Ice/Slime weight modifier to be selected without using the species code for either halibut or sablefish.

The With Ice/Slime was selected for the weight modifier field and halibut or sablefish is not the species code.

Verify the species code.  If the species code is not correct, enter the correct species code.  If the species is not halibut or sablefish, do not use With Ice/Slime weight modifier.

1180 ERROR: Either Weight or Number of  UNITS  must be entered where:  UNITS  is The unit for counting the number of animals in the catch, such as fish or crab.

All species, including prohibited species, discarded at sea, must be documented on a landing report.  Discarded prohibited species can be documented as pounds or number of animals, with the exception of herring.  Herring bycatch must be documented in pounds discarded.

The species discarded at sea did not include entry of pounds or number of animals.

Enter the number of animals or pounds for all species discarded at sea, as required by regulations.

1181 ERROR: Number of  UNITS  is required where:  UNITS  is The unit for counting the number of animals in the catch, such as fish or crab.

The number of animals is required information and must be entered for this species.  The system expects whole numeric values.

The number of animals was not entered.

Verify the number of animals, and enter the correct value.

1182 ERROR: Number of  UNITS  must be numeric where:  UNITS  is The unit for counting the number of animals in the catch, such as fish or crab.

The system does not allow fractions or data other than numbers to be entered for in the number field; however, the system does allow decimal values.

Data other than numbers have been entered in the number field.

Verify the number of animals, and enter the correct value.

1183 ERROR: Number of  UNITS  must be greater than zero where:  UNITS  is The unit for counting the number of animals in the catch, such as fish or crab.

The system does not allow data entered in the number field to be less than one.

A number less than one has been entered in the number field.

Verify the number field, and enter the correct number of animals.

1184 ERROR: Number of  UNITS  must be less than 1,000,000,000 where:  UNITS  is The unit for counting the number of animals in the catch, such as fish or crab.

1185 ERROR: Number of  UNITS  is invalid, gives an average weight of  WEIGHT  that is too small for the species where:  UNITS  is The unit for counting the number of animals in the catch, such as fish or crab. WEIGHT  is The weight in pounds.

The system computes an error check for average weight, using the number of animals and the total weight entered, and compares this average weight to the species entered.  See species codes look up tables for valid values.

The number of animals and total weight entered gives an average weight that is known to be too small for the species entered.

Verify the number of animals, weight, and species code.  Enter the correct values.

1186 ERROR: Number of  UNITS  is invalid, gives an average weight of  WEIGHT  that is too large for the species where:  UNITS  is The unit for counting the number of animals in the catch, such as fish or crab. WEIGHT  is The weight in pounds.

The system computes an error check for average weight, using the number of animals and the total weight entered, and compares this average weight to the species entered.  See species codes look up tables for valid values.

The number of animals and total weight entered gives an average weight that is known to be too large for the species entered.

Verify the number of animals, weight, and species code.  Enter the correct values.

1187 ERROR: Disposition is required

Disposition is required information and must be entered.  Disposition codes can be looked up on the eLandings website.

The disposition code was not entered in the disposition field.

Verify the disposition code, and enter the correct value.

1188 ERROR: Disposition  DISPOSITION_CODE  is not valid where:  DISPOSITION_CODE  is The numeric disposition code, indicating what is being done with the catch.

The disposition code entered was not found in the database.  Valid disposition codes can be looked up on the eLandings website.

The disposition code entered in the disposition field is not valid.

Verify the disposition code, and enter the correct value.

1189 ERROR: NMFS ID  NMFS_ID  is not yet valid on  DATE  where:  NMFS_ID  is The NMFS ID number for persons involved in IFQ fisheries. DATE  is The date entered for the announcement.

1191 ERROR: Disposition  DISPOSITION_CODE  is not valid for species  SPECIES_CODE  where:  DISPOSITION_CODE  is The numeric disposition code, indicating what is being done with the catch. SPECIES_CODE  is The numeric species code.

The system restricts certain disposition codes for crab and halibut species codes.  Disposition codes that are allowed for crab species codes are 60, 79, 98, and 99.  Disposition codes that are allowed for halibut species codes are 60, 61, 62, 63, 64, 86, 87, 88, 89, 92, 93, 95, 98, and 99.  See species code and disposition code lookups for valid codes.

The disposition code entered is not valid for the species code entered.

Verify the disposition code and species code, and enter the correct values.  If your species code is for crab, only enter a disposition code of 60, 79, 98, or 99.  If your species code is for halibut, only enter a disposition code of 60, 61, 62, 63, 64, 86, 87, 88, 89, 92, 93, 95, 98, or 99.

1192 ERROR: Disposition  DISPOSITION_CODE  is not valid for crab where:  DISPOSITION_CODE  is The numeric disposition code, indicating what is being done with the catch.

The disposition code entered is not valid for this crab.  Please review disposition codes and fisheries regulations to determine correct and allowable disposition codes.

The disposition code entered is not valid for this crab fishery.

Verify the disposition code, and enter the correct and allowable dispostion code.

1193 ERROR: Sold Condition Code is required

1194 ERROR: Sold Condition Code  CONDITION_CODE  is not valid where:  CONDITION_CODE  is The numeric condition code.

1195 ERROR: Product Type is required

Product type is required information and must be entered.  Available entries for product type are P and A, which are codes for primary and ancillary.

The product type was not entered.

Verify the product type, and enter the correct code.

1196 ERROR: Product Type must be A (ancillary) or P (primary).

The system requires the product type entered to be P or A, which stands for primary and ancillary.

The product type entered was not P or A.

Verify the product type, and enter the correct code.

1197 ERROR: Sold Weight is required

1198 ERROR: Sold Weight must be numeric, with no decimal point

1199 ERROR: Sold Weight cannot be a negative number

1200 ERROR: IFQ Permit  IFQ_PERMIT_NUMBER  for species  SPECIES_CODE  is not authorized for NMFS ID  NMFS_ID  on  DATE  where:  IFQ_PERMIT_NUMBER  is The NMFS Restricted Access Management Division IFQ permit number. SPECIES_CODE  is The numeric species code. NMFS_ID  is The NMFS ID number for persons involved in IFQ fisheries. DATE  is The date entered for the announcement.

1201 ERROR: Price is required

Price per pound is required information and must be entered.

The $/lb. field was not entered.

Verify the price per pound, and enter it in the $/lb. field.

1202 ERROR: Price cannot be a negative number

The system does not allow the price per pound to be less than zero.

A number less than zero has been entered in the $/lb. field.

Verify the price per pound, and enter it in the $/lb. field.

1203 ERROR: Price must be numeric

The system does not allow data other than numbers to be entered in the $/lb. field.

Data other than numbers have been entered in the $/lb. field.

Verify the price per pound, and enter it in the $/lb. field.

1204 ERROR: Price must be less than $100

The system does not allow the price per pound to be greater than 99.

The price per pound entered is greater than 99.

Verify the price per pound, and enter the correct value in the $/lb. field.

1205 WARNING: Price is more than $ PRC , is this right? where:  PRC  is The maximum expected price.

This warning is generated when the price per pound entered is between the maximum expected price of 10 and the maximum price of 100.  The system will let you continue when you select Save Ignoring Warnings.  This button only appears when no errors are generated with the warnings.

The price per pound entered is between the maximum expected price of 10 and the maximum price of 100.

Verify that the price per pound is correct, and if it is select Save Ignoring Warnings at the bottom of the website.  If the price per pound is not correct, enter the correct price per pound and select Save.

1206 ERROR: Size/Grade cannot be longer than 16 characters.

1207 ERROR: Total of Grading Pricing sold weights cannot be greater than line weight

The system does not allow the size/grade weights to total greater than the line's landed pounds.  The system allows for a poundage difference of up to one pound.

The size/grade weights total greater than the line's landed pounds.

Verify the sold pounds for each size/grade, and enter correct values that do not total over the line's landed pounds.

1208 ERROR: Harvest Code is required

The harvest code must be entered for each line item for data entry in the Agency Desktop application.  Harvest codes are available on the eLanding website.

The harvest code was not entered for the line item just completed.

Verify the correct harvest code for this line item and enter the code in the harvest code field.

1209 ERROR: Harvest Code  HARVEST_CODE  is invalid where:  HARVEST_CODE  is The ADF&G harvest code.

The harvest code is derived from the report type, the management program, the disposition code, and the comment code.  If you select the Assign Harvest Codes button, harvest codes will be generated for each line, on the Itemized Catch table.  In most cases, the harvest codes can be clearly assigned, but they should always be reviewed by agency staff.

The harvest code is not a valid code in the harvest code table.

Verify the harvest code on the harvest code lookup table, and enter the correct value.  You may let the system generate a harvest code for each line; however, reviewing the generated harvest codes is recommended.

1210 ERROR: Comment Code is required.

The system does not allow the final report to be submitted, if a comment code has not been selected.

The required comment code was not selected.

Select the Add/Edit Comments button and verify the comments.  Select the correct comments and click save.

1211 ERROR: Comment Code  COMMENT_CODE  is not valid where:  COMMENT_CODE  is The comment type identifier.

1212 ERROR: Comment text cannot be longer than  MAX  characters where:  MAX  is The maximum number.

The system limits the maximum length of comments.

Comment text entered exceeds maximum length.

Review comment text and edit it to be no longer than the maximum characters indicated.

1213 ERROR: Cannot allocate CFEC Permits for submitted report

1214 ERROR: No line items need CFEC Permit allocated to them

1215 ERROR: Line(s) already assigned to fish ticket  FISH_TICKET_NUMBER  have more weight than requested to max out IFQ permit(s) for species  SPECIES_CODE  where:  FISH_TICKET_NUMBER  is The ADF&G fish ticket id number. SPECIES_CODE  is The numeric species code.

1216 ERROR: Line(s) for species  SPECIES_CODE  do not have enough weight to max out IFQ permit(s) as requested where:  SPECIES_CODE  is The numeric species code.

1217 WARNING: No IFQ Permit has been entered for Fish Ticket  FISH_TICKET_NUMBER  Species  SPECIES_CODE  where:  FISH_TICKET_NUMBER  is The ADF&G fish ticket id number. SPECIES_CODE  is The numeric species code.

1218 ERROR: Search Name is not valid

1219 ERROR: No line items found for IFQ Permit  IFQ_PERMIT_NUMBER  species  IFQ_SPECIES  on fish ticket  FISH_TICKET_NUMBER  where:  IFQ_PERMIT_NUMBER  is The NMFS Restricted Access Management Division IFQ permit number. FISH_TICKET_NUMBER  is The ADF&G fish ticket id number. IFQ_SPECIES  is The numeric species code.

1220 ERROR: IFQ Permit  IFQ_PERMIT_NUMBER  species  SPECIES_CODE  cannot find line item weights to cover  POUNDS  pounds where:  IFQ_PERMIT_NUMBER  is The NMFS Restricted Access Management Division IFQ permit number. SPECIES_CODE  is The numeric species code. POUNDS  is The weight in pounds.

1221 INFO: One IFQ Report generated. Please review report contents and use Submit button to submit

One IFQ report was generated.  Please review the report contents and select the submit button.

1222 INFO: One IFQ Report generated. Please review report contents, edit to add IPHC Regulatory Area, and use Submit button to submit

One IFQ Report generated.  Please review the report contents, edit to add IPHC regulatory area, and select the submit button.

1223 INFO:  NUMBER_OF_REPORTS   IFQ Reports generated. Please review report contents and use Submit button to submit where:  NUMBER_OF_REPORTS  is The number of IFQ reports in the landing report.

The system gives this message when it auto-generates IFQ reports from the fish ticket data on the landing report. In most cases at least one report will be generated for each IFQ permit entered for the landing report. However, in many cases more than one IFQ report will be generated for each permit. For groundfish IFQ an IFQ report will be generated for each statistical area reported. For crab, the IFQ system has a limit of 9 statistical areas per IFQ report, so if the landing report has more than 9 statistical areas then more than one IFQ report will be generated for each permit.

You requested the system automatically generate IFQ reports from the landing report data.

None needed

1224 INFO:  NUMBER_OF_REPORTS  IFQ Report generated. Please review reports, edit to add IPHC Regulatory Areas, and use Submit button to submit where:  NUMBER_OF_REPORTS  is The number of IFQ reports in the landing report.

The system gives this message when it auto-generates IFQ reports from the fish ticket data on the landing report, and at least one of the statistical areas is bisected by an IPHC area boundary. In most cases at least one report will be generated for each IFQ permit entered for the landing report. If multiple statistical areas are entered on the report then one IFQ report will be generated for each permit and statistical area combination. The generated reports will be incomplete if the statistical area is bisected by an IPHC regulatory area boundary.

You requested the system automatically generate IFQ reports from the landing report data.

Use the IFQ Report Entry page to edit the generated IFQ reports, selecting the proper IPHC regulatory area for each report that needs it.

1225 ERROR: Landing Report has no IFQ reports

1226 ERROR: IFQ Report LrId:  RPTID  FT Num:  FT  Tran Num:  TRAN  Species:  SPECIES  has no report items where:  RPTID  is The landing report ID. FT  is The Fish Ticket number. TRAN  is The IFQ report transaction number. SPECIES  is The species code.

1227 ERROR: Gear modifier is required

1228 WARNING: Gear modifier is required

1229 ERROR: Gear modifier is invalid

1230 ERROR: Gear modifier should not be input for gear code  CODE  where:  CODE  is The numeric disposition code, indicating what is being done with the catch.

1231 ERROR: Gear modifier should not be input for  TYPE  reports where:  TYPE  is The operation type code.

1232 ERROR: IFQ sold weight total does not match Fish Ticket data

1233 ERROR: IFQ retained weight total does not match Fish Ticket data

1234 ERROR: IFQ deadloss weight total does not match Fish Ticket data

1235 ERROR: Sold weight, retained weight, or deadloss weight is required

1236 ERROR: NMFS ID  NMFS_ID  IFQ Permit  IFQ_PERMIT_NUMBER , Species  SPECIES_CODE  is not associated with Fish Ticket  FISH_TICKET_NUMBER  where:  NMFS_ID  is The NMFS ID number for persons involved in IFQ fisheries. IFQ_PERMIT_NUMBER  is The NMFS Restricted Access Management Division IFQ permit number. SPECIES_CODE  is The numeric species code. FISH_TICKET_NUMBER  is The ADF&G fish ticket id number.

1237 ERROR: NMFS ID  NMFS_ID  IFQ Permit  IFQ_PERMIT_NUMBER  Species  SPECIES_CODE , IPQ Permit  IPQ_PERMIT_NUMBER  is not associated with Fish Ticket  FISH_TICKET_NUMBER  where:  NMFS_ID  is The NMFS ID number for persons involved in IFQ fisheries. IFQ_PERMIT_NUMBER  is The NMFS Restricted Access Management Division IFQ permit number. SPECIES_CODE  is The numeric species code. IPQ_PERMIT_NUMBER  is The NMFS Restricted Access Management Division Processor quota share permit number. FISH_TICKET_NUMBER  is The ADF&G fish ticket id number.

1238 ERROR: Management Program  MANAGEMENT_PROGRAM  ID  MANAGEMENT_PROGRAM_ID  is not valid where:  MANAGEMENT_PROGRAM  is The management program that regulated the fishing. MANAGEMENT_PROGRAM_ID  is The fisher's identification number for the management program under which the fishing was conducted.

The program ID entered was not found in the database or does not match the management program code.  Valid program IDs can be looked up on the eLandings website.

The program ID entered on the CFEC Permit Worksheet is not valid.

Verify the management program and program ID.  Enter the correct management program and program ID on the CFEC Permit worksheet.

1239 WARNING: CFEC Permitholder name  PERMIT_HOLDER_NAME  does not match NMFS ID person name  NMFS_PERSON_NAME  where:  PERMIT_HOLDER_NAME  is The name of the person or entity a permit was issued to. NMFS_PERSON_NAME  is The name of the person or entity a NMFS ID was issued to.

The permit holder name of the CFEC permit entered does not match the person name of the associated NMFS ID entered.

The names do not appear to match.

Verify the NMFS ID is for the same individual as the CFEC permit.

1241 ERROR: User  USER_ID  is not authorized to access reports for the Proc Code  PROC_CODE  where:  USER_ID  is The eLandings system user ID. PROC_CODE  is The ADF&G Processor Code, also know as the F-code.

1242 ERROR: User  USER_ID  is not authorized to access reports for the Federal Processor Number   FED_PROC_NUM  where:  USER_ID  is The eLandings system user ID. FED_PROC_NUM  is The Federal Processor Permit Number.

1243 ERROR: Line items are required

1244 ERROR: Pre-printed ticket is required

The pre-printed fish ticket number is required information and must be entered.  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 ticket field was left blank.

Verify the fish ticket number, and enter the correct value.

1245 ERROR: Pre-printed ticket cannot start with 'E'

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.  A leader letter of 'E' stands for electronic, and is reserved for landing reports submitted through the eLandings website.

The pre-printed fish ticket entered starts with the letter 'E'.

Verify the fish ticket number, and enter the correct value.  The leading letter of the type of landing report will be the correct letter to enter.  For example, G is for groundfish and C is for crab.

1246 ERROR: Pre-printed ticket cannot start with 'D'

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.  A leader letter of 'D' stands for electronic, and is reserved for landing reports submitted through the eLandings website.

The pre-printed fish ticket entered starts with the letter 'D'.

Verify the fish ticket number, and enter the correct value.  The leading letter of the type of landing report will be the correct letter to enter.  For example, G is for groundfish and C is for crab.

1249 ERROR: IPQ Permit  IPQ_PERMIT  is invalid where:  IPQ_PERMIT  is The NMFS Restricted Access Management Division Processor quota share permit number.

1250 ERROR: Percent must be a whole number.

Percent must be a whole number.

You have entered a decimal or a non-number.

Enter your percentage as a whole number.

1251 ERROR: Percent cannot be less than zero

The system expects a percent of 0 or greater.

A percent less than 0 has been entered, for example: -10.

Verify the percent, and enter the correct value.

1252 ERROR: Percent cannot be less than one

1253 ERROR: Date Fishing Began cannot be in the future

The system restricts the date fishing began entered from being dated in the future.

A date that is in the future has been entered in the date fishing began field.

Verify the date fishing began, and enter the correct value.

1254 ERROR: Discard Report Type is required

1255 ERROR: Management Program is required

Management program is required information and must be entered.  Management programs can be found in the look up tables.

The management program was not selected.

Verify the management program, and select the correct value.

1256 ERROR: Management Program ID is required

1257 ERROR: Discard Report Type is invalid

1258 ERROR: Fish Ticket stamped sequence number is required

1259 ERROR: Fish Ticket stamped sequence number  FT_SEQ_NUM  is invalid where:  FT_SEQ_NUM  is The sequence number stamped on the fish ticket when received by ADF&G.

1260 ERROR: Batch Number is required

When entering batch year, sequence ticket, or batch office code, batch number is required information and must be entered.

Batch number was not entered.

Verify the batch number, and enter the correct value.

1261 ERROR: Batch Number  BATCH_NUM  is invalid where:  BATCH_NUM  is The ADF&G data entry batch id number.

The system does not allow batch number to be less than one or greater than 99,999.  Batch number must be a whole, numeric value.

The batch number entered was less than one, greater than 99,999, a decimal value, or not a numeric value.

Verify the batch number, and enter the correct value.

1262 ERROR: Fish Ticket Number is required

A fish ticket number was required data, but was not entered.

For landing reports that have already been submitted, the fish ticket must be specified if any new lines are added to the report.

Enter or select a fish ticket number.

1263 ERROR: Fish Ticket Number  FT_NUM  is invalid where:  FT_NUM  is The ADF&G fish ticket id number.

The system expects a fish ticket number in the form of a leading letter with two digits, a space, and six more following digits. Examples of this are E12 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 fish ticket number entered is not in the correct format.

Verify the fish ticket number, and enter the value in the correct format.

1264 ERROR: Percent less than 100 cannot be specified if only one CFEC Permit Line is input

The system does not allow less than 100 percent, on the CFEC Permit Worksheet, if there is only one line for input.  The percent field can be left blank.

The percent field, on the CFEC Permit Worksheet, is less than 100 percent.

Verify the data entered on the CFEC Permit Worksheet, and if it is correct, enter a percent of 100 or leave the field blank.

1265 ERROR: Only one NMFS ID may be used for each CFEC Permit

This is not a valid statement: you can enter multiple NMFS ids for each CFEC permit, so it appears that this is not a valid error.

1266 ERROR: Size/Grade is invalid

1267 ERROR: Size/Grade is required

1268 WARNING: Pricing and Grading item weights do not add up to sold weight for line

The total amount for Sold Lbs. in the Pricing and Grading item detail, must be equal to or less than the amount of Landed Lbs. that was designated as Sold.

The amount entered as Sold Lbs. was less than the amount that was entered as Landed Lbs. for dispositions of 'Sold'.

This is a warning message. Correct the amount of Sold Lbs. in Grading and Pricing detail lines to account for the amount landed. Or 'Save Ignore Warnings'.

1269 INFO: No errors

The system generated no errors.

1271 SYSTEM ERROR: Error reading zip entry  ZIP_ENTRY  where:  ZIP_ENTRY  is The file contained in a zip archive.

1272 SYSTEM ERROR: No user information file found in zip archive

1273 SYSTEM ERROR:  EXCEPTION   MSG  where:  EXCEPTION  is The name of the Java Exception class. MSG  is The Java Exception message.

This is a system error message for error situations that were not anticipated by the system designers. When this error occurs further progress with the current transaction is not possible (trying the same thing again isn't likely to help).

We didn't anticipate an error of this type, so we don't have foreknowledge of what caused it.

System technical support should be contacted with details of the problem (what activity resulted in the error, username, date and time of the error, and landing report number or other information to identify the transaction). System technical support staff will help you identify a resolution.

1274 ERROR: Weight modifer is required

1275 INFO: Please enter data for new Landing Report

Please enter the data for the new landing report.

1276 INFO: Data saved

The data has been saved.

1277 INFO: Report saved successfully

The report has been saved successfully.

1278 ERROR: User  USER_ID  could not be authenticated where:  USER_ID  is The eLandings system user ID.

The user login entered was not found in the database, or the password entered does not match the user login.  User logins for the eLandings website and eLandings Agency may not be the same.

The user login or password entered is not valid.

Verify your user login and password for the system you are trying to login to, and enter the correct values.  If you do not remember your user login information, contact eLandings support staff.

1279 ERROR: User  USER_ID  login not allowed where:  USER_ID  is The eLandings system user ID.

1280 ERROR: User  USER_ID  is not a Processor User where:  USER_ID  is The eLandings system user ID.

User logins for the eLandings website and eLandings Agency may not be the same.

The user ID entered is not applicable to the system you are using.

Verify the user ID, and enter the correct value.  If you do not remember your user login information, contact eLandings support staff.

1282 INFO: Password emailed to  EMAIL  where:  EMAIL  is The entered email address.

The password was emailed to the supplied email address.

1283 ERROR: Email to  EMAIL  failed:  MSG  where:  EMAIL  is The entered email address. MSG  is The Java Exception message.

1284 ERROR: User  USER_ID  not found where:  USER_ID  is The eLandings system user ID.

The user ID entered was not found in the database.  User logins for the eLandings website and eLandings Agency may not be the same.

The user ID entered is not valid.

Verify the user ID, and enter the correct value.  If you do not remember your user login information, contact eLandings support staff.

1285 ERROR: User  ADMIN_USER_ID  not authorized to update user  USER_ID  where:  USER_ID  is The eLandings system user ID. ADMIN_USER_ID  is The userid of the user attempting to exercise administrative privileges

1286 ERROR: No Landing Reports found that match search criteria

The system checks all the reports for every search criteria entered, and when no reports match all the search criteria, there will be no results.

The search criteria entered does not match any reports for the authorized operations.  Some users may have restricted operations.

Verify the search criteria, and enter the correct values.  Reports will not display, if they were created with an operation that is not authorized for the current user.  If you are not sure of all of your search criteria, only enter the search criteria that you are sure of to broaden your search results.

1288 ERROR: Landing Report  LANDING_REPORT_ID  already in database as a submitted report where:  LANDING_REPORT_ID  is The unique numeric identifier for the Landing Report.

1289 ERROR: Submission of initial report not allowed if report status is  STATUS  where:  STATUS  is The descriptive status of the Landing Report.

1290 ERROR: Unable to initialize NMFS RAM IFQ web service connection because of missing properties 

1291 SYSTEM ERROR: Unable to connect to NMFS RAM IFQ system at  URL  where:  URL  is The URL of the web service endpoint.

1292 ERROR: IFQ transaction failed, inspect IFQ Reports for details, fix errors, and resubmit

1293 ERROR: NMFS RAM IFQ System message:  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 is a system error message for error situations in the NMFS RAM IFQ system that were not anticipated by the system designers. When this error occurs further progress with the current transaction is not possible (trying the same thing again isn't likely to help).

We didn't anticipate an error of this type, so we don't have foreknowledge of what caused it.

Contact eLandings support to resolve the problem. 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.

1294 ERROR: Landing Report  REPORT_ID  not found where:  REPORT_ID  is The eLandings landing report ID

When searching by report ID, the system checks all reports for the authorized operations.  The report IDs are a numeric value and are generated in sequence as reports are created.

The report ID entered was not found in the list of reports for the authorized operations.

Verify the report ID, and enter the correct value.  Reports will not display, if they were created with an operation that is not authorized for the current user.  If you are not sure of the report ID, use the other search criteria to help narrow the results.

1295 SYSTEM ERROR:  MSG   ERROR_CODE   LINKED_MSG  where:  MSG  is The Java Exception message. ERROR_CODE  is The JAXB Error code. LINKED_MSG  is The message from the linked exception.

1296 SYSTEM ERROR: Feature not implemented

1297 ERROR: IPQ Permit  IPQ_PERMIT_NUMBER , Species Code  SPECIES_CODE  is not valid for RCR Number  RCR_NUMBER  where:  IPQ_PERMIT_NUMBER  is The NMFS Restricted Access Management Division Processor quota share permit number. SPECIES_CODE  is The numeric species code. RCR_NUMBER  is The NMFS Restricted Access Management Division registered crab receiver number for crab IFQ.

1298 INFO: Report on server redisplayed

The report on the server was redisplayed.

1299 INFO: Report cancelled

The report was cancelled.

1301 INFO: Report displayed

The report was displayed.

1302 INFO: Itemized catch allocated to 1 fish ticket

The itemized catch was allocated to one fish ticket.

1303 INFO: Itemized catch allocated to  NUMBER_OF_FISH_TICKETS  fish tickets where:  NUMBER_OF_FISH_TICKETS  is The number of fish tickets in the landing report.

The itemized catch was allocated to the number of fish tickets on the landing report.

1304 INFO: IFQ Reports were previously generated

The IFQ reports were previously generated.

1305 INFO: Allocation undone

The allocation was undone.

1306 INFO: Report was previously submitted

The report was previously submitted.

1307 INFO: Report submitted

The report was submitted.0

1308 INFO: IFQ Reports were previously submitted

The IFQ reports were previously submitted.

1309 INFO: IFQ Reports submitted

The IFQ reports were submitted.

1310 INFO: Permits were previously allocated

The permits were previously allocated.

1311 INFO: Please enter the following information:

Please enter the following information on the website.

1312 ERROR: Number of decimal places to display for weights is required

The number of decimal places to display for weights is required information and must be entered.  The system expects a value between zero and four.

The number of decimal places to display for weights was not entered.

Enter a number between zero and four.

1313 ERROR: Number of decimal places to display for weights must be numeric

The system expects a whole numeric value and restricts more than one digit to be entered.  The system does not allow an entry of more than four.

A value has been entered that is not numeric.

Enter a numeric value between zero and four.

1314 ERROR: Number of decimal places to display for weights cannot be negative

1315 ERROR: Number of decimal places to display for weights cannot be greater than  MAX_SIZE  where:  MAX_SIZE  is The maximum number of characters that can be stored in the database for the field.

The system does not allow a number greater than four to be entered.

A value greater than four was entered.

Enter a number between zero and four.

1316 ERROR: Number of decimal places to display for price is required

The number of decimal places to display for price is required information and must be entered.  The system expects a value between zero and four.

The number of decimal places to display for price was not entered.

Enter a number between zero and four.

1317 ERROR: Number of decimal places to display for price must be numeric

The system expects a whole numeric value and restricts more than one digit to be entered.  The system does not allow an entry of more than four.

A value has been entered that is not numeric.

Enter a numeric value between zero and four.

1318 ERROR: Number of decimal places to display for price cannot be negative

1319 ERROR: Number of decimal places to display for price cannot be greater than  MAX_SIZE  where:  MAX_SIZE  is The maximum number of characters that can be stored in the database for the field.

The system does not allow a number greater than four to be entered.

A value greater than four was entered.

Enter a number between zero and four.

1320 ERROR: Number of CFEC Permit lines to display for input is required

The number of CFEC Permit Lines to display for input is required information and must be entered.  The system expects a value between one and 99.

The number of CFEC Permit Lines to display for input was not entered.

Enter a number between one and 99.

1321 ERROR: Number of CFEC Permit lines to display for input must be numeric

The system expects a whole numeric value and restricts more than two digits to be entered.  The system does not allow an entry of more than 99.

A value has been entered that is not numeric.

Enter a numeric value between one and 99.

1322 ERROR: Number of CFEC Permit lines to display for input must be at least one

The system expects a value that is greater than zero.  Any numeric value between one and 99 will be accepted.

A value less than one has been entered.

Enter a numeric value between one and 99.

1323 ERROR: Number of CFEC Permit lines to display for input cannot be greater than  MAX_SIZE  where:  MAX_SIZE  is The maximum number of characters that can be stored in the database for the field.

1324 ERROR: Number of IFQ Permit lines to display for input is required

The number of IFQ Permit lines to display for input is required information and must be entered.  The system expects a value between one and 99.

The number of IFQ Permit lines to display for input was not entered.

Enter a number between one and 99.

1325 ERROR: Number of IFQ Permit lines to display for input must be numeric

The system expects a whole numeric value and restricts more than two digits to be entered.  The system does not allow an entry of more than 99.

A value has been entered that is not numeric.

Enter a numeric value between one and 99.

1326 ERROR: Number of IFQ Permit lines to display for input must be at least one

The system expects a value that is greater than zero.  Any numeric value between one and 99 will be accepted.

A value less than one has been entered.

Enter a numeric value between one and 99.

1327 ERROR: Number of IFQ Permit lines to display for input cannot be greater than  MAX_SIZE  where:  MAX_SIZE  is The maximum number of characters that can be stored in the database for the field.

1328 ERROR: Number of Statistical Area Worksheet lines to display for input is required

The number of Statistical Area Worksheet lines to display for input is required information and must be entered.  The system expects a value between one and 99.

The number of Statistical Area Worksheet lines to display for input was not entered.

Enter a number between one and 99.

1329 ERROR: Number of Statistical Area Worksheet lines to display for input must be numeric

The system expects a whole numeric value and restricts more than two digits to be entered.  The system does not allow an entry of more than 99.

A value has been entered that is not numeric.

Enter a numeric value between one and 99.

1330 ERROR: Number of Statistical Area Worksheet lines to display for input must be at least one

The system expects a value that is greater than zero.  Any numeric value between one and 99 will be accepted.

A value less than one has been entered.

Enter a numeric value between one and 99.

1331 ERROR: Number of Statistical Area Worksheet lines to display for input cannot be greater than  MAX_SIZE  where:  MAX_SIZE  is The maximum number of characters that can be stored in the database for the field.

1332 ERROR: Number of Itemized Catch lines to display for input is required

The number of Itemized Catch lines to display for input is required information and must be entered.  The system expects a value between one and 99.

The number of Itemized Catch lines to display for input was not entered.

Enter a number between one and 99.

1333 ERROR: Number of Itemized Catch lines to display for input must be numeric

The system expects a whole numeric value and restricts more than two digits to be entered.  The system does not allow an entry of more than 99.

A value has been entered that is not numeric.

Enter a numeric value between one and 99.

1334 ERROR: Number of Itemized Catch lines to display for input must be at least one

The system expects a value that is greater than zero.  Any numeric value between one and 99 will be accepted.

A value less than one has been entered.

Enter a numeric value between one and 99.

1335 ERROR: Number of Itemized Catch lines to display for input cannot be greater than  MAX_SIZE  where:  MAX_SIZE  is The maximum number of characters that can be stored in the database for the field.

1336 ERROR: Number of Grading/Pricing lines to display for input is required

The number of Grading/Pricing lines to display for input is required information and must be entered.  The system expects a value between one and 99.

The number of Grading/Pricing lines to display for input was not entered.

Enter a number between one and 99.

1337 ERROR: Number of Grading/Pricing lines to display for input must be numeric

The system expects a whole numeric value and restricts more than two digits to be entered.  The system does not allow an entry of more than 99.

A value has been entered that is not numeric.

Enter a numeric value between one and 99.

1338 ERROR: Number of Grading/Pricing lines to display for input must be at least one

The system expects a value that is greater than zero.  Any numeric value between one and 99 will be accepted.

A value less than one has been entered.

Enter a numeric value between one and 99.

1339 ERROR: Number of Grading/Pricing lines to display for input cannot be greater than  MAX_SIZE  where:  MAX_SIZE  is The maximum number of characters that can be stored in the database for the field.

1340 ERROR: Number of Production Report lines to display for input is required

The number of Production Report lines to display for input is required information and must be entered.  The system expects a value between one and 99.

The number of Production Report lines to display for input was not entered.

Enter a number between one and 99.

1341 ERROR: Number of Production Report lines to display for input must be numeric

The system expects a whole numeric value and restricts more than two digits to be entered.  The system does not allow an entry of more than 99.

A value has been entered that is not numeric.

Enter a numeric value between one and 99.

1342 ERROR: Number of Production Report lines to display for input must be at least one

The system expects a value that is greater than zero.  Any numeric value between one and 99 will be accepted.

A value less than one has been entered.

Enter a numeric value between one and 99.

1343 ERROR: Number of Production Report lines to display for input cannot be greater than  MAX_SIZE  where:  MAX_SIZE  is The maximum number of characters that can be stored in the database for the field.

1344 ERROR: Number of Discard lines to display for input is required

The number of Discard lines to display for input is required information and must be entered.  The system expects a value between one and 99.

The number of Discard lines to display for input was not entered.

Enter a number between one and 99.

1345 ERROR: Number of Discard lines to display for input must be numeric

The system expects a whole numeric value and restricts more than two digits to be entered.  The system does not allow an entry of more than 99.

A value has been entered that is not numeric.

Enter a numeric value between one and 99.

1346 ERROR: Number of Discard lines to display for input must be at least one

The system expects a value that is greater than zero.  Any numeric value between one and 99 will be accepted.

A value less than one has been entered.

Enter a numeric value between one and 99.

1347 ERROR: Number of Discard lines to display for input cannot be greater than  MAX_SIZE  where:  MAX_SIZE  is The maximum number of characters that can be stored in the database for the field.

1348 INFO: Please print, sign, and submit your form to the proper authorities

Please print, sign, and submit your form to the proper authorities.

1349 ERROR: Old password is invalid

The old password entered does not match the existing password in the database.

The password entered is not valid.

Verify that the caps-lock button is not pressed, and enter your password.  If you do not remember your password, request your password to be emailed to you from the eLandings website login, or contact eLandings support staff.

1350 ERROR: New password entries must match each other

The system requires you to enter the new password twice to verify that the password is entered as was intended.

The new password entries do not match.

Verify that the caps-lock key was not pressed, and carefully enter the new password twice.

1351 INFO: Password has been changed

The password has been changed.

1352 INFO: Please enter your User ID to login

Please enter your user ID to login.

1353 INFO: User  USER_ID  logged in where:  USER_ID  is The eLandings system user ID.

The user of the user ID supplied has been logged in.

1354 INFO: User  USER_ID  logged off where:  USER_ID  is The eLandings system user ID.

The previous user has logged off.

1355 INFO: No user logged in

No user was logged in.

1356 ERROR: Report ID is required

1357 ERROR: Report ID  REPORT_ID  is invalid where:  REPORT_ID  is The eLandings landing report ID

The system expects the report ID entered to be a whole, positive, numeric value.  Report IDs are generated in sequence as reports are created.

The report ID entered is not a whole, positive, numeric value.

Verify the report ID, and enter the correct, numeric value.

1358 ERROR: Status Code is required

1359 ERROR: Status Code  STATUS_CODE  is invalid where:  STATUS_CODE  is The numeric status code for reports.

1360 ERROR: From Date is required

A fishing From Date is required when reporting a landing.

The From Date was left blank.

Enter a valid From Date.

1361 ERROR: From Date is invalid

The system will accept the date in several commonly used formats, and will convert to the standard format.  The from date field was not entered with one of the following formats:  mm/dd/yyyy, m/d/y, mmddyyyy, mm-dd-yyyy, m-d-y.

The from date field was entered in a format that was not recognized. This message can also be seen if the from date field is entered with letters in place of digits.

Verify the from date field, and enter the correct value.

1362 ERROR: From Date cannot be in the future

The system does not allow the from date field entered to be in the future.

A date that is in the future has been entered in the from date field.

Verify the from date field, and enter the correct date.

1363 ERROR: From Date requires four digit year

1364 ERROR: To Date is required

A fishing To Date is required when reporting a landing.

The To Date was left blank.

Enter a valid To Date.

1365 ERROR: To Date is invalid

The system will accept the date in several commonly used formats, and will convert to the standard format.  The to date field was not entered with one of the following formats:  mm/dd/yyyy, m/d/y, mmddyyyy, mm-dd-yyyy, m-d-y.

The to date field was entered in a format that was not recognized. This message can also be seen if the to date field is entered with letters in place of digits.

Verify the to date field, and enter the correct value.

1366 ERROR: To Date cannot be in the future

The system does not allow the to date field entered to be in the future.

A date that is in the future has been entered in the to date field.

Verify the to date field, and enter the correct date.

1367 ERROR: To Date requires four digit year

1368 ERROR: Operation Type is required

Operation type is required information and must be entered.

An operation type was not selected in the drop-down list.

Verify your operation type, and select the correct value drop the drop-down list.

1369 ERROR: Operation Type  TYPE  is invalid where:  TYPE  is The operation type code.

1370 ERROR: Operation Name is required

The operation name is required information and must be entered to complete your operation registration.  The system does not allow an operation name more than 32 characters long.

The operation name was not entered.

Verify the operation name, and enter it on the register operation page.

1371 ERROR: Operation Name cannot be greater than  MAX_SIZE  characters where:  MAX_SIZE  is The maximum number of characters that can be stored in the database for the field.

The system does not allow an operation name more than 32 characters long.

The operation name entered is greater than 32 characters long.

Verify the operation name and abbreviate, if necessary to shorten the name.

1372 INFO: Please enter the XML file to import

Please enter the XML file to import.

1373 ERROR: File  FILE_NAME  not found on disk where:  FILE_NAME  is The name of the XML file

1374 ERROR: Error uploading  TYPE  file where:  TYPE  is The operation type code.

1375 ERROR: XML file was not a valid Landing Report document, check file format

1377 ERROR: The Landing Report has already been submitted.  Import of previously submitted Landing Reports is not allowed.

1378 ERROR: The Landing Report has submitted IFQ reports.  Import of previously submitted Landing Reports is not allowed

1379 ERROR: Server error getting new Landing Report numbers

1383 INFO: If you are not intended to be a user for Operation  OPERATION_NAME  please contact eLandings support where:  OPERATION_NAME  is The name of the operation.

1384 SYSTEM ERROR: Database Error:  CODE  State:  STATE  Msg:  MSG  where:  CODE  is The numeric disposition code, indicating what is being done with the catch. MSG  is The Java Exception message. STATE  is The database state message

1385 INFO: Contact administrator of Operation  OPERATION_NAME  to be added as a user on the operation where:  OPERATION_NAME  is The name of the operation.

1386 ERROR: User  USER_ID  is not authorized for operation  OPERATION_NAME  where:  USER_ID  is The eLandings system user ID. OPERATION_NAME  is The name of the operation.

1387 ERROR: User  USER_ID  is not authorized to update operation  OPERATION_NAME  where:  USER_ID  is The eLandings system user ID. OPERATION_NAME  is The name of the operation.

1388 ERROR: Operation  OPERATION_ID  not found where:  OPERATION_ID  is The ID of the operation.

The operation ID entered was not found in the database.  The system expects whole numeric values and that are not a negative.

The operation ID entered is not valid.

Verify the operation ID, and enter the correct value.

1389 ERROR: Operation is required

The action you attempted is available only after an operation has been specified.  An operation in eLandings is a set of codes (Processor Code, Federal Permit Number, Registered Buyer Number, Port, etc.) that identify a seafood harvesting business operation for the purposes of electronic reporting.  Your eLandings UserID may be authorized to represent one or more operations.

You may be authorized to represent multiple operations and you haven't specified which operation you are representing at this time.  In this case, you should have an Operations drop-down list providing multiple choices.  Or, you may not have been authorized yet, or you may have been authorized but the operation for which you are authorized is not yet enabled.  In both of these cases, the Operations drop-down list will be empty.

Either find the Operations drop-down list and select an operation, or, if the drop-down list is empty, contact an administrator for the operation you represent.

1390 ERROR: The operation is already in the database

1391 ERROR: Port Code is required for  OP_TYPE  operations where:  OP_TYPE  is The name of the operation type.

The system requires a port code to be entered when using an operation type of plant/receiver, custom processing owner, at-sea processor, or buyer station.

The port code was not entered.

Verify the operation type, and select the correct value.  If the operation type is correct, enter the correct port code.

1392 ERROR: User  USER_ID  is not authorized to view Landing Report  REPORT_ID  where:  USER_ID  is The eLandings system user ID. REPORT_ID  is The eLandings landing report ID

The combination of processor code, federal permit number, registered buyer number and/or RCR number for the landing report does not match one of your userID's authorized operations.

You tried to search for a landing report by report id that does not match one of your authorized operations. This can happen if you put in the wrong landing report id. You can also get this message if you tried to submit a landing report from the processor workstation and the landing report has a processor code, federal permit number, registered buyer number and/or RCR number combination that does not match one of your authorized operations. You can also get this message if you try to import a landing report with numbers that do not match one of your authorized operations.

If you are importing an XML file, check the codes and numbers in the file to make sure they are correct. If you are sure you should be able to view the landing report whose ID you entered, have your eLandings administrative user check to make sure you are authorized for the operation that applies to the report. They can authorize your user id for that operation. Otherwise, contact eLandings technical support to have them determine what you need to access the operation.

1393 ERROR: Vessel ADF&G Number should not be entered for  OP_TYPE  operations where:  OP_TYPE  is The name of the operation type.

1394 ERROR: Either ADF&G Proc Code or Federal Permit Number must be specified

1395 ERROR: Vehicle License Number is invalid

1396 ERROR: Vehicle License Number is required

1397 ERROR: Vehicle License Number is too long

1398 ERROR: User   USER_ID  registration has already been approved where:  USER_ID  is The eLandings system user ID.

1399 SYSTEM ERROR: No header row found in database for Report ID  REPORT_ID  -- suspect cross-polination between Training and Production where:  REPORT_ID  is The eLandings landing report ID

There are certain identifiers that eLandings manages to ensure unique database keys.  These include Report IDs and Fish Ticket Numbers.  This error indicates that an identifier is being submitted which was not issued to the submitter.

If an identifier is requested from the eLandings Training instance, and then submitted to the eLandings Production instance, this error will result.

Submit data only with identifiers issued to the submitter.

1400 INFO: Operation registration must be approved before Landing Reports can be made

The operation registration must be approved before landing reports can be made with this operation.

1407 ERROR:  USER_ID  is the sole admin user for operation  OPID  and cannot be disabled. where:  USER_ID  is The eLandings system user ID. OPID  is The operation ID.

1408 ERROR:  USER_ID  is the sole admin user for operation  OPID  and must have Admin privileges. where:  USER_ID  is The eLandings system user ID. OPID  is The operation ID.

1411 ERROR:  USER_ID  is the sole admin user for operation  OPID , replacement cannot be disabled. where:  USER_ID  is The eLandings system user ID. OPID  is The operation ID.

1412 ERROR:  USER_ID  is the sole admin user for operation  OPID , replacement must have Admin privileges. where:  USER_ID  is The eLandings system user ID. OPID  is The operation ID.

1413 ERROR: Login is required

The system requires a login before reports menu or user profile can be accessed.

A link to reports menu or user profile was selected before login information was entered and processed.

Enter your user ID and login information and select the login button before you access the reports menu or user profile.

1414 ERROR: IFQ Total Weight does not match Fish Ticket data

1415 ERROR: New IFQ Report values do not match any lines on Landing Report

1416 ERROR: Sold weight or Retained weight is required

1417 ERROR: IPHC Regulatory Area is required

The IPHC Regulatory Area is missing for that IFQ Report.

One or more of the statistical reporting areas entered, have ambiguous IPHC Regulatory Areas that must be resolved.

Edit the IFQ Report for the Fish Ticket that has the ambiguous reporting area.  In the Area column, use the drop down box to select the correct IPHC Regulatory Area.  For example Statistical Reporting Area '375630' may have an IPHC area of '2C' or '3A'.  Use the drop down box to select the correct option. Then Save.

1418 ERROR: IPHC Regulatory Area  AREA  is invalid where:  AREA  is The IPHC Regulatory Area.

1419 ERROR: Retained Weight is required

1420 ERROR: Retained Weight must be numeric, with no decimal point

Retained weight for IFQ reports must be a whole number. The system automatically edits out commas (used for values greater than 999), but does not handle decimal points and fractional values, even if the number to the right of the decimal point is zero.

A non-numeric value was entered. This message can also be given if a fractional value (i.e. a number with a decimal point) is entered

Enter a whole number.

1421 ERROR: Retained Weight cannot be a negative number

1422 ERROR: Deadloss Weight is required

1423 ERROR: Deadloss Weight must be numeric, with no decimal point

Deadloss weight for IFQ reports must be a whole number. The system automatically edits out commas (used for values greater than 999), but does not handle decimal points and fractional values, even if the number to the right of the decimal point is zero.

A non-numeric value was entered. This message can also be given if a fractional value (i.e. a number with a decimal point) is entered

Enter a whole number.

1424 ERROR: Deadloss Weight cannot be a negative number

1425 INFO: IFQ Reports deleted, click Generate IFQ Reports button to regenerate

The IFQ reports were deleted.  Select the Generate IFQ Reports button to regenerate the reports.

1426 INFO: IFQ Reports saved, use Submit IFQ Reports button to submit

The IFQ reports were saved.  Select the Submit IFQ Reports button to submit.

1427 INFO: User Profile updated successfully

Your user profile has been successfully updated.  Please review selections.

1428 ERROR: Pre-printed ticket  TICKET_NUMBER  is already in use where:  TICKET_NUMBER  is The pre-printed ticket number.

1429 ERROR: User  USER_ID  is not an Agency user where:  USER_ID  is The eLandings system user ID.

1430 ERROR: User  USER_ID  does not have Admin privileges where:  USER_ID  is The eLandings system user ID.

1431 ERROR: User  USER_ID  is already in use as a non-agency user where:  USER_ID  is The eLandings system user ID.

1432 ERROR: No Processor users found that match search criteria

This is a search related message that can occur when searching for a Processor User.

No Processor User was found by using the Federal Permit Number, Processor Code, Registered Buyer Number or Registered Crab Receiver Number that was entered on the Processor User Search Panel.

Verify that the search criteria used is correct and that you have not typed something in error.  Try again.  If you are certain that the Processor User exists but is not turning up in the search, there may be a database problem.  Call Restricted Access Management at (907) 596-7474

1433 ERROR: No agency users found that match search criteria

This is a search related message that can occur when searching for an Agency User.

No Agency User was found by using the Name or User ID that was entered on the Agency User Search Panel.

Verify that the search criteria used is correct and that you have not typed something in error.  Try again.  You might also try searching by Agency and looking for the user's name within that Agency.  If you are certain that the Agency User exists but is not turning up in the search, there may be a database problem.  Call Restricted Access Management at (907) 596-7474

1434 ERROR: Number of Landing Report Numbers to return cannot be less than  MIN_SIZE  where:  MIN_SIZE  is Minimum number of landing reports ids per request

1435 ERROR: Number of Landing Report Numbers to return cannot be greater than  MAX_SIZE  where:  MAX_SIZE  is The maximum number of characters that can be stored in the database for the field.

1436 ERROR: Landing Report has no fish tickets

1437 ERROR: Number of Fish Ticket Numbers to return cannot be less than  MIN_SIZE  where:  MIN_SIZE  is Minimum number of landing reports ids per request

1438 ERROR: Number of Fish Ticket Numbers to return cannot be greater than  MAX_SIZE  where:  MAX_SIZE  is The maximum number of characters that can be stored in the database for the field.

1439 ERROR:  USER_ID  is the sole admin user for operation  OPID  and cannot be deleted. where:  USER_ID  is The eLandings system user ID. OPID  is The operation ID.

1442 ERROR: Cannot save report without minimum data

1443 ERROR: Report Date is required

The report date is required information and must be entered.

The report date was not entered.

Verify the report date, and enter the correct value.

1444 ERROR: Report Date is invalid

The system will accept the date in several commonly used formats, and will convert to the standard format.  The report date field was not entered with one of the following formats:  mm/dd/yyyy, m/d/y, mmddyyyy, mm-dd-yyyy, m-d-y.

The report date was entered in a format that was not recognized.  This message can also be seen if the report date is entered with letters in place of digits.

Verify the report date, and enter the correct value.

1445 ERROR: Report Date cannot be in the future

The system does not allow the report date field entered to be in the future.

A date that is in the future has been entered in the report date field.

Verify the report date, and enter the correct value.

1446 ERROR: Report Date requires four digit year

1447 ERROR: Federal Reporting Area is required

1448 ERROR: Federal Reporting Area  AREA  is invalid where:  AREA  is The IPHC Regulatory Area.

1449 ERROR: Special Reporting Area is required

1450 ERROR: Special Reporting Area  AREA  is invalid where:  AREA  is The IPHC Regulatory Area.

1451 ERROR: FMP Area is required

1452 ERROR: FMP Area  AREA  is invalid where:  AREA  is The IPHC Regulatory Area.

1453 ERROR: Product Code is required

1454 ERROR: Product Code  CODE  is not valid where:  CODE  is The numeric disposition code, indicating what is being done with the catch.

1455 ERROR: Count is required

1456 ERROR: Number must be numeric

1457 ERROR: Number cannot be negative

1458 ERROR: Number is too large

1459 WARNING: Number is larger than expected, is that right?

1460 ERROR: Discards not allowed

1461 ERROR: Multiple production lines for FMP Area  AREA , Species  SPECIES , Product Type  TYPE , and Product Code  CODE  where:  AREA  is The IPHC Regulatory Area. SPECIES  is The species code. TYPE  is The operation type code. CODE  is The numeric disposition code, indicating what is being done with the catch.

1463 ERROR: No Production flag is required

1464 ERROR: No Deliveries flag is required

1465 ERROR: Number of Observers is required

An input is required for 'Number Of Observers In Plant' even if there where no observers.

The 'Number Of Observers In Plant' was left blank.

Input the number of observers.  If there were no observers, input '0' (zero).

1466 ERROR: Number of Observers must be numeric

An input is required and it must be a whole number (0,1,2, etc)

An invalid input was made.  Examples of invalid inputs are letters, fractions, decimal numbers (2.0 is invalid).

Input a whole number (0,1,2, etc)

1467 ERROR: Number of Observers cannot be less than zero.

There cannot be a negative (less than zero) number of observers.

A minus sign was mistakenly input.

Remove the minus sign and input the correct number of observers.

1468 ERROR: Number of Observers cannot be greater than  MAX_SIZE  where:  MAX_SIZE  is The maximum number of characters that can be stored in the database for the field.

The maximum number of observers allowed to be input is 20.

A number greater than 20 was input.

Reduce the number of observers to 20 or less.

1469 WARNING: Number of Observers is greater than  MAX_SIZE . Is that right? where:  MAX_SIZE  is The maximum number of characters that can be stored in the database for the field.

It is  unusual to have more than 3 observers in a plant. This is a warning message to confirm that the number of observers input is correct.

A number greater than 3 was input.  A confirmation warning is issued for inputs from 4 to 20.

If the input is correct, click 'Save Ignoring Warnings'.  Otherwise correct the number of observers.

1470 ERROR: At least one Production item is required, or use No Production flag

When submitting a production report either the 'No Production' box (flag) needs to be checked or at least one production detail line is required.

A production report has been submitted without any production detail lines AND the 'No Production' box (flag) has not been checked.

Either input the production detail line(s) or check the 'No Production' box,  whichever is correct for this production report.

1471 ERROR: No production items should be entered if No Production flag is set

If production detail line(s) have been input, then the 'No Production' box (flag) should not be checked.  If there is no production to report, and the 'No Production' box (or Flag) is properly checked, then there should  be no production report detail lines entered.

The 'No Production' box is checked when production detail lines have been input.

Either remove the production detail line(s) or uncheck the 'No Production' box,  whichever is correct for this production report.

1472 ERROR: Production Report  REPORT_ID  not found where:  REPORT_ID  is The eLandings landing report ID

When searching by report ID, the system checks all reports for the authorized operations.  The report IDs are a numeric value and are generated in sequence as reports are created.

The report ID entered was not found in the list of reports for the authorized operations.

Verify the report ID, and enter the correct value.  Reports will not display, if they were created with an operation that is not authorized for the current user.  If you are not sure of the report ID, use the other search criteria to help narrow the results.

1473 ERROR: Production Report is required

1474 ERROR: Production Report  REPORT_ID  already in database as a submitted report where:  REPORT_ID  is The eLandings landing report ID

1475 ERROR: No unsubmitted Production Report with ID  REPORT_ID  found in database where:  REPORT_ID  is The eLandings landing report ID

1476 ERROR: No Production Reports found that match search criteria

The system checks all the reports for every search criteria entered, and when no reports match all the search criteria, there will be no results.

The search criteria entered does not match any reports for the authorized operations.  Some users may have restricted operations.

Verify the search criteria, and enter the correct values.  Reports will not display, if they were created with an operation that is not authorized for the current user.  If you are not sure of all of your search criteria, only enter the search criteria that you are sure of to broaden your search results.

1477 ERROR: IPHC Regulatory Area  AREA  is not valid for stat area  STAT_AREA  where:  AREA  is The IPHC Regulatory Area. STAT_AREA  is The ADF&G Statistical Area identifier.

1478 ERROR: IPHC Regulatory Area is not allowed

1479 ERROR: IFQ Report has already been submitted

1480 ERROR: Fish Ticket  FISH_TICKET_NUMBER  has line items.  You must delete these line items before removing the Fish Ticket. where:  FISH_TICKET_NUMBER  is The ADF&G fish ticket id number.

The system requires the CFEC permit associated with a fish ticket that has line items.  The fish ticket numbers are assigned to the CFEC permits.  The line items are found on another part of the website, which allows you to designate itemized catch and pricing/grading information.

A request to save the landing report was sent, after a CFEC permit line was removed that has line items.

Verify the CFEC Permit Worksheet information.  If it is correct,  select cancle, remove all line items associated with the fish ticket number you are no longer using, go back to the CFEC Permit Worksheet, and remove the CFEC permit.  If you are missing a necessary CFEC permit, reenter the information or press cancle (other changes will be lost).

1481 ERROR: Report codes do not match those for a valid operation

An operation is defined by having a unique combination of any of the following codes: ADF&G Processor Code, Federal Processor Permit Number, Federal Registered Crab Receiver Number (for rationalized crab fisheries), Federal Registered Buyer Number (for halibut/sablefish IFQ fisheries).  These codes appear in a landing report or production report as defaults when you choose your operation.

A combination of codes was entered for ADF&G Processor Code, Federal Processor Permit Number,  Registered Crab Receiver Number,  Registered Buyer Number that does not match an established elandings operation.  This error appears when an operation has not been created for the codes that were entered.

Verify the accuracy of the codes and re-enter.  Or remove (blank out) the Registered Buyer or Crab Receiver if it doesn't belong. If the error persists, a new operation may need to be established. Create the new operation in eLandings. Otherwise call Customer Support at 1-800-304-4846, option #2.

1482 ERROR:  PARM_NAME  must be numeric where:  PARM_NAME  is The name of the parameter

1483 ERROR:  PARM_NAME  is required where:  PARM_NAME  is The name of the parameter

1484 ERROR:  PARM_NAME  exceeded maximum length of  MAX_LENGTH  where:  PARM_NAME  is The name of the parameter MAX_LENGTH  is The maximum length for the parameter

1485 ERROR:  PARM_NAME  must be either 'Y' or 'N' where:  PARM_NAME  is The name of the parameter

1486 ERROR: Grading and Pricing lines are only allowed for itemized catch with a sold disposition

Grading and pricing information may only be be entered for itemized catch with a disposition of 'Sold'.

A value was entered in  Grading and/or Pricing for a catch that does not have a disposition of 'Sold'.

Remove grading and/or pricing information for all catch entries that do not have a disposition of 'Sold'

1487 ERROR: Operation ID is required

Operation ID is required information and must be entered.

Operation ID was not entered.

Verify the operation ID that you wish to add, and enter the correct value.

1488 ERROR: Operation ID  ID  is invalid where:  ID  is The unique numeric identifier for the operation.

The operation ID was not found in the database.  The system expects whole numeric values and that are not a negative.

The operation ID entered is not valid.

Verify the operation ID, and enter the correct value.

1489 ERROR: Physical operation information is required for  OP_TYPE  operations where:  OP_TYPE  is The name of the operation type.

The system requires physical operation information to be entered when using an operation type of custom processing owner, tender, or buying station.

The physical operation information was not entered.

Verify the operation type, and select the correct value.  If the operation type is correct, enter the correct physical operation information.

1491 ERROR: No operations found matching search criteria

1492 ERROR: Operation  ID  cannot be deleted, has dependent operations where:  ID  is The unique numeric identifier for the operation.

1495 ERROR: Registered Crab Receiver name is required

1496 ERROR: Registered Crab Receiver name is too long

1497 ERROR: Registered Buyer name is required

1498 ERROR: Registered Buyer name is too long

1499 ERROR: NMFS Person Name is required

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 sam 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 neccisary.  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 compatable 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 compatable.

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: Percents add up to more than 100 percent

1551 ERROR: Percents 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

1584 ERROR: Message description is required

1585 ERROR: Message constant is required

1586 ERROR: Message constant  NAME  is invalid where:  NAME  is The constant name.

1587 ERROR: Message constant is too long

1588 ERROR: Announcement date is required

1589 ERROR: Announcement date  DATE  is invalid where:  DATE  is The date entered for the announcement.

1590 ERROR: Announcement expiration date is required

1591 ERROR: Announcement expiration date  DATE  is invalid where:  DATE  is The date entered for the announcement.

1592 ERROR: Announcement expiration date requries a four digit year

1593 ERROR: Announcement date requires a four digit year

1594 ERROR: The text of the announcement is required

1595 ERROR: The text of the announcement is too long

1596 ERROR: Announcement title is required

1597 ERROR: Announcement title is too long

1598 ERROR: Announcement ID  ID  is invalid where:  ID  is The unique numeric identifier for the operation.

1599 ERROR: Announcement ID is required

1600 ERROR: At least one announcement method is required

1601 ERROR: Announcement date cannot be after expiration date

1602 ERROR: Announcement expiration date cannot be in the past

1603 ERROR: Interim value for ADF&G Vessel Number must be replaced before Final Report can be submitted

1604 ERROR: Interim value for CFEC Permit Number must be replaced before Final Report can be submitted

1605 ERROR: Interim value for Species Code must be replaced before Final Report can be submitted

1606 INFO:  NUMBER  Landing Reports found that match search criteria where:  NUMBER  is The number of reports found.

The shown number of landing reports were found that match the supplied search criteria.

1607 INFO: One Landing Report found that matches search criteria

One landing report was found that matches the supplied search criteria.

1608 INFO:  NUMBER  Production Reports found that match search criteria where:  NUMBER  is The number of reports found.

The shown number of production reports found match the supplied search criteria.

1609 INFO: One Production Report found that matches search criteria

One production report was found that matches the supplied search criteria.

1610 WARNING: Date range  FROM  -  TO  is invalid, from date is after to date where:  FROM  is The start of the date range. TO  is The end of the date range.

1611 ERROR: Password is invalid

1612 ERROR: Processor Code does not match Processor Code on report

1613 ERROR: Vessel ADF&G Number does not match ADF&G Number on report

1614 ERROR: Port Code does not match Port Code on report

1615 ERROR: Date of Landing does not match Date of Landing on report

1616 ERROR: Federal Permit Number does not match Federal Permit Number on report

1617 ERROR: Date of Report does not match Date of Report on report

1618 INFO: Unsubmitted Landing Report  REPORT_ID  deleted where:  REPORT_ID  is The eLandings landing report ID

The displayed unsubmitted landing report was deleted.

1619 INFO: Unsubmitted Production Report  REPORT_ID  deleted where:  REPORT_ID  is The eLandings landing report ID

The displayed unsubmitted production report was deleted.

1620 ERROR: Query ID is required

1621 ERROR: Query Name is required

1622 ERROR: Query Output Format is required

1623 ERROR: Query Output Format  FORMAT  is invalid where:  FORMAT  is The output file format.

1624 ERROR: Query XML Template is required

1625 ERROR: Query Parameter  PARM  is required where:  PARM  is The query parameter name.

1626 ERROR: Query Parameter  PARM  is invalid,  VALUE  could not be converted to  TYPE  where:  PARM  is The query parameter name. VALUE  is The query parameter value input. TYPE  is The operation type code.

1627 ERROR: Query  ID  not found where:  ID  is The unique numeric identifier for the operation.

1628 ERROR: Query ID  ID  is invalid where:  ID  is The unique numeric identifier for the operation.

1629 ERROR: Query  ID  is not a processor query where:  ID  is The unique numeric identifier for the operation.

1630 ERROR: Query Name is too short

1631 ERROR: Query Name is too long

1632 ERROR: Query Name  NAME  is invalid where:  NAME  is The constant name.

1633 ERROR: Query Jasper Reports XML Template is too long

1634 ERROR: Jasper Reports Error:  MSG  where:  MSG  is The Java Exception message.

1635 ERROR:  NAME  User Security Role required for this function where:  NAME  is The constant name.

1636 ERROR: Comment Text is not allowed for comment code  CODE  where:  CODE  is The numeric disposition code, indicating what is being done with the catch.

1637 ERROR: Species  SPECIES  cannot be sold on a Crab Landing Report where:  SPECIES  is The species code.

Only crab can be sold on a crab landing report. Non-crab species may be entered in the itemized catch as discards or other non-sold dispositions, but sold catch should always be reported on a landing report or fish ticket of the appropriate type. The exception is cod, or other fish sold as bait.

A species that is not a crab species was entered on the crab landing report as sold.

Verify that the species was landed.  Conctact the local office of ADF&G or NMFS enforcement regarding allowable purchase of this species.

1638 ERROR: Species  SPECIES  cannot be sold on a Groundfish Landing Report where:  SPECIES  is The species code.

Only groundfish can be sold on a groundfish landing report. Non-groundfish species may be entered in the itemized catch as discards or other non-sold dispositions, but sold catch should always be reported on a landing report or fish ticket of the appropriate type.

A species that is not a groundfish species was entered on the groundfish ladning report as sold

Verify this species was landed.  Contact the local office of ADF&G or NMFS enforcement regarding allowable purchase of this species.

1639 ERROR: Quantity is required

1640 ERROR: Quantity must be numeric, without a decimal point

1641 ERROR: Quantity is too small

1642 ERROR: Quantity cannot be more than  MAX_QTY  where:  MAX_QTY  is The maximum value.

1645 ERROR: Fish Ticket Number  FT_NUM  is issued to an operation for which user  USERID  is not authorized where:  FT_NUM  is The ADF&G fish ticket id number. USERID  is The eLandings system user ID.

1646 ERROR: Fish Ticket Number  FT_NUM  is not available for import. It is not issued or is already used where:  FT_NUM  is The ADF&G fish ticket id number.

1648 ERROR: Cannot have both pre-issued importable Fish Ticket numbers and regular Fish Ticket numbers in the same landing report

1649 ERROR: A grading/pricing template already exists for species  SPECIES , condition  CONDITION  where:  SPECIES  is The species code. CONDITION  is The numeric condition code.

1650 ERROR: Either Size/Grade or Price is required 

1651 ERROR: At least one grading and pricing item is required 

1652 INFO: Please Enter Grading and Pricing Template Items

Please enter grading and pricing template items.

1653 INFO: Edit Grading and Pricing Template

Please edit the grading and pricing template.

1654 ERROR:  UNIT_OF_EFFORT  must be numeric, without a decimal point where:  UNIT_OF_EFFORT  is The unit of measurement for effort for the gear type, such as number of pot lifts for pot gear.

1655 ERROR: Number of  UNITS  must be numeric, without a decimal point where:  UNITS  is The unit for counting the number of animals in the catch, such as fish or crab.

1656 WARNING: A landing report already exists with the same vessel number, processor code, and date of landing

An identical landing has already been entered.  Only one unique landing is allowed based on the vessel, processor and landing date.

There has been a data entry error which happens to match a previous landing.  Or, this landing was previously input and could be submitted or saved as an un-submitted report.

Review the landing information for accuracy, particularly the date of landing. If data is accurate, then:  a) cancel this report, return to the Reports Menu, find the original report and complete it.  Or b) Save the Report, Ignoring Warnings

1657 INFO: Please review the messages in the Status column of the IFQ Reports section below for NMFS ID  NMFS_ID  and IFQ Permit Number  IFQ_NUMBER  where:  NMFS_ID  is The NMFS ID number for persons involved in IFQ fisheries. IFQ_NUMBER  is The IFQ report sequence number.

Please review the messages in the status column of the IFQ reports section below for the shown NMFS ID and the shown IFQ permit number.

1658 ERROR: A landing report already exists for Seq. Ticket Number  SEQ_NUMBER  and Batch  BATCH_INFO  where:  SEQ_NUMBER  is The sequence number stamped on the fish ticket when received by ADF&G. BATCH_INFO  is The batch year, office code, and batch number. FT_NUM  is The ADF&G fish ticket id number.

1659 ERROR: Special Area  SPECIAL_AREA  is not valid with Federal Reporting Area  FED_AREA . where:  SPECIAL_AREA  is The 5 character trawl gear Special Area. FED_AREA  is The 3 digit Federal Reporting Area.

1660 ERROR: Special Area  SPECIAL_AREA  is not valid with Gear Code  GEAR_CODE . where:  SPECIAL_AREA  is The 5 character trawl gear Special Area. GEAR_CODE  is The numeric gear code.

1661 INFO: No IFQ Reports were generated. Please review IFQ permit and species information.

No IFQ reports were generated.  Please review the IFQ permit and species information.

1664 ERROR: Species Code  SPECIES_CODE  cannot be used on a production line. where:  SPECIES_CODE  is The numeric species code.

The species code entered is invalid on a detail line of a production report.

An invalid species code was input.

Review the species code and correct.

1665 ERROR: Disposition code  CODE  cannot be used on a discard line. where:  CODE  is The numeric disposition code, indicating what is being done with the catch.

1666 ERROR: Product Code  PRODUCT_CODE  is not valid for species  SPECIES_CODE  where:  PRODUCT_CODE  is The product code. SPECIES_CODE  is The numeric species code.

1667 ERROR: Multiple discard lines for species  SPECIES_CODE  and disposition  DISPOSITION_CODE  where:  SPECIES_CODE  is The numeric species code. DISPOSITION_CODE  is The numeric disposition code, indicating what is being done with the catch.

1669 ERROR: Sold Condition Code must be the same as the Itemized Catch Condition Code for non-sold lines

1670 ERROR: Grading/Pricing weight must be the same as the Itemized Catch weight for non-sold lines

1671 ERROR: Price is not allowed on grading/pricing lines for non-sold itemized catch lines

1672 ERROR: Size/Grade is not allowed on grading/pricing lines for non-sold itemized catch lines

1673 WARNING: IFQ permits should be entered when management program is IFQ

1674 ERROR: Only IFQ permits for halibut are allowed when management program is CDQ

1676 ERROR: Sequential ticket number  SEQ_NUM  entered multiple times where:  SEQ_NUM  is The stamped sequential ticket number

1677 ERROR: At least one grading/pricing product type must be primary

1678 ERROR: No grading/pricing product types may be primary

1680 ERROR: Return Receipt already processed

1681 ERROR: Report file  FILE  on workstation, could not be read where:  FILE  is The user file name on the workstation

1683 INFO: Report file  FILE  found in return receipt but not found on workstation, and will be added where:  FILE  is The user file name on the workstation

1684 INFO: Processing return receipt file  FILE  where:  FILE  is The user file name on the workstation

1685 WARNING: Report file  FILE  was updated and resent. Expect another return receipt for the update where:  FILE  is The user file name on the workstation

1686 INFO: Report file  FILE  was resent. Expect another return receipt where:  FILE  is The user file name on the workstation

1687 ERROR: Report file  FILE  was updated more recently than the version in the return receipt. Please retransmit where:  FILE  is The user file name on the workstation

1688 INFO: Report file  FILE  on workstation was not marked as sent, return receipt version will be saved where:  FILE  is The user file name on the workstation

1691 INFO: User file  FILE  found in return receipt but not found on workstation, and will be added where:  FILE  is The user file name on the workstation

1692 ERROR: Return receipt user file  FILE  contained only messages where:  FILE  is The user file name on the workstation

1694 INFO:  NUMBER  report numbers received where:  NUMBER  is The number of reports found.

1695 INFO:  NUMBER  fish ticket numbers received where:  NUMBER  is The number of reports found.

1696 ERROR: A report that has been sent by email cannot be updated until the return receipt has been processed

1698 ERROR: User cannot be both an Admin and a Read-Only user

1699 ERROR: IFQ Area/Fishery is required.

1700 ERROR: IFQ Area/Fishery  AREA  is not valid. where:  AREA  is The IPHC Regulatory Area.

1699 ERROR: IFQ Area/Fishery is required.

1700 ERROR: IFQ Area/Fishery  AREA  is not valid. where:  AREA  is The IPHC Regulatory Area.

1701 ERROR: IFQ Area/Fishery  AREA  is not valid for Species  SPECIES . where:  AREA  is The IPHC Regulatory Area. SPECIES  is The species code.

1702 ERROR: Pounds to max-out permit can only be entered here if Area/Fishery has been entered

1703 ERROR: NMFS ID  NMFS_ID , IFQ Permit  IFQ_PERMIT_NUMBER , Species  SPECIES  combination is entered both with and without Area/Fishery where:  NMFS_ID  is The NMFS ID number for persons involved in IFQ fisheries. IFQ_PERMIT_NUMBER  is The NMFS Restricted Access Management Division IFQ permit number. SPECIES  is The species code.

The IFQ permit and species code, on the IFQ Permit Worksheet, can match more than once for each NMFS ID only if each has a different Area/Fishery.

1704 ERROR: NMFS ID  NMFS_ID , IFQ Permit  IFQ_PERMIT_NUMBER , Species  SPECIES , IPQ Permit  IPQ_PERMIT_NUMBER  combination is entered both with and without Area/Fishery where:  NMFS_ID  is The NMFS ID number for persons involved in IFQ fisheries. IFQ_PERMIT_NUMBER  is The NMFS Restricted Access Management Division IFQ permit number. SPECIES  is The species code. IPQ_PERMIT_NUMBER  is The NMFS Restricted Access Management Division Processor quota share permit number.

The IFQ permit, species code, and the IPQ permit, on the IFQ Permit Worksheet, can match more than once for each NMFS ID only if each has a different Area/Fishery.

1705 ERROR: Area/Fishery  AREA  in IFQ permits for species  SPECIES  has no itemized catch where:  AREA  is The IPHC Regulatory Area. SPECIES  is The species code.

1706 ERROR: Area/Fishery  AREA  for species  SPECIES  has itemized catch, but no IFQ permit(s) where:  AREA  is The IPHC Regulatory Area. SPECIES  is The species code.

1707 ERROR: Part or all of line item  ITEM_NUM  cannot be allocated to a CFEC permit where:  ITEM_NUM  is The itemized catch line item number.

The automatic allocation of itemized catch to CFEC permits has many complicated business rule to insure that the right weights and area/fisheries are assigned to the right permits, to allow IFQ reports to be generated according to the area/fisheries and max out pounds specified on the IFQ permit worksheet. The automated allocation logic was not able to completely allocate the indicated itemized catch line.

This error can be caused by itemized catch and statistical area data that cannot be divided up without violating the area/fishery and max out pounds requests entered on the IFQ permit worksheet. This might be because all of the IFQ permits for one or more of the CFEC permits have a particular area/fishery entered and one or more of the statistical areas on the statistical area worksheet do not have that area/fishery. It can also be causes by situations where the program cannot figure out the right way to divide up the itemized catch line, particularly if the statistical areas involved have ambiguous IPHC areas.

1708 ERROR: A line item assigned to Fish Ticket  FT_NUM  does not fit the area/fishery and max out pounds constraints entered on the IFQ Permit Worksheet for the CFEC permit where:  FT_NUM  is The ADF&G fish ticket id number.

An itemized catch line has been assigned to the specified fish ticket, either by the user or by the automated allocation program. However, the weights and area/fisheries for the line cannot be reconciled with the area/fisheries and max out pounds entered on the IFQ Permit Worksheet.

This error can be caused by itemized catch and statistical area data that cannot be divided up without violating the area/fishery and max out pounds requests entered on the IFQ permit worksheet. It can also be causes by situations where the program cannot figure out the right way to divide up the itemized catch line, particularly if the statistical areas involved have ambiguous IPHC areas.

1709 ERROR: Max out pounds for Area/Fishery  AREA  for Fish Ticket  FT_NUM  cannot be satisfied where:  AREA  is The IPHC Regulatory Area. FT_NUM  is The ADF&G fish ticket id number.

The automatic allocation of itemized catch to CFEC permits has many complicated business rule to insure that the right weights and area/fisheries are assigned to the right permits, to allow IFQ reports to be generated according to the area/fisheries and max out pounds specified on the IFQ permit worksheet. The automated allocation logic was not able to itemized catch line weight to satisfy the max out pounds specified.

This error can be caused by specifying more max out pounds than there are pounds on itemized catch lines that can be assigned to the fish ticket and area/fishery. It can also be causes by situations where the program cannot figure out the right way to divide up the itemized catch line, particularly if the statistical areas involved have ambiguous IPHC areas.

1710 SYSTEM ERROR: Total line item landed weight was  BEFORE_WT  before allocating to permits and  AFTER_WT  afterwards where:  BEFORE_WT  is The weight before allocations. AFTER_WT  is The weight after allocations.

The sum of the landed weights of all the itemized catch lines was one amount before splitting lines to assign fish ticket, and a different amount after the splits.

This error can only be caused by an internal system error.

1711 ERROR: XML Schema Version number is required

The XML Schema Version number identifies the version of the XML file format for import and export XML files for landing and production reports, and other eLandings data excehanged as XML files. It is required input.

1712 ERROR: XML Schema Version number must be numeric

The XML Schema Version number identifies the version of the XML file format for import and export XML files for landing and production reports, and other eLandings data excehanged as XML files. It must be numeric. A non-numeric value does not identify any file format.

1713 ERROR: XML Schema Version  NUM  is invalid where:  NUM  is The number of fish ticket numbers that have been issued but not imported yet.

The XML Schema Version number identifies the version of the XML file format for import and export XML files for landing and production reports, and other eLandings data excehanged as XML files. It must a version number that identifies a valid file format. eLandings production support personnel can provide information on valid schema version numbers and the file formats they represent.

1714 WARNING: Max out pounds  REQ_LBS  requested for NMFS ID/IFQ Permit  NMFS_ID_PERMIT  Area/Fishery  AREA  not honored, actual pounds is  LBS  where:  NMFS_ID_PERMIT  is The NMFS ID and IFQ Permit number. AREA  is The IPHC Regulatory Area. REQ_LBS  is The max out pounds requested for the permit. LBS  is The actual number of pounds on the IFQ reports.

The max out pounds requested for the IFQ permit and Area/Fishery does not match the actual pounds on the IFQ report(s). Pounds for max out are in IFQ quota management units, which is pounds in condition 05 for halibut and round pounds for other species.

This situation can be caused by problems in the automatic permit allocation and IFQ report generation process. Permit allocation is quite complicated, and some combinations of permits, area/fisheries, max out pounds, and itemized catch can prevent the automatic generation from completing successfully. This situation can also be caused by user input for IFQ reports.

1715 WARNING: Max out pounds  REQ_LBS  requested for NMFS ID/IFQ Permit/IPQ Permit  NMFS_ID_PERMIT  Area/Fishery  AREA  not honored, actual pounds is  LBS  where:  NMFS_ID_PERMIT  is The NMFS ID and IFQ Permit number. AREA  is The IPHC Regulatory Area. REQ_LBS  is The max out pounds requested for the permit. LBS  is The actual number of pounds on the IFQ reports.

The max out pounds requested for the IFQ permit and Area/Fishery does not match the actual pounds on the IFQ report(s). Pounds for max out are in IFQ quota management units, which is pounds in condition 05 for halibut and round pounds for other species.

This situation can be caused by problems in the automatic permit allocation and IFQ report generation process. Permit allocation is quite complicated, and some combinations of permits, area/fisheries, max out pounds, and itemized catch can prevent the automatic generation from completing successfully. This situation can also be caused by user input for IFQ reports.

1716 ERROR: The Statistical Area Worksheet cannot be used for this Landing Report. Please enter statistical areas on Itemized Catch lines

Fishery managers have determined that in some fisheries the statistical area worksheet does not provide adequate data. In these cases the statistical area and effort data must be input on the itemized catch lines. 

Statistical area data was entered in the statistical area worksheet on a landing report were the statistical area worksheet is not allowed.

1717 ERROR: Total sold weight for species  SPECIES  on Fish Ticket  FT_NUM  does not match sold weight on IFQ Report for stat area  STAT_AREA  where:  FT_NUM  is The ADF&G fish ticket id number. SPECIES  is The species code. STAT_AREA  is The ADF&G Statistical Area identifier.

1718 ERROR: Total retained weight for species  SPECIES  on Fish Ticket  FT_NUM  does not match retained weight on IFQ Report for stat area  STAT_AREA  where:  FT_NUM  is The ADF&G fish ticket id number. SPECIES  is The species code. STAT_AREA  is The ADF&G Statistical Area identifier.

1719 ERROR: Total deadloss weight for species  SPECIES  on Fish Ticket  FT_NUM  does not match deadloss weight on IFQ Report for stat area  STAT_AREA  where:  FT_NUM  is The ADF&G fish ticket id number. SPECIES  is The species code. STAT_AREA  is The ADF&G Statistical Area identifier.

1720 ERROR: Due to IFQ Permit allocation requirements, stat area is required on Itemized Catch lines for species  SPECIES  where:  SPECIES  is The species code.

1721 ERROR: Species  SPECIES  is not in effect for date  DATE  where:  SPECIES  is The species code. DATE  is The date entered for the announcement.

The species code 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.

1722 ERROR: Management Program  MGMTPGM  is not in effect for date  DATE  where:  MGMTPGM  is The Management Program. DATE  is The date entered for the announcement.

The management program 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.

1723 ERROR: Management Program ID  MANAGEMENT_PROGRAM_ID  is not in effect for date  DATE  where:  MANAGEMENT_PROGRAM_ID  is The fisher's identification number for the management program under which the fishing was conducted. DATE  is The date entered for the announcement.

The management program ID 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.

1724 ERROR: CFEC Fishery  FISHERY  is not in effect for date  DATE  where:  FISHERY  is The CFEC fishery code that is on the CFEC permit card. DATE  is The date entered for the announcement.

The CFEC fishery code 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.

1725 ERROR: Condition Code  CODE  is not in effect for date  DATE  where:  CODE  is The numeric disposition code, indicating what is being done with the catch. DATE  is The date entered for the announcement.

The condition code 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.

1726 ERROR: Disposition Code  CODE  is not in effect for date  DATE  where:  CODE  is The numeric disposition code, indicating what is being done with the catch. DATE  is The date entered for the announcement.

The disposition code 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.

1727 ERROR: FMP Area  AREA  is not in effect for date  DATE  where:  AREA  is The IPHC Regulatory Area. DATE  is The date entered for the announcement.

The FMP 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.

1728 ERROR: Gear Code  CODE  is not in effect for date  DATE  where:  CODE  is The numeric disposition code, indicating what is being done with the catch. DATE  is The date entered for the announcement.

The gear code 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.

1729 ERROR: Harvest Code  CODE  is not in effect for date  DATE  where:  CODE  is The numeric disposition code, indicating what is being done with the catch. DATE  is The date entered for the announcement.

The harvest 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.

1731 ERROR: Operation Type  TYPE  is not in effect for date  DATE  where:  TYPE  is The operation type code. DATE  is The date entered for the announcement.

The operation type 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.

1732 ERROR: Port Code  CODE  is not in effect for date  DATE  where:  CODE  is The numeric disposition code, indicating what is being done with the catch. DATE  is The date entered for the announcement.

The port code 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.

1733 ERROR: Area/Fishery  AREA  is not in effect for date  DATE  where:  AREA  is The IPHC Regulatory Area. DATE  is The date entered for the announcement.

The IFQ area/fishery 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.

1734 ERROR: Statistical Area  AREA  is 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.

1735 ERROR: Salmon/Shellfish Statistical Area  AREA  not valid for groundfish where:  AREA  is The IPHC Regulatory Area.

5 digit Salmon/Shellfish statistical areas cannot be used on groundfish landing reports or groundfish lines on salmon troll reports. 6 digit groundfish statistical areas should be used.

1736 ERROR: Salmon/Shellfish Statistical Area  AREA  not valid on crab reports west of Cape Suckling where:  AREA  is The IPHC Regulatory Area.

5 digit Salmon/Shellfish statistical areas cannot be used to report crab fishing west of Cape Suckling. 6 digit groundfish statistical areas should be used.

1737 ERROR: Groundfish Statistical Area  AREA  not valid on crab reports east of Cape Suckling where:  AREA  is The IPHC Regulatory Area.

6 digit groundfish statistical areas cannot be used to report crab fishing east of Cape Suckling. 5 digit Salmon/Shellfish statistical areas should be used.

1738 ERROR: Salmon/Shellfish Statistical Area  AREA  not valid for production reports where:  AREA  is The IPHC Regulatory Area.

5 digit Salmon/Shellfish statistical areas cannot be used on groundfish landing reports or production reports. 6 digit groundfish statistical areas should be used.

1739 WARNING: Out of State flag is set, but port code is in Alaska

The out of state flag indicates a landing outside of Alaska, but the port of landing is in Alaska.

The out of state flag does not make sense for the port of landing.

Reset the flag.

1741 ERROR: Tender Vessel ADF&G Number is required

The ADF&G number of the tender is required information and must be entered. ADF&G vessel numbers are five digit numbers issued by the Commercial Fisheries Entry Commission (CFEC).

Vessel ADF&G numbers are required for at-sea and tender operation setups, landing reports, and at-sea production reports.

Enter a valid ADF&G vessel number. Leading zeroes are not required, but may be entered.

1742 ERROR: Tender Vessel ADF&G Number  VESSEL_NUM  is not valid where:  VESSEL_NUM  is The ADF&G Vessel number, issued by CFEC.

The tender ADF&G vessel number entered was not found in the database.

The vessel ADF&G numbers are stored in the database. They are issued by CFEC, and are updated daily. The vessel ADF&G number can be at most 5 characters.

Enter a valid ADF&G vessel number. Leading zeroes are not required, but may be entered. If you are sure the vessel number is the correct one for the tender, contact eLandings system support.

1743 ERROR: Tender Vessel ADF&G Number cannot be the same as the delivering vessel ADF&G Number

The tender vessel ADF&G number entered was the same as the ADF&G Vessel number.

The Vessel ADF&G Number should be the vessel number of the catcher vessel. The Tender Vessel ADF&G Number should be the vessel number of the tender that took delivery from the catcher vessel. A vessel cannot deliver to itself, if it delivering its own catch it is not involved in tendering, even though it may act as a tender at other times.

If the tender took delivery from a catcher vessel enter that vessel's ADF&G vessel number as the ADF&G Vessel Number and the tender's ADF&G vessel number as the Tender ADF&G Vessel Number. If the vessel was doing its own fishing (i.e. not acting as a tender) don't enter anything in the Tender ADF&G Vessel Number, even if the vessel acts as a tender at other times.

1744 ERROR: Pre-printed ticket cannot start with 'I'

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.  A leader letter of 'I' stands for interim/import, and is reserved for landing reports imported through the eLandings website.

The pre-printed fish ticket entered starts with the letter 'I'.

Verify the fish ticket number, and enter the correct value.  The leading letter of the type of landing report will be the correct letter to enter.  For example, G is for groundfish and C is for crab. If the pre-printed fish ticket number starts with GI or CI the letter Z should be used.

1745 ERROR: Management Program must be  MGMT_PGMS  where:  MGMT_PGMS  is The allowable Management Program(s).

The management program must be one of the management programs specified.

This message is given when the business rules determine that only certain management programs are allowed for the reported data.

Change the Management Program to one of the allowable values. If you do not want to change the Management Program review all data especially gear code and CFEC permit fisheries, and change as needed.

1746 ERROR: Install Directory is required

1747 ERROR: Install directory name is too long

The directory provided is too long. Excessively long directory path names are commonly used in cracking attempts, extra long directories paths should not be required for eLandings.

1757 ERROR: Installation type is required

1758 ERROR: Installation type is too long

1768 ERROR: Transmit type is required

1769 ERROR: Transmit type is too long

1776 ERROR: Cannot write to directory  DIR  where:  DIR  is The directory path name.

1777 ERROR:  DIR  is not a directory where:  DIR  is The directory path name.

1780 WARNING: Production Report  REPORT  already exists for the same header information where:  REPORT  is The production report ID.

Another report was found with the same Federal Permit Number, Vessel ADF&G Number, Processor Code, Management Program, Port Code, Gear Code, Federal Reporting Area, Special Area, and Report Date.

1781 WARNING: The Federal Permit Number  FED_PERMIT  and ADF&G Number  ADFG_NUM  combination does not match any registered operation where:  FED_PERMIT  is The Federal Permit Number. ADFG_NUM  is The ADF&G Vessel number, issued by CFEC.

The Federal Permit Number and Vessel ADF&G Number combination on the report does not match any of the operations where the user is authorized

1782 ERROR: Trip event is required

1783 ERROR: Trip event  CODE  is invalid where:  CODE  is The numeric disposition code, indicating what is being done with the catch.

1784 ERROR: Trip event  CODE  not in effect for date  DATE  where:  CODE  is The numeric disposition code, indicating what is being done with the catch. DATE  is The date entered for the announcement.

1785 ERROR: Temperature is required

1786 ERROR: Temperature must be numeric

1787 ERROR: Temperature  TEMPERATURE  is too low where:  TEMPERATURE  is A fish temperature

1788 ERROR: Temperature  TEMPERATURE  is too high where:  TEMPERATURE  is A fish temperature

1789 ERROR: Groundfish Statistical Area  AREA  not valid for salmon where:  AREA  is The IPHC Regulatory Area.

6 digit Groundfish statistical areas cannot be used on salmon landing reports or salmon lines on salmon troll reports. 5 digit Salmon/Shellfish statistical areas should be used.

1790 WARNING: Directory  DIR  does not exist, and will be created where:  DIR  is The directory path name.

The directory specified does not exist. If the warning is ignored it will be created as a new directory.

1791 ERROR: Chill Water Temperature is required

1792 ERROR: Chill Water Temperature must be numeric

1793 ERROR: Chill Water Temperature  TEMPERATURE  is too low where:  TEMPERATURE  is A fish temperature

1794 ERROR: Chill Water Temperature  TEMPERATURE  is too high where:  TEMPERATURE  is A fish temperature

1795 WARNING: Chill Water Temperature  TEMPERATURE  is low where:  TEMPERATURE  is A fish temperature

1796 WARNING: Chill Water Temperature  TEMPERATURE  is high where:  TEMPERATURE  is A fish temperature

1797 ERROR: Report Date range is required

1798 ERROR: Report Date range is invalid

1799 ERROR: Update Date range is required

1800 ERROR: Update Date range is invalid

1801 ERROR: Logging Level is required

Logging level must be provided, and must be a valid value

1802 ERROR: Logging Level must be numeric

1803 ERROR: Logging Level cannot be negative

The logging level must be within the range used in the system. Values outside the valid range have no meaning to the system.

1804 ERROR: Logging Level cannot be greater than  LEVEL  where:  LEVEL  is The maximum Logging Level.

The logging level must be within the range used in the system. Values outside the valid range have no meaning to the system.

1805 INFO:  MSG  where:  MSG  is The Java Exception message.

This message is used to provide general information about activities on the system.

1817 ERROR: Period is required

Period is a fishing time indicator defined and determined by fishery managers. The period is a two digit numeric code, with leading zeros.

1818 ERROR: Period must be numeric

Period is a fishing time indicator defined and determined by fishery managers. The period is a two digit numeric code, with leading zeros.

1819 ERROR: Chill type is required

Chill (Refrigeration) Type specify the cooling technique used on a fishing / tender vessel to keep fish cool. Types include: ICE = ice, SLH = Slush ice, RSW = Refrigerated Seawater system, CSW = Circulating Seawater system, FAZ = Frozen at sea, and LIV = Fish delivered live. The chill (refrigeration) type is related to the fish temperature.

1820 ERROR: Chill type is invalid

Chill (Refrigeration) Type specify the cooling technique used on a fishing / tender vessel to keep fish cool. Types include: ICE = ice, SLH = Slush ice, RSW = Refrigerated Seawater system, CSW = Circulating Seawater system, FAZ = Frozen at sea, and LIV = Fish delivered live. The chill (refrigeration) type is related to the fish temperature.

1821 ERROR: Location code is required

The location code is used by agency staff to designate a region within a statistical area. These designations; their creation, definition, maintenance and use, are field office specific. Location codes are numeric and range from 00-99 in value. The definitions, interpretations and uses of these location codes are not currently available in the eLandings system at this time.

1822 ERROR: Location code must be numeric

The location code is used by agency staff to designate a region within a statistical area. These designations; their creation, definition, maintenance and use, are field office specific. Location codes are numeric and range from 00-99 in value. The definitions, interpretations and uses of these location codes are not currently available in the eLandings system at this time.

1823 INFO: Return receipt sent to  EMAIL  where:  EMAIL  is The entered email address.

A return receipt file was emailed to the specified email address.

1824 ERROR: Magnetic Stripe data not in valid format

The magnetic stripe data was read in, but it was not in the proper format.

1825 ERROR: Total sold weight on fish ticket  FISH_TICKET_NUMBER  does not match total sold weight on IFQ reports for species  SPECIES_CODE  where:  FISH_TICKET_NUMBER  is The ADF&G fish ticket id number. SPECIES_CODE  is The numeric species code.

1826 ERROR: Total retained weight on fish ticket  FISH_TICKET_NUMBER  does not match total retained weight on IFQ reports for species  SPECIES_CODE  where:  FISH_TICKET_NUMBER  is The ADF&G fish ticket id number. SPECIES_CODE  is The numeric species code.

1827 ERROR: Total deadloss weight on fish ticket  FISH_TICKET_NUMBER  does not match total deadloss weight on IFQ reports for species  SPECIES_CODE  where:  FISH_TICKET_NUMBER  is The ADF&G fish ticket id number. SPECIES_CODE  is The numeric species code.

1828 ERROR: Statistical area  STAT_AREA  does not map to Federal Reporting Area  FED_AREA  for report, maps to  FED_AREAS  where:  STAT_AREA  is The ADF&G Statistical Area identifier. FED_AREA  is The 3 digit Federal Reporting Area. FED_AREAS  is The federal reporting areas for the stat area.

1829 ERROR: Only at-sea operations can be used when creating consolidated landing reports

1830 ERROR: Only Catcher/Processor operations can create consolidated landing reports

1831 ERROR: CFEC Permit is required for management program  MGMT_PGM  where:  MGMT_PGM  is The management program.

1832 ERROR: No production reports with production or discards found for date range

1833 ERROR: At least one statistical area must be entered

1834 ERROR: Manual IFQ Report flag cannot be set if the landing report has IFQ reports

1837 ERROR: User  USER_ID  is not authorized to access reports for the Registered Buyer Number  REG_BUYER_NUM  where:  USER_ID  is The eLandings system user ID. REG_BUYER_NUM  is The NMFS Restricted Access Management Division registered buyer number for halibut and sablefish IFQ.

1838 ERROR: User  USER_ID  is not authorized to access reports for the RCR Number  RCR_NUM  where:  USER_ID  is The eLandings system user ID. RCR_NUM  is The NMFS Restricted Access Management Division registered crab receiver number for crab IFQ.

1839 ERROR: Weight must be less than 1,000 metric tons.

The system does not allow the weight entered to be greater than 1,000 metric tons.

The weight entered, in the weight field, is greater than 1,000 metric tons.

Verify the weight, and enter the correct value.

1840 WARNING: Weight is greater than  MAX_EXPECTED_WEIGHT  metric tons. Is this correct? where:  MAX_EXPECTED_WEIGHT  is The maximum allowable weight.

This warning is generated when the weight entered is between the maximum expected metric tons (varies by species) and the maximum of 1000 metric tons.  The system will let you continue when you select Save Ignoring Warnings.  This button only appears when no errors are generated with the warnings.

The weight entered, is between the maximum expected (varies by species) and the maximum of 1,000 metric tons.

Verify that the weight entered is correct, and if it is, select Save Ignoring Warnings at the bottom of the website.  If the weight is not correct, enter the correct weight and select Save.

1844 ERROR: Sample weight is required 

The sample weight must be entered.

1845 ERROR: Sample weight  WEIGHT  is invalid  where:  WEIGHT  is The weight in pounds.

The sample weight entered is not valid.

1846 ERROR: Sample count is required 

The sample count must be entered.

1847 ERROR: Sample count  COUNT  is invalid  where:  COUNT  is The sample count

The sample count entered is not valid.

1848 ERROR: Average weight is required 

The average weight must be entered.

1849 ERROR: Average weight  WEIGHT  is invalid  where:  WEIGHT  is The weight in pounds.

The average weight entered is not valid.

1850 ERROR: Average weight  WEIGHT  is too small for species  SPECIES  where:  WEIGHT  is The weight in pounds. SPECIES  is The species code.

The average weight entered is too small for the species.

1851 ERROR: Average weight  WEIGHT  is too large for species  SPECIES  where:  WEIGHT  is The weight in pounds. SPECIES  is The species code.

The average weight entered is too large for the species.

1852 ERROR: At least one user is required 

At least one userid must be entered or selected.

1853 WARNING: Condition Code of  CODE  is an unexpected delivery condition for a Chill Type of FAS and CFEC Fisheries of S05B and S15B, on a line with Chinook or Coho. where:  CODE  is The numeric disposition code, indicating what is being done with the catch.

This warning is generated when line items are entered with a Condition Code other than 07 for Chill Type of FAS and CFEC Fishery is S05B or S15B.  This is an unexpected Condition Code for Frozen At Sea processing for the troll fisheries in this area.

A line item was entered with a Condition Code of 07 when the Chill Type was determined to be FAS and the CFEC Fishery is S05B or S15B, on a line item with Chinook or Coho.

Verify the CFEC Fishery, Chill Type, Condition Codes, and Species and correct as needed.  If there is no correction needed, you can accurately report by save or submit ignoring warnings.

1854 ERROR: Time of landing is required 

The time of landing records is required. 

The time of landing was not entered on the form. 

Enter the time of landing on the form. 

1855 ERROR: Time of landing is invalid

The time of landing records is invalid. 

The time of landing was not entered incorrectly on the form. 

Enter the time of landing on the form in the formate HH:MM or HH.MM or HHMM For example, 01:30 or 01.30 or 0130 

1856 WARNING: Condition Code of  CODE  is an unexpected delivery condition for a Dock Delivered Chinook or Coho in a CFEC Fishery of S05B or S15B. where:  CODE  is The numeric disposition code, indicating what is being done with the catch.

This warning is generated when line items are entered with a Condition Code other than 04 for Dock Deliveries, and CFEC Fishery is S05B or S15B, on line items with Chinook or Coho.

A line item was entered with a Condition Code other than 04 for a Dock Delivery and the CFEC Fishery is S05B or S15B, on a line item with Chinook or Coho

Verify the CFEC Fishery, Dock Delivery flag, Condition Codes, and Species and correct as needed.  If there is no correction needed, you can accurately report by save or submit ignoring warnings.

1857 ERROR: From Time is required

A search From Date is required when searching for reports.

The From Time was left blank.

Enter a valid From Time.

1858 ERROR: From Time is invalid

The system will accept the time in several commonly used formats, and will convert to the standard format.  The from time field was not entered with one of the following formats:  HH:MM, HH:MM:SS, HHMM, HHMMSS.

The from time field was entered in a format that was not recognized. This message can also be seen if the from time field is entered with letters in place of digits.

Verify the from time field, and enter the correct value.

1859 ERROR: To Time is required

A search To Date is required when searching for reports.

The To Time was left blank.

Enter a valid To Time.

1860 ERROR: To Time is invalid

The system will accept the time in several commonly used formats, and will convert to the standard format.  The to time field was not entered with one of the following formats:  HH:MM, HH:MM:SS, HHMM, HHMMSS.

The to time field was entered in a format that was not recognized. This message can also be seen if the to time field is entered with letters in place of digits.

Verify the to time field, and enter the correct value.

1861 ERROR: No reports selected

The application allows the user to select reports for processing, but none was selected.

Select a report and try again.

1864 ERROR: Chum Percentage is required

A percentage must be entered in order to apply it to landing reports.

1865 ERROR: Chum Percentage must be numeric

The chum percentage entered is invalid, it must be a number between 0 and 100.

1866 ERROR: Chum Percentage cannot be less than zero

The chum percentage entered was less than zero, which is not possilble.

1867 ERROR: Chum Percentage cannot be greater than 100

The chum percentage entered was more than 100 percent , which is not possilble.

1868 WARNING: Chum Percentage is greater than  PERCENT , is that correct? where:  PERCENT  is The chum percentage.

The chum percentage entered was uncommonly large. The system gives this message so the user can confirm that the chum percentage was entered correctly.

1870 ERROR: From/To Date Range is too large

The date range specified by the From Date and To Date is too big.

The date range for chum percentage mass updates can be a maximum of 3 days.

1871 ERROR: Landing report  REPORT_ID  is not a Bristol Bay salmon landing report, Chum Percentage adjustment is not allowed where:  REPORT_ID  is The eLandings landing report ID

The chum percentage mass change capability is only for use with landing reports in the Bristol Bay salmon fisheries.

1873 ERROR: Landing report  REPORT_ID  does not have mixed salmon itemized catch, it is required for Chum Percentage mass change where:  REPORT_ID  is The eLandings landing report ID

In order to apply a chum percentage to a landing report the report must have mixed salmon itemized catch to take the percentage from.

1875 ERROR: Create Date  FROM  for data file cannot be after usage date  TO  where:  FROM  is The start of the date range. TO  is The end of the date range.

The create date of the data is after the date the data is being used. This is illogical.

1876 ERROR: The Create Date of the data file is too old. The data is stale

The data file must be used in a timely manner. Old data files contain stale data that can cause system problems.

1877 WARNING: Nearest Bay and Headland should not contain stat areas or district and subdistrict codes

It appears that the Nearest Bay and Headland contains the numeric pattern of a statistical area or district and subdistrict pattern.  The intention of this field is to record the commmon names of the nearest bays or headlands.

1878 ERROR: Chill Type  CHILL_TYPE  not effective for date  DATE  where:  CHILL_TYPE  is The selected Chill Type. DATE  is The date entered for the announcement.

The Chill Type has been retired or is not in effect yet.

A Chill Type was used that is no longer valid.

Verify your Chill Type and use the most accurate code.

1879 ERROR: Delivery Port or Region is invalid

Delivery Port or Region is required for IFQ crab deliveries to stationary floating processors. It should not contain special characters.

1880 ERROR: Encrypted Number is invalid

Encrypted number is invalid.

The Encrypted number was entered incorrecly or is invalid.

Review your encrypted number and try again, or verify the number with the processing plant.  You may request a new encrypted number.

1881 ERROR: Encrypted Number is stale

Encrypted number is stale.

The Encrypted number was reserved on a previous date.

Review your encrypted number and try again, or verify the number with the processing plant.  You may request a new encrypted number.

1882 ERROR: Encrypted Number is reserved for another vessel

Encrypted number is reserved for another vessel.

An encrypted number was used, which was intended for another vessel.

Review your encrypted number and try again, or verify the number with the processing plant.  You may request a new encrypted number.

1883 ERROR: Halibut may not be reported on a Salmon Landing.

Halibut are not permitted on Salmon landings

A halibut line item was included on a salmon landing

Remove the halibut line item from the salmon landing. Create a groundfish landing for the halibut items.

1884 WARNING: Nearest headland value is missing. This information may be required by the Area Management Biologists.

No value was entered in the Nearest Bay or Headland field

No value was entered in the Nearest Bay or Headland field

Enter a text description in the nearest bay or headland field

1885 ERROR: Date Fishing Ended is required

The date fishing ended is required information and must be entered.

The date fishing ended was not entered.

Verify the date fishing ended, and enter the correct value.

1886 ERROR: Date Fishing Ended is invalid

The system will accept the date in several commonly used formats, and will convert to the standard format.  The date fishing ended field was not entered with one of the following formats:  mm/dd/yyyy, m/d/y, mmddyyyy, mm-dd-yyyy, m-d-y.

The date fishing ended was entered in a format that was not recognized. This message can also be seen if the date fishing ended is entered with letters in place of digits.

Verify the date fishing ended, and enter the correct value.

1887 ERROR: Date Fishing Ended requires four digit year

1888 ERROR: Date Fishing Ended cannot be before this date in  YEAR  where:  YEAR  is The earliest year allowed to be entered.

The system restricts the date fishing ended field from being dated more than six years in the past.

A date earlier than six years in the past has been entered in the date fishing ended field.

Verify the date fishing ended, and enter the correct value.

1889 ERROR: Date Fishing Ended cannot be in the future

The system restricts the date fishing ended entered from being dated in the future.

A date that is in the future has been entered in the date fishing ended field.

Verify the date fishing ended, and enter the correct value.

1890 WARNING: CFEC Permit  PERMIT  year does not match Date of Landing year where:  PERMIT  is The CFEC Permit.

The year sequence date of the CFEC permit does not match the year of the date of landing.

This can be caused by using an old CFEC permit, or by using a new one that was received before the beginning of the year for which it is valid.

1891 ERROR: Delivery Port or Region is required

Delivery Port or Region is required for IFQ crab deliveries to stationary floating processors.

1892 ERROR: Date Fishing Ended cannot be before Date Fishing Began

The date fishing ended cannot be before the date fishing began, that is illogical.

A date fishing began or date fishing ended was mis-entered.

Verify the date fishing ended, and enter the correct value.

1893 ERROR: Date Fishing Ended cannot be after Date of Landing

The date fishing ended cannot be after the date of landing, that is illogical.

A date fishing ended or date of landing was mis-entered.

Verify the date fishing ended, and enter the correct value.

1894 ERROR: Average weight for  SPECIES  is required where:  SPECIES  is The species code.

The average weight for the species is required.

Average weight was not entered.