These pages cover SQL Clone 4, which is not the latest version. Help for other versions is also available.
Common issues
Published 08 February 2017
- "Attempted to perform an unauthorized operation" while creating images
- "Could not create virtual disk" ... "The process cannot access the file because it is being used by another process"
- "Initialization of SQL Clone failed" after a reboot
- "Login failed for user..." - 'orphaned users' problem
- "ManagementException: Invalid class" while creating/deleting images or clones
- "Newtonsoft.Json.JsonSerializationException: Cannot create and populate list type..."
- "Pad block corrupted" after changing the user that SQL Clone Server runs as
- "Request failed anti-forgery validation"
- "System.Data.SqlClient.SqlError: Could not upgrade the metadata for database that is enabled for Change Data Capture." while creating images from backup
- "The operating system returned error 21(The device is not ready.) ..."
- "User does not have permission to alter database 'SqlCloneTemp_...'" when creating image from a backup
- Cannot execute as the database principal because the principal "server_audit" does not exist ...
- Cloning a VM containing a SQL Clone agent causes strange behaviour
- Expected a single volume for partition 1 on disk
- Image creation fails (VssUnexpectedErrorException)
- In SSMS, 'The connection is broken and recovery is not possible' error is seen after a clone is deleted
- The agent on [MACHINE_NAME] needs additional permissions to access the server
- The files behind the Clone have grown to be very large
- The requested operation could not be completed due to a file system limitation (Win32Exception)
- The web app is stuck "loading"
