Remote Panel / Error 1352

[Gibbi]

Dear Community,

I upgraded a project with use of remote panel calls from LabVIEW 2011 (Windows 7) to a new PC with LabVIEW 2018 SP1 (Windows 10) and can't get it running. I searched a lot of posts, but most of them seem to be relatively old.

 I can't even get the NI example "Remote Panel Methods.lvproj" running with any LabVIEW revision. I tried at least 4 PCs with Windows 10 and also Windows 7 (LabVIEW 2011).  I tried to build the client of the example as an executable and ran the server in the development environment...still not working. The error most time is 1352 "Requested VI is not loaded into memory on the server computer". All of this doesn't make sense in the case of this small example.

I enabled the Webserver, configured the port, enabled access, disabled the firewall, disabled other networking cards...I know that client and server need to have the same LabVIEW revision.

No idea anymore. Can anyone try to get the shipped example running and post his experiences with it?

Thanks a lot!

Nicole

[Gibbi]

Dear All,

I'll answer myself - just to get it documented. I had to adapt the mentioned NI-example on client and server side to get it running.

Server: I added a own Untitled1.vi to the project and called it inside the server code. The method WebSrv.VIAccess gets the value "RPM.lvproj\My Computer\Untitled1.vi".

Client: I changed the VI name to "RPM.lvproj/My Computer/Untitled1.vi"

So it seems to be an issue with slash and backslash - this helped to get the small example running. Hopefully this is also the solution for my larger project.

[Gibbi]

Dear All,

again answering myself to document it.It is funny, to find my own thread while searching the web for help  😉

Now, 2 month later, I moved my client/server architecture to different clients an ran into the same trouble again. So i tried do us the NI-example to get it running and failed. This time, i only had the runtime on client available. My server system ran in november well, with the client I had that time. Now the client had again 1379, 1352, 1349.

After some time playing around with firewall ports i finally added the * to the machine access list in vi-server (additionally to my other pcs that where listed). I accept for my project, that it is tolerable to get unlisted clients connected.