SQL Server Errors or Failures from Error: 4320 to Error: 4342

 

Error: 4320, Severity: 16, The file “%ls” was not fully restored by a database or file restore. The entire file must be successfully restored before applying this backup set.,
Error: 4322, Severity: 10, This backup set contains records that were logged before the designated point in time. The database is being left in the restoring state so that more roll forward can be performed.,
Error: 4323, Severity: 16, A previous RESTORE WITH CONTINUE_AFTER_ERROR operation left the database in a potentially damaged state. To continue this RESTORE sequence, all further steps must include the CONTINUE_AFTER_ERROR option.,
Error: 4326, Severity: 16, The log in this backup set terminates at LSN %.*ls, which is too early to apply to the database. A more recent log backup that includes LSN %.*ls can be restored.,

Error: 4327, Severity: 16, The log in this backup set contains bulk-logged changes. Point-in-time recovery was inhibited. The database has been rolled forward to the end of the log.,
Error: 4328, Severity: 16, The file “%ls” is missing. Roll forward stops at log sequence number %.*ls. The file is created at log sequence number (LSN) %.*ls, dropped at LSN %.*ls. Restore the transaction log beyond the point in time when the file was dropped, or restore data to be,
Error: 4329, Severity: 10, This log file contains records logged before the designated mark. The database is being left in the Restoring state so you can apply another log file.,
Error: 4330, Severity: 16, This backup set cannot be applied because it is on a recovery path that is inconsistent with the database. The recovery path is the sequence of data and log backups that have brought the database to a particular recovery point. Find a compatible backup to,
Error: 4331, Severity: 16, The database cannot be recovered because the files have been restored to inconsistent points in time.,

Error: 4332, Severity: 16, RESTORE LOG has been halted. To use the database in its current state, run RESTORE DATABASE %ls WITH RECOVERY.,
Error: 4333, Severity: 16, The database cannot be recovered because the log was not restored.,
Error: 4334, Severity: 16, The named mark does not identify a valid LSN.,
Error: 4335, Severity: 16, The specified STOPAT time is too early. All or part of the database is already rolled forward beyond that point.,
Error: 4336, Severity: 16, The filegroup “%ls” has been dropped and cannot be restored into the online database.,
Error: 4337, Severity: 16, The file “%ls” has been dropped and cannot be restored into the online database.,
Error: 4338, Severity: 16, The STOPAT clause specifies a point too early to allow this backup set to be restored. Choose a different stop point or use RESTORE DATABASE WITH RECOVERY to recover at the current point.,
Error: 4339, Severity: 10, This RESTORE statement successfully performed some actions, but the database could not be brought online because one or more RESTORE steps are needed. Previous messages indicate reasons why recovery cannot occur at this point.,
Error: 4340, Severity: 16, The point-in-time clause of this RESTORE statement is restricted for use by RESTORE LOG statements only. Omit the clause or use a clause that includes a timestamp.,
Error: 4341, Severity: 16, This log backup contains bulk-logged changes. It cannot be used to stop at an arbitrary point in time.,
Error: 4342, Severity: 16, Point-in-time recovery is not possible unless the primary filegroup is part of the restore sequence. Omit the point-in-time clause or restore the primary filegroup.,

This is applicable on below versions of SQL Server

SQL Server 2005
SQL Server 2008 R2
SQL Server 2012
SQL Server 2014

Hope this was helpful.

Thanks,
SQLServerF1 Team
In-Depth Blogs on SQL Server, Information about SQL Server Conferences and Events, SQL Server Frequently asked questions, SQL Server Trainings.