The DMX generate an error, when I either choose TelerikUpload or CAUpload where ASP upload works fine. I've check the web.config, all entries there as per installation manual.

The errors:

CAUpload : JavaScript error
Message from webpage
Upload error: Error loading progress data.
Page error log:
Webpage error details
User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.0; Trident/4.0; GTB5; .NET CLR 3.5.30729; OfficeLiveConnector.1.3; OfficeLivePatch.0.0; .NET CLR 3.0.30618)
Timestamp: Thu, 12 Mar 2009 01:21:37 UTC
Message: Syntax error
Line: 1
Char: 6
Code: 0
URI: http://www.mydomain.org.n...mp;CollectionId=4386

TelerikUpload:Server side error

Error: DMX is currently unavailable.
DotNetNuke.Services.Exceptions.ModuleLoadException: You must upload a file ---> System.Exception: You must upload a file at Bring2mind.DNN.Modules.DMX.Controls.TelerikUpload.WriteToCurrentEntry() at Bring2mind.DNN.Modules.DMX.Controls.EditEntry.ᜀ(Control A_0) at Bring2mind.DNN.Modules.DMX.Controls.EditEntry.ᜀ(Object A_0, WizardNavigationEventArgs A_1) --- End of inner exception stack trace ---
The DMX generate an error, when I choose otherther
 

Hi Stas,

I can't tell from here what's happening. Both upload components call the site through Ajax to update the progress bar. The entries in the web.config make sure that asp.net knows which dll is supposed to handle those calls. So if this fails then primary suspects are:
1. IIS. If IIS does not route the call to the DNN site, then it will fail.
2. JS. If the JavaScript is wrong (e.g. it calls the wrong page) it will fail.
3. The response is mangled. The components will emit XML to the client to update the progress bar. If this is mangled by some component then that could cause the uploader to fail. Think in this respect of whitespace filters, compressors, etc.

Whichever way, the best way to find out is to use an http traffic sniffer like Fiddler. This will show what calls the client is emitting and what the responses are.

Regards,

Peter