Exe Not Executing

[Novatronics]

My exe program works when I am logged in but does not work for other users.  On the computer I gave all rights to the executable but they do not have access to the source code VI’s.  This should work since I am compiling it but it does not and I was wandering if it was because so VI’s call dll’s.

How do I solve the problem?  I do not want my source code available to others.

I have included the error pasted into work and one of the VI’s that cause the problem (AerAxisMove.vi within llb).

Thank you for any support.

Paul

[Robst]

HI:

I suppose the problem must come from the LabVIEW Run-time engine installation. In which platform are you running LabVIEW??. Which LabVIEW version are you running?  I run on Windows XP and haven´t experienced problems like that, but don't know what is your case.  Maybe the LabVIEW Run-time engine is not installed properly and the users cannot access it. Try installing the Run-time engine in the session of each user that must run the executables. Code sharing must not be necesary. Please feedback to see if this worked or what else can we do.

Regards.

[Novatronics]

The problem is not with the run time engine because other programs work fine on the computer.  I only ran into this problem with this new software that uses dll’s embedded into the vi that I previously posted.  It seems like the exe still need the vi (like a dynamic vi) but even with the vi on the c drive with rights to everyone it still does not work but the error points to the vi.

I am using LabVIEW 7.1 on XP profession.  The computer has lots of memory and is a 3.2 GHz processor.

Thanks for your support.

[Robst]

Hi:

Ok, that problem sounds quite strange. It would be helpful if you could upload the VI or the library that's generating the problem. It seems that you haven't uploaded it, since I can't see the attachments. And if it coud be in LabVIEW 7.0 version, even better.

Robst.

[Novatronics]

Attached is the library I am having troubles with and the error message pasted into Word.

[Robst]

Hi:

I've checked out the VI that's causing the problem and I can infer the following: The VI attempts to call the dll "A32sys.dll", and it can't find it. That's why the error is shown.  One of this three strategies may work to fix this. Try them secuentially.

- 1. Right click the Call Library Function Node and select "Configure..." in the pop-up menu. In the Library Name of Path Field type the Absolute Path of the DLL, for example "C:\Development\Motion\A32sys.dll". Build the application and check if it works.

- 2. When you build the application into an Stand Alone EXE go to the Source File tabs and click the "Add Support File..." button. Select the DLL. Configure anything else you need and build the application and check if this solves the problem.

- 3. Copy the DLL to the same directory of the .EXE or to the C:\Windows\System32 dir.

Regards.

Robst

[Novatronics]

It turns out that the hardware I am using starts a back ground server to monitor the equipment and the dll does not fuction without the server.  I had to change the computer configuration to start the server on bootup that way avoiding the windows conflict that only aloud administrators on the computer to start the server.

Thanks for all the support.
Paul