Publishing a VI front panel

[0Forest0]

Hi to all.

I am trying to publish VI front panel using Web server. And with "Web publishing tool" it works well.

But when I compile my application all goes bed.

My main VI looks like this:

VI

1. In "Web publishing tool" I configured the "1.vi" to publish. (I see it in browser when it's opened)

2. In build spesification options I deselect checkbox "Remove front panel" to "1.vi"

3. I think there is something I miss.

My config files looks like this:

Main.ini

[Main]
server.app.propertiesEnabled=True
server.ole.enabled=True
server.tcp.paranoid=True
server.tcp.serviceName="My Computer/VI Server"
server.vi.callsEnabled=True
server.vi.propertiesEnabled=True
WebServer.TcpAccess="c+*"
WebServer.ViAccess="+*"
WebServer.Enabled=True
DebugServerEnabled=False
DebugServerWaitOnLaunch=False

niwebserver.conf 

# Web server configuration file.
# Generated by LabVIEW 17.0.1
# 25.03.2020 12:06:17
WebServer.TcpAccess="c+*"
WebServer.ViAccess="+*"
WebServer.Enabled=True
#
# Global Directives
#
NI.AddLVRouteVars
ErrorLog "$LVSERVER_ROOT/logs/error.log", level=2, anew
AccessLog "/Program Files (x86)/National Instruments/LabVIEW 2017/resource/webserver/logs/error.log", anew
TypesConfig "$LVSERVER_ROOT/mime.types"
LimitWorkers 10
LoadModulePath "$LVSERVER_ROOT/..;$LVSERVER_ROOT/modules;$LVSERVER_ROOT/LVModules"
LoadModule LVAuth lvauthmodule
LoadModule LVSnapshot lvsnapshotmodule
LoadModule LVRFP lvrfpmodule
Listen 80

#
# Directives that apply to the default server
#
NI.ServerName LabVIEW
DocumentRoot "C:/Program Files (x86)/National Instruments/LabVIEW 2017/resource/webserver/../../www"
InactivityTimeout 60
SetConnector netConnector
AddHandler LVAuth
AddHandler LVSnapshot snap
AddHandler LVRFP
AddHandler LVSnapshot
AddHandler fileHandler ""
AddOutputFilter chunkFilter
DirectoryIndex index.html

[wiebe@CARYA]

How does it go bed (bad 😎)?

What do you expect and what do you get?

This could be anything.

My first guess would be a firewall blocking the application, while LabVIEW has access through it. Disable the firewall to check. If it helps, enable it again, and add the exe to the allowed application..

[0Forest0 · Accepted solution]

Thank you for answer.

I have solved all.

I open up some features:

1. Web server options in development system not influence on compiled application. (so we need to configure it in application). I think if we don't wire webserver config file - it will ignore all options in Application.ini file.

2. VI in project has a different path compare with simple VI

3. Compiled application when open VIs by reference, open it in development system if labview is running. (not in runtime)