Security Management stopped collecting

If Clarity stops collecting data, the issue often appears in the Collector Log. Click Settings in the left sidebar and select Collector. Then, go to the Collector Log tab and look for one of the following errors:

• Check messages from the SQL Server
• get_perf_mon

Check messages from the SQL Server

Error log found:

Traceback (most recent call last):\n File "src\\pymssql.pyx", line 448, in pymssql.Cursor.execute\n File "src\\_mssql.pyx", line 1064, in _mssql.MSSQLConnection.execute_query\n File "src\\_mssql.pyx", line 1095, in _mssql.MSSQLConnection.execute_query\n File "src\\_mssql.pyx", line 1228, in _mssql.MSSQLConnection.format_and_run_query\n File "src\\_mssql.pyx", line 1639, in _mssql.check_cancel_and_raise\n File "src\\_mssql.pyx", line 1683, in _mssql.maybe_raise_MSSQLDatabaseException\n_mssql.MSSQLDatabaseException: (297, bThe user does not have permission to perform this action.DB-Lib error message 20018, severity 16:\\nGeneral SQL Server error: Check messages from the SQL Server\\n)\n\nDuring handling of the above exception, another exception occurred:\n\nTraceback (most recent call last):\n File "collectors\\e1n_dbmgr.py", line 56, in f_conn\n File "src\\pymssql.pyx", line 468, in pymssql.Cursor.execute\npymssql.OperationalError: (297, bThe user does not have permission to perform this action.DB-Lib error message 20018, severity 16:\\nGeneral SQL Server error: Check messages from the SQL Server\\n)\n 

What it means:

Clarity is unable to connect to the database.

How to resolve the issue:

1. First, verify the Security Management module is running. 
2. If not, check that the Batch Jobs module is running. Since Security and Batch Jobs share an API, the issue could be here. If Batch Jobs is not running, follow these steps to troubleshoot.
   
   
3. If the Security Management page is running, go back to the Collector Log and look for an Traceback (most recent call last):\n File "tools\\execute_query.py", line 64, in create_connection\npyodbc.ProgrammingError: (42000, [42000] [IBM][System i Access ODBC Driver][DB2 for i5/OS]SQL0104 - Token . was not valid. Valid tokens: . (-104) (SQLExecDirectW))\n
4. An ORA-00942 error indicates that a table or view is missing data. Another issue could be that some column names could have been changed from the standard JDE names. Contact ERP Suites Product Support to test the queries and resolve the issue.

get_perf_mon

Error log found:

Traceback (most recent call last):\n File "tools\\e1n_api_bridge.py", line 774, in get_perf_mon\nTypeError: NoneType object is not iterable\n. 

What it means:

The Collector interval is set to zero.

How to resolve the issue:

1. Click Settings in the left sidebar and select Update Settings.
2. Go to the Change Collector Intervals tab.
3. Scroll down to find perfmonitor/run and set the interval set to 5 minutes. 
4. Click the action icon to update your settings.