Comments
Sort by recent activity
There's a few possibilities here- your commit comment looks correct so you might have other policy requirements which are missing from your machine, or a mismatch in versions. Please check the steps in this aritcle
We also issued a bugfix for one cause of this error, so you should also run the Help > Check for Updates process to ensure you're on the latest version / comments
There's a few possibilities here- your commit comment looks correct so you might have other policy requirements which are missing from your machine, or a mismatch in versions. Please check the step...
Hmm, that makes it tricky then. I installed the same version of VisualSVN here and it works ok for me [image]
Are you maybe able to use something like wireshark or fiddler to grab the network traffic on both the client and server and send those to me? Might also be worth seeing if the SVN server logs contain any reason for the connection being dropped? / comments
Hmm, that makes it tricky then. I installed the same version of VisualSVN here and it works ok for me
Are you maybe able to use something like wireshark or fiddler to grab the network traffic on b...
Thanks, I've just installed that server version on a VM and I can link to it and commit without trouble. Could you let me know of any specific settings on the Server Properties screen?
If you have the Enterprise edition, could you also turn on access logging and see if that shows anything when the errors occur? / comments
Thanks, I've just installed that server version on a VM and I can link to it and commit without trouble. Could you let me know of any specific settings on the Server Properties screen?
If you have...
What version of SVN do you use on the server side? I've seen another user recently report intermittent connection problems in newer versions of SQL Source Control, and it seems to relate to us shipping a newer build of the SharpSVN library. / comments
What version of SVN do you use on the server side? I've seen another user recently report intermittent connection problems in newer versions of SQL Source Control, and it seems to relate to us ship...
If you could do it would be great. When you submit the error report, it goes into the bugtracker used by our developers, but doesn't raise a support ticket automatically. You can either email the support address directly, or via the web portal here
Thanks! / comments
If you could do it would be great. When you submit the error report, it goes into the bugtracker used by our developers, but doesn't raise a support ticket automatically. You can either email the s...
Thanks- did you also email in to raise a support ticket? I didn't see that yet, but not sure if my colleagues in the US office picked it up already. / comments
Thanks- did you also email in to raise a support ticket? I didn't see that yet, but not sure if my colleagues in the US office picked it up already.
There's unfortunately not quite enough to go on here to give you an exact fix.
It'll generally indicate some sort of problem with us parsing either the DB itself, or the files in the repository.
To narrow down where the problem is, can you unlink the DB, restart SSMS, then link to a new "evaluation repository", commit all objects, and refresh the commit tab?
If the problem persists, it's most likely something in your DB, but if the problem goes away, it's more likely a problem in the files in the repository.
To then narrow it down, we most likely need to see the error report as this will often indicate the object causing trouble, so can you send that in (making sure you put your email in the box) and then email support@red-gate.com to raise a ticket, referencing this forum thread?
Thanks! / comments
There's unfortunately not quite enough to go on here to give you an exact fix.
It'll generally indicate some sort of problem with us parsing either the DB itself, or the files in the repository.
To...
I'd agree that it looks like there's something either in your application or the environment that the profiler doesn't like.
The first suggestion would be to ensure you've tried all the troubleshooting steps relevant to IIS and crashes in general as these help in a lot of cases. You'll find those links here and here
Often these things come down to a simple permissions problem.
If none of that helps, (or if the attach to process option works but not line/method level) it's likely that some component of your application doesn't like the instrumenting profiling methods. Sometimes we can work around these, sometimes not... post back if you're still stuck and we can get in touch directly to help out further. / comments
I'd agree that it looks like there's something either in your application or the environment that the profiler doesn't like.
The first suggestion would be to ensure you've tried all the troubleshoo...
If you use the Working Folder option, then all that SQL Source Control will do during a commit/get latest is update that folder.
All the checking out from TFS and committing changes back in will need to be done via Visual Studio or the TFS commandline tools etc. / comments
If you use the Working Folder option, then all that SQL Source Control will do during a commit/get latest is update that folder.
All the checking out from TFS and committing changes back in will ne...
Good news if you've managed to get around the issue with a commandlinehooks file.
The specific feature suggestion you ideally need is logged here - please do vote and comment there, as the more popular it is, the more likely it is that the team will be able to dedicate time to implementing it. / comments
Good news if you've managed to get around the issue with a commandlinehooks file.
The specific feature suggestion you ideally need is logged here - please do vote and comment there, as the more pop...