Viewer Notifications

Viewer notifications come in the form of message boxes. If the message box displays an error number, it is documented below. References to <socket error code> refer to errors defined in Winsock2.h, or in some cases Paul Bunyan specific socket error codes.

Code #:

5001

Severity:

Error

Message text: Unable to comply. An unknown system error has occured.

Remarks: This message will be displayed when an unexpected software exception is generated by MFC. Please report to technical support.

Code #:

5002

Severity:

Error

Message text: A list box error has occured, possibly due to insufficient memory.

Remarks: This error message is included because of the way the Win32 API is designed or at least how it’s documented. Each list box function is documented to potentially return an error, although if the API is used correctly the only error that should occur is lack of memory. This message may indicate that the system is low on memory. But if you see it, it’s more likely a bug in our code.

Code #:

5003

Severity:

Error

Message text: An unhandled exception of type <exception code> has occured in PBViewer.exe. Diamond Sierra is continuously working to eliminate bugs in our software and would appreciate your feedback. Please note the conditions that caused this error and report them.

Remarks: This prompt is presented because the “Edit | Delete all” command overrides all other safety checks and really deletes all the messages from the workspace. It’s an easy mistake to make to choose this command when all you really want to do is delete everything from the current query.

Code #:

5025

Severity:

Warning

Message text: The changes made affect one or more active connections. The changes will take affect at the next re-connect.

Remarks: The current socket protocol between viewers and message servers has all the parameters for the connection uploaded from the viewer to the message server at the time the connection is established. The only way to modify what messages are received over a connection is to disconnect and re-connect. Parameters include the filter, the list of MessageKeys, and the cookie. Thus for example if the list of selectors in the workspace is edited and one of the selectors edited is used by an active connection, the connection will continue to use the old selector until the next connect.

Code #:

5026

Severity:

Info

Message text: This action will permanently delete items marked as deleted.\nDo you wish to restore them first? (Yes | No | Cancel)

Remarks: If a query has auto-delete disabled and messages contained in that query are deleted from another query, the messages will be in limbo until the original query is refreshed or closed. The messages are not in the workspace but are temporarily stored in the query. The “Edit | Restore” command can be used to add the messages back to the workspace. If such a query is refreshed or closed, the disposition of these items must be determined. They must either be added back to the workspace or deleted from the query. Choosing Yes will add all the deleted messages marked with a red “X” back to the workspace. Choosing No will remove all the deleted messages from the query. Choosing Cancel will abort the close or restore operation in progress without modifying the deleted messages’ status.

Code #:

5027

Severity:

Error

Message text: The specified name already exists in the workspace. Please enter a unique name for the object.

Remarks: Elements of workspaces such as connections, queries, and selectors are identified by a unique, non-trivial name. The name is used to identify the object in list boxes and MRUs. It’s currently required that each object of a given type have a distinct name.

Code #:

5028

Severity:

Error

Message text: Please enter a name to identify the object.

Remarks: Elements of workspaces such as connections, queries, and selectors are identified by a unique, non-trivial name. The name is used to identify the object in list boxes and MRUs. It’s currently required that each object be given a non-trivial name.

Code #:

5030

Severity:

Error

Message text: Paul Bunyan is unable to obtain licensing information and will abort. Run the setup program to restore licensing information for this computer. If you continue to have problems, please contact technical support.

Remarks: The setup program establishes copy protection information on your machine. If the message viewer cannot access this information, it will show this message and abort.

Code #:

5031

Severity:

Error

Message text: Paul Bunyan is unable to validate licensing information and will abort. Run the setup program to restore licensing information for this computer. If you continue to have problems, please contact technical support.

Remarks: The setup program establishes copy protection information on your machine. If the message viewer cannot validate this information, it will show this message and abort.

Remarks: This message is displayed if the PBW file being opened is a valid workspace but the version number is incompatible with the viewer’s version.

Code #:

5033

Severity:

Error

Message text: Unable to open file '<workspace name>'. The file is corrupt or is not a valid PB workspace.

Remarks: Indicates the file being opened cannot be interpreted.

