Visaul Studio 2013 busy when checking out

[gregch]

I have vault professional 9.1. If I try to check out in VS 2013/2012, Visual Studio reports busy

I am running Visual Studio on a VMWare virtual machine, and running code on a shared folder on my host machine. The shared folder is full trust. Both machines are Windows 10 professional.

The interesting thing is that I can edit a bound file in a text editor, Vault Professional Client (on the Virtual Machine)will allow me to check the file in. But doing this through Visual Studio will always hang.

The source control repository is on the host machine

I did get this error reported in Vault Professional Client, not sure if related:

Exception: The web service method BeginTx returned some invalid results, but the server indicated no error. 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)

[jclausius]

Have you tried a setup where the local files are on the Guest OS are mapped to just a normal drive within the VM, and not to a mapped/shared folder with the Host OS?

[gregch]

Yes, that works fine. That is the way I was working. I am trying centralize code, because I have other virtual machines.

[jclausius]

Unfortunately, the working folders are tied to cache information stored and used by each client. The Client libraries were not designed to have different clients in multiple environments working off the same cache or stored over a network share. See:

http://kb.sourcegear.com/FortressHelp/v ... 495#p14726
http://kb.sourcegear.com/FortressHelp/v ... 37d10fe67b
http://kb.sourcegear.com/FortressHelp/v ... dd324af31a

You might be able to get by with storing the _sgvault cache folders inline with the working folder, but would recommend only running a single Vault client at a time. I believe the third link (the first two posts) provide some additional information on storing working folder state and baseline information in the working folders themselves.