You cannot start a front-end server when a SQL Server transaction log reaches maximum capacity in a Lync Server 2013 environment
Consider the following scenario:
- Many user activities occur in a server pool in a Microsoft Lync Server 2013 environment.
- The back-end server of the front-end server pool is running Microsoft SQL Server.
- The back-end server is in full recovery mode.
- Database mirroring is enabled on the back-end server.
In this situation, the transaction log for the user services database reaches maximum capacity. Therefore, you cannot start the front-end server, and the following is logged in an event log:
Also, you receive the following error:
SQL_9002_severity_17 sql_err # The log file for database '%.*ls' is full. Back up the # transaction log for the database to free up some log space. # as an HRESULT: Severity: SUCCESS (0), FACILITY_NULL (0x0), Code 0x232a # for decimal 9002 / hex 0x232a
Run the DBCC SQLPERF (LOGSPACE) query to check the size and current capacity of all transaction logs on the back-end server.
To work around this issue, truncate the transaction logs that reach maximum capacity by performing a SQL Server backup on them. This reduces the file size of the transaction logs.
Still need help? Go to Microsoft Community.