"Attempted to load a module for a step whose module has yet been specified"

[ChevyVolt1]

I have been working with TestStand sequences for a short while now. I keep on running into the "Attempted to load a module for a step whose module has yet been specified" error when hitting F5 (Run/Restart), but when I run the exact same sequence's using Execute -> Run Main Sequence, it works.  I've been using that for a while, but time is coming up soon when I need to run the full sequence that includes setup and cleanup, and I'd like to address this issue. 

Attached is the sample file that errors out. It only does message pop ups.  I have complex sequences that fail as well with the same error.  If it does not error out for you, it definitely is a configuration issue on my end, but for the life of me, I can't find the answer in this forum or elsewhere.  I even tried a couple seq files found in this forum (a couple by jigg) for posts with the same issue as mine - and these too failed.

I'm using TestStand 2017.

Thanks

[~jiggawax~]

So a lot goes on when you hit F5.  Do you use a custom process model?  Do you use Station Callbacks?  Do you use custom Plugins? 

These are the 3 sequence files that come to mind that could potentially have steps with modules that aren't set.

This error occurs whenever you are using an adapter step and don't specify a module on the module tab.  Could be a LabVIEW, .NET, ActiveX, Sequence, etc... adapter.

Basically when you kick off an execution, TestStand tries to load all of the sequences, and their modules, into memory.  If it sees a step without a module specified it will throw the warning.

For troubleshooting you can disable all result recording.  If it still happens then it is most likely in the process model.

Does it occur if you click Execute>>Single Pass?  If so then it is most likely in the Test UUTs entry point.  If not then it could be elsewhere in the process model.

Hope this helps,

[ChevyVolt1]

Jigg,

I just did:

1. File -> New -> New Sequence

2. Drag-n-drop "Message Popup" into the Main sequence

3. Change message Expression to "foo"

4. Save

5. F5.  That module message pops up.

There's no "Execute -> Single Pass" option in TS 2017. 

[~jiggawax~ · Accepted solution]

Are you in the sequence editor?

Single Pass is in your process model.  Has nothing to do with the version of TestStand. The default process model in TS 2017 definitely has a single pass.  I'm looking at it right now.

Which process model are you using?  Go to Configure>>Station Options and click on the Model tab.  What is your Station Model set to?  Open that file and run the sequence analyzer.  It will tell you which step is missing the module specification.

[ChevyVolt1]

Open Configure -> Station Options -> Model Tab's sequence

Run Debug -> Sequence Analyzer -> Analyze <sequence>

In my case, there was a missing custom DLL file that the sequence can't find.  I'm trying to find the 64 bit dll now and will retry with that present.  If I still have issues, I'll come back and follow up.

Thanks, Jigg!