- 5 minutes to read

FAQ and Troubleshooting guide for the Nodinite Logging Service

Quickly resolve issues with the Nodinite Logging Service. Most problems come from one of three places: SQL Server rights and connectivity, the System Parameters that steer the service, or how the service is hosted (set in the Nodinite Portal). Start with the table below, then follow the links.

The Logging Service stopped: the Status menu says Logging Service is now offline, the Log API still accepts an order, the Log View finds nothing, the Database Report counts the event as Unprocessed; started again, the Log View finds the order, animated walkthrough (7.12)
Animated walkthrough: while the Logging Service is stopped, the Log API still stores a new Log Event, but a Log View can't find it yet. The event waits as Unprocessed in the Log Database. Once the service runs again, it catches up by itself. See Where do Log Events wait while the Logging Service is stopped?

Common Logging Service Issues

Symptom What to check
Log Events stay unprocessed The Logging Service IIS web site and application pool are started (see How do I know if the Logging Service has stopped?). The waiting events show as Unprocessed in the Log Database's Show Database Report (see below). MessageProcessingBatchSize sets how many events each run takes; with 0, a negative or an invalid value the Logging Service uses 100 and logs a warning. Processing runs every 30 seconds for the active Log Database and every 5 minutes for archive Log Databases (Message Processing)
One message gets the Error processing state Its body is larger than MessageProcessingMaxBodySize; the Comment on the Log Event and the Log Audit say so
No Log Database after installation, or no new one is created The Logging Service creates the first Log Database on its first start, and later ones with the same rights. Check the SQL Server rights in Prerequisites, and the SqlServer, SqlPackageExecutable, LogLocations, and (Always On) AvailabilityGroupBackupPath System Parameters
Old data is not deleted The Days to keep values of the Message Types and the cleanup interval, see Data Retention
The Status menu says Logging Service is now offline The service is stopped, or the Web API can't reach it: start the service, then check the firewall rules between the Web API and the Logging Service ports (Prerequisites)
Slow processing or queries over Linked Servers The db_ddladmin right in Prerequisites, Linked Servers, and Performance
The service account can't start or reach SQL Server Logon as a Service right, gMSA accounts, Transactions MSDTC, and the service account set in the Portal (Service account defaults)

Common Logging Service symptoms and where to look.

No System Parameter needs a restart of the Logging Service; each parameter page states when a change takes effect.

Where do Log Events wait while the Logging Service is stopped?

In the Log Database. The Log API only stores events; the Logging Service processes them, which includes extracting the Search Field values a Log View searches on. So while the service is stopped, new events are stored with the processing state Unprocessed, and a Log View doesn't find them yet. Nothing is lost: once the service runs again it processes the waiting events by itself.

  1. Open the Status menu (the bell). Logging Service is now offline means the Web API can't reach the service.
  2. Go to Administration > Settings > Log Databases and open the online Log Database (the one without an End Date).
  3. Click Show Database Report and open the Data tab.
  4. The Unprocessed column shows how many events wait, per Message Type.
  5. Start the Logging Service again. Within about 30 seconds the Status menu says Logging Service is now online, and the Log View finds the events.

Contact our support

If you still have any questions or have trouble with the Logging Service, don't hesitate to get in touch with us, read more on the Support page.
Our team is ready to assist you with any challenges or special requirements.

Next Steps

Logging Service

System Parameters

Install and Update Troubleshooting

Windows Configuration

SQL Server

Administration