Chapter 9 DIAG Error Messages

This chapter describes messages for errors with a DIAG prefix.

DIAG Messages

DIAG9001

Could not copy {0} due to {1}

Cause:

TBD

Solution:

TBD

DIAG9002

Could not copy config files to dir {0} due to {1}

Cause:

TBD

Solution:

TBD

DIAG9003

Destination log file is {0}

Cause:

TBD

Solution:

TBD

DIAG9004

domain.xml DTD file name is {0}

Cause:

TBD

Solution:

TBD

DIAG9005

Generated report name is {0}

Cause:

TBD

Solution:

TBD

DIAG9006

diagnostic-service Attribute Name is {0}

Cause:

TBD

Solution:

TBD

DIAG9007

diagnostic-service Attribute value is {0}

Cause:

TBD

Solution:

TBD

DIAG9008

diagnostic-service capture-app-dd value is {0}

Cause:

TBD

Solution:

TBD

DIAG9009

diagnostic-service capture-hadb-info value is {0}

Cause:

TBD

Solution:

TBD

DIAG9010

diagnostic-service capture-install-log value is {0}

Cause:

TBD

Solution:

TBD

DIAG9011

diagnostic-service compute-checksum value is {0}

Cause:

TBD

Solution:

TBD

DIAG9012

diagnostic-service min-log-level value is {0}

Cause:

TBD

Solution:

TBD

DIAG9013

diagnostic-service max-log-entries value is {0}

Cause:

TBD

Solution:

TBD

DIAG9014

Report Generation target is {0}

Cause:

TBD

Solution:

TBD

DIAG9015

Error loading domain.xml due to {0}

Cause:

TBD

Solution:

TBD

DIAG9016

Loading domain.xml at {0}

Cause:

TBD

Solution:

TBD

DIAG9017

Error while collecting data due to {0}

Cause:

TBD

Solution:

TBD

DIAG9018

Could not compute checksum of {0} due to {1}

Cause:

TBD

Solution:

TBD

DIAG9019

Invalid target {0}

Cause:

TBD

Solution:

TBD

DIAG9020

Target while validating local target : {0} & targetDir {1}

Cause:

TBD

Solution:

TBD

DIAG9021

target {0}, targetDir {1} , type {2} ,instances {3}

Cause:

TBD

Solution:

TBD

DIAG9022

Error initializing client pluggable factory {0}

Cause:

TBD

Solution:

TBD

DIAG9033

While resolving target dir, instanceRoot = {0 } and targetDir = {1}

Cause:

TBD

Solution:

TBD

DIAG9034

Execution Context is DAS

Cause:

TBD

Solution:

TBD

DIAG9035

Execution Context is not DAS

Cause:

TBD

Solution:

TBD

DIAG9036

Target Dir is {0}

Cause:

TBD

Solution:

TBD

DIAG9037

Target is {0}

Cause:

TBD

Solution:

TBD

DIAG9038

Target type is {0}

Cause:

TBD

Solution:

TBD

DIAG9039

Execution Context is {0}

Cause:

TBD

Solution:

TBD

DIAG9040

Using EE local Target resolver for resolving target details

Cause:

TBD

Solution:

TBD

DIAG9041

Using EE remote Target resolver for resolving target details

Cause:

TBD

Solution:

TBD

DIAG9042

During invocation of report generation using Node Agent MBean instances are{0}

Cause:

TBD

Solution:

TBD

DIAG9043

Exception in retrieving node agent name for a server

Cause:

TBD

Solution:

TBD

DIAG9044

Creating NodeAgent Diagnostic MBean for node agent : {0}

Cause:

TBD

Solution:

TBD

DIAG9045

Error creating NodeAgent Diagnostic MBean

Cause:

TBD

Solution:

TBD

DIAG9046

Error generating report on nodeagent

Cause:

TBD

Solution:

TBD

DIAG9047

Repository Dir is {0}

Cause:

TBD

Solution:

TBD

DIAG9048

Unable to retrieve Pluggable Feature Factory

Cause:

TBD

Solution:

TBD

DIAG9001

Could not copy {0} due to {1}

Cause:

TBD

Solution:

TBD

DIAG9002

Could not copy config files to dir {0} due to {1}

Cause:

TBD

Solution:

TBD

DIAG9003

Destination log file is {0}

Cause:

TBD

Solution:

TBD

DIAG9004

domain.xml DTD file name is {0}

Cause:

TBD

Solution:

TBD

DIAG9005

Generated report name is {0}

Cause:

TBD

Solution:

TBD

DIAG9006

diagnostic-service Attribute Name is {0}

Cause:

TBD

Solution:

TBD

DIAG9007

diagnostic-service Attribute value is {0}

Cause:

TBD

Solution:

TBD

DIAG9008

diagnostic-service capture-app-dd value is {0}

Cause:

TBD

Solution:

TBD

DIAG9009

diagnostic-service capture-hadb-info value is {0}

Cause:

TBD

Solution:

TBD

DIAG9010

diagnostic-service capture-install-log value is {0}

Cause:

TBD

Solution:

TBD

DIAG9011

diagnostic-service compute-checksum value is {0}

Cause:

TBD

Solution:

TBD

DIAG9012

diagnostic-service min-log-level value is {0}

Cause:

TBD

Solution:

TBD

DIAG9013

diagnostic-service max-log-entries value is {0}

Cause:

TBD

Solution:

TBD

DIAG9014

Report Generation target is {0}

Cause:

TBD

Solution:

TBD

DIAG9015

Error loading domain.xml due to {0}

Cause:

TBD

Solution:

TBD

DIAG9016

Loading domain.xml at {0}

Cause:

TBD

Solution:

TBD

DIAG9017

Error while collecting data due to {0}

Cause:

TBD

Solution:

TBD

DIAG9018

Could not compute checksum of {0} due to {1}

Cause:

TBD

Solution:

TBD