Shelve doesn't work.

[lynnroth]

I am having some issues with the Shelve feature.

I am running version 2.0.0.18701

When I try to Shelve something, it fails silently. In the Visual Studio client, the Shelve window goes away, but nothing happens. In the regular client, after clicking the shelve button it goes into hourglass cursor for a few seconds and then comes back. Nothing happens and the window doesn't go away.

The server log shows these errors:

----8/6/2009 7:29:40 AM admin--canyon(10.5.0.)--SSL Disabled Login
----8/6/2009 7:30:03 AM admin--canyon(10.5.0.)SSL Disabled VaultFileUpload.aspx encountered: an error looking up the session's intermediate transaction object: FailFileTokenError
----8/6/2009 7:30:03 AM admin--canyon(10.5.0.)--SSL Disabled Uncaught Exception: Exception of type 'System.Web.HttpUnhandledException' was thrown.
Inner Exception: 1500 : FailFileTokenError
----8/6/2009 7:30:03 AM admin--canyon(10.5.0.)--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)


Is there anything I can check?

Thanks,
Lynn

[lbauer]

We've had a couple other reports of this error and we're looking into it. Could you post the information in the Fortress GUI Client under Help->Technical Support?

Is this a new installation of Fortress, or did you upgrade from a previous version?

Is some of the data from a VSS import?

[lynnroth]

This is an upgrade. (From 1.1.4)
The initial data from 4+ years ago was VSS.

Here is the info you requested:

Client Information
Fortress Client Version: 2.0.0.18701
.Net Framework Version: 2.0.50727.3074
Operating System: Microsoft® Windows Vista™ Ultimate
Service Pack: 1.0
OS Version: 6.0.6001
Total Physical Memory: 8 GB
Time Zone: (GMT-05:00) Eastern Time (US & Canada)

Server Information
Fortress Server Version: 2.0.0.18701
.Net Framework Version: 2.0.50727.3082
Operating System: Microsoft(R) Windows(R) Server 2003, Web Edition
Service Pack: 2.0
OS Version: 5.2.3790
Timezone: (GMT-05:00) Eastern Time (US & Canada)
SQL Version: Microsoft SQL Server 2005 - 9.00.4035.00 (Intel X86)
Nov 24 2008 13:01:59
Copyright (c) 1988-2005 Microsoft Corporation
Standard Edition on Windows NT 5.2 (Build 3790: Service Pack 2)

License Information
11 serial number(s):
1 of 11: 1 full users, permanent
2 of 11: 1 full users, permanent
3 of 11: 1 full users, permanent
4 of 11: 10 web-only users, permanent
5 of 11: 1 full users, permanent
6 of 11: 1 web-only users, permanent
7 of 11: 1 full users, permanent
8 of 11: 1 web-only users, permanent
9 of 11: 1 full users, permanent
10 of 11: 12 web-only users, permanent
11 of 11: 6 full users, permanent

[jeremy_sg]

Hi Lynn,

We've had three reports of shelve upload failures so far, all with the same behavior. We haven't seen it here yet, so I need to ask some general questions.

1. What types of changes are you shelving? Add file? File edits?

2. Are other checkins and add files working?

3. Can you check your IIS log file for a call to VaultFileUpload.aspx? A successful call looks like this:

2009-08-06 13:53:44 ::1 POST /VaultService/VaultFileUpload.aspx ShelveToken=02d523bd-0e5a-42dd-9c35-4713443f1dfc&FileToken=2aa0f65e-e9aa-4fb0-81e4-06d057d1a377 80 - ::1 - 200 0 0 867

[lynnroth]

1. What types of changes are you shelving? Add file? File edits?
I have tried shelving file edits.

2. Are other checkins and add files working?
Other checkins are working fine. Adding files works fine as well.

3. Can you check your IIS log file for a call to VaultFileUpload.aspx? A successful call looks like this:

Here is the one related to the log entry earlier.
2009-08-06 11:30:03 10.5.0.150 POST /VaultService/VaultFileUpload.aspx ShelveToken=74cee821-56f6-464b-bb64-6aba190e15b7&FileToken=6c9670a1-f322-4524-aa67-3dbbb45a2f26 80 - 10.5.0.222 - 400 0 0

[jeremy_sg]

Sorry to keep asking general questions, but does the shelve work if you try it on the server connecting to localhost?

[lynnroth]

Some behavior as I am getting on the other machines.

[jeremy_sg]

Hrm...

Can you turn on client logging and Debug server logging?

Thanks.

[lynnroth]

Ok. Both are turned on.

The server log shows the same thing that my initial post showed.

The client log is around 1300 lines. Can I email them both to you?

[jeremy_sg]

Yes, please email them to support at sourcegear.com ATTN: jeremy with a link to this thread.

[jeremy_sg]

The cause of this problem turned out to be a missing key in the vault.config file.

Adding:

Code: Select all

<ShelveQryParam>ShelveToken</ShelveQryParam>

to the vault.config file, and restarting IIS solved the problem.

This issue will be fixed in 5.0.1.