Error creating ITPAM workflow, Could not send flow to queue.

Document ID : KB000005409
Last Modified Date : 14/02/2018
Show Technical Document Details
Issue:

PAM processes are not being triggered from SD when a macro activates it. there is no error in the application, but the stdlogs show errors similar to the following:

02/01 09:45:56.49 SERSRCDPRD01 spelsrvr 16692 ERROR macro.spl 1017 Error creating ITPAM workflow (): Could not send flow to queue.
02/01 09:45:56.49 SERSRCDPRD01 spelsrvr 16692 ERROR bhvtpl.spl 503 bhvtpl::do_behavior() macro '' failed: Could not send flow to queue.

The PAM c2o.log shows errors similar to the following:

2017-02-01 09:45:56,395 INFO [com.optinuity.c2o.persistence.DatabaseManager] [107.145-8082-12] DatabaseManager.retrieveC2ODocumentForExecution: loading: path:/: 
2017-02-01 09:45:56,419 INFO [com.optinuity.c2o.workflowengine.WorkflowManager] [107.145-8082-12] WorkflowManager.loadWorkFlow: Loading the Workflow: /
2017-02-01 09:45:56,419 INFO [com.optinuity.c2o.workflowengine.WorkflowManager] [107.145-8082-12] Creating WorkFlow instance for Workflow /
2017-02-01 09:45:56,428 WARN [org.hibernate.util.JDBCExceptionReporter] [107.145-8082-12] SQL Error: 1105, SQLState: S1000
2017-02-01 09:45:56,428 ERROR [org.hibernate.util.JDBCExceptionReporter] [107.145-8082-12] Could not allocate space for object 'dbo.c2oworkflows'.'PK__c2oworkf__44C2921A7C4F7684' in database 'PAM_RunTime' because the 'PRIMARY' filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup.
2017-02-01 09:45:56,428 ERROR [com.optinuity.c2o.util.C2OSoapRequest] [107.145-8082-12] C2OSoapRequest: WorkFlow can not be instantiated. As It could not be found/authorized or loaded.
2017-02-01 09:45:56,428 ERROR [com.optinuity.c2o.util.C2OSoapRequest] [107.145-8082-12] C2OSoapRequest:could not insert: [com.optinuity.c2o.commandobject.flowchart.C2OWorkFlowInstanceRefObject]
2017-02-01 09:45:56,429 ERROR [com.ca.pam.soap.ExecuteProcessSoapAction] [107.145-8082-12] C2OSoapControllerServlet:C2OSoapController: Could not send flow to queue. Workflow could not be initiated.could not insert: [com.optinuity.c2o.commandobject.flowchart.C2OWorkFlowInstanceRefObject]
2017-02-01 09:45:56,429 ERROR [com.ca.pam.soap.ExecuteProcessSoapAction] [107.145-8082-12] unable to execute SoapRequest
com.optinuity.c2o.util.C2OException: Could not send flow to queue.

Environment:
Service Desk 14.1 or above PAM 4.3 or above
Cause:

PAM database does not have space available to save data and therefore the transaction is lost.  Note the error in the c2o.log:

2017-02-01 09:45:56,428 ERROR [org.hibernate.util.JDBCExceptionReporter] [107.145-8082-12] Could not allocate space for object 'dbo.c2oworkflows'.'PK__c2oworkf__44C2921A7C4F7684' in database 'PAM_RunTime' because the 'PRIMARY' filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup.

Resolution:

Ensure that PAM database has enough space so it can handle the transactions. Verify with the database administrator the log file (ldf) of the database to see if it is possible to shrink it, if possible do the same with the data file (mdf), before attempting this take a backup of the PAM database.

Also please ensure that you are archiving and deleting unnecessary data in the PAM database, PAM consumes many database resources and it needs to be monitored for cases such as this one. The documents bellow also are useful to administer the SQL server database.

Additional Information: