LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

LV 7 web server crashes for certain VI's

I have a relatively large data acqusition application using a number of local variables. I can use the web server to create a version of it embedded in a web page, which will function on my local machine. When I try to subscribe to this page using a machine on my internal network, I get a microsoft error indicating that the application needs to be stopped, and asking if I want to send microsoft an error report. When I close the microsoft window, the html page showing my application immediately closes, though it appears initially for a fraction of a second. I tried the same thing with the LabVIEW "Tank Monitor" example, and it worked fine. Are there coding style suggestions for VI's that are to be published via the web server?
0 Kudos
Message 1 of 2
(2,767 Views)
> I have a relatively large data acqusition application using a number
> of local variables. I can use the web server to create a version of it
> embedded in a web page, which will function on my local machine. When
> I try to subscribe to this page using a machine on my internal
> network, I get a microsoft error indicating that the application needs
> to be stopped, and asking if I want to send microsoft an error report.
> When I close the microsoft window, the html page showing my
> application immediately closes, though it appears initially for a
> fraction of a second. I tried the same thing with the LabVIEW "Tank
> Monitor" example, and it worked fine. Are there coding style
> suggestions for VI's that are to be published via the web server?

If you have
LV on the computer that crashes, you might try to open the
Remote panel into LV instead and see if that works. It might also be
worthwhile trying a different version of web browser, or try Netscape
versus IE.

Once you have those results, if you feel it is a LV problem and not
caused by some flaky verison of a browser, please try to include the VI,
or something similar and file a bug report so that it can be investigated.

In general, most things should work the same, but there are some
exceptions. ActiveX controls do not remote very well, though depending
on what the application is doing and if the control is installed on the
remote computer it will work in some situations. Popup system dialogs
will not work very well. The file dialog for example -- should it show
the files on the remote computer or the server computer? Showing the
server files is a bit of a security issue, so this basically isn't
supported. And finally, you might find some scattered bugs having to d
o
with charts. Keeping their history straight with attribute nodes and
different network connection rates is pretty tricky and there some snags
here and there.

Greg McKaskle
0 Kudos
Message 2 of 2
(2,766 Views)