When the database is in full recovery mode and scheduled log backups are being done regularly, the first and last log sequence number (LSN) numbers in SQL Server error logs are same for consequent log backups after the issue is hit. It is still advised to confirm if any user activity is expected during this timeframe. The LSN numbers may not change because there is no write operation caused by the lack of user activity. Related SQL Server error log entries are following:
Log was backed up. Database: <DataBaseName>, creation date(time): <Date><Time>, first LSN: 76383:11154:1, last LSN: 76383:11154:1….. This is an informational message only. No user action is required.
The hotfix will not resolve the issue completely. However, additional diagnostic information (based on type and error severity) may be logged in the SQL Server error logs when the issue occurs again. You have to identify the actual exception and fix it with the help of additional diagnostic information that you might retrieve after you apply the hotfix.
Article ID: 2963658 - Last Review: 30 Jun 2014 - Revision: 1