SourceGear Support

If we delete the folder, won't the original be deleted as well? We'd like to NOT have the original folder be deleted.

We've shared a folder and all of it's subfolders, etc. How do we "unshare" this folder?

As it turns out, the dbcc route didn't resolve the issue.
We restored the database from a daily back (from BEFORE the corruption), and things are working again.

After turning on debug:

Here is the page
<server name>.accipiter.com Server Installation
Version 3.1.9.3798 Installed 09 June 2006

I've sent you a copy of today's server log.

Other symptoms include: no transactions can be complete with the GUI client.

We're using Windows Server 2003 and SQL Server 2000, MS .NET 1.1. We run a cruisecontrol(.net) service from this box.

This began to happen right after a reboot of the server.

Upon rebooting a server hosting our Vault instance, we see this: ----9/11/2006 3:44:45 PM Jjeffers--172.31.70.186(172.31.70.186)--SSL Disabled System.Data.SqlClient.SqlException: Warning: Fatal error 625 occurred at Sep 11 2006 3:44PM . Note the error and time, and contact your system administrator....

Linda,

I will try a new working directory and see what happens.

One of the linux machines, but with the same login, just got the right files. Perhaps this is a local cache issue?

Version Check: Your Vault server is version 3.1.6.3658 The particular OS is RedHat ES 3, with Mono JIT compiler version 1.1.13.4, (C) 2002-2005 Novell, Inc and Contributors. www.mono-project.com TLS: normal GC: Included Boehm (with typed GC) SIGSEGV : normal I've only seen this with .java files, but...

With 3.1.6 command line client, we're seeing (for example) .java files with multiple copies of the source included in one file in a GET operation.


We're not seeing this in the Windows GUI client.

Is this a known issue?

I've only tried with the one machine. When I get another RHELv3 installation completed, I'll try again and see.

Thanks!

I cleared the client cache and the result was the same, unfortunately.

Let me try that.

I've seen the error without the Mono errors, but the Vault stack trace is the same.