Troubleshooting Application Issues
Some application issues and possible resolutions are listed below. This list is not complete but provides examples of messages that might be returned.
For a complete list of error codes, see the TIBCO ActiveMatrix BusinessWorks™ Error Codes guide.
| Issue | Message | Resolution |
|---|---|---|
| The specified application could not be deployed; no AppNodes exist. | TIBCO-BW-ADMIN-CLI-300432: Deployed application [Application:Version], The AppSpace [AppSpace] does not have any AppNodes. | No AppNodes have been created in the specified AppSpace. AppNodes are required for deployment. Create one or more AppNodes and issue the deploy command again. |
| The specified application could not be deployed; an application has already been deployed for that archive. | TIBCO-BW-ADMIN-CLI-300433: An application is already deployed with archive [Archive]. | The specified application has already been deployed for the specified archive. Use the show applications command to view it. |
| The specified application version format is not supported. | TIBCO-BW-ADMIN-CLI-500407: Version [Version] is not valid. Only <major>.<minor> version format is supported.]. | An application version must be specified as a major.minor version within an AppSpace. Check the formatting of the version number. |
| The specified application could not be started; application not found in domain. | TIBCO-BW-ADMIN-CLI-500409: Failed to start application [Application:Version]. <CausedBy> TIBCO-BW-ADMIN-500401: Application [Application] not found in the Domain [Domain] | The specified application is not found in the specified domain.
Use the show applications command to verify the application. |
| The specified application could not be started. | TIBCO-BW-ADMIN-CLI-500409: Failed to start application [Application:Version]. <CausedBy> TIBCO-BW-ADMIN-500444: Failed to start Application in AppNode [AppNode]. Check the AppNode log files for messages starting with TIBCO-THOR-FRWK, TIBCO-BW-FRWK, or TIBCO-BW-SR-FRWK for details. Application State [Start failed], reason: [Reason] |
The specified application failed to start. This could be caused by unresolved shared resources, missing constraints, or missing components. If you see this message, open the log file for the AppNode (in the BW_HOME\domains\<domain>\<AppSpace>\<AppNode>\log folder) and check for messages starting with: These messages should help you identify the source of the issue. You may need to adjust the logging level for the log file. See AppNode Logging for information. An application might not start if the specified AppNode is not running or is not reachable. In this case, the following message will be displayed: TIBCO-BW-ADMIN-CLI-500409: Failed to start application [Application:Version]. <CausedBy> TIBCO-BW-ADMIN-500313: AppNode [AppNode] is not running or cannot be contacted. |
| The specified application has been deployed but could not be started. | TIBCO-BW-ADMIN-CReasonLI-500414: Deployed application from the archive [Archive], however not all application instances started. <CausedBy> TIBCO-BW-ADMIN-500313: AppNode [AppNode] is not running or cannot be contacted. | The applicatoin instance couldn't be started on the specified node, as it is not running or is unreachable. Check that the bwagent the AppNode is registered to is reachable. Check that the Appnode is running. |
| The specified application is not in sync with the archive. | TIBCO-BW-ADMIN-CLI-500439: Applications are out of sync with the archive they were deployed from, They have to be re-deployed to keep them in sync. | The EAR file has been replaced with a new version or a new file of the same version. Redeploy the application using the -replace option: deploy -replace <EAR> |