Error checking in

If you are having a problem using Vault, post a message here.

Moderator: SourceGear

Post Reply
stefvanhooijdonk
Posts: 22
Joined: Thu Jan 19, 2006 10:05 am
Location: Tam Tam BV, The Netherlands
Contact:

Error checking in

Post by stefvanhooijdonk » Mon Nov 03, 2008 7:20 am

Got version 4.1.2 server and client.

When checking in a file i got this error.
This did not happen unitl 2 weeks ago.

Does this mean our DB is shot? And how do fix it ?

[3-11-2008 14:15:38] Checking out file $/VU/Portal/Mainline/VU/VU.Security/SSO.cs
[3-11-2008 14:15:38] Checked out file $/VU/Portal/Mainline/VU/VU.Security/SSO.cs
[3-11-2008 14:16:32] Preparing data to begin transaction
[3-11-2008 14:16:32] Beginning transaction
[3-11-2008 14:16:32] An error occurred while trying to begin a transaction.
[3-11-2008 14:16:32] Transaction failed
[3-11-2008 14:16:33] An exception was encountered during the transaction. Exception: Server was unable to process request. ---> Error creating reference copy for: Portal. It claimed to have no parents, but had some for revision 466396. at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
at VaultClientNetLib.ClientService.VaultService.BeginTx(Int32 nRepID, String strComment, VaultRequestItem[]& requests, String& strTxID)
at VaultClientNetLib.VaultConnection.BeginTx(Int32 nRepID, VaultRequestItem[]& requests, String& strTxID, String comment)
at VaultClientOperationsLib.ClientInstance.Commit(ChangeSetItemColl givenItems, String strChangeSetComment, Boolean keepCheckedOut, Boolean removeLocalCopy, CommitType committype, VaultDateTime dateImport, Int32 nUserIDImport, Int64& nRevID, Int32[]& retBegEndTx)
Stef


Architect/LeadDev @ Tam Tam
visit us at http://www.tamtam.nl

Beth
Posts: 8550
Joined: Wed Jun 21, 2006 8:24 pm
Location: SourceGear
Contact:

Re: Error checking in

Post by Beth » Mon Nov 03, 2008 11:18 am

This looks like something that was fixed in 4.1.3. Could you first upgrade to Vault 4.1.3 and let me know your results?

If it's still a problem, the do the following:
Go into the Help - Technical Support area of your client and copy the information from there an post it? The licensing information doesn't need to be posted.

Also, could I have your Vault Server Log? You can either post it here and remove it afterwards, or send it to support @ sourcegear.com (attn: Beth) with a link to this forum thread.
Beth Kieler
SourceGear Technical Support

Post Reply