Difference between revisions of "TUFLOW Message 0023"
(3 intermediate revisions by 2 users not shown) | |||
Line 2: | Line 2: | ||
|tuflow_message=ERROR 0023 - Invalid Event name starting with "-" or "/" specified after -e option. | |tuflow_message=ERROR 0023 - Invalid Event name starting with "-" or "/" specified after -e option. | ||
|alt_msg=ERROR 0023 - Invalid Scenario name starting with "-" or "/" specified after -s option. | |alt_msg=ERROR 0023 - Invalid Scenario name starting with "-" or "/" specified after -s option. | ||
+ | |||
+ | ERROR 0023 - Invalid copy path starting with "-" or "/" specified after -cp option. | ||
|type=[[ERROR]] | |type=[[ERROR]] | ||
− | |message_desc= | + | |message_desc=A short or long dash (-), or forward slash, exists after event (-e), scenario (-s) or copy path (-cp) option. These characters are reserved and cannot be part of an event or scenario name, or a filename or filepath. |
− | |suggestions=Ensure event or scenario name inputs do not begin with or contain the "-" or "/" characters. | + | |suggestions=Ensure event or scenario name, or filename/path inputs do not begin with or contain the "-" or "/" characters. |
− | + | ||
− | + | Check there is a space after the -e, -s or -cp option and the event/scenario name or filepath. | |
− | + | ||
− | + | If the event/scenario name or filepath has a space in it the name or path must be enclosed in quotes. | |
+ | <br> | ||
+ | |||
|uplink=[[0xxx_TUFLOW_Messages|0xxx Messages]] | |uplink=[[0xxx_TUFLOW_Messages|0xxx Messages]] | ||
− | |||
}} | }} |
Latest revision as of 09:31, 22 December 2022
TUFLOW Message
ERROR 0023 - Invalid Event name starting with "-" or "/" specified after -e option.
Alternate Message
ERROR 0023 - Invalid Scenario name starting with "-" or "/" specified after -s option.
ERROR 0023 - Invalid copy path starting with "-" or "/" specified after -cp option.
Message Type
ERROR
Description
A short or long dash (-), or forward slash, exists after event (-e), scenario (-s) or copy path (-cp) option. These characters are reserved and cannot be part of an event or scenario name, or a filename or filepath.
Suggestions
Ensure event or scenario name, or filename/path inputs do not begin with or contain the "-" or "/" characters.
Check there is a space after the -e, -s or -cp option and the event/scenario name or filepath.
If the event/scenario name or filepath has a space in it the name or path must be enclosed in quotes.
Up |
---|
0xxx Messages |