I upgrade from Vault 4.1 to 5.0 and tried to use the shelve feature.
I select a file from the pending changeset and select Shelve Selected Operations... After the dialog pops up I create a shelve set name and click the OK button. The cursor changes briefly and nothing happens.
The Vault database is SQL Server 2005 on Windows Server 2003 Standard Edition.
The Vault server is Windows Server 2003 Web Edition.
My client is Vista 64-bit.
I captured data out of the client and server logs.
A snippet of the client log:
8/5/2009 3:31:35 PM <mutex>: [Main:8592] Created mutex 2272 (Vault_CacheMember_ShelvesetItems_1729320931)
8/5/2009 3:31:35 PM <mutex>: [Main:8592] Took mutex 2272
8/5/2009 3:31:35 PM <cache>: [Main:8592] Did not UpdateObjectFromDisk in VaultClientOperationsLib.CacheMember_ShelvesetItems
8/5/2009 3:31:35 PM <cache>: [Main:8592] Cache file doesn't exist.
8/5/2009 3:31:35 PM <mutex>: [Main:8592] Released mutex 2272
8/5/2009 3:31:35 PM <mrd>: [Main:8592] Creating request for Modified: $/Sandbox/NFox/Test.txt; server-synched path for Modified: $/Sandbox/NFox/Test.txt is $/Sandbox/NFox/Test.txt
8/5/2009 3:31:35 PM <connection>: [Main:8592] BeginSaveShelveSet started.
8/5/2009 3:31:35 PM <connection>: [Main:8592] BeginSaveShelveSet finished.
8/5/2009 3:31:35 PM <upload>: [Main:8592] uploading item for shelve: c:\Nathan\CHKOUT\Sandbox\NFox\Test.txt
8/5/2009 3:31:35 PM <connection>: [Main:8592] UploadFile started.
8/5/2009 3:31:35 PM <connection>: [Main:8592] UploadFile finished.
8/5/2009 3:31:35 PM <eventengine>: [Main:8592] Event fired: VaultClientOperationsLib.ProgressChangedEvent
8/5/2009 3:31:36 PM <busy>: [GUIClientWorkerThread:8316] Setting GUI to unbusy from Shelve_Real.
8/5/2009 3:31:36 PM <repositoryexplorer>: [Main:8592] refresh requested updateKnown is False
From the server log:
----8/5/2009 3:31:35 PM Nfox--dev216.rc.inc(192.168.5.13)--SSL Disabled VaultFileUpload.aspx encountered: an error looking up the session's intermediate transaction object: FailFileTokenError
----8/5/2009 3:31:35 PM Nfox--dev216.rc.inc(192.168.5.13)--SSL Disabled Uncaught Exception: Exception of type 'System.Web.HttpUnhandledException' was thrown.
Inner Exception: 1500 : FailFileTokenError
----8/5/2009 3:31:35 PM Nfox--dev216.rc.inc(192.168.5.13)--SSL Disabled at System.Web.UI.Page.HandleError(Exception e)
at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
at System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
at System.Web.UI.Page.ProcessRequest()
at System.Web.UI.Page.ProcessRequestWithNoAssert(HttpContext context)
at System.Web.UI.Page.ProcessRequest(HttpContext context)
at ASP.vaultfileupload_aspx.ProcessRequest(HttpContext context)
at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)
Inner Exeption Stack Trace: at VaultService.VaultFileUpload.Page_Load(Object sender, EventArgs e)
at System.Web.UI.Control.OnLoad(EventArgs e)
at System.Web.UI.Control.LoadRecursive()
at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
If you could please let me know what I might try or what further information you need to help troubleshoot the issue.
Thank you
Shelve does not work
Moderator: SourceGear
Re: Shelve does not work
If you haven't done so already, could you send an email to support at sourcegear.com (attn: Beth) with a link to this forum thread?
Beth Kieler
SourceGear Technical Support
SourceGear Technical Support
Re: Shelve does not work
The cause of this problem turned out to be a missing key in the vault.config file.
Adding:
to the vault.config file, and restarting IIS solved the problem.
This issue will be fixed in 5.0.1.
Adding:
Code: Select all
<ShelveQryParam>ShelveToken</ShelveQryParam>
This issue will be fixed in 5.0.1.
Subscribe to the Fortress/Vault blog