22 DFW-40350 to DFW-40395

DFW-40350: The diagnostic dump {0} has been registered.

Cause: null

Action: null

Level: 1

Type: TRACE

Impact: Process

DFW-40351: executing diagnostic dump {0}

Cause: null

Action: null

Level: 1

Type: TRACE

Impact: Other

DFW-40352: 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-40353: failed to access Java System properties

Cause: There was an issue accessing the Java System properties, this may be due to permission issues.

Action: Check that the process executing the dumps is running with sufficient privileges to access the system properties.

Level: 1

Type: WARNING

Impact: Configuration

DFW-40354: 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-40355: 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-40356: 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-40357: failed to execute diagnostic dump {0} in component "{1}"

Cause: The component could not be contacted in order to execute the diagnostic dump.

Action: Check that component "{0}" is up.

Level: 1

Type: WARNING

Impact: Process

DFW-40358: failed to retrieve details of diagnostic dumps in component "{0}"

Cause: The component could not be contacted in order to retrieve diagnostic dump details.

Action: Check that the component is up.

Level: 1

Type: TRACE

Impact: Other

DFW-40359: failed to create ADR Base directory {0}

Cause: An error occurred whilst attempting to create the ADR Base directory, 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-40360: An incident has been signalled with the incident facts: {0}

Cause: null

Action: null

Level: 1

Type: NOTIFICATION

Impact: Other

DFW-40361: incident creation callback failed: {0}

Cause: During the creation of an incident the registered callback failed.

Action: See base exception for root cause.

Level: 1

Type: WARNING

Impact: Other

DFW-40362: failure during incident rule processing of incident {0}

Cause: During the processing of the incident rules an error occurred.

Action: See base exception for root cause.

Level: 1

Type: WARNING

Impact: Other

DFW-40363: failed to execute dump during creation of incident {0}: {1}

Cause: An error occurred during the execution of a diagnostic dump.

Action: See base exception for root cause.

Level: 1

Type: WARNING

Impact: Other

DFW-40365: incident {0} created with problem key "{1}"

Cause: null

Action: null

Level: 1

Type: NOTIFICATION

Impact: Other

DFW-40367: failed to execute dump {0} during creation of incident {1}

Cause: An error occurred during the execution of the dump.

Action: See base exception for root cause.

Level: 1

Type: WARNING

Impact: Process

DFW-40368: 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-40369: 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-40370: invalid diagnostic rules document

Cause: The diagnostic rules document has invalid content.

Action: See base exception for root cause.

Level: 1

Type: WARNING

Impact: Configuration

DFW-40371: registering diagnostic rules for topology node "{0}"

Cause: null

Action: null

Level: 1

Type: TRACE

Impact: Process

DFW-40372: unregistering diagnostic rules for topology node "{0}"

Cause: null

Action: null

Level: 1

Type: TRACE

Impact: Process

DFW-40375: unable to retrieve dump content during creation of incident {0}: {1}

Cause: The output generated by a diagnostic dump could not be fetched in order to store with the created incident.

Action: See base exception for root cause

Level: 1

Type: NOTIFICATION

Impact: Process

DFW-40376: failed to write and register incident {0} readme file with ADR: {1}

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-40377: failed to parse ADRCI XML output: {0}

Cause: The XML returned by the ADRI show incidents command could not be parsed.

Action: Check the process's logs for more information.

Level: 1

Type: NOTIFICATION

Impact: Other

DFW-40378: 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-40379: 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-40380: 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-40386: incident {0} not found

Cause: null

Action: null

Level: 1

Type: TRACE

Impact: Process

DFW-40387: 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-40388: 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-40389: failed to execute diagnostic dump {0}

Cause: An error occurred during the execution of the dump.

Action: Check component process logs for more information.

Level: 1

Type: WARNING

Impact: Process

DFW-40390: failed to create incident in ADR

Cause: An error occurred during the creation of an incident.

Action: See base exception for root cause.

Level: 1

Type: WARNING

Impact: Process

DFW-40391: failed to create diagnostics configuration XML

Cause: null

Action: null

Level: 1

Type: TRACE

Impact: Process

DFW-40392: Invalid fact name "{0}" specified for rule "{1}"

Cause: null

Action: null

Level: 1

Type: WARNING

Impact: Process

DFW-40393: component "{0}" is invalid

Cause: An invalid component was specified to the mas.ons dump.

Action: Specify one or more components from the available list of components: {0}

Level: 1

Type: WARNING

Impact: Other

DFW-40394: 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-40395: 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