Failed to start instance SiebelAdapterConfiguration on node
Article ID: KB0081399
Updated On:
| Products | Versions |
|---|---|
| TIBCO ActiveMatrix BusinessWorks Plug-in for Siebel | 6.1.0 |
Description
After the adapter application has been uploaded and deployed, when starting the TIBCO ActiveMatrix Adapter for Siebel, it fails with following error.
“Failed to start instance SiebelAdapterConfiguration on node”
***Sample error***
ERROR c.t.a.m.t.a.s.AdapterStartStopApplicationRemoteInvocable - Exception happened:
java.lang.Exception: Failed to start application on few nodes
Failed to start instance SiebelAdapterConfiguration on node,
at
com.tibco.adapter.management.transport.as.server.AdapterStartStopApplicationRemoteInvocable.invoke(AdapterStartStopApplicationRemoteInvocable.java:183) ~[com.tibco.
adapter.management.domain_1.1.0.015.jar:na]
at com.tibco.as.space.impl.InvocationDispatcher.invokeMember(InvocationDispatcher.java:207) [as-common.jar:na]
Causes:
-This occurs as the Manifest-Version in the properties MANIFEST.MF in the project is not 1. Because when TIBCO Business works generates a component implementation, the component's dependency on the plug-in containing the component implementation is expressed as [1.0.0.qualifier,1.0.0.qualifier].
-Check the status of EMS services.
-Check for the Siebel Server side Configuration.
Environment
Resolution
- Open the project. Go to Properties > MANIFEST.MF
- Change the Manifest-Version to 1 and save.
- Recreate the EAR.
- Deploy and then start.
Also check the EMS status. If the EMS services is not started you may get the above error.
Issue/Introduction
Feedback
