shell32.dll call returning error when program moved to new PC

[Steve Morris]

I have a program/executable that has been used on several Windows 10 PCs over the last two  years or so.  We went to set up a new laptop (still Windows 10) and now the attached PrintPDFr1 subvi is returning an error 32.

I am using LV2018 32bit.

I've been in touch with NI support and so far we haven't come to a solution.

We've tried:

1. Adding a copy of shell32.dll to the build of the exe under always included

2. Modifying the subvi to specify the path to shell32.dll in the CLFN

3. Running as administrator

4. Changing the subvi to use the .NET method found here:  Solved: Invoke Print File (Explorer) - NI Community

5.  Using 'FileMan Print File.vi' in winevent.llb in the attached zip file

They all work on my development PC and on a second laptop, but they all fail and generate an error on this new laptop.

Has anyone seen something like this before and/or have any suggested fixes.

Thanks in advance for any input,

Steve

PrintPDFr1.vi _labview_win_util_32.zip

[Rolf Kalbermatter]

37 minutes ago, Steve Morris said:

I have a program/executable that has been used on several Windows 10 PCs over the last two  years or so.  We went to set up a new laptop (still Windows 10) and now the attached PrintPDFr1 subvi is returning an error 32.

I am using LV2018 32bit.

The VI generates the error 32. What code does the ShellExecuteA() function return? That might be giving at least some idea what is going on. Most likely there is no print method registered for the PDF file type.