You will find the NIC System error message "Failed to read nst file". Dashboards, Event Viewer, Reports doesn't work as expected with errors.
Below are the NIC system error messages,
%NIC-3-500018: LSServer, LSServer, -, -, -, -, Detail: 832: Connection from NIC Server on Domain NIC, Site TRHSBC, Node TRHSBC-DS1 to NIC Server on Domain NIC, Site TRHSBC, Node TRHSBC-DS1 is Down - Failed to read nst file
%NIC-5-500017: LSServer, LSServer, -, -, -, -, Detail: 832: Connection from NIC Server on Domain NIC, Site TRHSBC, Node TRHSBC-DS1 to NIC Server on Domain NIC, Site TRHSBC, Node TRHSBC-DS1 is Up.
Solution
--------
Check the files in the below locations. I am specifying for ES. For LS, check for the same locations on NAS Vol0.
1. E:\nic\csd\config\<locators>\<node-name>\<node-name>.nst
2. E:\nic\csd\config\<collectors>\<node-name>\<node-name>.nst
3. E:\nic\csd\config\<nicservicemanagers>\<node-name>\<node-name>.nst
One of these or all files may be 0KB or corrupted.
Remove the specific file(take a backup) and restart NIC Service manager. This will resolve the issue and you won't see the above errors.
Related Articles
Recovering an enVision Database 72Number of Views Wrong system name used when creating mobilink subscription - EA configuration 46Number of Views Lsdata Utility Instructions for RSA enVision 289Number of Views Palo Alto Cloud Identity Engine - SAML My Page SSO Configuration - RSA Ready Implementation Guide 6Number of Views System Settings 36Number of Views
Trending Articles
How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device How to Download OTP Token Seed Files from myRSA Microsoft Entra ID External MFA - Relying Party Configuration Using OIDC - RSA Ready Implementation Guide Quick Setup Guide - Passwordless Authentication in Windows MFA Agent for Active Directory RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide