Cannot Add New File

[pogaz]

Some of our users have started having a problem where they cannot add new files to the repository, where they were able to do so before. What we've just discovered is that the file just sits in the "Pending Change Set" and if they keep trying to commit the file by right-clicking on it in the "Pending Change Set" list and choosing "Commit Selected Operation" it will go through.

The first user that had this problem, we were able to temporarily resolve it (they had to get some very critical work done) by creating a new account for them; it eventually started happening again. We had tried the following with none of them being successful:
1. Re-installing the Vault client
2. Clearing cache files
3. Committing various types of test files (e.g. .txt and .c files)
4. Using a different machine where the problem definitely did not exist for that different user

We had also tried using the Vault client on the user's machine but as a different user that had not experienced the problem and the different user was able to add the file successfully.

Here are the versions that we are using:

Server: SourceGear Vault, Version 4.1.0.16216
Client: 4.1.4 (18402)

Any help is appreciated.

Paul

[lbauer]

Is only one user having this problem?

Are they checking in from the Vault GUI Client or Visual Studio?

The first thing we'd suggest is to have the user check to see if Auto-Commits are disabled. This setting is in the Vault Client under Tools->Options->Concurrent Development Style. Items are added to the pending change set if they are not automatically committed and have to be committed manually. The setting is stored in theVault database, so uninstalling and reinstalling the client doesn't change it.

If that's not the problem, are there any errors in the Messages pane of the Vault GUI Client or the Output of Visual Studio?

Are there any errors in the Vault Server log that correspond to the problem? It's called sgvault.log and is in %windir%\temp\sgvault on the server machine.

[pogaz]

I saw this old post of mine and thought I should put a "closing" reply to it (I had gone on holiday a day or so after the original post)--

The problem ended up going away. It's been so long now, I don't recall what resolved it. I think we uninstalled the client and manually removed the directories for the client and then reinstalled.

Thanks.

[Beth]

Thank you for the update. I'm happy to hear it's working for you. If it ever happens again, just let us know.