Server does not support Remote Panels

[Shezaan]

Hello,

It seems that you may have worked with an Applications Engineer regarding this. Did you start encountering this issue when you upgraded to Windows 10? If so, it could be related to a problem with the NI Web Service in Windows 10.  

Regards,

Shezaan Noorani 

Applications Engineer

[Arcus111]

Yes, after no initial help on the forums, we contacted a support engineer. The only recommendation we have received was to change the web server Windows service to automatically restart after a failure. Initially we thought this helped, but we have since had the same problems crop back up and have had to restart the program to fix it.

So, we are expecting that the only real solution is to move all of our LabVIEW web-based projects away from LabVIEW and just implement them using native web protocols. That eliminates any conflicts or problems using the archaic remote front panels. It would be nice if LabVIEW had better support for web UIs. Or better integration opportunities. That would save us a lot of re-implementation, but moving away from LabVIEW brings us closer to open standards and better portability and extensibility. Most of our customers no longer want or need on premises control programs. They want and expect cloud-based solutions.

[rkotrol]

Hey Arcus

So it sounds like you and I have almost the exact same problem.  Remote panels work fine for a certain amount of time and then the server stops accepting requests.  One thing i've noticed is if you disable then enable the remote panel web server, this will clear out the queue and allow for remote connections again.  This can be done by going into options in LabView and clicking on the web server tab.  Another way is to create a simple VI (image attached) that can automate this process for you.  I thought with the latter I found a viable workaround; however, it isn't flawless.  Sometimes if I run that VI, and there is a remote connection, it will lock up labview, resulting in a forced restart of labview.  Most of the time it will just kick the remote client off.  Through this method, i'm able to avoid restarting LV everytime I receive the "server does not support remote panels" error.

After talking to multiple engineers at NI, its obvious remote panels is not their preferred method of web UI.  It'd be nice that, since they still include it as a feature, they would help troubleshoot the problem.  Their only solution for me was to implement web services.  This, to me, isn't a solution as it would result in a wholesale change of our Labview architecture.

As this is an ongoing issue for us, any additional info you've learned through your experience with the error would be greatly received.  Like I said, running the VI that restarts the remote panel service most of the time, but still occasionally locks up.  It would be nice to avoid that occasional lockup.

Regards