Wednesday, March 28, 2012

Installing AJAX on a production server...

i have a production server that I am attempting to install AJAX on. I have installed the latest release .msi file and I have the 2.0 framework running on it. do I need to do anything else? Here is the error I am getting when I run my sites that contain ajax controls...

Configuration Error

Description:An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately.

Parser Error Message:Could not load file or assembly 'Microsoft.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified. (C:\wmpub\WMRoot\web.config line 53)

Source Error:

Line 51: </httpHandlers>Line 52: <httpModules>Line 53: <add name="WebResourceCompression" type="Microsoft.Web.Handlers.WebResourceCompressionModule, Microsoft.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/>Line 54: <add name="ScriptModule" type="Microsoft.Web.UI.ScriptModule, Microsoft.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>Line 55: </httpModules>

I have read a few postings about similar errors, but have had no luck when following the steps. Is there a "step by step" list on how to install AJAX on a production server? Thanks in advance!

Nathan

This is what i think, your project is using old AJAX dll

because by looking at Microsoft.Web.Extensions in the web.config

The Microsoft.Web.Extensions is not for latest AJAX

the latest AJAX is using "System.Web.Extensions"

In the web.config should be like below

<httpModules>
<add name="ScriptModule" type="System.Web.Handlers.ScriptModule, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
</httpModules>

so you have either version conflict or web.config setting is incorrect


Thanks for catching that... I had not updated by web.config... stupid error. I appreciated it!

Nathan

No comments:

Post a Comment