Server RPC unavailabe using Report Generation Toolkit (Excel)

[michele.santucci]

I'm refactoring a LabView 2013 32bit procedure that uses Report Generation Toolkit for Microsoft Office.

I'm creating an executable and distribute the application trough an installer (everything generated trough the application builder toolkit).

I'm using LabView 2013 32bit on a Windows 11 machine with Office 365, report toolkit 2013... everything work flawlessly both running it as source code or building and executiing the binary.

I'm trying to deploy this application on different computers and everything seems to work correctly until I try to generate a report. The target computer is running Windows 10, Microsoft Office 365 etc. in this case the application stops working and no report file is created.

Running the application on the same machine by source code reveals that the error is in NI_Excel.lvclass and specifically on the "Automation Open Function" call ... probing parameters I found that Excel._Application is 0 (it doesn't seems correct of course).

I've a strong suspect that this labview installation could have been corrupted in some way and I will probably need to reinstall it, but I would like to know if there are any other options to try to fix this error (I already tried repairing the report toolkit).

[ZYOng]

Few red flags here:

• LabVIEW 2013 is not officially supported in Windows 10 and 11. Although many users have used unsupported LabVIEW version without issue, but it is not guaranteed.
• Most importantly, Installers and executables are only guaranteed to work on the operating system they are built on. See Running Executables or Installers on Different Windows Versions. You should use Windows 10 to build your executable.

[michele.santucci]

I'm currently using LabView 2013 on both Windows 10 and Windows 11 without problems but of course I got the point.

I could also agree on the binding between build/run Windows version ... but the issue is also present running it as source code and just on this Windows 10 machine. 

[michele.santucci]

Same problem found also building the installer on Windows 10 and running/installing it on Windows 10.