Code #:

5034

Severity:

Info

Message text: The workspace <file path> is an earlier version than this viewer. Continuing will convert to the latest version. The workspace will then not be readable by earlier viewers.

Remarks: Message viewers currently support working with only one version of a workspace. Earlier workspaces will be updated to the latest version; workspaces later than the viewer cannot be interpreted. Make separate copies of workspaces if you need to work with incompatible viewer versions simultaneously.

Code #:

5035

Severity:

Warning

Message text: Abort unfinished uploads?

Remarks: The Remote Configuration Dialog allows transfer of configurations to message servers over TCP/IP. This is an asynchronous process. If the dialog is closed before an operation is completed, the operation will be aborted. There will be no way to tell whether the operation successfully completed.

Code #:

5036

Severity:

Error

Message text: Please enter a ProgID or CLSID (enclosed in braces) to identify the message handler.

Remarks: Message handler configuration requires an identifier corresponding to the COM object that implements the IPBToMH interface. This can be a ProgID (appropriate for the API function CLSIDFromProgID) or a CLSID (specified as a string representation of a UUID structure enclosed in braces, appropriate for the API function CLSIDFromString).

Code #:

5037

Severity:

Error

Message text: Please enter a fully qualified directory (without quotation marks). The path must be valid in the context of the target message server and must not contain any network elements.

Remarks: While configuring a message server, directories must be specified for the location of the IPC buffer and the message server cache file (unless the message server is a Lite Edition). These directories must be valid paths on a fixed drive so the files can be read at boot before network elements are available.

Code #:

5038

Severity:

Warning

Message text: The configuration change will reset the cookies for the listed message handlers or forwarders. <list of message handlers and/or forwarders>

Remarks: When a new configuration is processed by the message server, any message handlers and forwarders check the configuration to see if an override is specified for their cookie. This mechanism is provided chiefly to allow specification of whether a message handler or forwarder processes the entire cache or no messages when it is first instantiated. It can also be useful to reset the cookie during reconfiguration, but if the same configuration is uploaded repeatedly, the cookies should not be reset with each upload. This would result in messages duplicated or missed, depending on whether the cookie is set to begin or end.

Code #:

5040

Severity:

Error

Message text: Please enter a number in hexadecimal format between 0 and 0xFFFFFFFF.

Remarks: This notification applies to entry of process ID and thread ID in the Filter Dialog. These are numerical fields representing an operating system identifier.

Code #:

5041

Severity:

Error

Message text: Please enter a valid date or leave this field blank.

Remarks: Indicates an improperly formatted date was entered in the Filter Dialog. Date and time strings are passed to the MFC function COleDateTime::ParseDateTime for validation.

Code #:

5042

Severity:

Error

Message text: Please enter a valid time or leave this field blank.

Remarks: Indicates an improperly formatted time was entered in the Filter Dialog. Date and time strings are passed to the MFC function COleDateTime::ParseDateTime for validation.

Code #:

5043

Severity:

Error

Message text: An inclusion filter with no inclusion elements will never pass any messages. Please try again.

Remarks: The Filter Dialog presents a list box with all the selectors in the workspace. Selectors are added to the filter being edited by setting the check box to the left of the selector as follows:
Checked: selector belongs to main list
Unchecked: selector belongs to exception list
Grayed: selector does not belong to current filter
For inclusion filters, if no selectors are checked, it’s logically impossible for any messages to pass. Such a filter will not be saved. To create a filter that passes all messages, gray the checkbox next to each selector and set as an exclusion filter.

Code #:

5044

Severity:

Error

Message text: The selector is null and cannot be saved.

Remarks: The Filter Dialog allows creation of selectors to be added to filters. A selector with no criteria for matching log messages will behave exactly as no selector at all and so there is no point in saving it.

Code #:

5045

Severity:

Error

Message text: An exclusion filter with no exclusion elements will never fail any messages. Please try again.

