Looking at the logs may show an error similar to:

Database 'SQLClone_Config' already exists. Choose a different database name.

This can occur because SQL Clone Server is starting up before the SQL Server that stores its configuration database is ready. Restarting the SQL Clone Server service should fix this problem.

It could also occur because the user that SQL Clone Server is set to run as does not have permissions to access the configuration database. Re-run SQL Clone Server Setup from the Start Menu and change the username and password that SQL Clone Server runs as, ensuring that it can access and modify the database using Windows Authentication.