RSA enVision NIC Windows Service stopped working
Originally Published: 2015-09-28
Article Number
Applies To
RSA Product/Service Type: enVision Core
RSA Version/Condition: 4.1 SP1
Platform: Windows
O/S Version: 2008R2/2003
Product Description: RSA enVision ES/LS
Issue
-
When storage locations for enVision single appliance "ES" or Multi-appliance environment
"LS" run out of storage-space, enVision NIC-related services get's shut-down through "pi_diskusage" exe file. -
Upon clearing out the storage problem and starting back NIC-services the collection for NIC Windows service/Agent-less service will not resume it's pulling of logs from MS windows servers normally.
Cause
-
Storage location runs out of free-space, hence collection services get's disrupted.
-
enVision not pulling logs from MS Windows-based servers.
Resolution
- POS file hosts the UTC and records ID of the last collected event(s) for the MS-windows 2003/2008 servers integrated with RSA enVision.
- POS file paths:
- For single-appliance [ES] "POS file will be stored locally on the server":
Path: E:\nic\csd\config\iwndows\lonely\pos
- For Multi-appliance [LS] "POS file will be stored over the NAS storage":
Path: \\NAS IP\\vol0\nic\csd\config\windows\LC1\pos
3. Based on your "RSA enVision" setup [ES or LS], delete the "POS" file from the above mentioned paths.
4. Restart NIC Service Manager & NIC Windows Service on your ES appliance or on your "LC" collector in case of an LS multi-appliance environment.
5. Go to the path where the POS is stored and notice that a new POS has been created.
6. On your GUI, Go to Analysis tab > event viewer > message view and you will be able to see real-time logs indicating that NIC Windows service has started back pulling events from your MS Windows Server(s).
4. Restart NIC Service Manager & NIC Windows Service on your ES appliance or on your "LC" collector in case of an LS multi-appliance environment.
5. Go to the path where the POS is stored and notice that a new POS has been created.
6. On your GUI, Go to Analysis tab > event viewer > message view and you will be able to see real-time logs indicating that NIC Windows service has started back pulling events from your MS Windows Server(s).
Related Articles
Encoding with Datafeeds Explained 37Number of Views Import policies from Cisco ESA no error message but no policies seen in DLP UI 9Number of Views NIC System message %NIC-4-400029 162Number of Views enVision: How to delete the sftpagent's .pos / position file 41Number of Views HardwareTokenReplacementBestPractices 82Number of Views
Trending Articles
Passwordless Authentication in Windows MFA Agent for Active Directory – Quick Setup Guide RSA Authentication Manager 8.9 Release Notes (January 2026) RSA Authentication Manager Upgrade Process RSA Authentication Manager 8.7 SP2 Setup and Configuration Guide An example of SSO using SAML and ADFS with RSA Identity Management and Governance 6.9.x
Don't see what you're looking for?