Open Application Reference (Executable) Error 63 on executable's name change

[ravyh]

Hello everyone,

I cannot figure out the folowing: I have an executable built with these lines in its .ini file: 

server.tcp.enabled=True
server.tcp.port=3369

Openning an application reference to this exe while it's running works fine (from the Development environment). But if I renameme the executable then the Open Application Reference gives error 63. How can I overcome this? Does the VI Server register the application path somewhere at first run or something similar?

Thanks!

[Ben]

Serving a VI in a exe gets complicated and you have to have the right stuff in the ini file. look a the setting in your LabVIEW.ini file for the correct settings.

You also have to know the path of the target VI inside the exe.

A cut-n-paste from an ini file that worked for me is...

___________

[AppName]
server.app.propertiesEnabled=True
server.tcp.acl="290000000A000000010000001D00000003000000010000002A10000000030000000000010000000000"
server.tcp.enabled=True
server.tcp.port=3364
server.tcp.serviceName="Appname"
server.vi.access="+...XXXYYY.vi"
server.vi.propertiesEnabled=True
WebServer.TcpAccess="c+*"
WebServer.ViAccess="+*"
...

____________

If you can get it to work in development and copy the ini settings and get the path straight it should work. The path inside the exe may be your issue. As a quick test show the FP of your target VI and show its path. That should help.

Edit:

The "server.vi.access="+...XXXYYY.vi" in the above cut-n-paste is an edit that you need to replace with the fully qualified names of the target VIs.

Ben

[dan_u · Accepted solution]

If it works with the exe before renaming it, you have to make sure that:

• you rename the .ini file according to the exe
• you adapt the section name in the .ini file to the same name
• if you run both applications (original and renamed) simultaneously you need to use different ports

[ravyh]

Thank you both for replies!

That was a silly mistake: I forgot to rename the section name in the ini (in combination with having the same port set in the development.. which should of course be different)

Thanks.