FRM-50000 TO FRM-92090
FRM-50000: Value is too long.
Cause: You entered a
value which contains too many bytes or characters for the item.
Action: Enter a
shorter value.
Level: 15
Trigger: ON-ERROR
FRM-50001: Acceptable characters are a-z, A-Z, and space.
Cause: You entered
an unacceptable character into the item.
Action: Enter a
character from a-z, A-Z, or a space.
Level: 15
Trigger: ON-ERROR
FRM-50002: Month must be between 1 and 12.
Cause: You entered
an invalid month value in a date field.
Action: Enter a month
value from 1 (for January) to 12 (for December).
Level: 15
Trigger: ON-ERROR
FRM-50003: Year must be in proper range.
Cause: You entered a
year that is not valid for the applicable format mask year element.
Action: Enter a valid
year. For most format mask year elements, a number between 0 and 9999 is
acceptable. For signed format mask year elements, a number between -4712 and -1
may also be specified.
Level: 15
Trigger: ON-ERROR
FRM-50004: Day must be between 1 and last of month.
Cause: You entered
an invalid day.
Action: Enter a valid
day. For April, for example, enter a number between 1 and 30.
Level: 15
Trigger: ON-ERROR
FRM-50006: Legal characters are 0-9 + and -.
Cause: You entered
an unacceptable character in a number item.
Action: Enter a valid
number. A valid number has digits 0 through 9. A number may be preceded by a
plus (+) or minus (-) sign. If the message allows it, a number may contain one
decimal point at any location, except before the sign.
Level: 15
Trigger: ON-ERROR
FRM-50007: Too many digits after decimal point.
Cause: You entered a
number with 3 or more decimal digits after the decimal point in an item with
the MONEY or RMONEY data type.
Action: Re-enter a
valid number.
Level: 15
Trigger: ON-ERROR
FRM-50009: Too many decimal points.
Cause: You entered a
number that contains two or more decimal points, or you have entered a number
that contains a decimal point in an item that requires a whole (non-decimal)
number.
Action: Enter a
number with no more than one decimal point. If you have used only one decimal,
remove the decimal and the decimal part of the number.
Level: 15
Trigger: ON-ERROR
FRM-50010: Money format is [+-]9999999.99
Cause: You entered
an invalid value in a MONEY or RMONEY item.
Action: Enter a valid
value. This value should have zero or dollar digits, followed by a decimal and
two cents digits. The entire number can be preceded by a plus (+) or a minus
(-) sign.
Level: 15
Trigger: ON-ERROR
FRM-50011: Not a valid month name.
Cause: You entered
an invalid month name in a date field.
Action: Enter a valid
month name. Oracle Forms recognizes the first three characters of a month name.
For example, JAN stands for January, JUN for June.
Level: 15
Trigger: ON-ERROR
FRM-50012: Date must be entered in a format like %s.
Cause: You entered
an invalid or incorrectly formatted date.
Action: Re-enter the
date in the requested format.
Level: 15
Trigger: ON-ERROR
FRM-50013: Plus or minus must be in first position.
Cause: You entered
the plus or minus sign in the wrong position.
Action: Retype with
the plus or minus sign in the first position.
Level: 15
Trigger: ON-ERROR
FRM-50014: Bad exponent.
Cause: You entered
an exponent in an item that does not accept exponents.
Action: Enter a value
without an exponent.
Level: 15
Trigger: ON-ERROR
FRM-50016: Legal characters are 0-9 - + E .
Cause: You entered
an unacceptable character in a number item.
Action: Enter a valid
number. A valid number has digits 0 through 9. A number may be preceded by a
plus (+) or minus (-) sign. If the message allows it, a number may contain one
decimal point at any location, except before the sign. You can use an E to
specify scientific notation.
Level: 15
Trigger: ON-ERROR
FRM-50017: Hour must be between 0 and 23.
Cause: You entered
an invalid hour.
Action: Enter a valid
hour. Oracle Forms records time on a 24-hour basis.
Level: 15
Trigger: ON-ERROR
FRM-50018: Minutes must be between 00 and 59.
Cause: You entered
an invalid minute value.
Action: Enter a valid
minute value.
Level: 15
Trigger: ON-ERROR
FRM-50019: Seconds must be between 00 and 59.
Cause: You entered
an invalid value.
Action: Enter a value
between 00 and 59.
Level: 15
Trigger: ON-ERROR
FRM-50020: Missing exponent.
Cause: You failed to
enter an exponent.
Action: Enter an
exponent.
Level: 15
Trigger: ON-ERROR
FRM-50021: Date must be entered in a format like %s.
Cause: You entered
an invalid or incorrectly formatted date.
Action: Re-enter the
date in the requested format.
Level: 15
Trigger: ON-ERROR
FRM-50022: Time must be entered in a format like %s.
Cause: You entered
an invalid or incorrectly formatted time.
Action: Re-enter the
time in the requested format.
Level: 15
Trigger: ON-ERROR
FRM-50023: Date must be entered in a format like %s.
Cause: You entered
an invalid or incorrectly formatted date.
Action: Re-enter the
date in the requested format.
Level: 15
Trigger: ON-ERROR
FRM-50024: Space are allowed in leading positions only.
Cause: You entered
spaces intermixed with data.
Action: Re-enter data
with no spaces intermixed.
Level: 15
Trigger: ON-ERROR
FRM-50025: Date/time must be entered in a format like %s.
Cause: You entered
an invalid or incorrectly formatted date and time.
Action: Re-enter the
date and time in the requested format.
Level: 15
Trigger: ON-ERROR
FRM-50026: Date must be entered in a format like %s.
Cause: You entered
an invalid or incorrectly formatted date.
Action: Re-enter the
date in the requested format.
Level: 15
Trigger: ON-ERROR
FRM-50027: Invalid format mask for given datatype.
Cause: The format
mask you assigned to a text item is incompatible with the data type of the text
item.
Action: Assign a new
format mask to the text item. For more information, refer to help on <a
href="../../designing_forms/items/f500842.html">About Formatting
Text Item Values with Format Masks</a>.
Level: 15
Trigger: ON-ERROR
FRM-50028: Format mask not allowed for this datatype.
Cause: The data
types LONG and IMAGE do not support a format mask.
Action: Do not try to
create a format mask for data types LONG or IMAGE.
Level: 15
Trigger: ON-ERROR
FRM-50029: Too many digits preceding decimal point for
scientific notation.
Cause: You specified
a number using scientific notation, but used more than one digit preceding the
decimal point.
Action: Re-enter the
number using scientific notation.
Level: 15
Trigger: ON-ERROR
FRM-50045: Seconds past midnight confilicts with hour.
Cause: You entered a
time where the seconds past midnight component does not agree with the hour
component.
Action: Make sure the
hour and seconds past midnight agree, or use a format mask without seconds past
midnight.
Level: 15
Trigger: ON-ERROR
FRM-50048: New passwords do not match. Please make them
identical.
Cause: You entered
different strings in 'New Password' and 'Retype New' fields.
Action: Re-enter the
values in (New and Retype) fields such that they identical.
Level: 99
Trigger: None
FRM-91124: fatal error in runtime process: %s specified for
FORMS_DECIMAL_PREFIX. Should be zero or the empty string
Cause: A fatal error
occurred in the Forms server, which will require the attention of your system
administrator.
Action: Contact your
system administrator.
Appears: Java console,
alert
Level: 99
Trigger: None
FRM-91126: fatal error in runtime process: invalid value %s
specified for environment variable %s
Cause: A fatal error
occurred in the Forms server, which will require the attention of your system
administrator.
Action: Contact your
system administrator.
Appears: Java console,
alert
Level: 99
Trigger: None
FRM-91127: fatal error in runtime process: invalid directory
name specified for environment variable %s
Cause: A fatal error
occurred in the Forms server, which will require the attention of your system
administrator.
Action: Contact your
system administrator.
Appears: Java console,
alert
Level: 99
Trigger: None
FRM-91129: fatal error in runtime process: no value specified
for required environment variable %s
Cause: A fatal error
occurred in the Forms server, which will require the attention of your system
administrator.
Action: Contact your
system administrator.
Appears: Java console,
alert
Level: 99
Trigger: None
FRM-91130: fatal error in runtime process: timezone file %s is
missing
Cause: A fatal error
occurred in the Forms server, which will require the attention of your system
administrator.
Action: Contact your
system administrator.
Appears: Java console,
alert
Level: 99
Trigger: None
FRM-91131: fatal error in runtime process: timezone file %s not
loaded - required memory unavailable
Cause: The timezone
file could not be loaded. This probably indicates insufficient swap space.
Action: Retry the
application when the system is less heavily loaded.
Appears: Java console,
alert
Level: 99
Trigger: None
FRM-91132: fatal error in runtime process: invalid data in
timezone file %s
Cause: A fatal error
occurred in the Forms server, which will require the attention of your system
administrator.
Action: Contact your system
administrator.
Appears: Java console,
alert
Level: 99
Trigger: None
FRM-91135: fatal error in runtime process: message file %s is
missing
Cause: A fatal error
occurred in the Forms server, which will require the attention of your system
administrator.
Action: Contact your
system administrator.
Appears: Java console,
alert
Level: 99
Trigger: None
FRM-92000: internal error: cannot access Java class
Cause: The Forms
server requested a Java class by specifying a numeric
"handlerClassId", and the Forms Java client found an entry for the
specified handlerClassId in the registry. However, the Java class that was
specified by the registry entry could not be accessed.
Action: Examine the
stack trace that accompanies this message. If the stack trace indicates a
possible cause (e.g. a configuration problem), correct it. If the problem
persists, contact Oracle Support Services.
Appears: Java console,
alert
Level: 99
Trigger: None
FRM-92010: Fatal error: serverArgs parameter is either not set
or is blank.
Cause: The
serverArgs applet parameter (which represents the command-line arguments that
are passed to the frmweb executable) is either missing or has a blank value.
The base HTML files that are shipped with the produce specify a valid value for
the serverArgs parameter, so presumably that value has been modified, or else a
non-standard base HTML file has been specified.
Action: The system
administrator should ensure that the base HTML file correctly defines the
serverArgs parameter.
Appears: Java console,
alert
Level: 99
Trigger: None
FRM-92020: invalid URL %s sent to browser with target %s. full
details: %s
Cause: The Forms
application executed the web.showDocument built-in, and the applet did not
define the clientBrowser parameter, which caused Forms to attempt to resolve
the specified URL relative to the applet's document base. However, this attempt
encountered a MalformedURLException. This is not a fatal error.
Action: Correct the
URL that is passed to the web.showDocument built-in.
Appears: Java console,
alert
Level: 99
Trigger: None
FRM-92030: internal error: no registry entry for
handleClassId=%s
Cause: The Forms
server requested a Java class by specifying a numeric
"handlerClassId", but the Forms Java client could not find an entry
for the specified handlerClassId in the registry.
Action: If the
problem persists, contact Oracle Support Services.
Appears: Java console,
alert
Level: 99
Trigger: None
FRM-92040: internal error: cannot find Java class
Cause: The Forms
server requested a Java class by specifying a numeric
"handlerClassId", and the Forms Java client found an entry for the
specified handlerClassId in the registry. However, the Java class that was
specified by the registry entry could not be found.
Action: Examine the
stack trace that accompanies this message. If the stack trace indicates a
possible cause (e.g. a configuration problem), correct it. If the problem
persists, contact Oracle Support Services.
Appears: Java console,
alert
Level: 99
Trigger: None
FRM-92050: fatal error: cannot connect to the server: %s:%s
Cause: An attempt
was made to connect to the Forms server. The serverURL applet parameter was not
specified, so Forms attempted to connect to the specified host machine, on the
specified port. (These are derived from the serverHost and serverPort applet
parameters, if specified). However, an unexpected Exception was encountered.
This message appears when there is no message that gives a more specific reason
for the connection failure.
Action: Examine the
stack trace that accompanies this message. If the stack trace indicates a
possible cause, correct it. If the problem persists, contact Oracle Support
Services.
Appears: Java console,
alert
Level: 99
Trigger: None
FRM-92052: fatal error: cannot connect to the server at URL %s
Cause: An attempt
was made to connect to the Forms server, at the specified URL. (This is derived
from the serverURL applet parameter). However, an unexpected Exception was
encountered. This message appears when there is no message that gives a more
specific reason for the connection failure.
Action: Examine the
stack trace that accompanies this message. If the stack trace indicates a
possible cause, correct it. If the problem persists, contact Oracle Support
Services.
Appears: Java console,
alert
Level: 99
Trigger: None
FRM-92060: fatal error: cannot connect to the server: bad
machine specification: %s:%s
Cause: An attempt
was made to connect to the Forms server. The serverURL applet parameter was not
specified, so Forms attempted to connect to the specified host machine, on the
specified port. (These are derived from the serverHost and serverPort applet
parameters, if specified). However, the format of the host/port combination was
invalid.
Action: Correct the
syntax of the serverHost and/or the serverPort applet parameter, or specify a
valid value for the serverURL applet parameter.
Appears: Java console,
alert
Level: 99
Trigger: None
FRM-92062: fatal error: cannot connect to the server: bad URL
specification: %s
Cause: An attempt
was made to connect to the Forms server, at the specified URL. (This is derived
from the serverURL applet parameter). However, the URL was malformed.
Action: Correct the
syntax of the serverURL applet parameter.
Appears: Java console,
alert
Level: 99
Trigger: None
FRM-92070: internal error: cannot instantiate Java class
Cause: The Forms
server requested a Java class by specifying a numeric
"handlerClassId", and the Forms Java client found an entry for the
specified handlerClassId in the registry. However, the Java class that was
specified by the registry entry could not be instantiated.
Action: Examine the
stack trace that accompanies this message. If the stack trace indicates a
possible cause (e.g. a configuration problem), correct it. If the problem
persists, contact Oracle Support Services.
Appears: Java console,
alert
Level: 99
Trigger: None
FRM-92080: fatal error: cannot execute command: %s %s. full
details: %s
Cause: The Forms
application executed the web.showDocument built-in, and the applet defined the
clientBrowser parameter, which caused Forms to attempt to start the specified
external client browser. However, this attempt encountered an Exception.
Action: If the
"full details" messages indicates the problem, correct it. Otherwise,
if the problem persists, contact Oracle Support Services.
Appears: Java console,
alert
Level: 99
Trigger: None
FRM-92089: unexpected fatal error while initializing the
applet's user interface
Cause: An unexpected
Exception was encountered while attempting to initialize the applet's user
interface.
Action: Examine the
stack trace that accompanies this message. If the stack trace indicates a
possible cause, correct it. If the problem persists, contact Oracle Support
Services.
Appears: Java console,
applet status window
Level: 99
Trigger: None
FRM-92090: unexpected fatal error in client-side Java code
during startup
Cause: An unexpected
Exception was encountered in client-side Java code during startup.
Action: Examine the
stack trace that accompanies this message. If the stack trace indicates a
possible cause, correct it. If the problem persists, contact Oracle Support
Services.
Appears: Java console,
alert
Level: 99
Trigger: None
No comments:
Post a Comment