HomeLOGbinder for SQL KBGetting Started GuideMonitoring LOGbinder for SQL Server

2.3. Monitoring LOGbinder for SQL Server

Monitoring LOGbinder for SQL Server

When installing, configuring, and running LOGbinder for SQL Server, the software writes diagnostic events to the Windows Application Event Log. Most of these will be from the source "LOGbndSE" and the category "LOGbinder." You may use the Windows Event Viewer to examine these events.

During Installation and Configuration

During installation and configuration, you will find these entries:

You can monitor these events to ensure that LOGbinder for SQL Server continues to be configured properly, and that unauthorized changes do not occur.

After configuring LOGbinder for SQL Server and starting the service, it automatically performs a check to ensure that LOGbinder's settings are valid and that the account running the Windows service has sufficient authority. If there is a problem, the LOGbinder for SQL Server (LOGbinder SQL) service will not start and a message will be presented to the user. In most cases, the details of the problem are written to the Application log. Common problems include:

If any of these errors are encountered, the LOGbinder for SQL Server (LOGbinder SQL) service will not run.

While LOGbinder for SQL Server is Running

While LOGbinder for SQL Server is running, you will see information entries in the Application log as follows:

These log entries are informational in nature. Generally no action is required. If more entries are being processed than what appear in the event logs or in your log management solution, it could be that the log size is too small and entries are being overwritten. See Appendix C: Diagnostic Events “551 – LOGbinder agent successful for more information on these events.

There may also be some warning event entries:

If LOGbinder for SQL Server has an error, an entry will be created in the Application log. If permissions are removed, or if the license expires, you may receive a "556 – LOGbinder insufficient authority" or "557 – License for LOGbinder invalid" error, which are explained above. Other errors will be entitled "LOGbinder error." If you cannot resolve the problem, please submit the issue to the LOGbinder support team.

This page was: Helpful | Not Helpful