Hi,
cRIO: LabVIEW 2020, NI Linux image 20.5
Systemlink: 2023 Q3
We have 8 cRIOs running 24/7, with tags and tdms files being pushed to Systemlink.
Over the weekend, we had an issue after midnight. The cRIO rebooted itself via watchdog.
When we started back up, we got this error:
{"status":true;
"code":-251042;
"source":"NI Skyline Utilities.lvlib:Parse HTTP Error.vi:5080001<ERR>\nThe web server responded with error 401 Unauthorized.\n\n\n<b>
Response body:</b>\n<!DOCTYPE HTML PUBLIC \"-//IETF//DTD HTML 2.0//EN\">\n<html><head>\n<title>401 Unauthorized</title>\n</head><body>\n<h1>Unauthorized</h1>\n<p>This server could not verify that you\nare authorized to access the document\nrequested. Either you supplied the wrong\ncredentials (e.g.; bad password); or your\nbrowser doesn't understand how to supply\nthe credentials required.</p>\n</body></html>\n\n\n\n<b>
Complete call chain:</b>\n NI Skyline Utilities.lvlib:Parse HTTP Error.vi:5080001\n NI Skyline Utilities.lvlib:Execute HTTP Verb.vi:7500001\n NI Skyline Tag HTTP Library.lvlib:Multi Write Core.vi:5310001\n NI Skyline Tag HTTP Library.lvlib:Multi Write.vi:4780001\n NI Skyline Tag HTTP.lvclass:Multi Write HTTP 2.vi:1870001\n NI Skyline Tag.lvclass:Multi Write 2.vi:6740001\n SystemLink.lvlib:Write Tags.vi\n SystemLink.lvlib:Main.vi:4140003\n SystemLink.lvlib:Main.vi.ACBRProxyCaller.E7F0001D<DQMH>MHL Frame: Send Tags</DQMH><DQMH>Event Handling Loop</DQMH>"}
From here on, the cRIO was disconnected from Systemlink, and no further uploads of files or tags from the cRIO to Systemlink were received, and this error continued to appear.
Any suggestions on where to look to resolve? Is the API key we're using timing out? Is Systemlink not realising that we rebooted, and therefore not allowing the same device with same credentials to reconnect?
Christopher Farmer
Certified LabVIEW Architect and LabVIEW Champion
DQMH Trusted Advisor
https://wiredinsoftware.com.au