Remarks: The Filter Dialog presents a list box with all the selectors in the workspace. Selectors are added to the filter being edited by setting the check box to the left of the selector as follows:
Checked: selector belongs to main list
Unchecked: selector belongs to exception list
Grayed: selector does not belong to current filter
For exclusion filters, if no selectors are checked, all messages will always pass. Such a filter will not be saved.

Code #:

5046

Severity:

Error

Message text: You have chosen to import from and to the same file. Please try again.

Remarks: The Import Dialog allows transfer of objects such as connections, selectors, and queries from a workspace on disk to the active workspace. The proper sequence is to open the destination workspace in the viewer, choose “File | Import,” and then specify the source workspace.

Code #:

5047

Severity:

Error

Message text: Failed to open import workspace.

Remarks: Indicates that an unknown error has occurred while attempting to open a workspace in the Import Dialog. Most errors should be reported more specifically. Please report this error to technical support.

Code #:

5048

Severity:

Error

Message text: The file chosen for import is corrupted or is not a valid PB workspace.

Message text: The file chosen for import is an invalid or incompatible version.

Remarks: Indicates the file chosen in the Import Dialog is a valid Paul Bunyan workspace but the version number is incompatible with the viewer version. Opening the workspace normally will convert the file to the current version, after which the import can take place.

Code #:

5050

Severity:

Error

Message text: Cannot find the string '<search string>'.

Remarks: The Find Dialog (or F3) allows matching of search text to one or more fields in the messages contained in the current query. Only fields which are currently visible and are checked in the Find Dialog will be searched. This message is displayed when no matches are found for the specified string and specified fields.

Code #:

5051

Severity:

Error

Message text: At least one field must be specified to define a search.

Remarks: The Find Dialog (or F3) allows matching of search text to one or more fields in the messages contained in the current query. Only fields which are currently visible and are checked in the Find Dialog will be searched. Specify at least one text field to perform a search.

Code #:

5052

Severity:

Error

Message text: The specified item number does not exist.

Remarks: Displayed by the Go To Dialog when the line number specified is larger than the message count for the current query.

Code #:

5053

Severity:

Error

Message text: Cannot open file.

Remarks: Displayed by the Export Dialog upon failure to open the specified file for write access.

Code #:

5104

Severity:

Error

Message text: Connection '<connection name>' has received an invalid command and is shutting down.

Remarks: Indicates that the message server has abandoned the connection. This could occur if the message server’s machine is rebooted. It could also indicate that a socket communication error occurred on the message server, in which case the message server will log an error to the application event log. A third scenario is if a viewer tries to connect to a message server of an incompatible protocol version, in which case this message will be displayed immediately when the connection is attempted. The message server will again log the event to the event log. The socket error number will usually be zero or 10053, both indicating that the close is a normal occurrence and not an error.

Code #:

5108

Severity:

Error

Message text: Please enter a machine name or IP address to identify the service to connect to. Press F1 for help.

Remarks: Insufficient memory is available to maintain a socket connection to a message server.

Code #:

5114

Severity:

Error

Message text: A memory allocation failure occurred while receiving data over an active connection. An unknown number of messages were lost.

Remarks: Indicates insufficient memory existed to process log messages after they were received. The messages will not be re-sent to the connection when re-connected. The lost messages can still be retrieved if they have not rolled off the message server cache by creating a new connection to the message server or resetting the cookie for a current connection.

Code #:

5115

Severity:

Error

Message text: Failed to establish connection '<connection name>'. The specified server is running but is not licensed. This viewer requires a valid Connectivity license to connect to such a server.

Remarks: The message server will continue to run in unlicensed mode if it is not licensed before the end of the demo period. A viewer must have a valid Connectivity license to connect to such a server.

Code #:

5116

Severity:

Error

Message text: Failed to establish connection '<connection name>'. The protocol version used by the specified server (<server version>) is incompatible with this viewer.

Remarks: The socket protocol includes a version negotiation for forward compatibility. This message indicates that the two sides of the attempted conversation were deliberately made incompatible. Upgrade the component with the lower version number to enable communication. Note that the protocol version used by a viewer or server is not the same thing as the product or file version displayed in the about box or file properties dialog.