01-28-2026 02:39 PM - edited 01-28-2026 02:40 PM
Windows, LV2025Q3, 32-bit, development and RTE
Getting an error when repeatedly executing SSH communication via vi.lib\net\SSH\API\Support\Execute SSH Command.vi.
C:\Program Files (x86)\National Instruments\LabVIEW 2025\resource\lvaskpass.exe: lvaskpass_pipe_open_server: ConnectNamedPipe(53fa7c, path=\\.\pipe\LOCAL\lvaskpass.10582E81D20.pipe) failed, GetLastError()=217
C:\Program Files (x86)\National Instruments\LabVIEW 2025\resource\lvaskpass.exe: Failed to open response pipe at \\.\pipe\LOCAL\lvaskpass.10582E81D20.pipe
Permission denied, please try again.
C:\Program Files (x86)\National Instruments\LabVIEW 2025\resource\lvaskpass.exe: open of LVASKPASS_PROMPT_PATH (\\.\pipe\LOCAL\lvaskpass.10582E81D20.prompt) failed
Permission denied, please try again.
C:\Program Files (x86)\National Instruments\LabVIEW 2025\resource\lvaskpass.exe: open of LVASKPASS_PROMPT_PATH (\\.\pipe\LOCAL\lvaskpass.10582E81D20.prompt) failed
user@172.17.15.37: Permission denied (publickey,password).
This executes 30-70 times correctly before encountering this error.
Anyone using this driver successfully?
01-29-2026 10:45 AM - edited 01-29-2026 11:20 AM
After some digging I determined lvaskpass.exe simply returns the password I specified when calling the driver: my workaround is to replace the exe with one that uses a mechanism I control to determine the password. YMMV.
Edit: this also resolves the problem I was originally working on which is in LabVIEW 2023 this driver has issues when running multiple app instances with similar lvaskpass errors. This new error relating to named pipes may indicate the cause was pipe name collisions.