Env change requiring to uncheck "Use chunked encoding&q

[Guest]

Hi,

We're using 2.0.6 client & server version of vault in w2k sp4 .net 1.1 without sp1.
This morning none of our users could upload any of their changes to the internal vault web server.

After calling support, it was suggested that we uncheck "use chunked encoding". That resolved our issue but after realizing the impact of this change, we'd rather not do that and investigate instead what could have caused this issue.

There's no proxy to access our internal vault web server...any other leads or further pointers on the requirements of this feature?

Sincerely
Mario Karagiorgas
Robert Mondavi Corp
707-251-4174

[nethatix]

Hi, (here's some more info)

Here's what the client is saying:
Upload for item $/RMC/SQL/BDN/StoredProcedures/ProcCubeProcess.sp 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 remote server returned an error: (404) Not Found."
the server is in debug mode:
----10/4/2004 5:39:04 PM mariok--mariok-d530s.robertmondavi.com(192.168.107.163)--SSL Disabled
BeginTx returned: Success
----10/4/2004 5:39:04 PM mariok--mariok-d530s.robertmondavi.com(192.168.107.163)--SSL Disabled
VaultServiceBase.VaultRequestCheckIn returned: Success
----10/4/2004 5:39:04 PM mariok--mariok-d530s.robertmondavi.com(192.168.107.163)--SSL Disabled
Ending transaction
----10/4/2004 5:39:04 PM mariok--mariok-d530s.robertmondavi.com(192.168.107.163)--SSL Disabled
EndTxSuccess

We've tried with the net options on the client as "use default proxy" or "use no proxy".
In addition the IIS settings (anonymous ok), temp requirements are ok for the asp.net user.

[jeremy_sg]

Can you see the web page http://VAULTSERVER/VaultService/VaultFileUpload.aspx

[nethatix]

Server Error in '/VaultService' Application.
--------------------------------------------------------------------------------

2103 : FailCookieInvalid
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: VaultLib.VaultSoapException: 2103 : FailCookieInvalid

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Stack Trace:


[VaultSoapException: 2103 : FailCookieInvalid ]
VaultService.VaultFileUpload.Page_Load(Object sender, EventArgs e) +1693
System.Web.UI.Control.OnLoad(EventArgs e) +67
System.Web.UI.Control.LoadRecursive() +35
System.Web.UI.Page.ProcessRequestMain() +720

Thanks for your help
Mario

[jeremy_sg]

I've just spoken with Mario on the phone.

1. The FailInvalidCookie error makes sense, because a web browser hitting this page has not gotten the authentication token from the Vault login process.
2. I explained that turning Use Chunked Encoding is not a real performance hit in most cases. All Vault versions after 2.0.4 disable chunked encoding by default. Chunked encoding is only useful for times when users are uploading very large files (CD iso files, etc).

[Mike Dimmick]

My copy of Vault is definitely working and spits out the same error:

[VaultSoapException: 2103 : FailCookieInvalid ]
VaultService.VaultFileUpload.Page_Load(Object sender, EventArgs e) +1701
System.Web.UI.Control.OnLoad(EventArgs e) +67
System.Web.UI.Control.LoadRecursive() +35
System.Web.UI.Page.ProcessRequestMain() +750

This was from my single-user copy of Vault here - IIS 5.1 on Windows XP SP2, but I also confirmed it on our server at work, which is 2.0.6 on Windows Server 2003/IIS 6.0.

Have your admins applied UrlScan (or the IIS Lockdown Tool, which contains it) to that web server recently? UrlScan can be configured to reject requests with the Transfer Encoding header. Likewise some firewalls may reject it. If something on the way is rejecting it (you may find Ethereal, run on the server, useful to see what actually arrived) you'll need to reconfigure UrlScan or the firewall to allow the Transfer Encoding header.