Hi

DNN 4.9.3,Doc Manager 5.2.9

We've spent weeks trying to get Document Manager to work for our client. Sometimes we can upload and download files, sometimes we cant.

When uploading an old .xls file, it often works as it should.
Same user, same browser, same pc another day and the upload results in server errors.

xlsx files rarely upload properly, though they have been known to.

When it's about to fail, the upload filename is often emptied after adding file, or shows c:\fakepath\....

and then we have to reselect file... and then it falls over. Or it loads, but the filesize is zero and it obviously hasnt worked.

I would like to send you some screenshots as example.. and please advise.
hosting is set as ASP4 though host settings shows site at .NET framework 2.0.50727.3625,in case this is important.
thanks
Jane

Below is an event log of a failed upload event
----------------------------
3/6/2012 2:07:56 PM General Exception AssemblyVersion: 04.09.03; PortalID: -1; PortalN ...
AssemblyVersion: 04.09.03
PortalID: -1
PortalName:
UserID: -1
UserName:
ActiveTabID: -1
ActiveTabName:
RawURL: /language/en-us/home/register.aspx?Command=Core_Edit&CollectionId=18&DMXRadUrid=08d441b7-2784-4b01-99f7-354ed266144d
AbsoluteURL: /language/en-us/home/register.aspx
AbsoluteURLReferrer: http://www.novacast.co.uk...10-90eb-fb9b59c2d214
UserAgent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 5.1; Trident/4.0; GTB7.3; .NET CLR 1.1.4322; .NET CLR 2.0.50727; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729)
DefaultDataProvider: DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider
ExceptionGUID: 0286648a-991a-45df-8892-5dc1275e3104
InnerException: Thread was being aborted.
FileName:
FileLineNumber: 0
FileColumnNumber: 0
Method: System.Web.UnsafeNativeMethods.EcbGetAdditionalPostedContent
StackTrace:
Message: System.Threading.ThreadAbortException: Thread was being aborted. at System.Web.UnsafeNativeMethods.EcbGetAdditionalPostedContent(IntPtr pECB, Byte[] bytes, Int32 offset, Int32 bufferSize) at System.Web.Hosting.ISAPIWorkerRequestInProc.GetAdditionalPostedContentCore(Byte[] bytes, Int32 offset, Int32 bufferSize) at System.Web.Hosting.ISAPIWorkerRequest.ReadEntityBody(Byte[] buffer, Int32 offset, Int32 size) at System.Web.Hosting.ISAPIWorkerRequest.ReadEntityBody(Byte[] buffer, Int32 size) at System.Web.HttpRequest.GetEntireRawContent() at System.Web.HttpRequest.GetMultipartContent() at System.Web.HttpRequest.FillInFormCollection() at System.Web.HttpRequest.get_Form() at System.Web.HttpRequest.FillInParamsCollection() at System.Web.HttpRequest.GetParams() at System.Web.HttpRequest.get_Params() at iFinity.DNN.Modules.UrlMaster.UrlRewriteModule.CheckForDebug(HttpRequest request, NameValueCollection queryStringCol, Boolean checkRequestParams) at iFinity.DNN.Modules.UrlMaster.UrlRewriteModule.ProcessRequest(HttpContext context, HttpRequest request, HttpServerUtility Server, HttpResponse response, Boolean useFriendlyUrls, String requestType, Uri requestUri, UrlAction result, NameValueCollection queryStringCol, FriendlyUrlSettings settings)
Source:
Server Name: WSI

A thread abort means the server cut off processing. Ultimately this comes down to how the server is configured (i.e. it is not a DMX issue). The information we have to drill down into this error must come from the details of the error message. Specifically the first bit says this:
Thread was being aborted. at System.Web.UnsafeNativeMethods.EcbGetAdditionalPostedContent
I have no idea about the specifics of this method as it lies well outside the DMX code (it’s in the .net framework). But there’s a hint in “PostedContent”, meaning the bytes the client is sending. Somehow the server is choking on what is being sent. The method it fails (EcbGetAdditionalPostedContent) should make easy Googling, by the way.

Note I assume you are familiar with executionTimeout and have set that parameter accordingly.

I hope that will help you get going toward a solution.

Peter