30 DFW-40004 to DFW-40204

DFW-40004: The requested diagnostic dump {0} is unknown.: Cause: The diagnostic dump {0} has either not been registered or the given name is incorrect.; Action: Ensure that a valid dump name is specified.
Level: 1

Type: WARNING

Impact: Configuration

DFW-40005: The mandatory dump argument {0} is not specified.: Cause: A request to execute a dump was made without specifying all mandatory arguments.; Action: Ensure that all mandatory arguments are specified.
Level: 1

Type: WARNING

Impact: Programmatic

DFW-40006: ignoring dump argument {0} as it is not defined for diagnostic dump {1}: Cause: The dump does not accept the specified argument.; Action: Ensure that only arguments defined by the dump are specified.
Level: 1

Type: NOTIFICATION

Impact: Programmatic

DFW-40007: The diagnostic dump argument {0} should be of type {1}.: Cause: The specified argument is of the wrong type.; Action: Ensure that arguments are of the correct type.
Level: 1

Type: WARNING

Impact: Programmatic

DFW-40008: failed to execute diagnostic dump {0}: Cause: An error occurred during the execution of the dump.; Action: Check process logs for more information.
Level: 1

Type: WARNING

Impact: Process

DFW-40009: failure creating dump file: Cause: An error occurred creaing a dump file; Action: See base error for root cause andcheck process logs for more information.
Level: 1

Type: WARNING

Impact: Process

DFW-40100: failed to create ADR Base directory {0}: Cause: An error occurred whilst attempting to create the ADR Base directory required to store captured diagnostics data. This may be due to file or process permissions.; Action: Check that the process has permission to create the directory.
Level: 1

Type: ERROR

Impact: Operating System

DFW-40102: failure during incident rule processing of incident {0}: Cause: During the processing of the incident rules an error occurred.; Action: See base error for root cause and check process logs for more information.
Level: 1

Type: WARNING

Impact: Other

DFW-40103: failed to execute dump during creation of incident {0}: Cause: An error occurred during the execution of a diagnostic dump.; Action: See base error for root cause and check process logs for more information.
Level: 1

Type: WARNING

Impact: Other

DFW-40105: failed to execute dump {0} during creation of incident {1}: Cause: An error occurred during the execution of the dump.; Action: See base error for root cause and check process logs for more information.
Level: 1

Type: WARNING

Impact: Process

DFW-40106: failed to load diagnostic rules schema {0}: Cause: The diagnostic rules schema could not be loaded.; Action: Check that the specified schema exists and is readable.
Level: 1

Type: WARNING

Impact: Process

DFW-40107: failed to parse diagnostic rules: Cause: The diagnostic rules do not conform to the schema.; Action: Fix the diagnostic rules XML to make the rules valid.
Level: 1

Type: WARNING

Impact: Process

DFW-40108: invalid diagnostic rules document: Cause: The diagnostic rules document has invalid content.; Action: See base error for root cause and check process logs for more information.
Level: 1

Type: WARNING

Impact: Configuration

DFW-40109: failed to write and register incident {0} readme file with ADR: Cause: An issue occurred during the registration of the readme file. This does not impact the associated diagnostic dump data.; Action: Check that the process writing the readme file has sufficient privileges.
Level: 1

Type: NOTIFICATION

Impact: Process

DFW-40110: failure parsing ADRCI XML output: Cause: The XML returned by the ADRCI show incidents command could not be parsed.; Action: Check the process logs for more information.
Level: 1

Type: NOTIFICATION

Impact: Other

DFW-40111: failed to determine incident id and path from adrci output "{0}": Cause: There was an error executing the command to create an incident using ADRCI.; Action: Ensure that command line tool "adrci" can be executed from the command line.
Level: 1

Type: ERROR

Impact: Data

DFW-40112: failed to execute the adrci commands "{0}": Cause: There was an error executing adrci commands; the following errors have been found "{0}"; Action: Ensure that command line tool "adrci" can be executed from the command line.
Level: 1

Type: ERROR

Impact: Other

DFW-40113: failed to execute adrci commands; adrci returned "{0}": Cause: There was an error executing adrci commands.; Action: Ensure that command line tool "adrci" can be executed from the command line.
Level: 1

Type: ERROR

Impact: Other

DFW-40114: The ADR Product ID exceeds the maximum length {0}.: Cause: The given ADR Product ID is too long.; Action: The ADR Product ID will automatically be truncated. No further action is required.
Level: 1

Type: WARNING

Impact: Files

DFW-40115: The ADR Instance ID exceeds the maximum length {0}.: Cause: The given ADR Instance ID is too long.; Action: The ADR Instance ID will automatically be truncated. No further action is required.
Level: 1

Type: WARNING

Impact: Files

DFW-40116: failure creating incident: Cause: An error occurred during the creation of an incident.; Action: See base error for root cause anc check process logs for more information.
Level: 1

Type: WARNING

Impact: Process

DFW-40118: ADR incident creation is disabled; incident not created.: Cause: Diagnostics Framework was unable to initialize ADR, resulting in ADR creation being disabled.; Action: Check the process logs for more information on why ADR could not be initialized.
Level: 1

Type: NOTIFICATION

Impact: Process

DFW-40119: file {0} cannot be added to incident {1} as it exceeds the maximum filename length of {2} characters: Cause: The specified filename length exceeds the maximum allowed by ADR.; Action: Specify a filename whose length does not exceed the maximum alloweed length.
Level: 1

Type: WARNING

Impact: Files

DFW-40121: failure creating incident from WLDF notification: Cause: An error occurred whilst attempting to create an incident.; Action: See the base exception for details, and check the process logs for more information.
Level: 1

Type: WARNING

Impact: Process

DFW-40123: file {0} is not registered with incident {1}: Cause: The specified filename is not associated with the incident; Action: Specify the name of a file that is registered with the incident
Level: 1

Type: NOTIFICATION

Impact: Programmatic

DFW-40200: failed to load diagnostics configuration schema {0}: Cause: The diagnostics configuration schema could not be loaded. See base exception for root cause; Action: Check that the specified schema exists and is readable.
Level: 1

Type: WARNING

Impact: Configuration

DFW-40201: failed to parse diagnostics configuration: Cause: The diagnostics configuration document does not conform to the schema.; Action: Fix the diagnostic configuration XML to make the configuration valid.
Level: 1

Type: WARNING

Impact: Process

DFW-40203: failure initializing diagnostics security context: Cause: An error occurred initializing the internal Diagnostic Framework security context.; Action: See the base exception for details, and check the process logs for more information.
Level: 1

Type: WARNING

Impact: Process

DFW-40204: invalid ADR Home path {0}: Cause: The specified ADR Home is not a valid path.; Action: Specify a valid ADR Home path of the form diag/<productType>/<productId>/<instanceId>
Level: 1

Type: WARNING

Impact: Programmatic