Bug: SQL Logging Stops Without an Error

Version Affected: Prior to 22.02
Bug Number: EE-2469
Bug Status: Closed - Fixed
Fixed in Version(s): 22.02+

 

Overview

When using SecureAuth's SQL Logging database, administrators may see logging stop without any error message being shown anywhere.

 

Cause

SecureAuth Identity Provider (IdP) sends NULL values to the Microsoft Logging library, which the library does not handle -- this causes logging to silently stop, with no error shown.

 

Resolution / Workaround

Upgrade to version 22.02 or later to resolve this issue.

If you cannot upgrade immediately, a temporary workaround is available: remove the formatter from the DB Trace Listener in the web.config file for each realm using SQL logging. Doing this changes how logs are formatted in the database compared to leaving the formatter in place -- upgrade instead when possible.

1. Decrypt the web.config file, either from the System Info tab or via the Decrypt web.config menu item in the classic admin area.
2. Find the line:

<add name="DatabaseTraceListner" type="MFC.SecureAuth.Logging.FormattedDatabaseTraceListener, MFC.SecureAuth.Logging" listenerDataType="MFC.SecureAuth.Logging.FormattedDatabaseTraceListenerData, MFC.SecureAuth.Logging" databaseInstanceName="LogDatabase" writeLogStoredProcName="WriteLog" addCategoryStoredProcName="AddCategory" formatter="Text Formatter" />

3. Remove the formatter="Text Formatter" portion of the line.

The line should look like this after the change:

<add name="DatabaseTraceListner" type="MFC.SecureAuth.Logging.FormattedDatabaseTraceListener, MFC.SecureAuth.Logging" listenerDataType="MFC.SecureAuth.Logging.FormattedDatabaseTraceListenerData, MFC.SecureAuth.Logging" databaseInstanceName="LogDatabase" writeLogStoredProcName="WriteLog" addCategoryStoredProcName="AddCategory" />

SecureAuth Knowledge Base Articles provide information based on specific use cases and may not apply to all appliances or configurations. Be advised that these instructions could cause harm to the environment if not followed correctly or if they do not apply to the current use case.

Customers are responsible for their own due diligence prior to utilizing this information and agree that SecureAuth is not liable for any issues caused by misconfiguration directly or indirectly related to SecureAuth products.