WebSphere Management Config Archive Subsystem messages |
ADMB0001E: The system configuration contains more than 1 node. In WebSphere 6.0 we only support single node for importWasprofile and exportWasprofile command.
Explanation:
This is a restriction in WebSphere 6.0.
User Response:
ADMB0002E: The system configuration contains more than 1 server. In WebSphere 6.0 we only support single server for importWasprofile and exportWasprofile command.
Explanation:
This is a restriction in WebSphere 6.0.
User Response:
ADMB0003E: The configuration archive contains more than 1 node. In WebSphere 6.0 we only support single node for importWasprofile and exportWasprofile command.
Explanation:
This is a restriction in WebSphere 6.0.
User Response:
ADMB0004E: The configuration archive contains more than 1 server. In WebSphere 6.0 we only support single server for importWasprofile and exportWasprofile command.
Explanation:
This is a restriction in WebSphere 6.0.
User Response:
ADMB0005E: Server {1} on Node {0} does not exist.
Explanation:
The specified node name or server name are not valid.
User Response:
Specify a valid node anema and server name.
ADMB0006E: Application {0} contains application scope resource or variable configurations which are not supported on version 5 deployment targets.
Explanation:
Application scope resource or variable configurations are not supported by WebSphere version 5.
User Response:
Remove the application scope resource or variable configuration from the application.
ADMB0007E: Server {0} exists on node {1} already.
Explanation:
The importServer command creates a new server based on the server configuration from the archive.
User Response:
Specify a different server name.
ADMB0008I: The importWasprofile command overwrites the current configuration of the wsprofile profile.
Explanation:
This message is for informational purposes only.
User Response:
No user action is required.
ADMB0009E: The specified node {0} does not exist.
Explanation:
The specified node name does not match any node that is defined in the configuration.
User Response:
Check the spelling of the node name.