Alert is fired with the following event:
Message Text %NIC-3-802003: Webserver-InvalidScheduledReportTask-ErrorDetection, Webserver, enVisionSystem, InvalidScheduledReportTask, "TaskName", ErrorDetection
Alert ID envision_ip:xxxxxxxxxxxx
Stale Permissions in the nicdb or broken permissions in the nicdb
Open a cmd prompt on the ES or ASRv:
1. change directory to %_Envision%\database\cmd.
2. run validatepermissions.
3. it will show something similar but for the device group table
=================== The following entries in permission table refer to a non-existent user or group ===================
Guid: has 1 references.
=================== The following entries in user_group table refer to a non-existent user ===================
=================== The following entries in user_group table refer to a non-existent group ===================
=================== The following entries in view_user_group table refer to a non-existent user ===================
=================== The following entries in view_user_group table refer to a non-existent group ===================
=================== The following entries in permission table refer to a non-existent device group ===================
=================== The following entries in permission table refer to a non-existent report folder ===================
=================== The following entries in permission table refer to a non-existent site ===================
=================== The following entries in permission table refer to a non-existent dashboard item ===================
=================== END OF PERMISSION VALIDATION ===================
Execution time: 0.062 seconds
if that is the case
run the following
E:\nic\4100\\database\cmd>validatePermissions.cmd DELETE<BR>it will show something similar but for the device group table<BR><BR>=================== The following entries in permission table refer to a non-existent user or group ===================<BR>Guid: has 1 references.<BR>Guid: deleted from permission<BR>=================== The following entries in user_group table refer to a non-existent user ===================<BR>=================== The following entries in user_group table refer to a non-existent group ===================<BR>=================== The following entries in view_user_group table refer to a non-existent user ===================<BR>=================== The following entries in view_user_group table refer to a non-existent group ===================<BR>=================== The following entries in permission table refer to a non-existent device group ===================<BR>=================== The following entries in permission table refer to a non-existent report folder ===================<BR>=================== The following entries in permission table refer to a non-existent site ===================<BR>=================== The following entries in permission table refer to a non-existent dashboard item ===================<BR>=================== END OF PERMISSION VALIDATION ===================</FONT></P> <P><FONT face="Times New Roman"><FONT size=2>Stop and start the nic webserver service and verify correction.</FONT></P></FONT></body>
Related Articles
Data Access Review for the file share does not show the accounts which have access to file share via the group in RSA Iden… 35Number of Views AIX - Syslogd flag -n should not be used (AIX event source not discovered) 14Number of Views Why are there N/A's seen in BackOffice Cases Transactions and Reports? 9Number of Views How to synchronize user accounts that do not have an email address to the SecurID Access Cloud Authentication Service 121Number of Views Access Manager 6.1sp4 and 6.2 Broke I18N internationalization support in AdminGUI 11Number of Views
Trending Articles
RSA Authentication Manager 8.9 Release Notes (January 2026) RSA announces the availability of the RSA SecurID Hardware Appliance 230 based on the Dell PowerEdge R240 Server How to troubleshoot Oracle database ORA-04030 errors in RSA Identity Governance & Lifecycle RSA Authentication Manager Upgrade Process Microsoft SQL Server Collectors can no longer connect to the SQL Server database after upgrade to Microsoft SQL Server 201…