Vault 5.1.1: FailDBReader when branch
Moderator: SourceGear
Vault 5.1.1: FailDBReader when branch
When I developer attempts to create a new branch out of an existing folder. The process failed
[6/12/2012 7:47:47 PM] Preparing data to begin transaction
[6/12/2012 7:47:47 PM] Beginning transaction
[6/12/2012 7:47:51 PM] Branch $/branches/7.0
[6/12/2012 7:47:51 PM] Ending the transaction
[6/12/2012 7:48:07 PM] Transaction failed
[6/12/2012 7:48:07 PM] An error occurred while trying to end a transaction.
[6/12/2012 7:48:07 PM] Transaction failed
[6/12/2012 7:48:07 PM] Item $/branches/7.0 caused the transaction to fail: A database error has occured (FailDBReader)
The 7.0 folder is 1.09GB and has many different layers of sub-folders.
Any idea why? Is there any settings that we have to change?
Also want to add:
1) The 7.0 folder has the .sln
2) There is a label at 7.0 folder level
Not sure if it is or isn't recommended to branch such folder.
[6/12/2012 7:47:47 PM] Preparing data to begin transaction
[6/12/2012 7:47:47 PM] Beginning transaction
[6/12/2012 7:47:51 PM] Branch $/branches/7.0
[6/12/2012 7:47:51 PM] Ending the transaction
[6/12/2012 7:48:07 PM] Transaction failed
[6/12/2012 7:48:07 PM] An error occurred while trying to end a transaction.
[6/12/2012 7:48:07 PM] Transaction failed
[6/12/2012 7:48:07 PM] Item $/branches/7.0 caused the transaction to fail: A database error has occured (FailDBReader)
The 7.0 folder is 1.09GB and has many different layers of sub-folders.
Any idea why? Is there any settings that we have to change?
Also want to add:
1) The 7.0 folder has the .sln
2) There is a label at 7.0 folder level
Not sure if it is or isn't recommended to branch such folder.
Re: Vault 5.1.1: FailDBReader when branch
Could you either post or send me your Vault Server Log found at %windir%\temp\sgvault\sgvault.log? That should provide more information as to the root cause of the issue.
Alternatively, you can look in the log and the errors should be fairly clear.
Alternatively, you can look in the log and the errors should be fairly clear.
Beth Kieler
SourceGear Technical Support
SourceGear Technical Support
Re: Vault 5.1.1: FailDBReader when branch
This is all it shows on the vault server log:Beth wrote:Could you either post or send me your Vault Server Log found at %windir%\temp\sgvault\sgvault.log? That should provide more information as to the root cause of the issue.
Alternatively, you can look in the log and the errors should be fairly clear.
----6/12/2012 6:56:23 PM bjohn--<machinename>(machineIP)--SSL Disabled (4943a98e-f938-40ff-84fd-22b3dc046ef6) EndTx (Revision - 0) returned: FailDBReader
Re: Vault 5.1.1: FailDBReader when branch
Check your SQL Server logs and your Event Viewer logs on the Vault server and the SQL Server. Are there any errors there?
Beth Kieler
SourceGear Technical Support
SourceGear Technical Support
Re: Vault 5.1.1: FailDBReader when branch
SQL Server log - nothing on 6/12/2012
Vault server event (application) log has this warning:
Vault server event (application) log has this warning:
Event Type: Warning
Event Source: ASP.NET 2.0.50727.0
Event Category: Web Event
Event ID: 1309
Date: 6/12/2012
Time: 5:55:07 PM
User: N/A
Computer: Servername
Description:
Event code: 3005
Event message: An unhandled exception has occurred.
Event time: 6/12/2012 5:55:07 PM
Event time (UTC): 6/12/2012 9:55:07 PM
Event ID: a576519b8cd24251b1cc9412035827d9
Event sequence: 28760
Event occurrence: 2
Event detail code: 0
Application information:
Application domain: /LM/W3SVC/1707013962/Root/VaultService-1-129836462994059890
Trust level: Full
Application Virtual Path: /VaultService
Application Path: C:\inetpub\wwwroot\VaultService\
Machine name: Servername
Process information:
Process ID: 900
Process name: w3wp.exe
Account name: NT AUTHORITY\NETWORK SERVICE
Exception information:
Exception type: OutOfMemoryException
Exception message: Exception of type 'System.OutOfMemoryException' was thrown.
Request information:
Request URL: http://servername/VaultService/VaultService.asmx
Request path: /VaultService/VaultService.asmx
User host address: IP
User:
Is authenticated: False
Authentication Type:
Thread account name: NT AUTHORITY\NETWORK SERVICE
Thread information:
Thread ID: 1
Thread account name: NT AUTHORITY\NETWORK SERVICE
Is impersonating: False
Stack trace: at System.Globalization.TextInfo.nativeChangeCaseString(Int32 win32LangID, Void* pNativeTextInfo, String str, Boolean isToUpper)
at System.Globalization.TextInfo.ToLower(String str)
at System.String.ToLower(CultureInfo culture)
at VaultLib.VaultRequestItem.set_ItemPath(String value)
at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationReader1.Read45_VaultRequestGetFile(Boolean isNullable, Boolean checkType)
at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationReader1.Read138_BeginDownloadFiles()
at Microsoft.Xml.Serialization.GeneratedAssembly.ArrayOfObjectSerializer84.Deserialize(XmlSerializationReader reader)
at System.Xml.Serialization.XmlSerializer.Deserialize(XmlReader xmlReader, String encodingStyle, XmlDeserializationEvents events)
at System.Xml.Serialization.XmlSerializer.Deserialize(XmlReader xmlReader, String encodingStyle)
at System.Web.Services.Protocols.SoapServerProtocol.ReadParameters()
at System.Web.Services.Protocols.WebServiceHandler.CoreProcessRequest()
at System.Web.Services.Protocols.SyncSessionlessHandler.ProcessRequest(HttpContext context)
at System.Web.Script.Services.ScriptHandlerFactory.HandlerWrapper.ProcessRequest(HttpContext context)
at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)
Custom event details:
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Re: Vault 5.1.1: FailDBReader when branch
Today, another user is seeing error "Exception of type "System.OutOfMemoryException" was thrown" after the connection timed out with Vault Server. He saw the error message above on his Vault Client pop up window.
I see the following error on vault server event log:
I see the following error on vault server event log:
Event Type: Error
Event Source: ASP.NET 2.0.50727.0
Event Category: None
Event ID: 1334
Date: 6/14/2012
Time: 1:17:21 PM
User: N/A
Computer: Servername
Description:
An unhandled exception occurred and the process was terminated.
Application ID: /LM/W3SVC/1707013962/Root/VaultService
Process ID: 364
Exception: System.OutOfMemoryException
Message: Exception of type 'System.OutOfMemoryException' was thrown.
StackTrace: at System.Threading.ExecutionContext.CreateCopy()
at System.Threading._TimerCallback.PerformTimerCallback(Object state)
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Re: Vault 5.1.1: FailDBReader when branch
I agree that appears to be the root cause.
What is the OS of the machine the Vault server is on.
Does SQL Server on the same machine or a different machine?
What are the specs of the machine the Vault server runs on? For example, what is it's RAM, free disk space, virtual RAM, etc.
What is the OS of the machine the Vault server is on.
Does SQL Server on the same machine or a different machine?
What are the specs of the machine the Vault server runs on? For example, what is it's RAM, free disk space, virtual RAM, etc.
Beth Kieler
SourceGear Technical Support
SourceGear Technical Support
Re: Vault 5.1.1: FailDBReader when branch
OS vault server - windows server 2003, 2GB RAM, free diskspace ~ 1GBBeth wrote:I agree that appears to be the root cause.
What is the OS of the machine the Vault server is on.
Does SQL Server on the same machine or a different machine?
What are the specs of the machine the Vault server runs on? For example, what is it's RAM, free disk space, virtual RAM, etc.
SQL server is on a separated machine - windows server 2003 as well, SQL 2005
I figured out the problem. It doesn't happen anymore after I dedicated to it a separate App Pool.
Thanks, Beth!
Re: Vault 5.1.1: FailDBReader when branch
Thank you for the update. I'm happy to hear you are working again.
Beth Kieler
SourceGear Technical Support
SourceGear Technical Support