Hi,

 

unfortunately I'm here to report an error again (for info about our customer's website and configuration, please refer to this topic: http://cutesoft.net/forums/thread/71647.aspx )

The "Object reference not set to an instance of an object" problem, experienced by only two users of our customer's company, has been solved by putting UseAspNetStream="true" in the web.config, and by removing the BrettleNeatUpload from our customer's website.

 

This time the situation is similar, the uploader now works fine for everyone but two users in the USA, who work for a branch of our customer's company.

When they try to upload some files (for example a PDF with a size of nearly 170 KBs), as soon as they press "START UPLOAD", the progress bar shows out, saying "Uploading File X etc...", but it stays stuck at 0% and it's impossible to complete the uploading process.

We gave to these users access to the Test Page that the last time we set up with you help ( https://portal.denora.com/TEST/TestUpload.aspx ) but they experience the problem also there.

We checked in the TempFolder and we noticed that:

- the RESX files that these two users are able to upload have a name that starts with "persisted";

- the RESX files that they are not able to upload have a name that starts with "uploading".

 

For example the PDF file that they are not able to upload (size 170 KBs) can be found in the temp directory, named "uploading" and with a size of 64 KBs.

Another information: both users who are experiencing the problem have Internet Explorer 9 and we already updated the uploader DLL to the latest version (dated 3rd of february 2012).

 

What could be the problem?

 

Best Regards,

 

Tux.

An update: more than those two US users are being impacted by the problem, yesterday an italian user experienced a similar issue, as soon as she clicks on START UPLOAD nothing happens and the upload process doesn't even start. In this case, we couldn't find any RESX file in the TempDirectory...

Another update, to try helping you understand what's the problem (and the solution) could be:

We added the OnTaskError and OnError javascript functions to our pages and this is the alert that our customer receives when he tries to upload a PDF file (inside a pop-up)... the message is "TaskError: FILENAME, undefined":

 

Hello... any answer........?

Please, we need help... :(

By the way, I update you about the situation: yesterday we managed to solve the issue of the italian user by ourselves. The problem was Microsoft Silverlight... that user didn't have it installed on her PC with IE. As soon as she installed and enabled it, she managed to upload files and the TaskError disappeared.

 

But we still can't solve the issue for the two US users... they are getting the same error that the italian user was getting: "TaskError: FILENAME, undefined, onunload", where this is the result of a JavaScript alert that we put inside the OnTaskError function and where we chose to show: 1) the type of error; 2) the file name; 3) the error message; 4) the reason message.

And this even after having installed and enabled SilverLight on their IEs (version 9).....

 

Please note that:

 

A) If they try to upload the same file in the TestUpload page (the one we set up with your help), the upload is succesful;

B) The page where they are trying to upload the files is different from the one used by the italian user, and the difference is that the italian user was using the Uploader inside a new Browser window, while the US users are using the Uploader inside a ModalPopupExtender of the AjaxControlToolkit.

Hi Tux,

 

Move the uploader control out of the ModalPopupExtender, does it work for your us clients?

 

Does it got problem with the special file/size? Or randomly? What silverlight version your us client using?

 

Regards,

 

Ken 

 

Hi Ken,

 

today we finally managed to solve the issue.

As for the italian user, her problem was SilverLight (it wasn't installed on her PC).

As for the two US users, they had to install SilverLight too, but it wasn't enough. We had to removed this HTML tag:

 

 

from the MasterPage which includes the ContentPage where the ModalPopupExtender (with the uploader) is. It was somehow interfering with the AjaxUploader, because as soon as we removed it, the problem disappeared.

 

Regards,

 

Tux.