Indeed changing the application pool in which the DotNetNuke is working, from 'ASP.NET V2 AppPool' to 'Classic .NET AppPool' solves the problem. Changing the application pool to classic mode, you may use Coolite ASP.NET/AJAX Components in DotNetNuke. However this problem doesn't appear in 'ASP.NET V4 AppPool'.