System Exec.vi - .dll - Problem

[Felix975678]

Hello everybody,

I build up an standalone .exe (not in labview) which I want to start with "System Exec.vi".

First Veristand is getting started in the first sequence without any problem.

In the second sequence the other executable should get startet but an error appears: "MBus-DLL for MBus-Bridge not available"

When I open the .exe by myself it opens without any problem. This means the System Exec.vi has a problem to include all the other

.dll´s (included in the .exe folder) when starting up the executable.

When I use the console CMD the same error appears. So my question:

Is there another option to start an executable without using direct/indirect the console CMD?

Do I have to change some settings in the System Exec.vi?

Thanks for any help...

Cheers

Felix

[Sam_Sharp]

I think your problem is because you need to set the 'working directory' to be the folder containing the executable.

As an alternative to System Exec - I think you can also use a .NET call to start an application - create a System.Diagnostics.Process constructor node (I think that's the name) and then call the 'Start' method - it'll take the path to the executable and any additional arguments you have.

[Felix975678]

Hey,

I tryed this already. To set the working directory to be the folder containing the executable. Doesn´t change anything.

Thanks for the .NET application. I will try this now.

[Felix975678 · Accepted solution]

Fixed the Problem with a vbs Script. Then I used CScrpit.exe to open it. Very simple.