SourceGear Support

I've solved the problem, it was the script handlers in IIS for ScriptResource.axd that went missing for some reason. Once I've restored those, everything went back to normal.

p.s. Using Vault 9

Hi, our Vault server ran out of disk space. After we cleared disk space, we're running into problems with the web administration and getting an error about ajaxcontroltoolkit, specifically: Uncaught Error: AjaxControlToolkit requires ASP.NET Ajax 4.0 scripts. Ensure the correct version of the script...

Will do. I've checked the Command Dialogs screen, and everything is checked there.

Auto commit is not checked. I've checked in VS and Vault client. Out of the 4 options in that screen, only "Require check out before check in" is checked.

Hi, we've recently upgraded our vault version, and I've noticed a difference in behavior when deleting files in VS. In the previous version, when you'd delete a file from the project, the file would be removed from the project and there would be a delete file operation in the Pending Change Set, and...

Thank you for the update. The only side affect of files being read only is that they can't be edited without a check out. Another option you have is to have a check out as part of the build. I've ran into much less problems than I'd thought I'd would with the read only flag. On the local machines i...

So it seems that the Bin folder was checked in on one of the projects, and that was the cause of the errors that I saw. After removing the Bin folder, deleting the solution folder and get latest with the options "Require Check Out before Check In" and "Make all files read-only", ...

When you went to the full VSS mode, did you allow the files to be set to read only? That's what it takes to be fully in VSS mode. After the change, you can either perform a Get Latest to change the writable setting on the files, or you can manually set them all to read-only. I see. That's a bit of ...

Well, I spoke too soon. I've had a period when there was no scanning today, but it came back, and even when I select the full VSS mode, I still get the scanning behaviour.

What else can be done ?

I've set the Concurrent Development Style options to check "Require Check out Before Check In" and "Make all files writable" and left the other two options unchecked. That stopped the scan and has improved the operations that caused the scan. So unless something new comes up, I t...

>> How were the projects added to Vault? Did you use Visual Studio to add them or the GUI client? New projects are added from Visual Studio >> Did you set any working folders in Vault, or did you let Visual Studio set them? We're setting the working folder for the version/branch from Vault and chec...

Also, every once in a while while this is running, there's this error: 20/12/2016 16:32:03 <wf>: [Watcher:6] wf h:\projects\PrioriPOS 2.0.7.0\PrioriPOSAPI.Common mutex released 20/12/2016 16:32:03 <wf>: [Watcher:6] wf for h:\projects\PrioriPOS 2.0.7.0\PrioriPOSAPI.Common created 20/12/2016 16:32:03 ...

What I've noticed is that this starts immediatly after building the solution in VS, even though there were no changes. I've enabled the vault client log with all log categories, and the only thing there is in the log is: 20/12/2016 16:31:11 <wf>: [Watcher:6] wf for h:\projects\PrioriPOS 2.0.2.19\Sal...

We have an application that we've been working on for the last 10 years or so, and it has grown to about 8000 files. We maintain in the same repository several major versions and create branches for each feature which are then merged to the required versions. This causes each developer to have sever...