ADMB

ADMB0001E: The system configuration contains more than 1 node. In WebSphere 6.x we only support single node for importWasprofile and exportWasprofile command.
Explanation This is a restriction in WebSphere 6.x.
Action
ADMB0002E: The system configuration contains more than 1 server. In WebSphere 6.x we only support single server for importWasprofile and exportWasprofile command.
Explanation This is a restriction in WebSphere 6.x.
Action
ADMB0003E: The configuration archive contains more than 1 node. In WebSphere 6.x we only support single node for importWasprofile and exportWasprofile command.
Explanation This is a restriction in WebSphere 6.x.
Action
ADMB0004E: The configuration archive contains more than 1 server. In WebSphere 6.x we only support single server for importWasprofile and exportWasprofile command.
Explanation This is a restriction in WebSphere 6.x.
Action
ADMB0005E: Server {1} on Node {0} does not exist.
Explanation The specified node name or server name are not valid.
Action 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.
Action 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.
Action 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.
Action 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.
Action Check the spelling of the node name.
ADMB0010E: The systemapps.xml in configuration archive for import does not contain prefix of {0} variable for {1} application.
Explanation This is a restriction in WebSphere 6.x.
Action The configuration archive file for import needs to be exported with a correct version of WebSphere 6.x service pack.
ADMB0011I: The application {0} ''s binaryURL {1} is not valid in this system. The default value is used.
Explanation The specified application's binaryURL is not valid in this system. It was replaced by the default installedApps directory.
Action This message is information.
ADMB0012I: The application {0} is distribution disabled. Also, the specified BinaryURL does not exist. This application is ignored.
Explanation The specified application's does not point to the valid binary. This application is not imported.
Action If the skipped application should be processed, the binary file should be provided at the location that binaryURL points to.
ADMB0013E: Importing the application {0} failed.
Explanation Error happened while importing the specified application.
Action This is an internal error. If this problem happened, the contents of imported application can not be guaranteed.
ADMB0014E: The system configuration contains no servers. In WebSphere 6.x we only support profiles with at least one server for importWasprofile and exportWasprofile command.
Explanation This is a restriction in WebSphere 6.x.
Action
ADMB0015E: The configuration archive contains no servers. In WebSphere 6.x we only support profiles with at least one server for importWasprofile and exportWasprofile command.
Explanation This is a restriction in WebSphere 6.x.
Action
ADMB0016E: The number of servers in the configuration archive does not match the number of servers in the system configuration. In WebSphere 6.x we only support importWasprofile for profiles with the same number of servers.
Explanation This is a restriction in WebSphere 6.x.
Action
ADMB0017E: The names of servers in the configuration archive do not match the names of servers in the system configuration. In WebSphere 6.x we only support importWasprofile for profiles with the same amount of servers with the same server names.
Explanation This is a restriction in WebSphere 6.x.
Action
Reference topic    

Terms and conditions for information centers | Feedback

Last updated: Jun 13, 2012 3:34:38 PM CDT
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.messages.doc/com.ibm.ws.management.resources.configarchive.html

© Copyright IBM Corporation 2006, 2011. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)