Cannot run LabVIEW executable over Remote Desktop Connection

[wildcatherder]

I have a couple of executables, which were compiled using LabVIEW 2011 Development System, installed on a WinXP laptop computer.  These programs run fine when I double-click on the icon while seated at the computer.

If I log onto the laptop remotely from another Windows XP machine using Remote Desktop Connection, I can operate the remote computer normally except for the LabVIEW executables. 

When I double-click on either one, I get the error message displayed in the attached file. The text portion of the report has no useful information, just two lines which appear to be field names for email.

What gives?

Remote debugging is not a good substitute because it requires the executable to already be running.

[smercurio_fc]

What version of RDC do you have installed? You could try to run RDC in "admin" mode to see if that makes any difference. You can do so from the Start -> Run and enter "mstsc.exe /admin" in the Run command dialog.

P.S. You spelled fludization incorrectly. Only one "L".

[wildcatherder]

Thanks, I'll give it a try.  Typos are everywhere. You spelled "fluidization" incorrectly; it has two "i"s.

[wildcatherder]

Sorry, three "i"s.

[wildcatherder]

Thanks, I have changed the spelling for the next compilation.

I tried using Remote Desktop Connection with the admin startup you suggested but still get the same error.

The version I am using is Shell Version 6.0.6001,  Control Version 6.0.001

[wildcatherder]

Typos ARE everywhere.  Should be:

Shell Version 6.0.6001

Control Version 6.0.6001

[smercurio_fc]

---

@wildcatherder wrote:

Thanks, I'll give it a try.  Typos are everywhere. You spelled "fluidization" incorrectly; it has two "i"s.

---

Ha! Good show!

---

Thanks, I have changed the spelling for the next compilation.

I tried using Remote Desktop Connection with the admin startup you suggested but still get the same error.

The version I am using is Shell Version 6.0.6001,  Control Version 6.0.001

---

Does this happen with just these two applications, or any LabVIEW executable that you build? If it happens with just these two apps, then the question is what are these two apps doing?

[smercurio_fc]

Thanks, I have changed the spelling for the next compilation.

I tried using Remote Desktop Connection with the admin startup you suggested but still get the same error.

The version I am using is Shell Version 6.0.6001,  Control Version 6.0.001

[wildcatherder]

These are the only two apps I've built in months.  Programming is just one of my jobs.  I have a feeling this is something LabVIEW has done as a security measure (reaction to Stuxnet?).  The other app just opens a file, allows you to change the values onscreen and writes them back.  So, nothing fancy.

[wildcatherder]

It appears to be a case of too few resources on the host machine.  

The WinXP is running as a virtual machine on a MacBookPro.  I can only allocate 768MB of RAM which is very likely not enough to support both the Remote Desktop Client and the LabVIEW executable. I will have a machine with more resources available next week and be able to confirm this.

I do appreciate the help I have been offered.  It appears to be a Windows problem and not a LabVIEW problem.

[wildcatherder · Accepted solution]

I have been able to run both LabVIEW executables over Remote Desktop Connection to a Windows 7 virtual machine with 2GB of RAM, operating on a MacBookPro utilizing Parallels for Desktop.

This confirms that the problem was insufficent memory resources.