By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
424,681 Members | 1,864 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 424,681 IT Pros & Developers. It's quick & easy.

Could not load file or assembly 'System.Web.Extensions

P: n/a
I am testing AJAX. I've downloaded the AJAX Extension and the CTP
December package and installed on BOTH my development machine and the
production server.

Then I created a very very simple web application, which contains a
button and a label. When the button is clicked, some message is shown
on the label. That's it.

The AJAX works great on my development machine, but on the production
server, I got the typical error as follows:

Server Error in '/' Application.
--------------------------------------------------------------------------------

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
'System.Web.Extensions, Version=1.0.61025.0, Culture=neutral,
PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system
cannot find the file specified.

Source Error:

Line 36: <compilation debug="false">
Line 37: <assemblies>
Line 38: <add assembly="System.Web.Extensions,
Version=1.0.61025.0, Culture=neutral,
PublicKeyToken=31bf3856ad364e35"/>
Line 39: </assemblies>
Line 40: </compilation>

There is a difference between the development machine and the
production server: On the development machine everything is on drive
C:. On the production server, the AJAX packages are installed on drive
C whereas the web applications run on a separate partition, drive F. I
am not sure if this is important.

I searched this forum, one guy mentioned that
Microsoft.Web.Extensions.dll and Microsoft.Web.Extensions.Design.dll
need to stay in the bin folder of the application. I don't think this
is true any more. That said, I still tried it, with no luck on the
production server.

Could you please help diagnose what might be wrong with the production
server side? Thanks.

Jan 11 '07 #1
Share this Question
Share on Google+
2 Replies


P: n/a
I am having the same exact problem. Ajax 1.0 works great on my
developement machine and gives the following error when I deploy the
application to my production webserver.
Server Error in '/' Application.

--------------------------------------------------------------------------------

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
'System.Web.Extensions, Version=1.0.61025.0, Culture=neutral,
PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The
system cannot find the file specified.

Source Error:
Line 36: <compilation debug="true">
Line 37: <assemblies>
Line 38: <add
assembly="System.Web.Extensions, Version=1.0.61025.0, Culture=neutral,
PublicKeyToken=31bf3856ad364e35"/>
Line 39: <add assembly="System.Design,
Version=2.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>
Line 40: <add
assembly="System.Web.Extensions.Design, Version=1.0.61025.0,
Culture=neutral, PublicKeyToken=31BF3856AD364E35"/></assemblies>

Source File: d:\WebSites\Secure\test\web.config Line: 38

Assembly Load Trace: The following
I called Microsoft "off shore" support and was walked through
installing "hotfix for issue 915782". This hotfix updated the
aspnet_wp.exe, System.Web.dll, webengine.dll files. After two hours
on technical support I was told this hotfix will not fix this problem
and they currently do not have a fix for this problem. I was told
that if I wanted to open another paid support case that they would be
happy to research this problem.

I am very impressed with AJAX and would love to implement its
functionality on my corporate website BUT my conclusion is that AJAX
is NOT READY FOR PRIMETIME. Like all Microsoft products it is a great
concept and really cool but maybe it might work after AJAX SP1 or AJAX
SP2?????

If you will excuse me, I think I will go install Vista on all of my
users systems so I can continue my efforts as a "Microsoft GuineePig"

On Jan 10, 5:03 pm, "antonyliu2...@yahoo.com"
<antonyliu2...@yahoo.comwrote:
I am testing AJAX. I've downloaded the AJAX Extension and the CTP
December package and installed on BOTH my development machine and the
production server.

Then I created a very very simple web application, which contains a
button and a label. When the button is clicked, some message is shown
on the label. That's it.

The AJAX works great on my development machine, but on the production
server, I got the typical error as follows:

Server Error in '/' Application.
--------------------------------------------------------------------------------

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
'System.Web.Extensions, Version=1.0.61025.0, Culture=neutral,
PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system
cannot find the file specified.

Source Error:

Line 36: <compilation debug="false">
Line 37: <assemblies>
Line 38: <add assembly="System.Web.Extensions,
Version=1.0.61025.0, Culture=neutral,
PublicKeyToken=31bf3856ad364e35"/>
Line 39: </assemblies>
Line 40: </compilation>

There is a difference between the development machine and the
production server: On the development machine everything is on drive
C:. On the production server, the AJAX packages are installed on drive
C whereas the web applications run on a separate partition, drive F. I
am not sure if this is important.

