error message

Additionally, not all error information is classified as an error message. For example, a core dump or a stack trace may be reported about an error condition, but although they are a form of error information, they are not considered error messages. A more abstract representation of an error is sometimes used instead of a message such as an indicator light or a numeric display which may require the user to consult documentation to interpret the error. An error message can be reported in a variety of ways. For example, in a graphical user interface (GUI), an error message may be displayed in a dialog box. In a command-line interface (CLI), an error message may be printed to a standard stream. A program may write an error message to a log file. The proper design of error messages is an important aspect of usability and human–computer interaction. When the content of an error message is misleading or wrong, the user struggles to correct the issue and to complete their desired task.

While graphical user interfaces have different conventions for displaying error messages, several techniques are common. • Modal dialog box (a.k.a. pop-up message): Appears in a window on the screen, blocking further interaction until it is dismissed. • Notification icon: An icon appears to notify the user about a condition without interrupting their work (not modal). On Windows, a notification icon appears in the System Tray. On Mac OS X, a notification icon may appear in the menu bar, or may take the form of an application's icon "bouncing" in the Dock. The GNOME user interface for Unix-based systems can display notification icons in a panel. • Status bar: Relatively short error messages may be displayed in a status bar which is generally at the bottom of an application's window.

The three main factors that influence the design of error messages are technical limitations, the amount of information to be presented, and what kind of user input is required. Some systems have technical limitations that may constrain the amount of information an error message can contain. For example, a printer with a sixteen-character alphanumeric display can only show a very limited amount of information at once, so it may need to display very terse error messages. Even with computer monitors, the programmer must consider the smallest monitor that a user might reasonably use, and ensure that any error messages will fit on that screen. The nature of the error determines the amount of information required to effectively convey the error message. A complex issue may require a more detailed error message in order to adequately inform the user of the problem. In general, software designers should take care that the content of a messages does not expose security risk. An error message should not expose information that can be exploited by a cracker to obtain information that is otherwise difficult to obtain. Examples are systems which may show either "invalid user" or "invalid password" depending on which is incorrect, and the error page in the web server IIS 5.0 which provides a complete technical description of the error including a source code fragment.

The following error conditions are often reported via an error message. When such a condition occurs, the section header text might be reported as an error message and in fact is in some contexts, but different text is used for the condition in other contexts. • Access denied: The user does not have privilege to complete an operation. • Device not ready: Most often occurs when there is no floppy disk (or a bad disk) in the disk drive and the system tries to a access that disk. • Disk Boot Failure: Commonly occurs when the hard drive of the computer is having problems. If the computer can boot from a network, it may instead display the message "Media test failure, check cable". • File not found: A specified file is not found as specified. A similar error occurs on the web as HTTP status code 404 to indicate that a resource is not found. • Low Disk Space: This condition occurs when a storage drive is nearly full. To fix this, the user should release storage space (i.e. delete files) or use a different drive. • Out of memory: The system has insufficient RAM for an operation. Fixes include closing programs and installing more memory. • Resource not found: HTTP status code 404 usually results from a link to a page that has been moved or deleted, or a mistyped URL.

Notable error messages in specific computing contexts include: •?: the ed text editor infamously replies with a single question mark for nearly all error conditions. • Abort, Retry, Fail?: A notoriously confusing error message seen in MS-DOS • Illustration — An example of an Error message.vbs script • Bad command or file name: A notoriously common and confusing error message seen in MS-DOS • Blue Screen of Death (BSoD): In Windows and ReactOS, this screen appears when the operating system encounters a severe error. It is roughly analogous to a kernel panic on Linux, Unix, or macOS. • Guru Meditation: In Amiga, roughly analogous to a kernel panic or BSoD, also adopted by more recent products such as VirtualBox. • lp0 on fire: A Unix warning that the printer may be "on fire", literally or not.doubt that it's literal • Not a typewriter: A Unix error message that is confusing due to its now obsolete use of the word "typewriter", and which is sometimes output when the nature of the error is seemingly entirely different. • PC LOAD LETTER: An error on several HP laser printers that simply asked the user to add "Letter" size paper in a confusing way. • SYNTAX ERROR: Seen in many older computing contexts when the received instruction is not understood. • Error 1603: A problem during installation of a computer program. This error particularly occurs on Windows computer systems. • application has stopped: An error message commonly found on Android devices, that indicates that an application unexpectedly stopped working or crashed. • Success: In POSIX and other contexts, success is sometimes and confusingly reported as an error. This is a form of sloppy error handling resulting from reporting a success status code as an error.

• Illustration — Tumbeasts gnawing on servers, used by Tumblr in 2011 With the rise of Web 2.0 services such as Twitter, end-user facing error messages such as HTTP 404 and HTTP 500 started to be displayed with whimsical characters, termed Fail Pets or Error Mascots. The term "Fail Pet" was coined, or at least first used in print, by Mozilla Engineer Fred Wenzel in a post on his blog entitled "Why Wikipedia might need a fail-pet — and why Mozilla does not." Dr. Sean Rintel argues that error messages are a critical strategic moment in brand awareness and loyalty. Fail pets are of interest to marketers because they can result in brand recognition (especially through earned media). "However, that same recognition carries the danger of highlighting service failure." The most famous fail pet is Twitter's Fail Whale (see Twitter service outages). Other fail pets include: • Ars Technica: Moon Shark (March 3, 2013) • Chuck E. Cheese: Chuck E. jumping • Facebook: Thumbs up with bandage • FarmVille on Facebook: Sad cow. • GitHub: Octocat • Google: Broken robot (March 2, 2011) • iCloud: Cloud with Apple System 7 emoticon-style face and a magnifying glass • Macintosh: Sad Mac • Palliser Furniture: Between the cushions (January 31, 2018) • Tumblr: Tumbeasts (January 25, 2011) • Twitter: Fail Whale / Twitter Robot (July 30, 2008) • YouTube: Televisions (on main site), light static inside video window (embedded video), Monkey • Cartoon Network: BMO from Adventure Time, Domo in Asian regions • Google Chrome: T-Rex • Patreon: Red fox with a helmet floating in space • VK: Sad VK dog • Scratch: Giga scratching their head