server does not support remote panels, server overwhelmed

[rkotrol]

After an unknown amount of connections to remote panels, I recieve the "server does not support remote panels" error.  Often times it will further say server is overwhelmed.  It seems like sometimes we can have almost 100 succesful connections without the error and sometimes just only 10.  

Ive combed over all other similar posts regarding this error and most others seem to have an issue with the initial connection, not after numerous succesful connections. 

This error can be resolved by restarting labview; however, restarting means interupting some physical processes that are running in our warehouse.  Is there a way to locate and empty this log that appears to be overwhelming the server?

[kevins33]

Hi rkotrol,

What development environment are you using? What version? Also, what hardware are you using? Is there anything that causes these error messages, or are they seemingly random? Please reference the below KnowledgeBase for information on how to resolve this error message.

"Server Does Not Support Remote Panels" Error When Connecting to a Remote Front Panel

http://digital.ni.com/public.nsf/allkb/C23EF1551D8C52ED86256B140073EE2E

[rkotrol]

Thanks for the reply.

Using Labview 2013 Full Development on windows server 2008.  IO communication done through compact field point modules.  All remote computers used to access remote VIs have been loaded with the correct runtime engine.  The issue seems to happen on the server end because once it happens, all remote computers get the same message, instead of one isolated computer having an issue. 

There doesn't really seem to be a pattern to this error occuring(to my knowledge).  Sometimes we can go a week or two without seeing it, other times, a few days.  We upgraded to labview 2013 and the new server almost a year ago.  This error didn't start happening until after about 4 or so months of use. 

I came across this knowledgebase earlier this week and have verified that all of our settings are correct.

Thanks again for the reply!

[kevins33]

How many computers are communicating with the server?

[rkotrol]

During regular work hours, just two; however, periodically, a few more non local network computers could be accessing the http site from home via WAN IP address.  

[BoKnows]

Everything worked for four months.  Did anything in the system change around this point?  Did we change computers?  Did we modify the code?  Did the system just sit there operating as normal before one day complaining?

[rkotrol]

Nothing has been changed since the transfer to the new server and labview 2013.  The system sat and operated normally- much to our surpise- until one day that error popped up.  When it started to occur more often, I created a log file from labview options menu to see if I could see a pattern in the frequency of remote connections before the error- I didn't really see one.

Could it be one particular VI that is triggering this?  The remote computers access a index.html page that then has 20+ links to different VIs.  I only get that error inside the iframe that is trying to access the link to the VI.  The rest of the index.html page still displays all of the different links.  I suppose that could just be because index page is stored in the computers cache.

[BoKnows]

Is anything else running on this network?  Traffic that is not related to this server but takes place on the network can bog things down and contribute to this error.

When we say nothing has changed, we are including web browers, firewall, and traffic or are we talking about NI software and the server's hardware?

If a single VI is triggering this, it would be due to absorbing more resources than others.  

[rkotrol]

The same network we use for remote panels is the same local network for up to 10 computers, a printer, and other miscellaneous hardware you'd find in the office; however, the only thing that communicates with this particular server is our NI hardware and Labview.  We use a different server for file sharing. 

Regarding changes, everything from firewall, web browser, all software, remained the same.

Our IO hardware is really outdated.  Is it even possible for that to be a contributing factor?

[rkotrol]

One thing I did just come across: Undder the Web Services options menu, I noticed debugging port is sharing the same as the http port.  Do these need to be different?  Is this even something that would cause the server not supporting remote panels error?