File '%1!s!' has been rolled forward to LSN %2!s!. This log terminates at LSN %3!s!, which is too early to apply the WITH RECOVERY option. Reissue the RESTORE LOG statement WITH NORECOVERY.
File "%1!s!" cannot be opened for reading. Error may occur when there are no privileges or the file is not found. Exact cause ...
File "%1!s!" cannot be restored over the existing "%2!s!". Reissue the RESTORE statement using WITH REPLACE to overwrite ...
File "{0}" already exists. Do you want to reuse this file as the configuration file or overwrite the file with new configuration ...
File '%1!s!' appears to have been truncated by the operating system. Expected size is %2!s! KB but actual size is %3!s! KB. ...
File '%1!s!' has been rolled forward to LSN %2!s!. This log terminates at LSN %3!s!, which is too early to apply the WITH ...
File '%1!s!' is claimed by '%2!s!'(%3!s!) and '%4!s!'(%5!s!). The WITH MOVE clause can be used to relocate one or more files. ...
File '%1!s!' is not a valid undo file for database '%2!s! (database ID %3!s!). Verify the file path, and specify the correct ...
File '%1' already exists. If this error occurs, locate this file in the Web synchronization directory, delete the file, and ...
File '%{fileName/}' specified in Restore command is AS encrypted backup file that was created by earlier prerelease of SQL ...