Convert to PDF not functioning correctly.

Have seen the same issue on M-Files 2018 and tried the same measures with little success. However, after having run the Convert to PDF process on a Word document, I was able to do the same on Excel documents afterwards. Weird, but nevertheless a way get going....

This did not work for me.

Hi Seanl,

If you have an active support and maintenance agreement then I suggest you contact your reseller and/or support@m-files.com to diagnose this further.

Regards,

Craig.

In the long run it doesn't work for me either, nor does it for my client. We have a support case open. Will let you know when they have a solution.
You might still want to open your own case just to let them know it is more than a single PC / customer issue.

I've logged a support ticket too. I'll post any feedback I receive

Support was not able to recreate the problem. We tested a bit on my computer:
1) If Excel is or has been started before the attempt to convert to PDF, the procedure completes successfully.
2) If logged on to the PC with a different Windows user account, the procedure completes successfully.
It appears that the error is related to some sort of corruption in the Windows profile on your computer.
The hard way would be to create a new user account and copy everything but Ntuser.dat, Ntuser.dat.log and Ntuser.ini to the new profile.
Hoping that someone can come up with an easier solution....?
For now I would recommend that you makes sure to start Excel before you attempt to convert xls(x) documents to PDF.

Having excel open does not help in our case. I received notification back on our case (Below is response from M-Files):

"After testing and getting some logs of the test, I found out this is a known issue that came along with M-Files 2015.3.
This is a client-side issue. We've noted our R&D about this bug.
We do apologies of the issues this could cause to you.
Most likely this will be fixed during the product development. "

so basically we are stuffed.

As a temporary workaround you could create a new workflow and use the state action "Convert to PDF format" to do the conversion. Workflow actions are executed on the server so they are not affected by any client-side issues.

Went through all the trouble of creating a new Windows account and getting everything set up according to my wishes again. It solved the problem at first, but it came back. So that is not a solution either!

@Joonas
The workflow works fine for the first conversion. Our users like the option of the 'Create a separate file), which basically creates a Multifile document with the original file and the new PDF. The problem is that they add a few other supporting documents to this multifile doc, and if you run the workflow again, it basically targets the multifile doc (so all documents in the multifile are converted to pdf, and not a specific doc inside the multifile doc). Not sure if there is a way to target only a specific file in the multifile doc?

@Bright-ideas
M-Files support also confirmed that the issue seems to lie with the 3rd party app (PDF Exchange), so reinstalling wont necessarily work. It is however a little peculiar, that we have pc/laptops preset with all the software, and one will work fine, and the other not. I can however state that this has only become a problem since Windows 10 build 1703 or 1709. Are you finding a similar result?