ASP.NET Ajax client-side framework failed to load

Discussion in 'ASP.NET / ASP.NET Core' started by mezzanine74, May 13, 2011.

  1. Hi,
    I am totally lost!! :eek:
    I am trying to move my site from Arvixe.com into DiscountASP.Net.

    I spent 2 days on searching to figure out what is causing following Ajax error.

    I tried hundreds of different variation on webconfig.
    all files in Bin folder are correct
    everything works perfect in Arvixe.com and on my local computer.

    Message: ASP.NET Ajax client-side framework failed to load.
    Message: 'Sys' is undefined

    I dont have even any hope as i spent lots of hours on this already and no result.

    How do you run Ajax with DiscountASP in success ?
    Any help appreceated.
     
  2. Make sure all of the AJAX assemblies and files are uploaded to your applications Bin folder.

    Another tool to use is Fiddler. It is a program that will record all http calls coming to your site. This can give a better insight on what is going on in the back end. Unfortunately, the error you are seeing is not very descriptive.

    http://www.fiddler2.com/fiddler2/
     
  3. hi raymondp

    thanks for your reply.

    i have created a new web site on my home computer which is running Visual Web Developer 2008 (not like my work computer running VWD2010).
    Then i added ToolKitScriptManager and several Ajax controls just to revise webconfig file and Bin folder automatically.

    Then i checked brand new WebConfig file to compare my existing webconfig which gives error.

    I realized that <handlers> section was completely missing in <system.webServer>. I added handlers section and it is working now. If you follow all those steps by Visual Web Developer 2010, <system.webServer> looks different, there is no handlers and modules.

    Surprisingly, my ajax controls are working properly on Arvixe without handler section!!

    I hope this information would be helpfull for new customers here.

    <system.webServer>
    <validation validateIntegratedModeConfiguration="false"/>
    <modules>
    <remove name="ScriptModule"/>
    <add name="ScriptModule" preCondition="managedHandler" type="System.Web.Handlers.ScriptModule, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/>
    </modules>
    <handlers>
    <remove name="WebServiceHandlerFactory-Integrated"/>
    <remove name="ScriptHandlerFactory"/>
    <remove name="ScriptHandlerFactoryAppServices"/>
    <remove name="ScriptResource"/>
    <add name="ScriptHandlerFactory" verb="*" path="*.asmx" preCondition="integratedMode" type="System.Web.Script.Services.ScriptHandlerFactory, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/>
    <add name="ScriptHandlerFactoryAppServices" verb="*" path="*_AppService.axd" preCondition="integratedMode" type="System.Web.Script.Services.ScriptHandlerFactory, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/>
    <add name="ScriptResource" preCondition="integratedMode" verb="GET,HEAD" path="ScriptResource.axd" type="System.Web.Handlers.ScriptResourceHandler, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/>
    </handlers>
    </system.webServer>
     
  4. ...Good job. I've been helping some of the DASP customers with this and they were all confused with this same thing. ;-)
     

Share This Page