remote control the connection with the server is broken

[andcell]

I'm using Web Publishing Tool and I have create an HTML page with an embedded VI. I saved it in LV Web Server's root directory as described in the help.
When i want to connect from another PC to my application via browser MS Internet Explorer, the application is loaded correctly to the page, but after 10-15 seconds the connection is broken and in the page appear this message: "the connection with the server is broken". If i create the web page with "request control" enabled, then when i connect to the VI, the connection is stable as soon as i release the control of VI from the browser, after some seconds, the connection crash. I'm working with LV7.0.
The CPU usage of my application is very very low on the computer
server (a P4 2.4GHz)
What's happened?

[AlessioD]

Hi,
I guess you are using a while loop without any timing function in it. If so, just add a WaitUntilNextMsMultiple with a constant of 10 ms or so and the problem should not appear anymore.
hope this helps,

AlessioD
National Instruments

[andcell]

Dear AlessioD,
Thank you for reply.
In my vi there 3 while loop, but with a timing very very slow (about 250ms for each). I'm working with an OPC server and i acquire about 30 digital signals per quarter of second. (very quiet routine). In the front panel i have load 4 pictures from 4 bmp files for an amount of about 800Kb of bmp images. When i load the vi from remote computer the size of the application is about 2500Kb because i have any other small pictures.
Thanks,
Andrea

[AlessioD]

I suggest you get in touch with one of our Applications Engineer by calling this number
02.41.30.92.17
so that we can try and look at your code.

Regards,
AlessioD
National Instruments

[Marijn]

I was having the same problem. My VI runs fine locally, but when I take the control remotely, I get this message "The connection with the server is broken" after a while (sometimes a few seconds, sometimes say 1 minute). I tried to make the delays of the loops higher, but it does not seem to help. Once the VI reported a fatal internal error in "image.cpp" line 12313, but I don't know if it has something to do with it.  Any suggestions or hints?

Thanks,

Marijn