I searched this forum, one guy mentioned that
Microsoft.Web.Extensions.dll and Microsoft.Web.Extensions.Design.dll
need to stay in the bin folder of the application. I don't think this
is true any more. That said, I still tried it, with no luck on the
production server.

Could you please help diagnose what might be wrong with the production
server side? Thanks.

Feb 14 '07 #2

P: n/a
Hi people..... then....

I read this topic, and try fix this bug.
I copy twice DLL.

Microsoft.Web.Extensions.dll and Microsoft.Web.Extensions.Design.dll

and paste in my server (bin folder)

restart IIS and POOLS

bingoooooo!!!!!!!!!!!

all right.

cya guys.

regards.

On 14 fev, 19:12, ought...@gmail.com wrote:
I am having the same exact problem. Ajax 1.0 works great on my
developement machine and gives the following error when I deploy the
application to my production webserver.

Server Error in '/' Application.

--------------------------------------------------------------------------------

Configuration Error
Description: An error occurred during the processing of a
configurationfilerequired to service this request. Please review the
specific error details below and modify your configurationfile
appropriately.

Parser Error Message:Couldnotloadfileorassembly
'System.Web.Extensions, Version=1.0.61025.0, Culture=neutral,
PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The
system cannot find thefilespecified.

Source Error:

Line 36: <compilation debug="true">
Line 37: <assemblies>
Line 38: <addassembly="System.Web.Extensions, Version=1.0.61025.0, Culture=neutral,
PublicKeyToken=31bf3856ad364e35"/>
Line 39: <addassembly="System.Design,
Version=2.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>
Line 40: <addassembly="System.Web.Extensions.Design, Version=1.0.61025.0,
Culture=neutral, PublicKeyToken=31BF3856AD364E35"/></assemblies>

SourceFile: d:\WebSites\Secure\test\web.config Line: 38

AssemblyLoadTrace: The following

I called Microsoft "off shore" support and was walked through
installing "hotfix for issue 915782". This hotfix updated the
aspnet_wp.exe, System.Web.dll, webengine.dll files. After two hours
on technical support I was told this hotfix willnotfix this problem
and they currently donothave a fix for this problem. I was told
that if I wanted to open another paid support case that they would be
happy to research this problem.

I am very impressed with AJAX and would love to implement its
functionality on my corporate website BUT my conclusion is that AJAX
isNOTREADY FOR PRIMETIME. Like all Microsoft products it is a great
concept and really cool but maybe it might work after AJAX SP1 or AJAX
SP2?????

If you will excuse me, I think I will go install Vista on all of my
users systems so I can continue my efforts as a "Microsoft GuineePig"

On Jan 10, 5:03 pm, "antonyliu2...@yahoo.com"

<antonyliu2...@yahoo.comwrote:
I am testing AJAX. I've downloaded the AJAX Extension and the CTP
December package and installed on BOTH my development machine and the
production server.
Then I created a very very simple web application, which contains a
button and a label. When the button is clicked, some message is shown
on the label. That's it.
The AJAX works great on my development machine, but on the production
server, I got the typical error as follows:
Server Error in '/' Application.
--------------------------------------------------------------------------------
Configuration Error
Description: An error occurred during the processing of a configuration
filerequired to service this request. Please review the specific error
details below and modify your configurationfileappropriately.
Parser Error Message:Couldnotloadfileorassembly
'System.Web.Extensions, Version=1.0.61025.0, Culture=neutral,
PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system
cannot find thefilespecified.
Source Error:
Line 36: <compilation debug="false">
Line 37: <assemblies>
Line 38: <addassembly="System.Web.Extensions,
Version=1.0.61025.0, Culture=neutral,
PublicKeyToken=31bf3856ad364e35"/>
Line 39: </assemblies>
Line 40: </compilation>
There is a difference between the development machine and the
production server: On the development machine everything is on drive
C:. On the production server, the AJAX packages are installed on drive
C whereas the web applications run on a separate partition, drive F. I
amnotsure if this is important.
I searched this forum, one guy mentioned that
Microsoft.Web.Extensions.dll andMicrosoft.Web.Extensions.Design.dll
need to stay in the bin folder of the application. I don't think this
is true any more. That said, I still tried it, with no luck on the
production server.
Couldyou please help diagnose what might be wrong with the production
server side? Thanks.

Feb 21 '07 #3

This discussion thread is closed

Replies have been disabled for this discussion.