HomeLOGbinder for SP KBHow ToRecovery options for LOGbinder service

3.24. Recovery options for LOGbinder service

The other day our support staff received the following error:

LOGbinder error
Error when translating entries. Details: A transport-level error has occurred when sending the request to the server. (provider: TCP Provider, error: 0 - An existing connection was forcibly closed by the remote host.); at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection) ...

After some investigation, we found it was because the SQL server that SharePoint was installed on was rebooted. Well, first of all, we put in a ticket to improve the message. But what can be done to keep LOGbinder running?

In the Services MMC snap-in, open the properties of the LOGbinder service, and go to the Recovery tab. You can set the recovery option for first, second, and subsequent failures to "Restart the Service." We would suggest changing the value of "Restart service after" to 15 minutes, to allow SQL to restart.

Let us know what you find practical for your organization.

This page was: Helpful | Not Helpful