ULx for LabVIEW Physical Channels Crash

[MrHappyAsthma]

I built a LabVIEW application that uses the ULx for NI LabVIEW library from MCC.  The program works fine, however whenever I build an .exe out of the VI, I get a crash whenever I try to browse for Physical Channels.

To recreate this, I made a stupidly simple test VI that just has a Physical Channels I/O control:

Using the VI, it works as intended.  (I didn't have the module plugged in during this picture, so the list is intentionally blank.  This is expected output.)

Then I simply create a Build Specification and create an EXE out of this VI.  (NOTE:  Both the VI and the EXE are being run on the same computer that has LabVIEW 2013 and the ULx library installed.)

When I run this .exe, it opens fine.  But whenever I click "browse", the program crashes instead of opening that window:

Whenever I click "View Report", this is all I see:

<Version>2.0</Version>
<Autosend>False</Autosend>
<Email>
</Email>
<FileAttached>
</FileAttached>
<Comments>
</Comments>

Anyone have any suggestions as to what I am doing wrong?  I do not do any modification during the Build Specification.  I just set my VI to be the startup VI.  Perhaps I am missing a library? 

I also could not find any information about a similar issue on the MCC website nor on the LabVIEW forums.

[kruiz17]

Hi MrHappyAsthma,

The error that you are getting is very difficult to troubleshoot since it can be caused by multiple reasons. Most common reason includes not having administrator rights on the computer you are running the executable on. Try running the executable as an administrator and also disabling any antivirus software and the firewall on your computer. Let me know if you see any changes. 

Regards, 

K. 

[MrHappyAsthma]

---

@kruiz17 wrote:

Hi MrHappyAsthma,

The error that you are getting is very difficult to troubleshoot since it can be caused by multiple reasons. Most common reason includes not having administrator rights on the computer you are running the executable on. Try running the executable as an administrator and also disabling any antivirus software and the firewall on your computer. Let me know if you see any changes. 

Regards, 

K. 

---

K, thank you for your reply.

Neither disabling firewall nor running as administrator helped with the issue.

Let me know if you have any other suggestions.

[RTSLVU]

Does this error occor only on the target machine?

You still have to install the Measurment Computing drivers and "Instacal" program on the target macnine and setup the device in Instacal before using a LabView program.

Doh! I just reread you origonal post and see you are running it on your development station. 

But I just ran a test and it seems to work fine for me on my development station.

On a target machine without installing the MCC software it does not crash with an Exception Error, but does not run either.

[MrHappyAsthma]

---

@RTSLVU wrote:

Does this error occor only on the target machine?

You still have to install the Measurment Computing drivers and "Instacal" program on the target macnine and setup the device in Instacal before using a LabView program.

Doh! I just reread you origonal post and see you are running it on your development station. 

But I just ran a test and it seems to work fine for me on my development station.

On a target machine without installing the MCC software it does not crash with an Exception Error, but does not run either.

---

For me, it crashes on the development machine ONLY for the exe.  The VI browse works fine.  (Windows 7 - Labview 2013)

On a target machine, it won't run without MCC software.  If i install the drivers, then the exe behaves the same way on that machine as well.  (Windows XP - RTE 2013).

Any clue why it seems to be causing me an issue?  Its odd that it works fine for you in both cases, and works fine for me for the VI.  Somehow I think a path issue occurs when I build the exe.