0

Issue with Establishing Connectivity for New SQL Collectors in Canary Data Historian

Hello everyone,

I'm currently facing a challenge with setting up new data sets and SQL collectors in the Canary Data Historian. Despite following the process that worked for other data sets, the 'Connected' status for the new collectors remains 'False', indicating a lack of connectivity. It's perplexing because the existing data sets are functioning correctly, and the replication of these settings to the new data sets has not yielded success.

Here's a brief rundown of the situation:

  • The SQL Server is pulling data correctly, so the issue appears to be isolated to the connection between SQL Server and Canary.
  • I've double-checked the configurations to ensure consistency with the working data sets.
  • All necessary permissions and settings have been verified to match those of the operational collectors.

One potential cause I'm considering is the presence of NULL values. Could they be interfering with the connectivity in some way? Has anyone encountered a similar issue or have insights on whether NULL values could affect the connection status within Canary?

Any advice or troubleshooting tips would be greatly appreciated. Thank you in advance for your help!

1 reply

null
    • smason
    • 8 mths ago
    • Reported - view

    Hi keshav. misra ,

    I don't think NULL values would prevent a connection, but we do log an error if the value is NULL. Are there any other errors in the message log concerning the connection?

Content aside

print this pagePrint this page
  • 8 mths agoLast active
  • 1Replies
  • 33Views
  • 2 Following