Labview application not working on certain PCs with WinXP

[Rohit_Chawla]

I made an application in LV2012 which works fine on Win7 PCs.

However when I install it on my client's PC which has WinXP SP3, it doesnot work.

I even installed the latest DOTNET framework and separately installed LV Runtime and VISA 5.20 runtime.

But still it gives me an error "This is not a valid Labview Executable.

Any suggestions ?

Labview should have a small utility which runs on the target PC and checks if the system configuration is suited for a Labview App deployment.

[Craig_]

Can you enable debugging on the executable and connect to it from the development machine? This will download the VIs from the target system and you should be able to look through them normally for problems.

[Rohit_Chawla]

Wow.... Can it be done ? How do I do it ?

Sorry for acting like a newbie. I am a newbie infact.

[Rohit_Chawla]

I am not sure if I specified well enough, the target PC is doesnot have a Labview Development System.

I am deploying my EXE to that system.

Also I have no physical access to it.

Its about 2000 Kms from my office and I am trying to help them with a Remote VNC like TEAMVIEWER.

What will I see in the debugging screen ?

[Craig_]

Sorry on my phone so I neglected to post a link!

http://digital.ni.com/public.nsf/allkb/8DA679805915DE40862572D5007B2F70

[Rohit_Chawla]

Wow this really sounds great. Thanks for the link Craig.

One doubt though. My original problem is that my application is not running (see my error screenshot).

So if the app doesnot start and says that its not a valid executable, will remote debugging work ? 

My best guess is that the app should work for debugging to work.

What's your take on this ?

[Craig_]

You should be able to connect to it in the same manner even if it shows as broken.

While you cannot see the error list window that comes up when you press on the broken run arrow in development you can search through subvis to figure out what is broken.

[rolfk]

Does your application happen to interface to any external components like shared libraries (DLLs) or ActiveX or .Net assemblies? In that case you have to make sure that the entire external component indcluding all its dependencies is correctly installed. LabVIEW can't know what your external components dependencies are and therefore can't help you by including them automagically in an executable.