Troubleshooting Admin UI Issues

Some Admin UI 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. When a new version of the product is installed, you may need to open the Admin UI Agents page and reconnect to the bwagent.

Issue Message Resolution
The specified bwagent could not be registered in the Admin UI. Failure registering agent with [URL]. This error can be caused by several issues:
  • The specified bwagent at the URL provided in the Register Agent dialog box could not be located. Verify the URL and register the bwagent again.
  • A bwagent with the specified name already exists. Verify the name of the bwagent and register the bwagent again.
  • The specified bwagent might not be running. Make sure the bwagent is running and register the bwagent again.
The specified bwagent is unreachable. The status of Unreachable is displayed on the Agent Management page for the specified bwagent. The specified bwagent might not be running. Make sure the bwagent is running and register the bwagent again.
The details for a selected runtime entity cannot be displayed. Error executing operation 'getStates'; status '0'; reason 'Connection refused: no further information'. Since the Admin UI page for the selected runtime entity was displayed, either the runtime entity was deleted or the bwagent was stopped. Use bwadmin commands for the registered bwagent to verify the state of runtime entities and check the status of the bwagent.
The specified domain already exists. TIBCO-BW-TEAAGENT-500309: Failed to created Domain [Domain] TIBCO-BW-ADMIN-500101: Domain [Domain] already exists, check this and re-try. The specified domain already exists. Domain names must be unique; enter a different name. View existing domains on the Domain Management page.
The specified domain could not be created; the bwagent on the remote machine is not running. TIBCO-BW-TEAAGENT-500309: Failed to created Domain [Domain] TIBCO-BW-ADMIN-500004: Error invoking [joinmachine] method on the agent [bwagent], The BW Agent [bwagent] on the remote machine is not running. Verify the bwagent name. Check that the bwagent on the remote machine is running.
The specified AppSpace in the selected domain already exists. TIBCO-BW-TEAAGENT-500425: AppSpace [AppSpace] already exists in domain [Domain]. The specified AppSpace already exists. AppSpace names must be unique; enter a different name. View existing AppSpaces on the AppSpaces page.
The AppSpace status is Degraded and cannot be started. The status of Degraded is displayed on the AppSpaces page for the specified AppSpace. An AppSpace can only be started if it contains at least one AppNode. Check the minNodes value on the AppSpaces page and then pivot to the AppNodes page. Verify that the minimum number of AppNodes has been created. When the minNodes value is reached, the status of the AppSpace is changed to Stopped.
The specified AppNode in the selected AppSpace and domain already exists. TIBCO-BW-TEAAGENT-500313: Failed to create AppNode [AppNode] in AppSpace [AppSpace] in Domain [Domain], TIBCO-BW-ADMIN-500301: The AppNode [AppNode] already exists in the AppSpace [AppSpace] Domain [Domain]. The specified AppNode already exists. AppNode names must be unique; enter a different name. View existing AppNodes on the AppNodes page.
The specified archive could not be uploaded. Failed to Upload. TIBCO-BW-ADMIN-500447: Archive [Archive] is already present in the domain, use -replace option to replace the existing archive. The specified archive has already been uploaded to the specified domain.

To replace the archive, select the Replace any version check box in the Upload EAR File dialog box, and upload the archive again.

The specified archive could not be deployed. TIBCO-BW-TEAAGENT-300016: Deployed Application [Application] in AppSpace [AppSpace] of Domain [Domain]. The AppSpace [AppSpace] does not have any AppNodes. The specified AppSpace does not have any associated AppNodes. Click Create AppNodes on the AppNodes page. Select the specified AppSpace in the Create AppNode dialog.
The specified application could not be started. TIBCO-BW-TEAAGENT-500315: Failed to deploy Application from archive [Archive] 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:

  • TIBCO-THOR-FRWK
  • TIBCO-BW-FRWK
  • TIBCO-BW-SR-FRWK

These messages should help you identify the source of the issue. You may need to adjust the logging level for the log file. For more information, see AppNode Logging.

The specified application could not be started. TIBCO-BW-TEAAGENT-500410: Failed to start Application

TIBCO-BW-ADMIN-500313: AppNode [AppNode] is not running or cannot be contacted.

The specified AppSpace may not have associated AppNodes or it might be on a bwagent that is not reachable.

An application can only be started if the specified AppNode is running. Pivot to the AppNodes page and verify the status of AppNodes in the AppSpace. If no AppNodes exist, create at least one and try to start the application again. If the minimum number of AppNodes was specified when the AppSpace was created, that minimum number of AppNodes need to exist.

If the application is on a remote machine, the machine might be down or the bwagent might not be running.

The specified archive could not be deleted. Archive could not be deleted.

TIBCO-BW-ADMIN-500450: Archive [Archive] has been deployed to the AppSpaces: [AppSpaces].

The specified archive has been deployed. Undeploy the archive from the Application Archives page, then click Delete to delete the archive.
The application is not in sync with the archive. The Out of Sync state is displayed for the application Deployment state on the Applications page. Click the Details link to view the reason for the state. The Out of Sync state is displayed when the EAR file is replaced with a new version or a new file of the same version. The software can detect that the application for this archive was already deployed. Redeploy the application to resolve the Out of Sync state.

The following error message can also be displayed for an out of sync situation:

TIBCO-BWTEAAGENT-300015: Uploaded Archive [Archive] in Domain [Domain]. Application deployed in the following AppSpace(s) [AppSpace] is out of sync. Please re-deploy.