Troubleshooting
Problem
IBM Tivoli Service Automation Manager (TSAM) projects can be registered and get approved, but then go into “In Progress” state and remain there indefinitely.
Symptom
You are unable to create projects which provision virtual servers from within TSAM 7.2 in Cloudburst 1.2.
Projects would register and get approved but then go into “In Progress” state and remain there indefinitely.
You can perform other tasks not related to the management plan.
You may also see an exception similar to the following in the SystemOut.log file located at WAS_HOME\profiles\ctgAppSrv01\logs\MXServer\SystemOut.log
- Windows system example might look like: C:\Program Files\IBM\WebSphere\ctgAppSrv01\log\MXServer\SystemOut.log.
- UNIX system example might look like: /opt/IBM/WebSphere/AppServer/profiles/ctgAppSrv01/logs/MXServer/SystemOut.log.
<log start>
[1/8/10 11:44:13:819 EST] 00000041 SystemOut O 08 Jan 2010
11:44:13:819 [ERROR] Failed to execute action on escalation:
{PMZHBCCOWFE} reference point: {21} for object {PMZHBWLSWO} with id
{397}
psdi.util.MXSystemException: BMXAA3761E - Failed to fire the event.
null
at psdi.server.event.EventTopic.eventAction(EventTopic.java:317)
at
psdi.server.event.EventTopicTree.genericSubsAction(EventTopicTree.java:1
116)
at
psdi.server.event.EventTopicTree.eventAction(EventTopicTree.java:520)
at psdi.mbo.StatefulMbo.fireEvent(StatefulMbo.java:762)
at psdi.mbo.MboSet.fireEventsAfterDB(MboSet.java:6970)
at
psdi.txn.MXTransactionImpl.fireEventsAfterDB(MXTransactionImpl.java:457)
at
psdi.txn.MXTransactionImpl.saveTransaction(MXTransactionImpl.java:235)
at
psdi.txn.MXTransactionImpl.saveTransaction(MXTransactionImpl.java:239)
at
psdi.txn.MXTransactionImpl.saveTransaction(MXTransactionImpl.java:239)
at
psdi.txn.MXTransactionImpl.saveTransaction(MXTransactionImpl.java:239)
at psdi.txn.MXTransactionImpl.save(MXTransactionImpl.java:162)
at psdi.mbo.MboSet.save(MboSet.java:6583)
at psdi.mbo.MboSet.save(MboSet.java:6524)
at
psdi.app.escalation.engine.EscalationTask.executeAction(EscalationTask.j
ava:1080)
at
psdi.app.escalation.engine.EscalationTask.executeActions(EscalationTask.
java:1001)
at
psdi.app.escalation.engine.EscalationTask.executeReferencePoint(Escalati
onTask.java:556)
at
psdi.app.escalation.engine.EscalationTask.processReferencePoint(Escalati
onTask.java:466)
at
psdi.app.escalation.engine.EscalationTask.performTask(EscalationTask.jav
a:148)
at
psdi.app.escalation.engine.EscalationCronTask.cronAction(EscalationCronT
ask.java:45)
at
psdi.server.CronTaskManager.callCronMethod(CronTaskManager.java:1549)
at psdi.server.CronTaskManager.access$400(CronTaskManager.java:83)
at
psdi.server.CronTaskManager$CronThread.run(CronTaskManager.java:2067)
Caused by:
java.lang.NullPointerException
at psdi.workflow.WFInstance.getCurrentNode(WFInstance.java:255)
at psdi.workflow.WFInstance.waitComplete(WFInstance.java:288)
at
com.ibm.ism.pmzhb.was.mbo.LandscapeWorkorderStatusChangeListener.continu
eWorkflowInstance(LandscapeWorkorderStatusChangeListener.java:410)
at
com.ibm.ism.pmzhb.was.mbo.LandscapeWorkorderStatusChangeListener.managem
entPlanCompleted(LandscapeWorkorderStatusChangeListener.java:220)
at
com.ibm.ism.pmzhb.was.mbo.LandscapeWorkorderStatusChangeListener.eventAc
tion(LandscapeWorkorderStatusChangeListener.java:144)
at
psdi.server.event.EventTopic$Subscription.eventAction(EventTopic.java:67
5)
at psdi.server.event.EventTopic.eventAction(EventTopic.java:288)
... 21 more
<log end>
Resolving The Problem
To resolve this problem, perform the following steps:
- Go to TSAM (Web 2.0) view of projects and find project(s) with "Decommissioning" state:
click image to enlarge
- View and go to the problematic project
- Login to the TSAM Maximo interface
- Service Automation > Service Deployment Instances
- Find the Decommissioining instance(s)
click image to enlarge
- Drill down into the Service Deployment Instance
- Select the arrow in the Workorder Num column
- Go to IT Service
click image to enlarge
click image to enlarge
- From IT Topology Work Orders, pause the execution:
click image to enlarge
Workflows will get created in TPM and start to run.
[{"Product":{"code":"SSFG5E","label":"Tivoli Service Automation Manager"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"General Information","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF016","label":"Linux"},{"code":"PF033","label":"Windows"}],"Version":"7.2;7.2.0.1;7.2.2;7.2.3;7.2.4","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}},{"Product":{"code":"SSWMQW","label":"IBM CloudBurst"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":" ","Platform":[{"code":"","label":""}],"Version":"","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Was this topic helpful?
Document Information
Modified date:
17 June 2018
UID
swg21418044