Last post Apr 18, 2010 01:14 AM by cnranasinghe
Apr 13, 2010 04:50 PM|Programor|LINK
We recently encountered a problem where the server is rejecting all requests that are asp.net post backs. the site will load initially, but any button click event or post back event will display a error in the brower. it is not an asp.net type error but
Internet Explorer "Internet Explorer cannot display the web page"
Mozilla "The connection was reset.
The connection to the server was reset while the page was loading."
The browser errors are always displayed immediately with no wait time ruling Timeouts are not the issue. I started to log every request in the Global_BeginRequest method in the global.asax file and confirmed that the application is not even being hit during
The error started to occur when the sysadmin install 4 updates. They are
- Update for Windows Server 2003 (KB973917)
- Windows Malicious Software Removal Tool - March 2010 (KB890830)
- Update for Windows Server 2003 (KB979306)
- Cumulative Security Update for Internet Explorer 6 for Windows Server 2003 (KB980182)
Besides the above mentioned updates, I don't know what changed that may cause all post backs to be refused. Any help much appreciated.
PS: The company does not want to uninstall the updates or do a system restore as there are several web sites being hosted on the server.
Apr 14, 2010 01:27 AM|Waqar_ali|LINK
Run aspnet_regiss.exe command, this will reset dotnet compatibility with iis.
Apr 14, 2010 02:25 AM|night_dog|LINK
Is service pack 2 installed on your system?
Here it says that it is required for KB973917:
Check this too - it has similar problem after installing this update:
Apr 14, 2010 09:49 AM|Programor|LINK
Is there any way to solve this error without uninstalling the update or reinstalling service pack 2.
This server hosts several live web sites that cannot be disrupted. Basically, I want a very smooth and
easy solution. I know uninstalling the update would do the job, but boss doesn't like that solution ... i know i know, tell me about it.
Anyways, any help appreciated.
Apr 18, 2010 01:14 AM|cnranasinghe|LINK
Repaire your dotnetframework you have installed.