NewSubproperty with named type in remote execution

[pwaszkewitz]

Hello,

I have a problem in TestSTand 4.1 with using the NewSubProperty API call on a remote system. I use it to create a StationGlobal on the fly having a named type. The TestStand configuration is identical on both machines and it includes the TypePalette with the named type in question.

When executing the sequence locally on the remote computer (using the standard Operator Interface), it works. When executing it under the remote engine, it gives an error that the type is not known. Other NewSubProperty calls using built-in types work fine.

Any ideas?

Best regards

Peter

[Erik_Crank · Accepted solution]

This is a known problem that will be corrected in a future version of TestStand. The remote engine does not load type palette files so that is why the type is not found. For a workaround you should be able to load the type palettes directly by calling the LoadTypePaletteFilesEx Engine API function in your remote sequence.

[pwaszkewitz]

Took me a while to get back to the machines to set up the test. Suggestion works perfectly, thank you.