If you have been using SQLBackupAndFTP with the advanced options to schedule the automatic creation of your backups, there is a possibility that during the backup operation someone manually stops the process.
In the event that such a thing happens, there is a chance that trying to re-run the operation through a schedule you are going to encounter a problem with the schedule not being initiated.
The solution for this is to install the latest version of SQLBackupAndFTP, which has an updated scheduler and then re-run the schedule again.
If the problem persists, then please follow the next steps:
- Turn on log tracing for the scheduler service
- Find the service-log.off file in <ProgramData>Pranas.NETSQLBackupAndFTP folder and rename it to service-log.on
- Open the file with a simple text editor like Notepad and update the time values of <begin-time>*<end-time>. For example: 2013-04-12T18:21:00*2013-04-13T18:21:30.
- In this situation the scheduler service will write debug information into a file since 2013-04-12T18:21:00 until 2013-04-13T18:21:29.
- In the event that there is no service-log.off file in the folder, just start the SQLBackupAndFTP service and wait for a few minutes.
So, when you save the service-log.on file and when the time comes to debug, you will find a record with notes similar to:
“Debug ON. The log file: C:ProgramDataPranas.NETSQLBackupAndFTPLogsqlbf2013-4-12.log” in Windows Event Log. In other words the scheduler service writes log into “<ProgramData>Pranas.NETSQLBackupAndFTPLog” folder.
In a log file you can observe detailed information how the scheduler handles all scheduled jobs.
If you still encounter issues even after making this service log configuration, please send us your log file so we can come to a solution.