Dynamic call does not work on standalone PC!

[Intaris]

Well you can see nicely the extra path level (the name of your exe "Application.exe" which is represented internally as a folder) before the relative path even starts.  It's most likely because of this that your dynamic call is not working.

You need to account for this in the exe.

Shane.

[Freelance_LV]

The way it is, the '.exe' in the path is the problem.

If you want to continue to use the dynamic vi reference, strip the path once more after 'current vi path', then remove 'LQM\' in the string constant before 'trunk\

Try this and let us know.

I would also suggest you try the static vi reference. Place a static vi reference on the block digarm from 'Application' funcitons pallete, right click and select Browse for path, select your sub vi that needs to be called. Include the same in the build as 'always included'.

[Norick_17]

Hello

thanks for the suggestions but...

@Freelance LV

I tried to use the static vi reference which is working on the dev. PC but NOT on the standalone PC. There I get the error 1043.

About the dynamic call again. I dont think the .exe path is the problem. I tried to strip path the .exe and the \LQM but it failed again with an error. What I am trying to do is a call to a RELATIVE path meaning the called vi is NOT in the same path as the main vi! I think this is importand.

Main vi path (dev PC):                            C:\temp\test.vi

application.exe path (standalone PC): C:\program Files\LQM\application.exe

Dynamic called vi path:                          C:\LQM\trunk\Application Manager\AP_LQM\Application_Manager AP_LQM.vi

Question: How does the path looks like on my standalone PC to the dynamic called vi now?

[Intaris]

Your code as shown in the image will NOT run the VI.

You can use the property node to get the path of the VI by the way.  And you can use an INVOKE Node to actually run the VI.

Shane.

[Freelance_LV]

Notice that the node used in the latest image is 'Run on Open'.

You should try with 'Run VI' Invoke node.

Even if that does not work, please post your code, with the entire folder strucutre, is possible.

Edit:

Ok ok. now one more question: you have PC1, PC2 and another PC with Win7 and LV 2011 SP1. Right?

the EXE works on two PCs: PC2 and the one with Win7/LV 2011 SP1. Right?

What is the LV version/ RTE version on all the three PCs?

ok.. thats three questions.

[Norick_17]

@Shane

yes your version works - but only on my dev. PC!

@Freelance

PC1: Dev. PC with LV 2011 SP1                                             any version (static or dynamic call) works fine

PC2: standalone PC with LV2009 - LV 2011 SP1               first version with dynamic call works; last version with static call does not work error 1198

PC3. standalone PC with RTE 2011 (latest)                         no version is working; last version with static call with error 1003 again

Here are some printscreens of the build, paths and the vi:

[Intaris]

---

@Norick_17 wrote:

@Shane

yes your version works - but only on my dev. PC!

@Freelance

PC1: Dev. PC with LV 2011 SP1                                             any version (static or dynamic call) works fine

PC2: standalone PC with LV2009 - LV 2011 SP1               first version with dynamic call works; last version with static call does not work error 1198

PC3. standalone PC with RTE 2011 (latest)                         no version is working; last version with static call with error 1003 again

---

Then my reaction would be that it's not the calling of the BI which is giving youheadaches, but the VI itself.

Check just the VI you are trying to load on the target computer and see what happens.

Shane.

[Norick_17]

finally I figured out what the problem caused on the dynamic call. Therefore two issues were involved:

• A different RTE on the standalone PC which was formally used on a different application was still installed and seems to give some troubles on my new application which uses the latest RTE. After deinstalling all application and reinstall the latest RTE it looked much better but I still had some errors...
• Another problem was that the dynamic call to my vi has been running prior I have started my main application. Unfortunately I could not see this because the vi was running in the background. Therefore I always got a "strange" error back when I run my main application. This behaviour was set in the installer settings...!

Now everything works fine on all PC's even with my first code!

Thanks for the help!