This problem will occur for any kind of restore operation (Full, Differential OR Log). The problem will occur ONLY if the restore is performed from the LiteSpeed GUI or SSMS (by using LiteSpeed XPROCs). The problem doesn’t occur on LiteSpeed version 4.8 to version 5.1. This problem will manifest even if the SQL Service Account’s default database is the database being restored. This error happens if any login logged into the SQL instance has their default database set to the database that is currently being restored. This is a known issue with LiteSpeed when they call the client side version GetConfiguration function. The above set of messages can be misleading at times. 7:39:47 AM: Error: 12300, Msg: SLS::execSQL -> End execute with unsuccessfull return code 7:39:47 AM: SLS::ExecSQL -> Error: 12300, Msg: RESTORE LOG is terminating abnormally. 7:39:47 AM: SLS::ExecSQL -> Original Msg: RESTORE LOG is terminating abnormally. 7:39:47 AM: SLS::ExecSQL -> Forced close the VDI config thread 7:39:27 AM: SLS::ExecSQL -> Wait for VDI config thread 7:39:27 AM: SLS::ExecSQL -> End Execute Command Please refer to SQL Server books online or Microsoft technical support for a solution:
The following message is not a LiteSpeed 2005 message. 7:39:27 AM: SLS::ExecSQL -> Error: 12309, Msg: SQL Server has returned a failure message to LiteSpeed 2005 which has prevented the operation from succeeding. It is recommended that the master database be used when performing this operation. RESTORE cannot process database ‘’ because it is in use by this session. 7:39:27 AM: RESTORE LOG is terminating abnormally. 7:39:27 AM: VDI::ConfigureVDI -> Waiting 4294967s for backup/restore command to begin 7:39:27 AM: VDI::ConfigureVDI -> Read registry value for configuration timeout
0 kommentar(er)
