Transaction failed error

tomt84 · Post by **tomt84** » Sun Feb 12, 2006 11:51 am

Just trying to check our modified installation of SugarCRM into Vault - not done this before. It's going in to a new repository.

Error messages reproduced below.

Client version 3.1.5. The client and the Vault service were both installed on the same machine in this instance.

Thanks for any input.

Code: Select all

[12/02/2006 17:36:23]     Upload for item $/sugarcrm/cache/modules/Schedulers/pid.php failed, retrying...
[12/02/2006 17:36:23]     Upload for item $/sugarcrm/cache/modules/Schedulers/pid.php failed, retrying...
[12/02/2006 17:36:23]     Upload for item $/sugarcrm/cache/modules/Schedulers/pid.php failed, retrying...
[12/02/2006 17:36:23] Upload for item $/sugarcrm/cache/modules/Schedulers/pid.php failed too many times, aborting transaction.  
        Please verify your network settings using the Options dialog under the Tools menu in the Vault GUI Client.  
        The specific error was "The server returned an unknown error header: VaultFileUpload.aspx encountered:  FailFileInvalidCheckSum"
An exception was encountered during the transaction.  Exception: The server returned an unknown error header: VaultFileUpload.aspx encountered:  FailFileInvalidCheckSum   at VaultClientOperationsLib.ClientInstance.UploadItem(ChangeSetItem item, String txID, Byte[]& streamBuffer, Int32& bytesWrittenThisFile, Boolean bIsImport)
   at VaultClientOperationsLib.UploadThread.ProcessCommand(UploadThreadCommand command, UploadThreadCommandResult& outputResult)
[12/02/2006 17:37:00] Ending the transaction
[12/02/2006 17:37:00] Transaction failed
[12/02/2006 17:37:00] Transaction failed
[12/02/2006 17:37:01]     Upload for item $/sugarcrm/cache/upload/2300b8c2-bcab-13f6-7f41-43e09fa827a08031 installation notes.doc failed, retrying...
[12/02/2006 17:37:01]     Upload for item $/sugarcrm/cache/upload/2300b8c2-bcab-13f6-7f41-43e09fa827a08031 installation notes.doc failed, retrying...
[12/02/2006 17:37:01]     Upload for item $/sugarcrm/cache/upload/2300b8c2-bcab-13f6-7f41-43e09fa827a08031 installation notes.doc failed, retrying...
[12/02/2006 17:37:01] Upload for item $/sugarcrm/cache/upload/2300b8c2-bcab-13f6-7f41-43e09fa827a08031 installation notes.doc failed too many times, aborting transaction.  
        Please verify your network settings using the Options dialog under the Tools menu in the Vault GUI Client.  
        The specific error was "The server returned an unknown error header: VaultFileUpload.aspx encountered:  an error looking up the session's intermediate transaction object: FailFileTokenError"
An exception was encountered during the transaction.  Exception: The server returned an unknown error header: VaultFileUpload.aspx encountered:  an error looking up the session's intermediate transaction object: FailFileTokenError   at VaultClientOperationsLib.ClientInstance.UploadItem(ChangeSetItem item, String txID, Byte[]& streamBuffer, Int32& bytesWrittenThisFile, Boolean bIsImport)
   at VaultClientOperationsLib.UploadThread.ProcessCommand(UploadThreadCommand command, UploadThreadCommandResult& outputResult)

Post by **jclausius** » Sun Feb 12, 2006 10:17 pm

From the looks of the client, its as if the Vault server was restarted during your upload.

Can you check the Vault Server Log to see what kind of problems it is reporting.

tomt84 · Post by **tomt84** » Mon Feb 13, 2006 7:21 am

060212sgvault.log just contains the line:

# SourceGear Vault Server
and nothing else.

The previous file finishes at 11/02/06 - the day before the problem.

The Windows application event log was reporting a missing key logFilePath in web.config as a critical error, so I added one a couple of days ago:

<add key="logFilePath" value="C:\Inetpub\wwwroot\vaultService\vault.log" />

This hasn't stopped the error message in the event log. Could be totally unrelated.

Should I put the server into debug logging mode and try the checkin again?

Post by **jclausius** » Mon Feb 13, 2006 9:10 am

The Vault Server installation should have created the path / set permissions on the log file. Do you recall if there was a problem during Server installation?

If you're not using impersonation, can you give the local ASPNET or NETWORK SERVICE account read/write permissions on C:\Inetpub\wwwroot\vaultService.

tomt84 · Post by **tomt84** » Mon Feb 13, 2006 9:15 am

I don't remember there being a problem during installation.

We're not using impersonation - I've set the NETWORK SERVICE account to have r/w permissions on that folder.

Was I right to modify the web.config file as I did to include that line?

The initial problem has now gone - I just tried again and it worked fine.

Like I said, the client and the server were both on the same machine and I was the only user connected to the dev box so it's an impossibility that IIS was restarted during the transaction without my knowledge.

Cheers for your help

Post by **jclausius** » Mon Feb 13, 2006 9:38 am

tomt84 wrote:Was I right to modify the web.config file as I did to include that line?

That should be fine. If the logging is working correctly, and you can produce the error again, you should be able to capture more information about the problem and let us know.

Post by **jclausius** » Mon Feb 13, 2006 9:41 am

Since we're on the topic of permissions. Within the Admin Tool, you will see a setting the Vault Server uses for a working directory. Verify the NETWORK SERVICE account has full control in that directory otherwise you will see all kinds of errors including errors when uploading files to the server.

tomt84 · Post by **tomt84** » Mon Feb 13, 2006 9:51 am

The reported effective permissions for Network Service over c:\windows\temp (the working directory reported by the admin tool) are:

ticked:
Traverse Folder / Execute File
List Folder / Read Data
Read Attribs
Read Extended Attribs
Create Files / Write Data
Create Folders / Append Data
Write Attribs
Write Extended Attribs
Read permissions

unticked:
full control
Delete subfolders and files
delete
Change permissions
Take ownership

and for the same over c:\windows\temp\sgvault - nothing explicitly defined on sgvault.