Runtime Command–Line Interface Error Messages

JBIUG001 

Warning 

Wrong input parameter(s). Usage: java -jar jbi-upgrade-tool.jar ${APPSERVER_INSTALL_ROOT} ${DESTINATION_DOMAIN_ROOT}  

Cause: Input parameters provided to the upgrade tool are not correct.

Action: Check the input parameter values.

Resource Key: jbi.upgrade.tool.usage

JBIUG002 

Severe 

Exception/Error Summary: {0}  

Cause: The upgrade tool encountered an exception with summary {0}.

Action: Review the server log for more information about the cause of the error.

Resource Key: jbi.upgrade.tool.exception.summary

JBIUG003 

Severe 

JBI Registry not found 

Cause: The upgrade tool could not locate the JBI runtime registry, jbi-registry.xml, in the current installation.

Action: Check if the correct value is provided for the existing installation root directory.

Resource Key: jbi.upgrade.tool.jbi.registry.not.found

JBIUG004 

Severe 

JBI Registry parsing error 

Cause: The upgrade tool could not parse the jbi-registry.xml file.

Action: Check whether the installation in current installation root directory is corrupted.

Resource Key: jbi.upgrade.tool.jbi.registry.parsing.error

JBIUG005 

Severe 

App Server install root not found: "{0}" 

Cause: The upgrade tool did not find an application server installation at {0}.

Action: Check the values of the parameters for the upgrade command.

Resource Key: jbi.upgrade.tool.jbi.appserverInstallRoot.not.found

JBIUG006 

Severe 

domain root not found: "{0}"  

Cause: The upgrade tool did not find a domain at the provided destination domain root.

Action: Check the values of the parameters for the upgrade command.

Resource Key: jbi.upgrade.tool.jbi.domain.root.not.found

JBIUG007 

Warning 

jbi.xml not found  

Cause: The upgrade tool did not find the jbi.xml file for an existing component installation.

Action: Check the status of the component in the domain.

Resource Key: jbi.upgrade.tool.jbi.xml.not.found

JBIUG008 

Warning 

jbi.xml parsing error  

Cause: The upgrade tool could not parse the jbi.xml file in an existing component installation.

Action: Check the status of the component in the domain.

Resource Key: jbi.upgrade.tool.jbi.xml.parsing.error

JBIUG009 

Warning 

component install jar or compoent not found for "{0}", upgrade or migration skipped.  

Cause: The upgrade tool could not upgrade component {0} because the component installation root directory is corrupted.

Action: Check the status of the component {0}.

Resource Key: jbi.upgrade.tool.component.install.jar.not.found

JBIUG010 

Warning 

component install_root not found for "{0}" 

Cause: The upgrade tool could not upgrade component {0} because the component installation root directory is corrupted.

Action: Check the status of the component {0}.

Resource Key: jbi.upgrade.tool.component.install.root.not.found

JBIUG011 

Warning 

shared library install_root not found for "{0}"  

Cause: The upgrade tool could not locate the installation root directory for the shared library {0}.

Action: Check the status of the shared library in the domain.

Resource Key: jbi.upgrade.tool.shared.lib.install.root.not.found

JBIUG012 

Warning 

Service Assembly install root not found for "{0}"  

Cause: The upgrade tool could not locate the deployment root directory for the Service Assembly {0}.

Action: Check the status of the shared library deployment.

Resource Key: jbi.upgrade.tool.service.assembly.install.root.not.found

JBIUG013 

Warning 

component directory not found for "{0}"  

Cause: The upgrade tool could not upgrade component {0} because the component installation root directory is corrupted.

Action: Check the status of the component {0}.

Resource Key: jbi.upgrade.tool.component.dir.not.found

JBIUG014 

Warning 

More than two component install jars found  

Cause: The upgrade tool could not upgrade component {0} because the component installation root is corrupted.

Action: Check the status of the component {0}.

Resource Key: jbi.upgrade.tool.more.than.two.component.dirs.found

JBIUG015 

Severe 

Unknown error occurred. 

Cause: An error occurred during the upgrade process.

Action: Check the server log.

Resource Key: jbi.upgrade.tool.unknown.io.exception

JBIUG016 

Info 

Component "{0}" found in destination domain "{1}", migration for "{0}" skipped. 

Cause: Component {0} is already found in the destination domain and was not migrated from the source domain.

Action: None required.

Resource Key: jbi.upgrade.tool.component.found.in.dest.domain

JBIUG017 

Severe 

destination domain root not found: "{0}"  

Cause: The upgrade tool did not find a domain at the provided destination domain root directory.

Action: Check the values of the parameters for the upgrade command.

Resource Key: jbi.upgrade.tool.dest.domain.root.not.found

JBIUG018 

Severe 

source domain root not found: "{0}"  

Cause: The upgrade tool did not find a domain at the provided source domain root directory.

Action: Check the values of the parameters for the upgrade command.

Resource Key: jbi.upgrade.tool.src.domain.root.not.found

JBIUG019 

Info 

shared library "{0}" found in destination domain "{1}", migration for "{0}" skipped. 

Cause: The shared library {0} is already found in the destination domain and was not migrated from the source domain.

Action: None required.

Resource Key: jbi.upgrade.tool.shared.lib.found.in.dest.domain

JBIUG020 

Info 

Service Assembly "{0}" found in destination domain "{1}", migration for "{0}" skipped.  

Cause: The Service Assembly {0} is already found in the destination domain and was not migrated from the source domain.

Action: None required.

Resource Key: jbi.upgrade.tool.service.assembly.found.in.dest.domain

JBIUG021 

Warning 

directory not found: "{0}"  

Cause: The upgrade tool could not find the directory {0}.

Action: Check the status of the installation directory for the source domain.

Resource Key: jbi.upgrade.tool.directory.not.found

JBIUG022 

Severe 

Can not create file: "{0}"  

Cause: The upgrade tool could not create files in the destination domain.

Action: Make sure the destination domain root directory has write permissions.

Resource Key: jbi.upgrade.tool.can.not.create.file

JBIUG023 

Severe 

IOException occurred during file copying from "{0}" to "{1}".  

Cause: The upgrade tool could not copy files in the destination domain.

Action: Make sure the destination domain root directory has write permissions.

Resource Key: jbi.upgrade.tool.io.exception.during.file.copy

JBIUG024 

Warning 

Unjar error for "{0}".  

Cause: The upgrade tool could not extract the files from archive {0}.

Action: Check the status of the installation in the destination domain.

Resource Key: jbi.upgrade.tool.io.unjar.error

JBIUG039 

Severe 

Error when updating JBI registry. 

Cause: The upgrade tool could not update the jbi-registry.xml file in the destination domain.

Action: Check the status of the installation in the destination domain.

Resource Key: jbi.upgrade.tool.error.when.updating.jbi.registry