How to set the "Timeout" feature in "doc2any.exe" executable?

We are using "Doc to any convertor" 4 licenses. We are using ASP.Net/C# application to call "doc2any.exe" executable file.

We are looking for following help:
1) How to set the "Timeout" feature in "doc2any.exe" executable?
2) How to catch the exception from "doc2any.exe" executable?
3) How to kill the particular conversion process (which is running on "doc2any.exe" executable)? On exception, the entire conversion is getting stopped. So the next conversion from the queue is not happening.

This is very CRITICAL issues, as we got stuck and our conversion is failing big time.

Below is the sample code:

Process lsProcess = new Process();
lsProcess.StartInfo.UseShellExecute = false;
lsProcess.StartInfo.RedirectStandardOutput = true;
lsProcess.StartInfo.CreateNoWindow = true;
lsProcess.StartInfo.RedirectStandardError = true;
lsProcess.StartInfo.FileName = "D:\doc2any\doc2any_service\docPrint_client.exe";
string lsDOC2AnyExePath = ConfigurationManager.AppSettings["DOC2Any"].ToString();
lsProcess.StartInfo.Arguments = " nowait D:\doc2any\doc2any.exe -$ LICENSEKEY \\\e$\BOTTOM.PPTX \\\e$\BOTTOM.PDF"


We have created a new version of doc2any.exe to you today, please download the new version from following URL,

The new version of doc2any.exe is support "-killoffice" and "-timeoutkillself" parameters, you can use these parameters to kill MS Office and itself after timeout,

-killoffice <int> : Kill or not kill MS Office instances before conversion
-timeoutkillself <int> : specify a timeout to avoid hanging doc2any process, in millisecond

You can run following command line to kill MS Office (WINWORD.EXE, POWERPNT.EXE, EXCEL.EXE) and doc2any.exe process itself after timeout,

doc2any.exe -killoffice 1 -timeoutkillself 60000 "D:\downloads\password_test.docx" "D:\downloads\password_test.pdf"


VN:F [1.9.20_1166]
Rating: 10.0/10 (1 vote cast)
VN:F [1.9.20_1166]
Rating: 0 (from 0 votes)
How to set the "Timeout" feature in "doc2any.exe" executable?, 10.0 out of 10 based on 1 rating

Related Posts

Leave a Reply

Your email address will not be published. Required fields are marked *

Verify Code   If you cannot see the CheckCode image,please refresh the page again!