Home/ Questions/Q 6201695
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-24T04:36:06+00:00

I am trying to deploy a .NET 2.0 ASP.NET application with AJAX 1.0 on

  • 0

I am trying to deploy a .NET 2.0 ASP.NET application with AJAX 1.0 on a Windows Server 2008 system running IIS 7.

The same application that runs perfectly on my development machine, but when published and deployed it won’t run AJAX, even though no error messages are displayed. Asynchronous calls will just refresh the entire page (the same symptom described here, but my xhtmlConformance tag is set to Transitional). The absence of any errors and messages proves that the AJAX library was found and successfully added to the project.

I’ve read some posts on this subject, and supposedly there are some tweaks on web.config that should make it work, but after following some of them, I had no success.

I’ve added every additional tag available on this sample web.config file to my running web.config.

This application was not originally created as an “AJAX-enabled ASP.NET Application”, but as a regular ASP.NET application, although it works perfectly while on my development environment.

Question: What should I do to run a .NET Framework 2.0 ASP.NET application with AJAX 1.0 on Windows Server 2k8 with IIS 7 ?

Before it’s suggested: I do want to update it to the newest version of the .NET Framework, and that’s being worked on, but I’m not the one making calls regarding subjects like this..

Update:

Trying to access /ScriptResource.axd (with the proper querystrings) gives me the following error:

Session state is not available in this context.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    It turns out that the issue I added on the update to the question was what caused the whole problem.

    Ajax tried to access /ScriptResource.axd, and it ran a method on global.asax that accessed a session variable when in fact there was no session.

    All I had to do is to check if the session is available before using it on Global.asax, as follows:

    if (HttpContext.Current.Session!=null)
{
   // my code
}

    The solution was found on this blog.

    • 0