500.19 - There is a duplicate 'system.web.extensions/scripting/scriptResourceHandler' section defined (3 replies)
Mary, this is most probably due to the .net 4.5 installation.
We've seen that after it's install a copy of each existing IIS Application Pool is created, where the .net version is 4.5 and each of the applications switched over to use .net 4.5
If you select/click the IMan application (not the pool), go Back Settings and reassign it back to the original IMan .net 2.0 application pool, it should start working again.
Thanks
To clarify, the solution is:
In IIS, select the IMan web site, select Basic Settings. Under Application Pool it had changed to ".Net 4.5". Use the dropdown to select the Application Pool IMan (do not select ".Net v2.0", which is what I did at first).
It is now fixed.
Closed due to inactivity.
The customer's Iman website is getting this error "There is a duplicate 'system.web.extensions/scripting/scriptResourceHandler' section defined". (See screen shot for full details).
I have checked the web.config file, and there do appear to be 2 such sections. The web config file is dated 12/11/2014 and has not been changed since the site was installed. A copy is attached.
There was no problem last week
The Iman scheduled jobs are still running but I am unable to make any changes because I cannot get into the designer, in either Firefox or IE.
Firefox (version 42.0), IE (version 11.0.9600.18036)
Windows Server 2012 R2 Standard
Last windows update 28/9/15, server rebooted
Java last update 17/11/15 (server not reboot)
Since the last time I was able to log into Iman, we have:
- Implemented the Sage Portal, including adding IIS role asp.net 4.5, and server reboot, which has created a new web site and app pool
- installed MISys on this server, which has created a new web site and app pool
I don't know if either otf these has changed settings in the default web site or default app pool.
I have run the Iman Console, cycled IIS and restarted the realisable services, and checked the Permissions button.
Do you have a solution to this problem?
Could the addition of asp.net 4.5 have caused this error?
Can you supply a corrected web.config?