NI TestStand

cancel
Showing results for 
Search instead for 
Did you mean: 

Deployment Utility: No warning about bad source location / Abort with no error

Two things to report. Maybe it's already known but I couldn't find it on the board so maybe this will help someone in the future or the bug(s) will be fixed in a future release.

 

1. I did not get the warning of `Bad source folder` when closing the Drivers and Components dialog. The Include Hardware Configuration from MAX option was selected. I did get the warning when the MAX option was unselected.

 

2. The build process seems to complete (quickly) with no errors except an "Abort" at the end of the log. Make sure that all Installer Source Location have correct paths for all components.

 

Regards,
Pat

 

+++++++++++++++++++++++++++++++++++++++
Starting Analysis
Processing Workspace...
Workspace Processed
Finished Analysis
Building...
8:21 AM
Creating an installer...
Adding files to installer
Validating...
Copying files...
Scanning files...
Updating files...
Build complete successfully.
Done adding files
Preparing to build deployment
Copying products from distributions
Done building deployment
The installer is finished.
Loading product deployment information
The build is finished.
8:21 AM
Aborted
+++++++++++++++++++++++++++++++++++++++

0 Kudos
Message 1 of 15
(5,446 Views)

Pat,

 

which version of TestStand are you talking about?

 

Norbert

Norbert
----------------------------------------------------------------------------------------------------
CEO: What exactly is stopping us from doing this?
Expert: Geometry
Marketing Manager: Just ignore it.
0 Kudos
Message 2 of 15
(5,443 Views)

TestStand 2013 5.1.0.226

 

Always, no err, Never forget to include the software version when reporting a possible bug.  🙂

 

Pat

0 Kudos
Message 3 of 15
(5,440 Views)

Pat,

 

can you provide a simple list of steps on how to reproduce this? Is there anything specific necessary for this?

If so, can you please attach the sources (including workspace and build script)?

 

thanks,

Norbert

Norbert
----------------------------------------------------------------------------------------------------
CEO: What exactly is stopping us from doing this?
Expert: Geometry
Marketing Manager: Just ignore it.
0 Kudos
Message 4 of 15
(5,436 Views)

Note that this is my first attempt at deployment other than the online course which included deployment of a CD Test project so some default paths are laying around in the Deployment utility. So I think this issue is only going to happen on first time deployment after installation from a CD.

 

Steps: I think only the bold steps are important.

Install TestStand from a CD

Create a workspace, project, and sequence

Deploy with these options:

    Mode - Create new Full Development selected, revision left at default (1.0.0)

    System Source - From TestStand Workspace File

    Distributed files- I had a sequence and a DLL in my project

    Installer Options - Create Installer and Install TestStand Engine options selected

        Drivers and Components - Default components selected, Include Hardware ... from MAX selected with a configuration file selected.

        Click on NI TestStand Graph Control and check the Installer Source Location. Mine was "E:" and editable.

        Click Ok. Here is where a warning normally occurs, about a source path not having installation software, but it did not show.

Click Build - Installer was not put in the designated installer folder but image was built

 

Reopen the Driver and Components dialog

    Unselect the Include Hardware ... from MAX option

    Click OK. Now I got a warning about the path having no installer

    I clicked cancel (I think) then looked at my Installer Source Locations, I selected the NI TestStand Graph Control, for no apparent reason, and browsed to a location on my harddrive where the TestStand CD was copied

    The Include Hardware ... from MAX option was reselected

Click Build - Success!

 

Reopen the Driver and Components dialog - NI TestStand Graph Control source path is now disabled and reads "C:\ProgramData\National Instruments\MDF\ProductCache".

So what do I do if I want change the installer source? 🙂 Well, you go to C:\ProgramData\National Instruments\MDF\ProductCache and rename "NI TestStand Graph Control [5.10.226]" to "zzz-NI TestStand Graph Control [5.10.226]", Include Hardware ... from MAX option is selected, and attempt to Build. The Abort at the end of the log is back!

Reopen the Driver and Components dialog and now the NI TestStand Graph Control source path is now enabled for editing! 🙂

 

Do I get a cookie or what!?  You can't eat a Kudo. LOL

Message 5 of 15
(5,430 Views)

Now that I can reproduce this, a simpler way is to first cause this and click Cancel.

 TSa.JPG

 

Then click the MAX option.

 TSb.JPG

 

Click OK and you will not get the warning. To a newb like me it threw me off for a few hours... I need a cookie to heal my wounds caused by distress.  🙂

 

Regards,

Pat

0 Kudos
Message 6 of 15
(5,426 Views)

@PatSpring wrote:

 

Do I get a cookie or what!?  You can't eat a Kudo. LOL


 

Pat, 

 

Whenever you drop by Austin I'll get you a well deserved cookie 🙂

 

- Francisco

 

0 Kudos
Message 7 of 15
(5,421 Views)

Thanks!  Austin, MN or Austin, TX? 🙂     I could do MN, -15F this morning, but TX is a longer walk, but maybe worth it for the warmer temperature!

0 Kudos
Message 8 of 15
(5,417 Views)

Austin, TX, I'm afraid. Cookies and warm climate definitely sound like a tempting combination.

0 Kudos
Message 9 of 15
(5,408 Views)

@PatSpring wrote:
[...]

        Click on NI TestStand Graph Control and check the Installer Source Location. Mine was "E:" and editable.

        Click Ok. Here is where a warning normally occurs, about a source path not having installation software, but it did not show.

[...]

I assume that E: is your DVD drive. Correct?

I don't see this behavior when following your steps, but my source location path points to the complete installer available on a network file server.

For your information: The installer is a "Microsoft Installer". In order to build a new "top-level installer", the tool creating the installer requires elements from the original installer package of all components you want to include.
 One of these elements are the "Merge Modules", which are not installed when you execute the installer itself.

I assume that you haven't the installer package (source location) available and therefore expected the warning.

 

I honestly don't understand the last part of the post as i haven't seen issues when creating the installer.

 

Norbert

Norbert
----------------------------------------------------------------------------------------------------
CEO: What exactly is stopping us from doing this?
Expert: Geometry
Marketing Manager: Just ignore it.
0 Kudos
Message 10 of 15
(5,376 Views)