IBM WebSphere Validation messages |
CHKW1500I: IBM WebSphere Validation
Explanation:
No additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW1501I: Cell Validation
Explanation:
No additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW1502E: Failed to recognize object of type {0}
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW1505E: The bootstrap address of the foreign cell {0} is absent.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW1506E: The name of a foreign cell, beneath cell {0}, is absent.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW1511E: The name of the cell stored in {0} is absent.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW1512E: The discovery protocol of cell {0} is absent.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW1513E: The discovery protocol {0}, of cell {1}, is not valid.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW1514E: The security enablement of cell {0} is absent.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW1515E: The foreign cell name {0} is duplicated.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW1518E: The property name {0}, beneath cell {1}, is duplicated.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW1519E: The name of a property beneath cell {0} is absent.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW1600I: IBM WebSphere Validation
Explanation:
No additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW1601I: Cluster Validation
Explanation:
No additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW1605E: The bootstrap address of server cluster {0} is absent.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW1605W: The location of the application's EAR file contains character(s), "{0}", that may not work for all platforms.
Explanation:
No additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW1606E: The name of a server cluster in {0} is absent.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW1607E: The name is a cluster member beneath server cluster {0} is absent.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW1608E: The unique id of cluster member {0} is absent.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW1609E: The prefer local setting of server cluster {0} is absent.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW1610E: The cluster has no members.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW1611E: The cluster member name {0} is duplicated.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW1612E: The cluster member unique ID {0} is duplicated.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW1613E: The member weight of a cluster member is absent.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW1614W: The member weight, {0}, of a cluster member is not valid. The weight must be between {1} and {2}, inclusive.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW1615E: The cluster member {0} matches multiple configured servers, on nodes {1} and {2}.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW1616E: The cluster member {0} matches no configured servers.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW1701I: IBM WebSphere Multi-Broker Validation
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW1702E: Multi multi-broker entries have the name {0} are present.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW1703E: The broker end-point of multi-broker entry {1}, of multi-broker {0}, is absent.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW1704E: The client end-point of multi-broker entry {1}, of multi-broker {0}, is absent.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW1705E: The replication settings of multi-broker domain {0} is absent.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW1706E: The name of a multi-broker entry beneath multi-broker {0} is absent.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW1707E: Multiple multi-brokers having the name {0} are present.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW1708E: The name of a multi-broker in {0} is absent.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW1709E: Multiple system messages matching broker name {0} of multi-broker domain {1}.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW1710W: No system message server matching broker name {0}, of multi-broker domain {1}, is configured.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW1711E: No multi-broker domains are present.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW1900I: IBM WebSphere Validation
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW1900I: IBM WebSphere Validation
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW1900I: IBM WebSphere Validation
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW1900I: IBM WebSphere Validation
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW1900I: IBM WebSphere Validation
Explanation:
No additional in formation is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW1901I: IBM WebSphere Name Bindings Validation
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW1901I: IBM WebSphere Name Store Validation
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW1901I: IBM WebSphere Node Validation
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW1901I: IBM WebSphere PMI Request Metrics Validation
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW1901I: IBM WebSphere Platform Validation
Explanation:
No additional in formation is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW1902E: Failed to recognize object of type {0}
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW1902E: Failed to recognize object of type {0}
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW1902I: Failed to recognize object of type {0}
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW2500I: IBM WebSphere Validation
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW2501I: IBM WebSphere Node-Servers Validation
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW2502I: Failed to recognize object of type {0}
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW2503E: Wrong application deployment information. Application "{0}" has not been deployed.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW2504E: The end point of named end point {0} is absent.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW2505E: The name of a named end point is absent.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW2506E: Named end points having the same name, {0}, are present beneath a server entry.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW2507E: The server {0}, on node {1}, has no corresponding server entry in the server index {2}.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW2508E: The name of a server entry is absent.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW2509E: The type of server entry {0} is absent.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW2510E: The port assignment, host {0}, port {1}, of end point {2} in server entry {3} conflicts with a global port assignment.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW2511E: Named end points having the same name, {0}, are present as special end points of the server index.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW2512E: Server entries having the same server name, {0}, are present within the server index.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW2513E: The global port assignment (host {0}, port {1}) of end point {2} in server entry {3} conflicts with other assigned ports.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW2514E: The host name in server index {0} is absent.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW2515E: No entry having the type {0} is present in the server index. Exactly one entry having this type is required.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW2516E: No end point named {0} is present beneath the entries of the server index. Exactly one end point having this name is required.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW2517E: The port assignment, host {0}, port {1}, of end point {2} in server entry {3}, is the same as another port assignment.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW2518E: More than one entry having the type {0} is present in the server index. Exactly one entry having this type is required.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW2519E: More than one end point named {0} is present beneath the entries of the server index. Exactly one end point having this name is required.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW2520W: The end point name {0} is not one of the recognized end point names.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW2521W: No applications are deployed beneath server entry {0}.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW2522W: The server entry {1} has an unrecognized type, {0}.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW2604E: Failed to recognize object of type {0}
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW2605E: The name of the node in {0} is absent.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW2606E: The node name {0}, stored in {1}, is not a valid node name.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW2607E: The binaries directory of node {0} is absent.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW2608E: The work area of node {0} is absent.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW2609E: The discovery protocol of node {0} is absent.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW2610E: The discovery protocol {0}, of node {1}, is not valid.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW2611E: Properties having the name {0}, on node {1}, are duplicated.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW2612E: The name of a property of node {0} is absent.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW2800I: IBM WebSphere Validation
Explanation:
No dditional in formation is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW2801I: IBM WebSphere Variables Validation
Explanation:
No dditional in formation is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW2802E: An object of an unrecognized type was sent for variables validation. The object type is {0}.
Explanation:
No dditional in formation is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW2805E: A variable map entry''s symbolic name, in {0}, is absent.
Explanation:
No dditional in formation is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW2806E: The variable map entry''s symbolic name {0}, in {1}, is not valid.
Explanation:
No dditional in formation is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW2807W: The variable map entry {0} has no assigned value.
Explanation:
No dditional in formation is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW2808E: The variable map entry symbolic name {0} is duplicated.
Explanation:
No additional in formation is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW2809I: The Variable {0} has been redefined as {2} in server {1}.
Explanation:
No additional in formation is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW2810E: The variable {0} is defined in both cell {1} and node {2}.
Explanation:
No additional in formation is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW2811E: The variable {0} has been doubly defined, in cell {1} as {3} and node {2} as {4}.
Explanation:
No additional in formation is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW2811E: The variable {0} has been doubly defined, in cell {1} as {3} and node {2} as {4}.
Explanation:
No additional in formation is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW2812E: The variable {0} is defined in both cell {1} and node {2}.
Explanation:
No additional in formation is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW2900I: IBM WebSphere Validation
Explanation:
No additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW2901I: IBM WebSphere Virtual Hosts Validation
Explanation:
No additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW2904E: Failed to recognize object of type {0}
Explanation:
No additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW2905E: The name of a virtual host in {0} is absent.
Explanation:
No additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW2906E: The name of a virtual host alias, beneath virtual host {0}, is absent.
Explanation:
No additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW2907E: The name of a virtual host alias, {0}, beneath virtual host {1}, is not valid.
Explanation:
No additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW2908E: The port value of the virtual host alias {0} is absent.
Explanation:
No additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW2909E: The virtual host alias port value, {0}, is not a number.
Explanation:
No additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW2910E: The virtual host alias port value, {0}, is not a valid port number.
Explanation:
No additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW2911E: The type of a mime entry beneath virtual host {0} is absent.
Explanation:
No additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW2912E: Type type of a mime entry, {0}, beneath virtual host {1}, is not valid.
Explanation:
No additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW2913E: A mime entry extension, on mime entry of type {0}, is absent.
Explanation:
No additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW2914E: The mime entry extension {0}, on mime entry of type {1}, is not valid.
Explanation:
No additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW2915E: No virtual hosts are present.
Explanation:
No additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW2916E: The virtual host name {0} is duplicated.
Explanation:
No additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3000I: IBM WebSphere Validation
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3001I: Resources Validation
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3003E: An object of an unrecognized type was sent for resources validation. This is an internal error. The object type is {0}.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3004E: The name of a J2EE resource provider in {0} is absent.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3007E: No database name was specified for data source {1}, of resource provider {0}.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3009E: The minimum pool size, {0}, of a data source is not valid. The minimum pool size may not be less than {1}.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3011E: The maximum pool size, {0}, of a data source is not valid. The maximum pool size may not be less than {1}.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3012E: A minimum pool size, {0}, is greater than the maximum pool size {1}, of data source {3}, of resource provider {2}.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3013E: A connection timeout which is too low has been specified for a data source. The connection timeout of a data source may not be less than {0}.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3015E: An idle timeout which is too low has been specified for a data source. The idle timeout of a data source may not be less than {0}.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3017E: An orphan timeout which is too low has been specified for a data source. The orphan timeout of a data source may not be less than {0}.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3019E: A statement cache size which is too low has been specified for a data source. The statement cache size of a data source may not be less than {0}.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3021E: The specification of URL {1}, of resource provider {0}, is absent.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3022E: The stream handler class name of URL provider {0} is absent.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3023E: The protocol of URL provider {0} is absent.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3024E: The display name of the J2C resource adaptor is absent.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3025E: The JNDI name of the J2EE resource factory, {0}, must be specified.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3026E: The name of the J2EE resource factory is absent.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3027E: The J2EE resource provider of J2EE resource factory {0} is absent.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3028E: The type of a J2EE resource provider''s resource property is absent. (Provider name = {0})
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3029E: The name of a J2EE resource provider''s resource property is absent. (Provider name = {0})
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3030E: The type of a J2EE resource factory''s resource property is absent. (Provider name = {0}, Factory name = {1})
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3031E: The name of a J2EE resource factory''s resource property is absent. (Provider name = {0}, Factory name = {1})
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3032E: The external JNDI name of the JMS connection factory is absent.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3033E: The implementation class name, {0}, is invalid for JDBC driver, {1}.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3034E: A connection type must be specified for connection factory, {0}.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3035E: The connection type, {0}, is invalid for connection factory, {1}. Valid values are {TOPIC|QUEUE}.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3036E: A destination type must be specified for JMS destination, {0}.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3037E: The destination type is invalid for JMS destination, {0}. Valid values are {TOPIC|QUEUE}.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3038E: The stream handler class name of URL provider {0} is not valid. Stream handler classes must implement the java.net.URLStreamHandlerFactory interface.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3039E: No ''serverName'' property is available for data source {1}, of resource provider {0}. (The case of this property name must match exactly.)
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3040E: No ''URL'' property is available within data source {1}, of resource provider {0}. (The case of the property name must match exactly.)
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3041E: Neither the default user, nor a ''user'' property is available within data source {1}, of resource provider {0}. (The case of the property name must match exactly.)
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3042E: Neither the default user, nor a ''password'' property is available within data source {1}, of resource provider {0}. (The case of the property name must match exactly.)
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3043E: No ''portNumber'' property is available within the data source {1}, of resource provider {0}. (The case of the property name must match exactly.)
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3044E: No ''url'' property is available within data source {1}, of resource provider {0}. (The case of the property name must match exactly.)
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3045E: Duplicated resource factory JNDI name {0} on resource factory {1} under resource provider {2}.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3047E: Duplicated resource property {0}.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3048E: Duplicated SSL property name {0}.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3049E: Duplicated user registry property name {0}.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3050E: Duplicated resource factory name {0}. Another resource factory already has this name. (The names of resource factories beneath a single resource provider must be distinct.)
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3051E: Duplicated resource factory JNDI name {0}. Another resource factory already has this JNDI name. (The JNDI Names of resource factories beneath a single resource provider must be distinct.)
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3052E: The persistence value of MQ Topic {1}, of resource provider {0}, is absent.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3053E: The persistence value {0}, of MQ Topic {1}, of resource provider {0}, is not valid.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3054E: The priority value of MQ Topic {1}, of resource provider {0}, is absent.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3055E: The priority value {0}, of MQ Topic {2}, of resource provider {1}, is not valid.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3056E: The specified priority of MQ Topic {1}, of resource provider {0}, is absent.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3057E: The specified priority {0}, of MQ Topic {2}, of resource provider {1}, is not valid.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3058E: The MQ topic priority, {0}, is out of range. The priority may be no less than {1} and no more than {2}.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3059E: The expiry setting of MQ topic {1}, of resource provider {0}, is absent.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3060E: The expiry value, {0}, of MQ topic {2}, of resource provider {1}, is not valid.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3061E: The specified expiry setting of MQ topic {1}, of resource provider {0}, is absent.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3062E: The base topic name of MQ topic {1}, of resource provider {0}, is absent.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3063E: The use native encoding flag of MQ topic {1}, of resource provider {0}, is absent.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3064E: The integer encoding value of MQ topic {1}, of resource provider {0}, is absent.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3065E: The integer encoding value {0}, of MQ topic {2}, of resource provider {1}, is not valid.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3066E: The decimal encoding value of MQ topic {1}, of resource provider {0}, is absent.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3067E: The decimal encoding value {0}, of MQ topic {2}, of resource provider {1}, is not valid.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3068E: The floating point encoding value of MQ topic {1}, of resource provider {0}, is absent.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3069E: The MQ topic floating point encoding value, {0}, is not valid.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3070E: The target client value of MQ topic {1}, of resource provider {0}, is absent.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3071E: The target client value {0}, of MQ topic {2}, of resource provider {1}, is not valid.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3072E: The expiry value of MQ queue {1}, of resource provider {0}, is absent.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3073E: The expiry value {0}, of MQ queue {2}, of resource provider {1}, is not valid.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3074E: The specified expiry of MQ queue {1}, of resource provider {0}, is absent.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3075E: The specified expiry {0}, of MQ queue {2}, of resource provider {0}, is not valid.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3076E: The native encoding setting of MQ queue {1}, of resource provider {0}, is absent.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3077E: The integer encoding value of MQ queue {1}, of resource provider {0}, is absent.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3078E: The integer encoding value {0}, of MQ queue {2}, of resource provider {1}, is not valid.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3079E: The transport type of MQ topic connection factory {1}, of resource provider {0}, is absent.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3080E: The transport type, {0}, of MQ topic connection factory {2}, of resource provider {1}, is not valid.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3081E: The host of MQ topic connection factory {1}, of resource provider {0}, is absent.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3082E: The port of MQ topic connection factory {1}, of resource provider {1}, is absent.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3083E: The MQ topic connection factory port {0} is not a valid port number. Valid port values must be no less than {1} and no greater than {2}.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3084E: The clone support setting of MQ topic connection factory {1}, of resource provider {0}, is absent.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3085E: The client ID of MQ topic connection factory {1}, of resource provider {0}, is absent.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3086E: The broker version of MQ topic connection factory {1}, of resource provider {0}, is absent.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3087E: The broker version {0}, of MQ topic connection factory {2}, of resource provider {1}, is not valid.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3088E: The classpath of J2EE resource provider {0} is absent.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3089E: The native path of J2EE resource provider {0} is absent.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3090E: The MQ queue connection factory transport type is absent.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3091E: The MQ queue connection factory transport type, {0}, is not valid.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3092E: The host of MQ queue connection factory {1}, of resource provider {0}, is absent.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3093E: The port of MQ queue connection factory {1}, of resource provider {0}, is absent.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3094E: The MQ queue connection factory port {0} is not a valid port number. Port values must be no less than {1} and no greater than {2}.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3095E: The persistence value of MQ Queue {1}, of resource provider {0}, is absent.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3096E: The persistence value, {0}, of MQ Queue {2}, of resource provider {1}, is not valid.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3097E: The priority value of MQ Queue {1}, of resource provider {0}, is absent.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3098E: The priority value {0}, of MQ Queue {2}, of resource provider {1}, is not valid.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3099E: The specified priority value of MQ Queue {1}, of resource provider {0} is absent.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3102E: The decimal encoding value of MQ Queue {1}, of resource provider {0}, is absent.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3103E: The decimal encoding value {0}, of MQ Queue {2}, of resource provider {1}, is not valid.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3104E: The floating point encoding value of MQ Queue {1}, of resource provider {0}, is absent.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3105E: The floating point encoding value {0}, of MQ Queue {2}, of resource provider {0}, is not valid.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3106E: The target client value of MQ Queue {1}, of resource provider {0}, is absent.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3107E: The target client value {0}, of MQ Queue {2}, of resource provider {0}, is not valid.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3109E: The persistence value of WAS Queue {1}, of resource provider {0}, is absent.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3110E: The specified priority value {0}, of MQ Queue {2}, of resource provider {1}, is not valid.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3110E: The persistence value {0}, of WAS Queue {2}, of resource provider {1}, is not valid.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3111E: The priority value of WAS Queue {1}, of resource provider {0}, is absent.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3112E: The priority value {0}, of WAS Queue {2}, of resource provider {1}, is not valid.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3113E: The specified priority value of WAS Queue {1}, of resource provider {0}, is absent.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3114E: The specified priority value {0}, of WAS Queue {2}, of resource provider {1}, is not valid.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3115E: The specified expiry value of WAS Queue {1}, of resource provider {0}, is absent.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3116E: The specified expiry value, {0}, of WAS Queue {2}, of resource provider {1}, is not valid.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3117E: The connection factory node of WAS Queue {1}, of resource provider {0}, is absent.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3118E: The topic value of WAS Topic {1}, of resource provider {0}, is absent.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3119E: The persistence value of WAS Topic {1}, of resource provider {0}, is absent.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3120E: The persistence value {0}, of WAS Topic {2}, of resource provider {1},is not valid.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3121E: The priority value of WAS Topic {1}, of resource provider {0}, is absent.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3122E: The priority value {0}, of WAS Topic {2}, of resource provider {1}, is not valid.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3123E: The specified priority value of WAS Topic {1}, of resource provider {0}, is absent.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3124E: The specified priority value {0}, of WAS Topic {2}, of resource provider {1}, is not valid.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3125E: The specified expiry value of WAS Topic {1}, of resource provider {0}, is absent.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3126E: The specified expiry value {0}, of WAS Topic {2}, of resource provider {1}, is not valid.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3127E: The factory node of WAS Top {1}, of resource provider {0}, is absent.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3128E: The factory port of WAS Top {1}, of resource provider {0}, is absent.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3129E: The WAS topic factory port {0}, is not a valid port value. A port value may not be less than {1} and may not be greater than {2}.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3130E: The clone support setting of WAS topic connection factory {1}, of resource provider {0}, is absent.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3131E: The client id of WAS topic connection factory {1}, of resource provider {0}, is absent.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3132E: The factory associated with mail provider {1} is not a mail session. The actual factory type is {0}.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3133E: The provider of mail session {0} is absent.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3134E: The provider associated with a mail session {2}, of resource provider {1}, is not a mail provider. The actual provider type is {0}.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3135E: The transport protocol of mail session {1}, of resource provider {0}, is absent.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3136E: The transport protocol ({0}) of mail session ({2}), of resource provider ({1}), does not exist.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3137E: The mail store provider of mail session {1}, of resource provider {0}, is absent.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3138E: The store protocol ({0}) of mail session ({2}), of resource provider ({1}) does not exist.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3140E: The node {0}, specified for WAS queue connection factory {2}, of resource provider {1}, matches no configured node.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3142E: The node {0}, specified for WAS queue topic factory {2}, of resource provider {1}, matches no configured node.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3143E: A JDBCProvider implementation class name must be provided.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3144E: The maximum number of connections specified {0}, is invalid.
Explanation:
The value must be greater than zero.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3145E: The minimum number of connections specified {0}, is invalid.
Explanation:
The minimum number of connections must be greater than zero and less than the maximum number of connections.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3146E: The connection timeout value of {0} is invalid.
Explanation:
The connection timeout value must be a number greater than zero.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3147E: The Reap Time value of {0} is invalid.
Explanation:
The Reap Time value must be a number greater than zero.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3148E: The Un-Used Timeout value of {0} is invalid.
Explanation:
The un-used Timeout value must be a number greater than zero.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3149E: The Aged Timeout value of {0} is invalid.
Explanation:
The Aged Timeout value must be a number greater than zero.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3152E: The statement cache size ({0}) of the data source ({1}) is invalid.
Explanation:
The cache size must be 0 or greater.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3153E: The WAS queue name ({0}), which has a length of {1}, is too long. A WAS queue name may not be more than {2} characters long.
Explanation:
No additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3155E: The property value ({0}) is not matched to the type ({1}) specified in the J2EE Resource Provider ({2}).
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3156E: The property value ({0}) is not matched to the type ({1}) specified in the J2EE Resource Factory ({2}).
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3157E: The WAS queue name ({0}) has invalid character(s). Valid characters are "{1}".
Explanation:
No additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3158E: The type, {0}, of GenericJMSDestination ({2}), of resource provider ({1}), is not valid.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3159E: The type, {0}, of GenericJMSConnectionFactory ({2}), of resource provider ({1}), is not valid.
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3160E: The value of a J2EE resource provider''s resource property is absent. (Provider name = {0})
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3161E: The value of a J2EE resource factory''s resource property is absent. (Provider name = {0}, Factory name = {1})
Explanation:
No Additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3605E: The host of a transport is absent.
Explanation:
No additional in formation is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3606E: The port of a transport with host {0} is absent.
Explanation:
No additional in formation is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3607E: The transport port {0} is not a valid port number. Valid port values must be no less than {1} and no greater than {2}.
Explanation:
No additional in formation is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3608E: The transport property name {0} is duplicated.
Explanation:
No additional in formation is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3609E: The name of a transport property is absent.
Explanation:
No additional in formation is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3611E: A transport SSL enablement is absent.
Explanation:
No additional in formation is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3612E: A transport has SSL enabled, but the SSL configuration value is absent.
Explanation:
No additional in formation is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3616E: The initial state of the state manageable of managed object {0} is absent.
Explanation:
No additional in formation is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3617E: The initial state, {0}, of the state manageable of managed object {0} is not valid.
Explanation:
No additional in formation is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3618E: Transport aliases could not be retrieved as the security object could not be loaded from {0}.
Explanation:
No additional in formation is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3619E: Transport aliases could not be retrieved as the security object in {0} is not valid.
Explanation:
No additional in formation is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3620E: Transport aliases could not be retrieved as the security object in {0} is not valid.
Explanation:
No additional in formation is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3700I: IBM WebSphere Validation
Explanation:
No additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3701I: MOF Validation
Explanation:
No additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3702W: Failed to recognize object of type {0}.
Explanation:
No additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW3703E: Failed to load model from {0}.
Explanation:
No additional information is available.
User Response:
Please use either the admin application or the command line scripting tool to update the part of the configuration which is in error.
CHKW5525E: The user ID {0} is used by more than one security authorization entry.
Explanation:
The validator for the security configuration document, security.xml detected that the user ID {0} is used by more than one security authorization entry .
User Response:
Make sure there is only one security authorization entry with the user ID {0}.
CHKW6000E: J2EE Web Services validation failed: {0}.
Explanation:
None.
User Response:
None.
CHKW6001E: Access of model from IHelper failed.
Explanation:
An internal error occurred.
User Response:
None.
CHKW6002I: Validating webservices in {0}.
Explanation:
Starting JSR109 validation of module {0}.
User Response:
Information only, no action is required.
CHKW6003E: WSDL file {0} was not found in this module. (JSR109 1.0: 4.2.6)
Explanation:
webservice.xml or webservicesclient.xml referred to file {0} that could not be found in this module.
User Response:
Add a WSDL file named {0} in this module.
CHKW6004E: JAX-RPC mapping file {0} was not found in this module. (JSR109 1.0: 4.2.6)
Explanation:
webservice.xml or webservicesclient.xml referred to file {0} that could not be found in this module.
User Response:
Add a JAX-RPC mapping file named {0} in this module.
CHKW6005E: Service Endpoint Interface {0} was not found in this module. (JSR109 1.0: 4.2.6)
Explanation:
webservice.xml or webservicesclient.xml referred to class {0} that could not be found in this module.
User Response:
Add a Service Endpoint Interface named {0} in this module.
CHKW6006E: Service Endpoint Interface {0} must extend java.rmi.Remote either directly or indirectly. (JSR109 1.0: 5.3.1)
Explanation:
The Service Endpoint Interface (SEI) must follow the JAX-RPC rules for WSDL to Java mapping.
User Response:
Change the declaration of interface {0} to extend java.rmi.Remote.
CHKW6007E: Method {0} in Service Endpoint Interface {1} does not throw java.rmi.RemoteException. (JSR109 1.0: 5.3.1)
Explanation:
The Service Endpoint Interface (SEI) must follow the JAX-RPC rules for WSDL to Java mapping. They require that all interface methods throw java.rmi.RemoteException.
User Response:
Change the declaration of method {0} in {1} to throw java.rmi.RemoteException.
CHKW6008E: Method {0} in Service Endpoint Interface {1} uses type {2}, which is not a JAX-RPC supported type. (JSR109 1.0: 5.3.1)
Explanation:
The Service Endpoint Interface (SEI) must follow the JAX-RPC rules for WSDL to Java mapping. They specify that method parameters and return types must be the JAX-RPC supported types.
User Response:
Change the declaration for method {0} in Service Endpoint Interface {1} to use JAX-RPC supported types.
CHKW6009E: Method {0} in Service Endpoint Interface {1} uses type {2}, which is not a JAX-RPC serializable type. (JSR109 1.0: 5.3.1)
Explanation:
The Service Endpoint Interface (SEI) must follow the JAX-RPC rules for WSDL to Java mapping, which require that all referenced types must be JAX-RPC serializable.
User Response:
Change the declaration for method {0} in Service Endpoint Interface {1} to use JAX-RPC supported types.
CHKW6010E: Constant field {0} in interface {1} is not permitted. (JAX-RPC 1.0: 5.2)
Explanation:
The Service Endpoint Interface (SEI) must follow the JAX-RPC rules for WSDL to Java mapping. They specify that the Service Endpoint Interface class must not include constant (as public final static) declarations.
User Response:
Delete field {0} in Interface {1}.
CHKW6011E: Default public constructor for service implementation class {0} was not found. (JSR109 1.0: 5.3.2.1)
Explanation:
Service implementation class {0} must have a default public constructor in order to be a Stateless Session EJB.
User Response:
Add a public default constructor to class {0}.
CHKW6012E: Class {0} does not implement method {1} of the Service Endpoint Interface {2}. (JSR109 1.0: 5.3.2.1)
Explanation:
The implementation class must implement the methods of the Service Endpoint Interface.
User Response:
Implement all the method signatures in the {0} class for the Service Endpoint Interface {2}.
CHKW6013E: The visibility for method {0} in class {1} must be public. (JSR109 1.0: 5.3.2.1)
Explanation:
The business methods of the class must be public.
User Response:
Change the visibility for method {0} in class {1} to public.
CHKW6014E: Method {0} in class {1} must not be final. (JSR109 1.0: 5.3.2.1)
Explanation:
The business methods of the class must not be final.
User Response:
Remove the final modifier for method {0} in class {1}.
CHKW6015E: Method {0} in class {1} must not be static. (JSR109 1.0: 5.3.2.1)
Explanation:
The business methods of the class must not be static.
User Response:
Remove the static modifier for method {0} in class {1}.
CHKW6016E: The visibility for the service implementation class {0} must be public. (JSR109 1.0: 5.3.2.1)
Explanation:
The service implementation class must be public, must not be final and must not be abstract.
User Response:
Change the visibility for the service implementation class {0} to public.
CHKW6017E: The service implementation class {0} must not be declared final. (JSR109 1.0: 5.3.2.1)
Explanation:
The service implementation class must be public, must not be final and must not be abstract.
User Response:
Remove the final modifier for class {0}.
CHKW6018E: Service implementation class {0} must not be declared abstract. (JSR109 1.0: 5.3.2.1)
Explanation:
The service implementation class must be public, must not be final and must not be abstract.
User Response:
Remove the abstract modifier for class {0}.
CHKW6019E: Service implementation class {0} must not contain a finalize() method. (JSR109 1.0: 5.3.2.1)
Explanation:
A service implementation class must not define the finalize() method.
User Response:
Remove finalize() method from service implementation class {0}.
CHKW6020E: The transaction attributes of method {0} in class {1} must not include Mandatory. (JSR109 1.0: 5.3.2.1.3)
Explanation:
An existing Enterprise Java bean may be used as a Service Implementation Bean if the transaction attributes of the SEI methods do not include Mandatory.
User Response:
Remove Mandatory from the transaction attributes of method {0} in class {1}.
CHKW6021E: Service implementation class {0} was not found in this module. (JSR109 1.0: 5.4)
Explanation:
Service implementation class {0} could not be found this module.
User Response:
Add a service implementation class named {0} in this module.
CHKW6022E: Session EJB {0} must be declared as Stateless in ejb-jar.xml. (JSR109 1.0: 7.1.2)
Explanation:
Service implementation classes using a session bean must be defined in the ejb-jar.xml deployment descriptor file using the session element and cannot be declared with a session-type of Stateful.
User Response:
Define the EJB named {0} in ejb-jar.xml to have a Stateless session-type.
CHKW6023E: Enterprise-beans class {0} defined in ejb-jar.xml must be a session bean. (JSR109 1.0: 7.1.2)
Explanation:
Service Implementations must be defined in the ejb-jar.xml deployment descriptor file using the session element.
User Response:
Define the class named {0} in ejb-jar.xml using the session element of enterprise-beans.
CHKW6024E: The value of the servlet-link attribute {0} does not correspond to an servlet definition in web.xml. (JSR109 1.0: 7.1.2)
Explanation:
The servlet-link must refer to a servlet in web.xml.
User Response:
Add a servlet named {0} or change the servlet definition in web.xml.
CHKW6025E: Mapping file {0} must not be specified when no wsdl-file element is specified in webservicesclient.xml. (JSR109 1.0: 4.2.2.6)
Explanation:
If wsdl-file is not specified in webservicesclient.xml, jaxrpc-mapping-file must not be specified.
User Response:
Remove mapping file {0} or add a wsdl-file element in webservicesclient.xml.
CHKW6026W: Stub file {0} should not be packaged in module {1}. (JSR109 1.0: 4.2.6)
Explanation:
The developer must not package generated stubs.
User Response:
Remove all generated stubs from the module.
CHKW6027E: The value of the ejb-link attribute {0} does not correspond to an Enterprise Bean definition in ejb-jar.xml. (JSR109 1.0: 7.1.5)
Explanation:
The value of the ejb-link element must be the ejb-name of an enterprise bean in the same module.
User Response:
Add a Enterprise Bean named {0} or change the ejb-link definition in ejb-jar.xml.
CHKW6028E: The component-name element {0} does not refer to an ejb-name element in the ejb-jar.xml. (JSR109 1.0: 7.2.5)
Explanation:
The component-name element defines a link to a component name such as the ejb-name in the module deployment descriptor. Its value must exist in the module level deployment descriptor.
User Response:
Change the component-name element {0} to refer to a ejb-name element in the ejb-jar.xml.
CHKW6029E: Could not find the port component named {0} referenced by port-component-link in service-ref {1} of webservicesclient.xml. (JSR109 1.0: 7.2.5)
Explanation:
The value of a port-component-link must be the port-component-name of a port-component in the same module or another module in the same application unit.
User Response:
Add a port component named {0} or change the reference in service-ref {1} of webservicesclient.xml.
CHKW6030E: Implementation class {0} referred to by port components {1} and {2}. (JSR109 1.0: 7.1.2)
Explanation:
A servlet must only be linked to by a single port-component. A session EJB must only be linked to by a single port-component.
User Response:
Change either port component {1} or port component {2} so that they do not both reference implementation class {0}.
CHKW6031E: Multiple servlet mappings detected for servlet named {0} in web.xml. (JSR109 1.0: 7.1.2)
Explanation:
No more than one servlet-mapping may be specified for a servlet that is linked to by a port-component.
User Response:
Remove duplicate servlet mappings for servlet named {0} in web.xml.
CHKW6032E: Servlet mapping for servlet {0} must not contain an asterisk in the url-pattern. (JSR109 1.0: 7.1.2)
Explanation:
The url-pattern of the servlet-mapping must be an exact match pattern.
User Response:
Change servlet mapping for servlet {0} so it does not contain an asterisk.
CHKW6033E: Port {0} is not compatible with Service Endpoint Interface {1}. (JSR109 1.0: 8.3)
Explanation:
When providing a binding for a port-component-ref, the deployer must ensure that the port-component-ref is compatible with the port being bound to.
User Response:
Change port {0} to be compatible with Service Endpoint Interface {1}.
CHKW6034E: wsdl-file {0} cannot use both mapping files {1} and {2}. (JSR109 1.0: 7.2.2)
Explanation:
Only one mapping file can be associated with a wsdl-file.
User Response:
Specify a unique mapping file for the wsdl-file in webservicesclient.xml.
CHKW6035E: Missing jaxrpc-mapping-file in webservicesclient.xml. (JSR109 1.0: 7.2.2)
Explanation:
The developer must specify the jaxrpc-mapping-file if wsdl-file is specified.
User Response:
Add a jaxrpc-mapping-file element in webservicesclient.xml.
CHKW6036E: The serviceRefLink {0} specified in ibm-webservicesclient-bnd.xmi is not the name of a service-ref in webservicesclient.xml.
Explanation:
serviceRefLink must name a service-ref in webservicesclient.xml.
User Response:
Correct the serviceRefLink to name a service-ref in webservicesclient.xml.
CHKW6037E: The deployedWSDLFile path {0} specified in ibm-webservicesclient-bnd.xmi does not reference a WSDL file in this module.
Explanation:
deployedWSDLFile must be the relative path within the module of the WSDL file.
User Response:
Correct the path or add the WSDL file at the specified path.
CHKW6038E: The defaultMappings element specified for service-ref {0} in ibm-webservicesclient-bnd.xmi references portType {1} or port {2} that is not present in WSDL file {3}.
Explanation:
defaultMappings must reference a port and portType in the wsdl-file associated with the service-ref.
User Response:
Correct the attributes of the defaultMappings element to refer to a port and portType in {3}.
CHKW6039E: The portQnameBindings port name {0} specified for service-ref {1} in ibm-webservicesclient-bnd.xmi references a port that is not present in WSDL file {2}.
Explanation:
portQnameBindings must reference a port in the wsdl-file associated with the service-ref.
User Response:
Correct the portQnameBindings attributes to refer to a port in {2}.
CHKW6040E: The componentNameLink attribute {0} in ibm-webservicesclient-bnd.xmi references a component-name that does not exist in webservicesclient.xml.
Explanation:
The componentNameLink attribute must reference a component-name in webservicesclient.xml.
User Response:
Modify the componentNameLink attribute to match a component-name in webservicesclient.xml.
CHKW6041E: The scope attribute {0} specified for port-component {1} in ibm-webservices-bnd.xmi is not Request, Session, or Application.
Explanation:
The scope attribute must reference must be either Request, Session, or Application.
User Response:
Correct the scope attribute.
CHKW6042E: The pcNameLink attribute {0} specified for webservice-description {1} in ibm-webservices-bnd.xmi references a port-component that does not exist in webservices.xml.
Explanation:
The pcNameLink attribute must reference a port-component-name in webservices.xml.
User Response:
Modify the pcNameLink attribute to match a port-component-name in webservices.xml.
CHKW6043E: The wsDescNameLink attribute {0} specified in ibm-webservices-bnd.xmi references a webservice-description-name that does not exist in webservices.xml.
Explanation:
The wsDescNameLink attribute must reference a webservice-description in webservices.xml.
User Response:
Modify the wsDescNameLink attribute to match a webservice-description-name in webservices.xml.
CHKW6045E: The routerModules name {0} in ibm-webservices-bnd.xmi references a module that does not exist in the application.
Explanation:
The routerModules name attribute must reference a module in the current application. It is normally added by the endptEnabler
User Response:
Either repair the routerModules name or delete the routerModules element and run the endptEnabler command again on the application.
CHKW6046E: No Service Interface specified in the service-interface element for service-ref {0} in webservicesclient.xml. (JSR109 1.0: 4.2.2)
Explanation:
webservicesclient.xml did not specify a value for the required service-interface element.
User Response:
Add a valid value for the service-interface element.
CHKW6047E: No Service Endpoint Interface specified in a service-endpoint-interface element in service-ref {0} in webservicesclient.xml. (JSR109 1.0: 7.2.3)
Explanation:
webservicesclient.xml did not specify a value for the required service-endpoint-interface element.
User Response:
Add a valid value for the service-endpoint-interface element.
CHKW6048E: Service Endpoint Interface {0} in {1} is not an interface. (JSR109 1.0: 3.10)
Explanation:
The class specified in the service-endpoint-interface element must be an interface.
User Response:
Specify an interface for the service-endpoint-interface element.
CHKW6049E: Servlet-link element {0} in port component {1} in webservices.xml should be ejb-link for EJB modules. (JSR109 1.0: 7.1.2)
Explanation:
The servlet-link element of webservices.xml can only appear in Web modules.
User Response:
Change the servlet-link element in webservices.xml to an ejb-link element.
CHKW6050E: Ejb-link element {0} in port component {1} in webservices.xml should be servlet-link for Web modules. (JSR109 1.0: 7.1.2)
Explanation:
The ejb-link element of webservices.xml can only appear in EJB modules.
User Response:
Change the ejb-link element in webservices.xml to a servlet-link element.
CHKW6051E: Required servlet-link element was not found for port component {0} in webservices.xml. (JSR109 1.0: 7.1.2)
Explanation:
A servlet-link element must appear in webservices.xml in Web modules.
User Response:
Add a servlet-link element to webservices.xml.
CHKW6052E: Required ejb-link element was not found for port component {0} in webservices.xml. (JSR109 1.0: 5.3.2.1.3)
Explanation:
A ejb-link element must appear in webservices.xml in EJB modules.
User Response:
Add an ejb-link element to webservices.xml.
CHKW6053E: Parse error in {0}: {1}: {2}. (JSR109 1.0: 7.1, 7.2)
Explanation:
A SAXParseException occurred reading descriptor {0}.
User Response:
Correct the problem reported in {0}.
CHKW6054E: Error in {0}: {1}: {2}.
Explanation:
A exception occurred reading descriptor {0}.
User Response:
Correct the problem reported in {0}.
CHKW6055E: Required service-impl-bean element was not found for port component {0} in webservices.xml. (JSR109 1.0: 5.3.2.1.3)
Explanation:
A service-impl-bean element must appear each port component in webservices.xml.
User Response:
Add a service-impl-bean element to webservices.xml.
CHKW6056E: Required webservice-description-name attribute was not found in webservices.xml. (JSR109 1.0: 7.1.5)
Explanation:
A webservice-description-name attribute must appear for each webservice-description in webservices.xml.
User Response:
Add a webservice-description-name attribute to each webservice-description in webservices.xml.
CHKW6057E: Required webservice-description element was not found in webservices.xml. (JSR109 1.0: 7.1.5)
Explanation:
A webservice-description element must appear in webservices.xml.
User Response:
Add a webservice-description element to webservices.xml.
CHKW6058E: Required wsdl-file element was not found in webservice-description {0} in webservices.xml. (JSR109 1.0: 7.1.5)
Explanation:
A wsdl-file element must appear in each webservice-description webservices.xml.
User Response:
Add a wsdl-file element to each webservice-description element to webservices.xml.
CHKW6059E: Required jaxrpc-mapping-file element was not found in webservice-description {0} in webservices.xml. (JSR109 1.0: 7.1.5)
Explanation:
A jaxrpc-mapping-file element must appear in each webservice-description in webservices.xml.
User Response:
Add a jaxrpc-mapping-file element to each webservice-description element in webservices.xml.
CHKW6060E: Required pcNameLink attribute was not found in ibm-webservices-bnd.xmi.
Explanation:
A pcNameLink attribute must appear in each pcBindings element in ibm-webservices-bnd.xmi.
User Response:
Add a pcNameLink attribute to each pcBindings element in ibm-webservices-bnd.xmi.
CHKW6061E: Required port-component-name element was not found in webservice-description {0} in webservices.xml.(JSR109 1.0: 7.1.5)
Explanation:
A port-component-name element must appear in each webservice-description element in webservices.xml.
User Response:
Add a port-component-name element to each webservice-description element in webservices.xml.
CHKW6062E: Required wsDescNameLink attribute was not found in ibm-webservices-bnd.xmi.
Explanation:
A wsDescNameLink attribute must appear in each wsdescBindings element in ibm-webservices-bnd.xmi.
User Response:
Add a wsDescNameLink attribute to each wsdescBindings element in ibm-webservices.xmi.
CHKW6063E: Required component-name element was not found in webservicesclient.xml. (JSR109 1.0: 7.2.5)
Explanation:
The component-name element must appear for each component-scoped-ref in webservicesclient.xml.
User Response:
Add a component-name element to refer to a ejb-name element in the ejb-jar.xml.
CHKW6064E: Required service-ref-name element was not found in service-ref in webservicesclient.xml. (JSR109 1.0: 7.2.5)
Explanation:
The sevice-ref-name element must appear for each service-ref in webservicesclient.xml.
User Response:
Add a service-ref-name element to each service-ref in webservicesclient.xml.
CHKW6065E: Required service-ref element was not found in webservicesclient.xml. (JSR109 1.0: 7.2.5)
Explanation:
The sevice-ref element must appear webservicesclient.xml.
User Response:
Add a service-ref element to webservicesclient.xml.
CHKW6066E: Required componentNameLink attribute was not found in ibm-webservicesclient-bnd.xmi.
Explanation:
A componentNameLink attribute must appear in each componentScopedRefs element in ibm-webservicesclient-bnd.xmi.
User Response:
Add a componentNameLink attribute whose value is a component-name in webservices.xml.
CHKW6067E: Error in {0}: {1}: {2}.
Explanation:
A SAXParseException occurred reading binding file {0}.
User Response:
Correct the problem reported in {0}.
CHKW6068E: Required serviceRefLink attribute was not found in serviceRefs element ibm-webservicesclient-bnd.xmi.
Explanation:
A serviceRefLink attribute must appear in each serviceRefs element in ibm-webservicesclient-bnd.xmi.
User Response:
Add a serviceRefLink attribute whose value is a service-ref-name in webservices.xml.
CHKW6069E: Required service-endpoint-interface element was not found in port-component {0} in webservices.xml. (JSR109 1.0: 7.1.5)
Explanation:
The service-endpoint-interface element must appear in each port-component in webservices.xml.
User Response:
Add a service-endpoint-interface element to port-component {0} to webservices.xml.
CHKW6070E: Required component-scoped-refs element or service-ref element was not found in webservicesclient.xml. (JSR109 1.0: 7.2.5)
Explanation:
Either a component-scoped-refs or service-ref element must appear in webservicesclient.xml.
User Response:
Add a service-ref element or component-scoped-refs element to webservicesclient.xml.
CHKW6071E: Required port-component element was not found in webservice-description {0} in webservices.xml.(JSR109 1.0: 7.1.5)
Explanation:
A port-component element must appear in each webservice-description element in webservices.xml.
User Response:
Add a port-component element to each webservice-description element in webservices.xml.