07-15-2024 03:17 PM
When I try to upload a file to the systemlink server using the LabVIEW SystemLink API, I get the following error. I am using a self signed cert on the server. This exact same API call to upload a file works on 2 other machines and I did not configure anything special on those machines. Any idea why this would fail? The screenshot below shows that I am connected to the server and I am just calling a very basic send file API call to upload a file. The weird thing is that I can "GET" all file information from the system link server using the LABVIEW API (which tells me I am connected) I just cant upload.
I am also able to publish all results and upload file via teststand on this machine so it appears to be very specific to the LabVIEW API call to send the file. The motivation to use this LabVIEW API call instead of the default teststand upload file step is because I sometimes get a timeout when uploading large files and since teststand does not expose a timeout for this step. If there is some other way to increase the timeout for the teststand upload step this would also work.
Thanks for any help!
07-15-2024 04:38 PM
Ensure you have a valid SSL certificate on the server side i.e., HTTPS.
If using self-signed SSL, ensure you set Verify to false in the LV APIs.
07-15-2024 05:31 PM
santo_13, I already tried that and it makes no difference. The server has a self signed cert.
07-15-2024 07:34 PM
@jdkdev wrote:
santo_13, I already tried that and it makes no difference. The server has a self signed cert.
To confirm, you experienced this error even when set Verify to False as in the below diagram?
07-16-2024 12:45 PM
Hi Santo,
Thanks for your quick responses here! Yes that's right, I have tried running the exact code you have pasted and I still get the same error. It seems like a bug if the send file VI still says it cant verify the authenticity of the server even when I explicitly ask it to not verify the cert. As I was saying though, I have 2 other test systems in use that are successfully able to upload files to the server with no errors. And on those system I don't even call the Open Configuration VI, I just call the send file VI with the file and it works as expected.
07-16-2024 04:31 PM
As a quick check, disconnect the SystemLink client from the server and reconnect it, this should refresh the authentication configurations.
I recommend stepping into the Upload File to find the root cause of this error and see if it is a bug.
Please ensure you are using the latest SystemLink client and APIs.