We cannot commit to one of repositories.

Yuri Ilyin · Post by **Yuri Ilyin** » Thu May 12, 2005 6:01 am

Dear support team.

We use SourceGear Vault Client Version 3.0.5(2833) and Vault Server Version 3.0.5
We have rather large repository
[revision 14133, 22593 files] and today we have faced with the problem

[12.05.2005 15:42:45] Preparing data to begin transaction
[12.05.2005 15:42:45] Beginning transaction
[12.05.2005 15:42:45] Server unavailable for transaction begin
[12.05.2005 15:42:45] Transaction failed
[12.05.2005 15:42:45] An exception was encountered during the transaction. Exception: Server was unable to process request. --> Error in the application. 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, Boolean keepCheckedOut, Boolean removeLocalCopy, Boolean bIsImport, DateTime dateImport, Int32 nUserIDImport, Int64& nRevID)

I.e. we CANNOT commit files, which were checked out.

We have several repositories on Vault server and we can commit to another (smaller) repository.

What can be a problem?

I have tried to enable LOG in VaultGUIClient.exe.config and I can see the error in LOG file, please see the attachement

Please reply as soon as possible!

{attachement has been deleted after solving the problem}

lbauer · Post by **lbauer** » Thu May 12, 2005 6:52 am

Is there anything in the server log file that corresponds to this error? The log is in the %windir%\temp\sgvault directory.

Yuri Ilyin · Post by **Yuri Ilyin** » Thu May 12, 2005 7:14 am

Yes, there are many error reports in the server's log.

Please look at the attachment
{attachement has been deleted after solving the problem}

lbauer · Post by **lbauer** » Thu May 12, 2005 7:26 am

Looks like there are some dictionary errors. Could you send me your email address and phone number and we'll have one of our developers contact you directly.

lbauer · Post by **lbauer** » Thu May 12, 2005 7:27 am

Email linda at SourceGear.com.

Yuri Ilyin · Post by **Yuri Ilyin** » Thu May 12, 2005 7:33 am

Dear lbauer

I do not know Linda's email.

I have sent my contact information to your email.

Yuri Ilyin · Post by **Yuri Ilyin** » Thu May 12, 2005 7:36 am

My email, MSN messager can be visible also from my profile.

Post by **jclausius** » Thu May 12, 2005 8:22 am

Let's see if you were affected by a problem which was can be prevented by using Vault 3.0.7. Unfortunately, once you encounter this problem Vault 3.0.7 will not help.

Can you restart IIS (iisreset.exe). Next connect with a Vault GUI client. After this, browse the list of repositories (File->Choose Repository). Is the repository missing?

Yuri Ilyin · Post by **Yuri Ilyin** » Thu May 12, 2005 8:35 am

I have followed the suggested steps.

I still can see the problematic repository in Ctrl+P (File->Choose Repository), I can connect to it and even get the latest version.

But I cannot make any modifications (commit, delete and etc).

(and no problems in other smaller repositiories).

Post by **jclausius** » Thu May 12, 2005 8:45 am

OK. If you can see the repository, let's see if we can get a clean look at what is happening.

1) Clearing client side cache. After shutting down all IDE clients as well as all Vault GUI clients, delete CacheMember_Repository and CacheMember_LastStructureGetDate from the %APPDATA%\SourceGear\Vault_1\Client\* directories.

2) Assuming IIS has already been restarted from above, now connect with the client where the cache was cleared. Once the repository has been loaded, try a quick add folder.

If step 2 fails, can you send your sgvault.log from the point of the restart. You should see a "System Started" message in your sgvault.log.

Yuri Ilyin · Post by **Yuri Ilyin** » Thu May 12, 2005 9:18 am

I have deleted everything from
"%APPDATA%\SourceGear\Vault_1\Client\FB2EEF8B-4921-4DDF-B1FF-411ADF132A26\Yuri_Ilyin\"
directory, including _sgvault directory (the size of deleted files was about 2GB).

But now I can see the dialog box "You have no rigths to view any items it this repository" when I try to login to the problematic repository.
(a person near me, who did not delete temporary files, can login to the problematic repository and we did not change permissions on Vault Server).

Post by **jclausius** » Thu May 12, 2005 9:27 am

OK. This is the problem I mentioned above. This will take a couple of go arounds with the sgvault database on your SQL Server.

If you would prefer to use email, just click the email link below.

Let's see what is going on. I'll need results for the following queries.

1) SELECT repid, name, currenttxid FROM sgvault.dbo.tblrepositories

2) SELECT x.repid, x.txid FROM sgvault.dbo.tblfulltreerevisionfolders x WHERE EXISTS ( SELECT y.repid FROM sgvault.dbo.tblrepositories y WHERE y.repid = x.repid AND y.currenttxid = x.txid )

3) SELECT COUNT(x.treelevel) FROM sgvault.dbo.tbltreerevisionfolders x WHERE EXISTS ( SELECT y.repid FROM sgvault.dbo.tblrepositories y WHERE y.currenttxid = x.txid )

Post by **jclausius** » Thu May 12, 2005 2:59 pm

This was resolved offline.

They hit a transaction integrity problem in the server. Incidentally, this problem is avoidable by upgrading the Vault Server to 3.0.7.

Yuri Ilyin · Post by **Yuri Ilyin** » Thu May 12, 2005 11:53 pm

Yes. Now it works.

Thank you very much.

SourceGear Support

We cannot commit to one of repositories.

We cannot commit to one of repositories.

Yes, there is