Invoke Method: Run VI produces error when run as an application

[lippis]

Hello,

I have upgraded from LabView 7.0 to 2009. One test program uses Run VI Invoke Method to start the main UI. On LabView 7.0 it works OK , when build as an application, but with LabView 2009 it gives error 1003: Invoke Node xxx.vi <APPEND> VI Path: xxx. (I have checked that the path to "Open VI Reference" is correct.)

When run on LabView 2009 development environment (.vi) - no problem. I used the "Convert built script.." tool to convert to LabView 2009 built specifications. I have tried numerous different variations building application with LabView 2009 (including main UI files, different setups, etc.), but no luck. If someone has any ideas...

-timo

[J-M]

Did you included the VI in the properties of the executable?

JM

[lippis]

Yes, I sure tried that too - same result.

In the original LabView 7.0 build script there is only the source file that contains Run VI invoke method. In LabView 7.0 the .exe can invoke the other .vi but with LabView 2009 it ends up with an error. There is also .ini file in the same folder as .exe which contains viSearchPath.

-timo

[F._Schubert]

Error 1003 means, that your vi is not executable. Did you already convert it to 2009?

You could check the State of the Vi (There is a property for this) before the invoke note to make sure it the arrow is broken/state -> bad. 

Felix 

[JK1]

There might be a problem while converting between versions and hence the vi is not in executable state [broken vi].  Open the VI to be launched and re-compile the vi.  So that if there are some incompatible dll's or invoke nodes labview will update them and will show broken arrow if there are unresolved errors.

post back for queries.

[F._Schubert]

One more guess, it might be that the dynamically called vi is broken when you build the executable, because it misses some references (e.g. a *.dll). Can you build an executable with the vi you are calling (without the caller)?

Felix 

[lippis]

I have opened the VI to be launched and re-compiled and saved it - it runs OK in development environment. I can build up an executable of the vi I am calling, it builds up, no error messages. It will even start up the main UI, but some functionality doesn't work. It gives an error message that (sub)vi is not executable.

Thank you all for helping me to the right direction!

-timo

[F._Schubert]

Did you check that SubVI in 2009 and saved it? Can you post the error message?

Felix

[F._Schubert]

Maybe it helps you for debugging:

I checked the property for the broken arrow. You need a property node and go Select Class 'Vi Server'->'VI' (skip this in your Application but navigate to the VI via the server and feed it to the node). Then it is Execution->State.

I need to draw some code to do it for me as well, once I'm done I'll post it here.

Felix

[JK1]

While build the application...Check the option "Enable debugging" in application builder.  This will include the block diagram along with the applicaition. this might solve the issue.

post back for queries.