Hi,
A couple of us were working with SG and our VS.NET IDE's hung on checkin operations. We gave it some time but the IDEs did not respond. We eventually shutdown the IDEs with Task Manager and also rebooted the SG server. Since then we have been unable to access the repository. Our SG Clients say "You have no rights to view any items in this repository" after logging in. Nothing appears in the Client window even though logging in appears to have worked. "Developer Source" is what we routinely use and is what we cannot access. On the server using the Vault Admin client we can log in we see the following: 1) Our two repositories appear on the Repositories tab, "Developer Source" and "Prodution - ECOMMDB1". Highlighting "Production - ECOMMDB1" and clicking "Properties" properly brings up the property window. (This repository also appears to be working fine with the Vault client). Trying to bring up properties for "Developer Source" fails with the following message:
"An unhandled exception has occured in your application... (snipped) 1104 : FailDBReader"
Details follow:
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.Web.Services.Protocols.SoapException: 1104 : FailDBReader
at VaultAdmin.AdminManager.HandleException(Exception e, Boolean bHandle, Boolean isSoap)
at VaultAdmin.AdminManager.LoadRepositoryProperties(Int32 repID)
at VaultAdmin.FormMain.CommandShowProperties()
at VaultAdmin.FormMain.buttonProperties_Click(Object sender, EventArgs e)
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnClick(EventArgs e)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
************** Loaded Assemblies **************
mscorlib
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.2032
CodeBase: file:///c:/windows/microsoft.net/framework/v1.1.4322/mscorlib.dll
----------------------------------------
VaultAdmin
Assembly Version: 3.0.1.2769
Win32 Version: 3.0.1.2769
CodeBase: file:///C:/Program%20Files/SourceGear/Admin%20Tool/VaultAdmin.exe
----------------------------------------
System.Windows.Forms
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.2032
CodeBase: file:///c:/windows/assembly/gac/system.windows.forms/1.0.5000.0__b77a5c561934e089/system.windows.forms.dll
----------------------------------------
System
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.2032
CodeBase: file:///c:/windows/assembly/gac/system/1.0.5000.0__b77a5c561934e089/system.dll
----------------------------------------
VaultPresentationLib
Assembly Version: 3.0.1.2769
Win32 Version: 3.0.1.2769
CodeBase: file:///C:/Program%20Files/SourceGear/Admin%20Tool/VaultPresentationLib.DLL
----------------------------------------
System.Drawing
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.2032
CodeBase: file:///c:/windows/assembly/gac/system.drawing/1.0.5000.0__b03f5f7f11d50a3a/system.drawing.dll
----------------------------------------
VaultLib
Assembly Version: 3.0.1.2769
Win32 Version: 3.0.1.2769
CodeBase: file:///C:/Program%20Files/SourceGear/Admin%20Tool/VaultLib.DLL
----------------------------------------
VaultClientUILib
Assembly Version: 3.0.1.2769
Win32 Version: 3.0.1.2769
CodeBase: file:///C:/Program%20Files/SourceGear/Admin%20Tool/VaultClientUILib.DLL
----------------------------------------
VaultClientNetLib
Assembly Version: 3.0.1.2769
Win32 Version: 3.0.1.2769
CodeBase: file:///C:/Program%20Files/SourceGear/Admin%20Tool/VaultClientNetLib.DLL
----------------------------------------
System.Web.Services
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.2032
CodeBase: file:///c:/windows/assembly/gac/system.web.services/1.0.5000.0__b03f5f7f11d50a3a/system.web.services.dll
----------------------------------------
VaultClientOperationsLib
Assembly Version: 3.0.1.2769
Win32 Version: 3.0.1.2769
CodeBase: file:///C:/Program%20Files/SourceGear/Admin%20Tool/VaultClientOperationsLib.DLL
----------------------------------------
System.Xml
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.2032
CodeBase: file:///c:/windows/assembly/gac/system.xml/1.0.5000.0__b77a5c561934e089/system.xml.dll
----------------------------------------
System.Web
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.2037
CodeBase: file:///c:/windows/assembly/gac/system.web/1.0.5000.0__b03f5f7f11d50a3a/system.web.dll
----------------------------------------
7awq4fe-
Assembly Version: 0.0.0.0
Win32 Version: 1.1.4322.2032
CodeBase: file:///c:/windows/assembly/gac/system/1.0.5000.0__b77a5c561934e089/system.dll
----------------------------------------
w4urqlki
Assembly Version: 0.0.0.0
Win32 Version: 1.1.4322.2032
CodeBase: file:///c:/windows/assembly/gac/system/1.0.5000.0__b77a5c561934e089/system.dll
----------------------------------------
System.Management
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.2032
CodeBase: file:///c:/windows/assembly/gac/system.management/1.0.5000.0__b03f5f7f11d50a3a/system.management.dll
----------------------------------------
vs
Assembly Version: 1.0.1808.31550
Win32 Version: 1.0.1808.31550
CodeBase: file:///C:/Program%20Files/SourceGear/Admin%20Tool/vs.DLL
----------------------------------------
************** JIT Debugging **************
To enable just in time (JIT) debugging, the config file for this
application or machine (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.
For example:
<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>
When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the machine
rather than being handled by this dialog.
-----------------------------------
Clicking "Continue" does nothing but give us an hour glass.
When clicking the "Folder Security" tab on the Vault Admin client, and selecting "Production - ECOMMDB1", the list populates with what we would expect to see. When selecting "Developer Source", nothing appears in the windows.
-- We had happened to have debug on so i found this in the log around the problems started:
----7/9/2005 3:13:20 PM eric--(snipped)--SSL Enabled Getting repository Structure.
----7/9/2005 3:13:20 PM eric--(snipped)--SSL Enabled GetRepositoryStructure returned: Success
----7/9/2005 3:13:20 PM eric--(snipped)--SSL Enabled Getting list of checkout changes.
----7/9/2005 3:13:21 PM eric--(snipped)--SSL Enabled Violation of PRIMARY KEY constraint 'PK__#tbltreerevfolde__573DE937'. Cannot insert duplicate key in object '#tbltreerevfolders__________________________________________________________________________________________________000100000419'.
The statement has been terminated.
----7/9/2005 3:13:21 PM eric--(snipped)--SSL Enabled GetCheckOutListChanges returned: FailDBReader
Your help would greatly be appreciated!
-Eric Johnson
URGENT - Users Cannot Access Repository
Moderator: SourceGear
- What version of the server are you running?
- Can you send me (click the email button below) the sgvault.log file? I'd like to look for any other errors.
If you need to be up to speed immediately, you could temporarily disable folder security on the repository. Don't worry, you will not lose your current security rights, they are just not checked for the time being.
On Monday, I'll have the tools available to take a look at your log file / database to get an idea of where we can go from here.
- Can you send me (click the email button below) the sgvault.log file? I'd like to look for any other errors.
If you need to be up to speed immediately, you could temporarily disable folder security on the repository. Don't worry, you will not lose your current security rights, they are just not checked for the time being.
On Monday, I'll have the tools available to take a look at your log file / database to get an idea of where we can go from here.
Jeff Clausius
SourceGear
SourceGear
The reboot happened during a share operation, causing the repository to not have all the information.
There is an issue rectified in Vault 3.1 where sharing an item in a path that has shared folders within shared folders within shared folders... seems to lock the server. The server is not locked, but in a tight, inefficient loop calculating all the new paths to the newly shared item. This case is now optimized in Vault 3.1
There is an issue rectified in Vault 3.1 where sharing an item in a path that has shared folders within shared folders within shared folders... seems to lock the server. The server is not locked, but in a tight, inefficient loop calculating all the new paths to the newly shared item. This case is now optimized in Vault 3.1
Jeff Clausius
SourceGear
SourceGear