JimBollinger

Laserfiche Workflow to Request Signature Failing

0 votes

I have a workflow that was previously working but is now terminating the workflow with messages "Failed to send documents for signing.  For more details see the logs in the windows event viewer"

The only logs in the event viewer that seem to correspond are in the system logs with an event ID of 10016 and a source of DistributedCOM.  I triggered the workflow twice and this error showed both times:

The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{2593F8B9-4EAF-457C-B68A-50F6B8EA6B54}
 and APPID 
{15C20B67-12E7-4BB6-92BB-7AFF07997402}
 to the user WHEATLANDCOUNTY\lfservice SID (S-1-5-21-989961754-2499879169-1435520219-5632) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.

My setup was previously working in our test environment but today nothing seems to be going through.  I recently rebuild the setup on the production environment but that is using a completely different database and servers.

Is this an error you have seen before?

Thank you for any assistance you can provide.

 

Jim

 


Reply to: Laserfiche Workflow to Request Signature Failing

0 votes

Hi Jim,

 

Thanks for your post!

"Failed to send documents for signing." error happens when the connector failed to send the transaction. So before we dive further into the issue, could you quickly check below:

(1)Does the transaction exist in DRAFT status, if you logged onto your OneSpan Sign UI portal > Transactions > and select DRAFT folder?

(2)What if you retried the suspended workflow? Does it make any difference?

 

Duo

Duo Liang OneSpan Evangelism and Partner Integrations Developer


Reply to: Laserfiche Workflow to Request Signature Failing

0 votes

Hi Duo,

Sorry for the delay, just getting back to this.

 

1. The transaction does show up in DRAFT status on the dashboard.

2. Retrying the suspended workflow ends up suspending again.

 

Jim


Reply to: Laserfiche Workflow to Request Signature Failing

0 votes

Hi Jim,

 

Can I have the package ID of this DRAFT transaction? Package ID is part of the URL.

 

Duo

Duo Liang OneSpan Evangelism and Partner Integrations Developer


Reply to: Laserfiche Workflow to Request Signature Failing

1 votes

I found the issue Duo!

 

Our signing workflow uses tags instead of a template and an update to our forms process was preventing the signing page with the tags from being included in the file being sent to OneSpan.  OneSpan didn't know where the signatures were supposed to go so it saved as draft and couldn't send for signature.

Pointing me towards the draft got me looking in the right direction.

 

Thank you!

 

Jim


Hello! Looks like you're enjoying the discussion, but haven't signed up for an account.

When you create an account, we remember exactly what you've read, so you always come right back where you left off