SourceGear Support

Hi Tonya. I started encountering the issue again. Here are some of the errors in the log. Which email should I send the log to? Error (replaced the username and server info with USER1 and SERVER fpr the server info, USER2 is a client). Script fired up and started doing getlatest on some of the files...

Tonya, I just saw your reply. Sorry for the delay. I will send over the log once it happens again. Sadly, I cannot access the SQL DB. After Vault was setup in this new server, the admin pass I selected it is not letting me access it (nor login as admin to the vault page) but I am hoping the vault lo...

This issue happened again. CPU and Memory high. Memory up to 95% in the server. IIS process and SQL Server processes are the most active ones. SQL Server process is the most active one. Vault log showing timeouts when attempting operations, a lot of rollbacks. Issue went away after bouncing the serv...

Thanks for the reply. All users were experiencing the issue. It occurred for all files. This is something new, at least the first time it was noticed. Files were not large at all, I was testing with a file that uses 1KB. I fixed this by bouncing the whole server. I believe something was happening on...

Hi SG team! Hope you all well. Sorry to bother you guys. I am having an issue when doing check outs from the Vault client or VS. From the messages in the client, it takes 7 minutes for check out; 10 min in some cases. Other operations like view history, compares, undo check-ins, get are quick. Only ...

Beth wrote:Could you send an email to support at sourcegear.com (attn: Beth) with a link to this forum thread? Then I can take a closer look at the issue.

Will do. Thanks Beth.

I haven't seen anything more. Did anything change? The issue did not occurred again until today. I configured the logging to log ALL events but I cannot see any entries for the error I added as title to the post. I did found an [System.Web.Services.Protocols.SoapException: 1011 : FailInvalidSession...

What is your OS? You can set up some logging for your command-line client using this article: http://support.sourcegear.com/viewtopic.php?p=5375. You might also set your server to debug logging to try and capture the issue. That is performed in the Vault admin web page under logging. The app runs o...

Hello guys. A bit ago when working on the old 3.1.9 client I was hitting this issue from time to time but it was/is a matter of just re-running the app pretty much. Today, working with Vault Pro Client (v7.2.1) I hit this issue again twice. Now, re-running the app works but I don't understand why it...

I ran a few tests and only get errors when the version doesn't exist. C:\Program Files (x86)\SourceGear\VaultPro Client>vault HISTORY -host vaultprodemo.sourcegear.com -user guest4 -password guest4 -repository "Initial Repository" -beginversion 6 -rowlimit 1 $/Documents/Folder2/Test2e.txt...

Sorry, I meant removing the -beginversion as a troubleshooting step, not a solution. I'm going to have you try a few different commands so we can see what the response would be. From those responses, I hopefully will get a better idea of the root cause. Try a test without -beginversion and let me k...

Are you looking for a file or a file's particular version? If it is just a file, what if you removed the '-beginversion X' parameters? Sorry for the delay. I was waiting to see certain type of alert on my email. I am ensuring a particular version of a file exists. This is how I check if a version e...

Is the file you are checking shared, branched, or renamed? You might need to adjust your query for those. For example, if there is a branch, the history from before the branch actually resides in the original folder the branch was created from. Try getting from there. Nope. No branching done whatso...

Hello. I got an issue with a command line app using vault.exe. I got a bunch of files I am checking to see if they exist in the repository. This is the same code that is being used with previous Vault version (old 3.1.9 vault client) and even initial tests with the new 7.2.1 worked fine but did not ...