Comments
Sort by recent activity
Wait-SqlCloneOperation should throw the relevant error from the create/delete operation rather than "A task was canceled", e.g. [image] Are you seeing an error in the SQL Clone Server or Agent logs? Would you be able to share the relevant part of your PowerShell script? / comments
Wait-SqlCloneOperation should throw the relevant error from the create/delete operation rather than "A task was canceled", e.g.Are you seeing an error in the SQL Clone Server or Agent logs? Would y...
The PowerShell cmdlets are an alternative interface to the web UI, and so their job is just to send requests over HTTP to the SQL Clone Server backend. If the server returned an exception, that ought to be thrown by the cmdlet, and if you use the Wait-SqlCloneOperation cmdlet after starting a create/remove operation, it will throw any exception that occurred during the creation/deletion of an image/clone. If an unhandled exception was thrown in the Server or Agent, it should be logged in the relevant log files, as described here: https://documentation.red-gate.com/clone2/troubleshooting/log-locations Given that you're seeing "A task was canceled", particularly with Connect-SqlClone which only does a very simple handshake, I wonder whether this might actually be a timeout occurring when the cmdlet is trying to communicate with SQL Clone Server? / comments
The PowerShell cmdlets are an alternative interface to the web UI, and so their job is just to send requests over HTTP to the SQL Clone Server backend. If the server returned an exception, that oug...
Hi, hopefully you've resolved your problem, but this is a problem that we see if the login being used by the SQL Clone Agent doesn't have sysadmin privileges when creating images from backup. The backup path needs to be one which can be restored by the instance of SQL Server that you're using. UNC paths should work, but note that the account being used to access the backup is the account that the SQL Server service is running as in this case, not e.g. the SQL Clone Agent service's account. / comments
Hi, hopefully you've resolved your problem, but this is a problem that we see if the login being used by the SQL Clone Agent doesn't have sysadmin privileges when creating images from backup.The ba...
Hi! This error occurs because your agent machine has an old version of Newtonsoft.Json.dll in the Global Assembly Cache (GAC). The .NET runtime loads this preferentially over the DLL shipped with SQL Clone, and this version doesn't support deserialization of IReadOnlyCollection. This DLL will have been added to the GAC by another product. We've heard this problem a few times, but we're not sure which software might be responsible - any suggestions you might be able to give would be useful! This could be resolved either by removing this DLL from the GAC so that the version we ship is loaded (although this may affect the software that installed it there) or updating the version in the GAC to at least version 8.0.2. / comments
Hi! This error occurs because your agent machine has an old version of Newtonsoft.Json.dll in the Global Assembly Cache (GAC). The .NET runtime loads this preferentially over the DLL shipped with S...
A kind of "reset" feature for a clone makes a lot of sense, yes! Thanks for the suggestion - we'll definitely take a look at doing something like this. / comments
A kind of "reset" feature for a clone makes a lot of sense, yes! Thanks for the suggestion - we'll definitely take a look at doing something like this.
Sounds like a reasonable thing to add - we'll get on that soon!
Given that we want to minimise the likelihood of breaking changes at the PowerShell interface, we try to be cautious about exposing all the metadata we have, but if we're missing something else that might be useful we can certainly look at adding it. / comments
Sounds like a reasonable thing to add - we'll get on that soon!
Given that we want to minimise the likelihood of breaking changes at the PowerShell interface, we try to be cautious about exposing a...
This makes a lot of sense, and it's definitely something that we'd like to improve. Making it happen unfortunately isn't trivial, so I can't commit to anything specific here, but we'll definitely take your feedback into account in planning our work. / comments
This makes a lot of sense, and it's definitely something that we'd like to improve. Making it happen unfortunately isn't trivial, so I can't commit to anything specific here, but we'll definitely t...
SQL Clone 2.4.3 now has an option to hide this "Show feedback" link in the current browser which is accessible from the in-app Settings. / comments
SQL Clone 2.4.3 now has an option to hide this "Show feedback" link in the current browser which is accessible from the in-app Settings.
Thanks for the feedback. We're currently working on a way to hide this - I'll update when we release it. / comments
Thanks for the feedback. We're currently working on a way to hide this - I'll update when we release it.
Hi, apologies for the delay in getting back to you.
I've been looking into possible reasons for getting this error message despite having local admin privileges. Do you use any systems which provide additional access protection, e.g. McAfee VirusScan Enterprise? It's possible that this could be blocking the operation being performed by the SQL Clone Agent. / comments
Hi, apologies for the delay in getting back to you.
I've been looking into possible reasons for getting this error message despite having local admin privileges. Do you use any systems which provid...