You are viewing limited content. For full access, please sign in.

Question

Question

ClientAutomationTools Page Generation

asked on October 15 Show version history

I built a C# script that uses ClientAutomationTools on a dedicated server to generate pages in a repository. Everything is running with perfect stability so far, except it is very slow due to the sheer size of some of the documents and that it has to handle one document at a time. I attempted to run two instances of my application at the same time on different folders, which worked at first, but ran into issues where after a certain point every attempt to generate pages on a document errored out.

 

The error in question: "The RPC server is unavailable. (Exception from HRESULT: 0x800706BA)"

 

The resources on the server this is running from are barely being utilized, but it doesn't appear that we can take advantage of that by running this page generation in a multithreaded approach. Is there any way that we can handle more than one document simultaneously with this programmatic approach other than involving more than one machine?

0 0

Replies

replied on October 20

Hi Brian,

I don't know the answer to your specific question but did want to ask if you'd looked into the native PDF page generation feature of Laserfiche Distributed Computing Cluster (DCC) via the Workflow Schedule PDF Page Generation activity. That's multi-threaded by design. DCC also uses a different library for page gen (Aspose.PDF) than the client and anecdotally has better results on average and seems to handle more PDF edge cases. If you assessed DCC and determined it couldn't meet the needs of the use case, we'd be curious as to why.

Cheers,
Sam

0 0
replied on October 20

Hi Samuel,

 

We were under the understanding that DCC was not an option for a Cloud repository.

0 0
replied on October 21 Show version history

Ah, it's not. The post didn't mention Cloud or have a Cloud topic tag (I just added it). That's always useful context.

1 0
You are not allowed to follow up in this post.

Sign in to reply to this post.