Hi, thanks for the reply.
You are correct about the functionality of the process. It runs as a SharePoint Timer Job and monitors the "watch" folder for files to combine. As a file is processed, it is copied to the "Running" folder. If the combine succeeds, the file is copied to the "Completed" folder. If any error occurs during the combine process, it is copied to the "Error" folder and the error description is written to the logs.
To get the full stack-trace of the errors, you can modify the NLog configuration settings in the sample's app.config file. Change the following line:
This should indicate where the errors are occurring.
Please read the _readme.txt file to get the sample working. You can replicate the issues by copying the attached sample files to the "watch" folder and running the application. All files should be processed and moved to the "Error" folder with the full tracing/error information in the logs files. If you put a breakpoint in the "combinePDFWithAssociatedFilescombinePDFWithAssociatedFiles" method, you can step through it and see where each of the file combines fail. Depending on the file type, either Aspose.PDF or Aspose.Words causes the errors.
The problem could be that some of the input files are simply corrupt. I can confirm the one of attached .rtf files is corrupt and is not a valid .rtf file. But the other HTML/PDF/TIF files appear to be fine and I cannot see any problem with them.