.doc problems with vault 3.5.3

[kasti]

Hi,

Lately we have been having problems getting various word documents from vault (v 3.5.3). The download from the server seems to fail as follows:


Critical Error downloading file! The remote host closed the connection. The error code is 0x80072746.
at System.Web.Hosting.ISAPIWorkerRequestInProcForIIS6.FlushCore(Byte[] status, Byte[] header, Int32 keepConnected, Int32 totalBodySize, Int32 numBodyFragments, IntPtr[] bodyFragments, Int32[] bodyFragmentLengths, Int32 doneWithSession, Int32 finalStatus, Boolean& async)
at System.Web.Hosting.ISAPIWorkerRequest.FlushCachedResponse(Boolean isFinal)
at System.Web.Hosting.ISAPIWorkerRequest.FlushResponse(Boolean finalFlush)
at System.Web.HttpResponse.Flush(Boolean finalFlush)
at System.Web.HttpWriter.WriteFromStream(Byte[] data, Int32 offset, Int32 size)
at System.Web.HttpResponseStream.Write(Byte[] buffer, Int32 offset, Int32 count)
at System.IO.BufferedStream.Write(Byte[] array, Int32 offset, Int32 count)


This is reproducible on all clients, clearing cache/rebooting etc does not help. Strangest thing about this is that the file can be downloaded in the web interface or directly on the server where vault resides. Once it has been downloaded on the server, it can also be downloaded on all clients without any problems.

Any ideas?

Thanks,
Herbert.

[lbauer]

Once it has been downloaded on the server, it can also be downloaded on all clients without any problems.

That's strange. Is the problem just with word documents? Or is it with files of a particular size? What about other binary files?

If you can download the file on Vault server machine itself, this could indicate some sort of network issue, like a firewall, router, antivirus software, etc.

However it's not clear why downloading on the server machine would make the file then available for download on other clients. The first step would be to take a look at the Vault server log as well as the client log. First, enable debug server logging in the Admin Web Client under Server Settings->Logging->Log Level.

Then enable logging for all events in the user's GUI Client. Open the Vault GUI Client and hold down the following keys on your keyboard: Control-Alt Shift F12.

Reproduce the problem, then send me copies of the logs. Let me know what user was experiencing the error and what time the error occurred so I know where to look for in the logs.