Vault 4.12, check in failed (_htFolderEntries did not conta)

[Tri]

Hi,

This is URGENT. Would appreciate a quick solution as people are waiting for checking code.
This occurred a week after we upgraded from v3.53 to 4.12.

In MyBusinessProject, we can check out and undo check out. But a check in always get an error:

An exception was encountered during the transaction.
Exception: Server was unable to process request. --->
Error deleting from <OurRepositoryName>: _htFolderEntries did not contain an entry for MyBusinessProject. But it did have the following keys {a comma delimited list of may folders in OurRepositoryName } 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)


I have attempted solution suggested in other posts (Delete the MyBusinessProject folder and undelete it). Moving the MyBusinessProject folder to another place (still same check in error). Move the folder back to it's original location. The check in error is systematically reproducible regardless where we move it. This folder is shared to two other folders, not sure if it is the cause of the check in error.

Question: why would a check in attempts to delete something from the repository? (Error deleting from <OurRepositoryName>) and more importantly, can you please suggeste a work around? Sorry cannot mail/ftp you the DB as it would take time. We would like to fix this quick.

Thanks in advance.

[jeremy_sg]

Tri,

This bug is addressed in 4.1.3. Initially, an iisreset operation on the server should get you working again. As for a checkin deleting objects, it's deleting the old version of the object and inserting a new version of the object.

If you would like a 4.1.3 prerelease server, please email support at sourcegear.com ATTN: jeremy with a link to this thread.

[Tri]

Thanks for the quick answer, an IISReset did solve the issue. We can survive with this work around while waiting for 4.13. Do you have an approx release date?

[jeremy_sg]

All of the coding has been done, and we're verifying fixes now. We should release it "very soon".

[davenovak]

I am using Vault 4.1.4.18402 and just ran into this same exact issue. Steps to reproduce for us are:

• Create new branch in root (e.g., $/Global Services 9.2.0, branched from $/Global Services 9.1.0)
• Check out some file under $/Global Services 9.2.0
• Rename $/Global Services 9.2.0 to $/Global Services 10.0.0
• Check in your file -- ERROR

As in the case previously reported, an IISRESET seems to have fixed the issue.

Apparently this was not fixed then in Vault 4.13??? Is this a known issue in Vault 4.1.x???

Any information about this bug would be appreciated.

Thanks

[jeremy_sg]

It's likely that you're seeing a different manifestation of the same error message. Does an iisreset on the server fix the problem for you?

[davenovak]

Yes, as stated in my post, "an IISRESET seems to have fixed the issue."

Looks like this problem needs to be resubmitted to the defect queue.