This usually happens when the installed service cannot start. Check the Application section of the Windows Event Viewer for extra information.
This can also mean a service with that name already exists. Ensure any previous SQL Clone installations are removed, and try again.
If you have installed any previous version of SQL Clone, ensure you have a clean starting state by:
Ensure the image destination you chose has more free space than the size of your database, and ensure the disk is defragmented.
Unfortunately, we don't currently have a way to clear out the failed items on the Web UI. However, we are aware of this restrictions and it's on our backlog to get it done. As a workaround, you can run the below update command against our config database. it will mark those failed images as deleted. Please make sure that the database name reflects the database name that you configured it to. It's "SQLClone_Config" by default.
UPDATE [SQLClone_Config].[dbo].[Images] SET [State] = 4, DeletedOn = GETUTCDATE() WHERE [State] = 6 AND DeletedOn IS NULL; |