NI TestStand 2017 suddenly quits when performing a sequence analysis and/or performing a source file analysis in the deployment tool.

[Mal_G.]

If I remove one or two code modules from the sequence, there's no issue. I'm using TS(64-bit). Could this still be a memory issue?

[~jiggawax~]

How many VIs/Sequence Files are in your project that you are trying to analyze?  Do you get any warnings or errors on the output on the Build Status tab?  Even during analysis it is outputting to that tab.

[Mal_G.]

I have a total of nine sequence files in which each sequence file calls a unique .lvproj file that contains a decent number of .vi(s) and it's dependencies including instr.lib, vi.lib, user.lib, Advapi32.dll,and kernel32.dll. Also each .lvproj file has it's own set of objects and TypeDefs. To bring clarity, each sequence file calls a .lvproj that was originally designed to a standalone Labview Test application(.exe). My task in short order is take the these nine apps and sequence them in TestStand. I'm sure there is a lot of redundancy between the .lvproj dependencies that could be causing a problem. 

As far a warnings are concerned, there are no warnings thrown by the build utility or sequence analyzer. It will just quit and disappear off the screen.

[~jiggawax~]

With these kinds of issues I find it best to try and narrow it down by process of elimination.  So start removing stuff until it works or do kind of a binary search where you eliminate half and see if it works.  If so then try the other half. Etc... until you get it to work.

See if you can just analyze a single one of the projects without it crashing?

Is there a reason you need to deploy them all at once?  Why not have 9 installers? 

[~jiggawax~]

Another questions: Are you using a TestStand Workspace?  Or are you just pointed to a directory?

[Mal_G.]

I'm pointed to a workspace file.

[Mal_G.]

In summary after going through the " Process of Elimination" I've found that I can only deploy up to seven tests maximum. I will have to create another installer for the balance of the two remaining tests. The question now, is how to create an installer for the remaining tests that can be called by sequence file in the previous installation.

[~jiggawax~]

Just install them to the same location you were going to before.  It shouldn't matter that 2 installers are putting files in the same folder.  As long as the files aren't named the same.

I think the hairy part of this will depend on how you are deploying your code modules.  You wouldn't be able to put those in the same location if they are sharing any VIs at all.  Then you'll have issues with loading them into memory, amongst other things. 

I'm surprised there was a limitation.  I've seen people deploy upt to 100s of sequence files no problem (not recommended by the way).  My guess is that there is a conflict somewhere and that the limitation isn't the maximum number of tests but rather the right combination of tests.