Custom TestStand UI Cannot Run Remote TestStand Sequence

Updated Apr 27, 2023

Reported In

Software

  • TestStand

Operating System

  • Windows

Issue Details

When I use Windows 7, I can run a remote TestStand sequence from the main TestStand sequence editor, or run the remote TestStand sequence from a custom user/operator interface (built in LabVIEW), and this works fine. 

However, when I use Windows 10, I can run a remote TestStand sequence from the main TestStand sequence editor, but when I try to run the remote TestStand sequence from a custom user/operator interface, I get this error: 

Error code -17850, Access denied. 

Solution

If the custom user/operator interface is built using LabVIEW, then there will be a LabVIEW ini token that enables/disables authentication for DCOM, which enables the application to remote connect as guest without authentication. OLE and DCOM security got improved in Windows 10 vs Windows 7, so the DCOM security would affect remote sequence access from a LabVIEW custom interface. TestStand and its custom interfaces (named TestExec.exe) are all registered with the OS, so they have DCOM authentication. This is an extra step needed for LabVIEW built OIs.
 
  1. Open the custom interface ini file, stored in the same location as the custom interface .exe
  2. Add the line:  ole.AuthnLevel=1
  3. Save and close

Additional Information

This information can be found in the TestStand Reference Manual under DCOM Settings for the Local Computer for Accessing Synchronization Objects Remotely, or in the TestStand help files. 

To ensure that the remote setting are configured correctly, read through these sections of the TestStand user manual:

Other Support Options

Ask the NI Community

Collaborate with other users in our discussion forums



Request Support from an Engineer

A valid service agreement may be required, and support options vary by country.