Problem regaining control and accesing/using MainVI on Server PC

[RealBjörkis]

Hi community and experts,

I have manage to publish an application on a server PC that only has RunTime Enginee (LV 2009 SP1). The Main.vi has an equivalent main.html under C:/Program Files/National instruments/Labview 2009/www/main.html.  I can access the compiled main.vi from a client computer and I can see the message on the server computer that the client PC took control of the VI. That is not the problem. The problem ocurrs when I release control of the VI from the client PC and even close the browser. I see the message on the server PC that the client PC has released control and that server has control, BUT in the server PC I can't click or use anything on the Main.vi. Everything is stuck. If i access the MainVI again from any client PC I can use and click around again but never from the server PC. What could be the problem?

/Björkis

[Gibbi]

Hi Björkis,

did you solve this problem until now? I do have  the same effect as you described, but i am using LabVIEW 8.6.1.

I am looking forward for any idea.

Thanks a lot,

gibbi.

[RealBjörkis]

Hi Gibby,

I haven't solved the problem completely. It doesn't ocurr so often. Perhaps it depends on other PC-configuration factors not related to LV. Anyhiow I made a workaround by giving the client PC the possibility of restarting the server PC if necessary. After restart the server PC gets access to the running LV-program without any problem.

/RealBjörkis

[Gibbi]

Hi Björkis,

thank you for your quick answer. Your workaround seems to be a good idea, but it is unfortunatelly not applicable at my system.

I thought about the source of ths bug, and maybe it is a browser-dependend thing.

Did your clients use firefox or microsoft IE?

I noticed that firefox sometimes does no good job in showing the web-panel, it crashes itself and sometime the application too. Maybe the browser  doesn't release some activeX-stuff in the lower levels of tcp.

gibbi

[RealBjörkis]

Hello!

I have been on vacation and came back today. I have used both Firefox and MS I Explorer and hadn't really thought about it could be browser dependent. I will keep an eye on the behaviour when using the differnt browsers and inform you later.