These pages cover SQL Clone 4, which is not the latest version. Help for other versions is also available.
Troubleshooting
Published 27 October 2016
The majority of SQL Clone installation issues occur because the OS does not have the latest updates.
Install the latest OS updates, and check the requirements and limitations pages to ensure your system is compatible before proceeding.
How to access SQL Clone
Log locations
Prepare for Windows 7 and Windows Server 2008 R2 end of support for SQL Clone
Installation Issues
- "An existing connection was forcibly closed by the remote host" error
- "Could not load file or assembly 'RedGate.SqlClone.Unmanaged.dll' or one of its dependencies" error
- Agent communication problems during install configuration
- An agent doesn't work after using the SERVERURL command line flag during installation ('unauthorized received from server')
- Could not execute "...VCRedist2017": Installation error 1 when running
- Error 1603 Service ... could not be installed. Verify that you have sufficient privileges to install system services.
- Error 1923. Service ... could not be installed. Verify that you have sufficient privileges to install system services.
- Multiple agents installed following upgrade on Windows 7 / Windows Server 2008 R2
- Problems during configuration wizard
- Security alert during SQL Clone update
Common Issues
- "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"
