Ajax Callback Error

Most often reasons for receiving the error

1. Missing or incorrect registration of the RadUploadHttpModule and  RadUploadProgressHandler in the Web.config file
2. There are other conflicting handlers or modules registered in the Web.config file
3. URL Rewriter rules
4. Trust Level
5. Web server is configured to check for existence of the requested files
6. Running your application in Integrated IIS7 mode
7. Using Forms Authentication
8. Using RadUpload in DNN

Resolutions

1. Register RadUploadHttpModule and RadUploadProgressHandler in the Web.config file if they are not registered or check whether they are registered correctly if they are already registered in the Web.config file.
    
   STRONGLY RECOMMENDED
   Check whether  the RadUploadProgressHandler’s registration is correct. You can do this if you access directly the handler’s url from the browser in the following way:
   
   http://mysite/Telerik.RadUploadProgressHandler.aspx
   
   where mysite is your site’s url 
   
   If everything is registered correctly, you should see the following line:
   
   var rawProgressData = {InProgress:false,RadProgressContextCustomCounters:false}; 
2. Check for other conflicting modules and handers in the Web.config and the order in which they are registered
   
   Example:
   
   If you register a handler which is more common and handles the requests which should actually be handled by handlers registered below, the Ajax Callback Error will be reproduced, e. g.:
   
   <add verb="*" path="*.aspx" type="sfHttpHandler.HttpXmlHandler, sfHttpHandler"/>
   
   <add verb="*" path="Telerik.RadUploadProgressHandler.aspx"   type="Telerik.WebControls.RadUploadProgressHandler, RadUpload.Net2"/>
   
   The first handler is actually registered for every .aspx file because of the path="*.aspx". RadUploadProgressHandler is also an aspx -Telerik.RadUploadProgressHandler.aspx and thus the request for Telerik.RadUploadProgressHandler.aspx will be handled by the wrong handler -sfHttpHandler.HttpXmlHandler. The order in which the handlers in Web.config are registered is extremely important. If you change the order of the above handlers Telerik.RadUploadProgressHandler.aspx will be handled by the correct handler - RadUploadProgressHandler. 
3. Check for URLRewriter rules which may redirects the call to Telerik.RadUploadProgressHandler.aspx to somewhere else.
4. RadMemoryOptimization requires ReflectionPermission in order to operate correctly. To achieve this you can choose one of the following options: 
   •  Run your application with Full Trust permission set. To achieve this put the following in your web.config:
       ...
      <system.web>
       ...
     <trust level="Full" />
       ...
      </system.web>
     
   • Create custom security policy which allows ReflectionPermission. 
   • Run your application in Medium trust and put RadUpload’s assembly in the GAC.
     More information about the trust levels can be found here .  
5. When RadProgressManager tries to access Telerik.RadUploadProgressHandler.aspx, the server searches for a physical file, but it is not existing, because it is only registered in the web.config. To resolve the problem you should make sure that the web server isn't checking for existence of the requested files: 
     
6. Currently RadUpload works in IIS7 Classic mode and Cassini, however, it does not support Intergrated IIS7 mode. To run RadUpload in IIS7 you should make sure that the ApplicationPool setting of your application is set to Classic .NET AppPool. To do this you should right click on you application in IIS7 choose Advanced Settings and set the ApplicationTool option to Classic .NET AppPool.
7. Refer to the Using Forms Authentication help article and follow the instructions listed there.
8. Before all rewriter rules in the Rules section in the SiteUrls.config
   should be added the following rewriter rule:
   
   <RewriterRule> 
      <LookFor>.*Telerik.RadUploadProgressHandler.aspx(.*)</LookFor> 
      <SendTo>~/Telerik.RadUploadProgressHandler.aspx$1</SendTo> 
   </RewriterRule>