TestStand deployment does not install LabView on WinXp SP1

[Ed Kuzemchak]

I have built a TestStand 3.1 deployment that installs correctly on Windows XP SP2. However, when I install the same deployment on Windows XP SP1, it does not seem to get the LabView runtime installed correctly. LabView does not show up on the Start menu, and attempting to load any .seq files that use .vis lead to an error message about not being able to start the LabView ActiveX server.

Any ideas what could cause this? I found the FAQ about running dcomcnfg.exe, and, of course LabView is not listed as a DCOM application on the Win XP SP1, but it is OK on Win XP SP2. That still doesn't tell me why it isn't loading - it just confirms that it isn't.

Thanks and regards,
Ed Kuzemchak
Software Design Solutions, Inc.

[Odd_Modem]

LabVIEW development system is the only thing that shows up in the start menu; the runtime engine does not have an entry there. Based on your messages I'll bet you have LabVIEW installed on your SP2 machine but not installed on the SP1 machine.

Did you set the LabVIEW module adaptor to use the runtime engine instead of the development system?

[Ed Kuzemchak]

Yes, that was exactly it. I had missed that the WinXP SP2 machine did have the LabView dev system on it.

I've changed the module adapter in my deployment, and am rebuilding. Thanks for the help!

Ed