Our IIS6 ASP.NET site has been running fine for the past few years. But as of the first week of February this year, we started seeing a lot of connection/timeout errors, and our users began having intermittent problems with loading our pages. The strange
thing is that when the site stalls in one browser, if I open a completely different browser (e.g., IE instead of Firefox, or vice versa) the site seems to connect and load fine, though repeated usage in that browser may eventually cause it to stall there too
(but sometimes not). And it doesn't behave this way consistently--the site will run fine most of the time, and then for whatever reason, things will start to slow down/stall, eventually leading to the errors, and it doesn't
seem to be prectable as far as time of day. I didn't make any major changes to any of the site code around the time this all began, and we didn't install any new hardware or anything.
Below are some error entries from the server logs from today. On the pages listed, I believe it is the Streamreader I have running on the Page_Load that is failing. Again, this code has been otherwise working fine and hasn't changed. Yes, I could add a try/catch
(and probably should after this) to handle exceptions, but I am 100% convinced that is not the cause of the aforementioned problems, just a symptom. If anyone has any ideas of what might be going wrong, I sure could use the help. I've been going over this
with our I.T. department and our I.P. folks, and so far nobody has any answers.
Process information:
Process ID: 8144
Process name: w3wp.exe
Account name: NT AUTHORITY\NETWORK SERVICE
Exception information:
Exception type: NullReferenceException
Exception message: Object reference not set to an instance of an object.
at ASP.pageincludes_teentabcontent_aspx.Page_Load(Object sender, EventArgs e)
at System.Web.Util.CalliHelper.EventArgFunctionCaller(IntPtr fp, Object o, Object t, EventArgs e)
at System.Web.Util.CalliEventHandlerDelegateProxy.Callback(Object sender, EventArgs e)
at System.Web.UI.Control.OnLoad(EventArgs e)
at System.Web.UI.Control.LoadRecursive()
at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
Request information:
Request URL: http://www.greenwichlibrary.org/pageincludes/TeenTabContent.aspx
Request path: /pageincludes/TeenTabContent.aspx
User host address: 172.22.1.52
User:
Is authenticated: False
Authentication Type:
Thread account name: NT AUTHORITY\NETWORK SERVICE
Thread information:
Thread ID: 41
Thread account name: NT AUTHORITY\NETWORK SERVICE
Is impersonating: False
Stack trace: at ASP.pageincludes_teentabcontent_aspx.Page_Load(Object sender, EventArgs e)
at System.Web.Util.CalliHelper.EventArgFunctionCaller(IntPtr fp, Object o, Object t, EventArgs e)
at System.Web.Util.CalliEventHandlerDelegateProxy.Callback(Object sender, EventArgs e)
at System.Web.UI.Control.OnLoad(EventArgs e)
at System.Web.UI.Control.LoadRecursive()
at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
Custom event details:
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Process information:
Process ID: 8144
Process name: w3wp.exe
Account name: NT AUTHORITY\NETWORK SERVICE
Exception information:
Exception type: NullReferenceException
Exception message: Object reference not set to an instance of an object.
at ASP.pageincludes_teentabcontent_aspx.Page_Load(Object sender, EventArgs e)
at System.Web.Util.CalliHelper.EventArgFunctionCaller(IntPtr fp, Object o, Object t, EventArgs e)
at System.Web.Util.CalliEventHandlerDelegateProxy.Callback(Object sender, EventArgs e)
at System.Web.UI.Control.OnLoad(EventArgs e)
at System.Web.UI.Control.LoadRecursive()
at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
Request information:
Request URL: http://www.greenwichlibrary.org/pageincludes/TeenTabContent.aspx
Request path: /pageincludes/TeenTabContent.aspx
User host address: 172.22.1.52
User:
Is authenticated: False
Authentication Type:
Thread account name: NT AUTHORITY\NETWORK SERVICE
Thread information:
Thread ID: 16
Thread account name: NT AUTHORITY\NETWORK SERVICE
Is impersonating: False
Stack trace: at ASP.pageincludes_teentabcontent_aspx.Page_Load(Object sender, EventArgs e)
at System.Web.Util.CalliHelper.EventArgFunctionCaller(IntPtr fp, Object o, Object t, EventArgs e)
at System.Web.Util.CalliEventHandlerDelegateProxy.Callback(Object sender, EventArgs e)
at System.Web.UI.Control.OnLoad(EventArgs e)
at System.Web.UI.Control.LoadRecursive()
at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
Custom event details:
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Process information:
Process ID: 8144
Process name: w3wp.exe
Account name: NT AUTHORITY\NETWORK SERVICE
Exception information:
Exception type: NullReferenceException
Exception message: Object reference not set to an instance of an object.
at ASP.pageincludes_maingltabcontent_aspx.Page_Load(Object sender, EventArgs e)
at System.Web.Util.CalliHelper.EventArgFunctionCaller(IntPtr fp, Object o, Object t, EventArgs e)
at System.Web.Util.CalliEventHandlerDelegateProxy.Callback(Object sender, EventArgs e)
at System.Web.UI.Control.OnLoad(EventArgs e)
at System.Web.UI.Control.LoadRecursive()
at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
Request information:
Request URL: http://www.greenwichlibrary.org/pageincludes/MainGLTabContent.aspx
Request path: /pageincludes/MainGLTabContent.aspx
User host address: 172.22.1.52
User:
Is authenticated: False
Authentication Type:
Thread account name: NT AUTHORITY\NETWORK SERVICE
Thread information:
Thread ID: 18
Thread account name: NT AUTHORITY\NETWORK SERVICE
Is impersonating: False
Stack trace: at ASP.pageincludes_maingltabcontent_aspx.Page_Load(Object sender, EventArgs e)
at System.Web.Util.CalliHelper.EventArgFunctionCaller(IntPtr fp, Object o, Object t, EventArgs e)
at System.Web.Util.CalliEventHandlerDelegateProxy.Callback(Object sender, EventArgs e)
at System.Web.UI.Control.OnLoad(EventArgs e)
at System.Web.UI.Control.LoadRecursive()
at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
Custom event details:
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
We heard back from our provider folks, and it appears that we also had a number of MS patches and updates made to the server on the last day of January. The coincidence seems uncanny in regard to timing, and it's possible that the problems were already occurring
and that I was merely the first to really notice it 7 days later. Anyone have any thoughts on this? Thanks...
Anyone? Please? I could really use some help on this.
The only other thing I can think of trying is to uninstall all the updates that went through on January 31 and see if that resolves the issue, then selectively add them back in to see which one is the culprit. But if it's something I could be doing better/different
in my code, I'd rather know that. At this point I'm thinking that I should at least put in the try/catch so that the page will at least load (albeit with an error message in place of the content that was supposed to be scraped), but that still doesn't sound
like a real solution to me.
It's a dedicated server, hosted by us, but it is also host for our development site which is available by local intranet (can also be accessed externally via VPN though when we need such). We also have 3rd-party support that has access to the server (and
other parts of our network) that is responsible for maintenance, backups, applying updates, etc.
I tried Googling around for the various patch versions that were applied at the end of January, but I didn't have any luck pinpointing any of those in regard to causing similar problems elsewhere. As mentioned, my code was working fine up until then, and
it still works, up to and until the server hangs for a given browser session.
Our network maintenance folks rolled back the 2 .NET 4 patches earlier tonight:
KB2656351 and
KB2572078
My testing as of a half hour ago failed to cause any errors whatesoever, no matter how many times I clicked/refreshed, many dozens of times in a row. I'll be testing some more tomorrow when server load is closer to normal usage, but it's looking like one
or both of those patches were responsible for causing the errors.
I know so far this has been a stumper for folks here. Now that the issue seems to have narrowed down, anyone have any thoughts on this?
Hi just wondering on the status of your site now that its been a few days since you rolled back your patches? Has the site continued to run correctly?
We updated our server with those patches(among others) on Tuesday and have been having connection problems and site slowdowns ever since. The symptoms look exactly like what you originally described.
However I haven't been able to find any other internet posts about other people experiencing this problem so we are hesitant to roll back the updates without more confirmation that they are actually the root of the problem.
How did you come up with those two patches as the cause?
Thanks, any info you can provide to help convince my coworkers that we actually need to do this is very appreciated.
Our site has been running great since we rolled back those two patches. No time-outs, no errors, and speed is as good as it ever was.
We determined those patches by looking at when the problems were first observed--around the 7th of February. Taking into account a delay in noticing the symptoms due to not expecting them, and the fact that they were intermittent as opposed to consistent,
and the timing coincided with the latest server patches/updates that went in at the end of January. Basically I said to our network folks: "the site was running fine prior to then, and none of the code has changed. So what *has* changed?", and the updates
were the answer; out of the dozen or so patches that were applied at the time, these 2 were specifically for ASP.NET 4.
I haven't seen anything official from Microsoft about them either, but as is the nature of many of these patches, they will often affect one segment of users and not others. Googling around will confirm that...
The easiest way to see if they're the problem is to just roll them back (and restart the server, etc). If the site works fine again, then you know you nailed it. If not, then look at any other changes made. Patches can always be re-applied in the case that
they weren't at fault.
I still don't know what they broke, exactly, but if I had to guess, I would say it's probably session-related. While the site was hanging in one browser, another could be opened and the site loaded just fine (for a while).
If you decide to roll back the patches, I'd be interested to hear if that works for you!
One of our internal sites has been experiencing this same problem since moving it to a new server.
Initially I thought the difference was the new server is running IIS 7 (old was IIS 6), but now I think the it's that the new server has these two patches installed while the old one did not.
I'm curious to know if you have since re-applied either of these two patches and/or installed any newer MS patches? I'd love to know if any newer patches supercede (and fix) these ones?
--Will--
Member
72 Points
28 Posts
Intermittent connection errors on ASP.NET 4 site
Mar 20, 2012 10:12 PM|LINK
Our IIS6 ASP.NET site has been running fine for the past few years. But as of the first week of February this year, we started seeing a lot of connection/timeout errors, and our users began having intermittent problems with loading our pages. The strange thing is that when the site stalls in one browser, if I open a completely different browser (e.g., IE instead of Firefox, or vice versa) the site seems to connect and load fine, though repeated usage in that browser may eventually cause it to stall there too (but sometimes not). And it doesn't behave this way consistently--the site will run fine most of the time, and then for whatever reason, things will start to slow down/stall, eventually leading to the errors, and it doesn't seem to be prectable as far as time of day. I didn't make any major changes to any of the site code around the time this all began, and we didn't install any new hardware or anything.
Below are some error entries from the server logs from today. On the pages listed, I believe it is the Streamreader I have running on the Page_Load that is failing. Again, this code has been otherwise working fine and hasn't changed. Yes, I could add a try/catch (and probably should after this) to handle exceptions, but I am 100% convinced that is not the cause of the aforementioned problems, just a symptom. If anyone has any ideas of what might be going wrong, I sure could use the help. I've been going over this with our I.T. department and our I.P. folks, and so far nobody has any answers.
Event Type: Warning
Event Source: ASP.NET 4.0.30319.0
Event Category: Web Event
Event ID: 1309
Date: 3/20/2012
Time: 4:10:54 PM
User: N/A
Computer: *REDACTED*
Description:
Event code: 3005
Event message: An unhandled exception has occurred.
Event time: 3/20/2012 4:10:54 PM
Event time (UTC): 3/20/2012 8:10:54 PM
Event ID: d70ae2cf8ec1400f8f15347ac96facda
Event sequence: 30687
Event occurrence: 927
Event detail code: 0
Application information:
Application domain: /LM/W3SVC/2018911400/Root-1-129767166973177500
Trust level: Full
Application Virtual Path: /
Application Path: C:\Inetpub\wwwsites\LibraryWeb\
Machine name: *REDACTED*
Process information:
Process ID: 8144
Process name: w3wp.exe
Account name: NT AUTHORITY\NETWORK SERVICE
Exception information:
Exception type: NullReferenceException
Exception message: Object reference not set to an instance of an object.
at ASP.pageincludes_teentabcontent_aspx.Page_Load(Object sender, EventArgs e)
at System.Web.Util.CalliHelper.EventArgFunctionCaller(IntPtr fp, Object o, Object t, EventArgs e)
at System.Web.Util.CalliEventHandlerDelegateProxy.Callback(Object sender, EventArgs e)
at System.Web.UI.Control.OnLoad(EventArgs e)
at System.Web.UI.Control.LoadRecursive()
at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
Request information:
Request URL: http://www.greenwichlibrary.org/pageincludes/TeenTabContent.aspx
Request path: /pageincludes/TeenTabContent.aspx
User host address: 172.22.1.52
User:
Is authenticated: False
Authentication Type:
Thread account name: NT AUTHORITY\NETWORK SERVICE
Thread information:
Thread ID: 41
Thread account name: NT AUTHORITY\NETWORK SERVICE
Is impersonating: False
Stack trace: at ASP.pageincludes_teentabcontent_aspx.Page_Load(Object sender, EventArgs e)
at System.Web.Util.CalliHelper.EventArgFunctionCaller(IntPtr fp, Object o, Object t, EventArgs e)
at System.Web.Util.CalliEventHandlerDelegateProxy.Callback(Object sender, EventArgs e)
at System.Web.UI.Control.OnLoad(EventArgs e)
at System.Web.UI.Control.LoadRecursive()
at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
Custom event details:
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Event Type: Warning
Event Source: ASP.NET 4.0.30319.0
Event Category: Web Event
Event ID: 1309
Date: 3/20/2012
Time: 3:55:33 PM
User: N/A
Computer: *REDACTED*
Description:
Event code: 3005
Event message: An unhandled exception has occurred.
Event time: 3/20/2012 3:55:33 PM
Event time (UTC): 3/20/2012 7:55:33 PM
Event ID: 8a7e60b6ead9467a98ff5c2e1e2f0ca2
Event sequence: 29333
Event occurrence: 879
Event detail code: 0
Application information:
Application domain: /LM/W3SVC/2018911400/Root-1-129767166973177500
Trust level: Full
Application Virtual Path: /
Application Path: C:\Inetpub\wwwsites\LibraryWeb\
Machine name: *REDACTED*
Process information:
Process ID: 8144
Process name: w3wp.exe
Account name: NT AUTHORITY\NETWORK SERVICE
Exception information:
Exception type: NullReferenceException
Exception message: Object reference not set to an instance of an object.
at ASP.pageincludes_teentabcontent_aspx.Page_Load(Object sender, EventArgs e)
at System.Web.Util.CalliHelper.EventArgFunctionCaller(IntPtr fp, Object o, Object t, EventArgs e)
at System.Web.Util.CalliEventHandlerDelegateProxy.Callback(Object sender, EventArgs e)
at System.Web.UI.Control.OnLoad(EventArgs e)
at System.Web.UI.Control.LoadRecursive()
at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
Request information:
Request URL: http://www.greenwichlibrary.org/pageincludes/TeenTabContent.aspx
Request path: /pageincludes/TeenTabContent.aspx
User host address: 172.22.1.52
User:
Is authenticated: False
Authentication Type:
Thread account name: NT AUTHORITY\NETWORK SERVICE
Thread information:
Thread ID: 16
Thread account name: NT AUTHORITY\NETWORK SERVICE
Is impersonating: False
Stack trace: at ASP.pageincludes_teentabcontent_aspx.Page_Load(Object sender, EventArgs e)
at System.Web.Util.CalliHelper.EventArgFunctionCaller(IntPtr fp, Object o, Object t, EventArgs e)
at System.Web.Util.CalliEventHandlerDelegateProxy.Callback(Object sender, EventArgs e)
at System.Web.UI.Control.OnLoad(EventArgs e)
at System.Web.UI.Control.LoadRecursive()
at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
Custom event details:
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Event Type: Warning
Event Source: ASP.NET 4.0.30319.0
Event Category: Web Event
Event ID: 1309
Date: 3/20/2012
Time: 4:03:35 PM
User: N/A
Computer: *REDACTED*
Description:
Event code: 3005
Event message: An unhandled exception has occurred.
Event time: 3/20/2012 4:03:35 PM
Event time (UTC): 3/20/2012 8:03:35 PM
Event ID: 16155f96f03a4866afb4039622523146
Event sequence: 30240
Event occurrence: 906
Event detail code: 0
Application information:
Application domain: /LM/W3SVC/2018911400/Root-1-129767166973177500
Trust level: Full
Application Virtual Path: /
Application Path: C:\Inetpub\wwwsites\LibraryWeb\
Machine name: *REDACTED*
Process information:
Process ID: 8144
Process name: w3wp.exe
Account name: NT AUTHORITY\NETWORK SERVICE
Exception information:
Exception type: NullReferenceException
Exception message: Object reference not set to an instance of an object.
at ASP.pageincludes_maingltabcontent_aspx.Page_Load(Object sender, EventArgs e)
at System.Web.Util.CalliHelper.EventArgFunctionCaller(IntPtr fp, Object o, Object t, EventArgs e)
at System.Web.Util.CalliEventHandlerDelegateProxy.Callback(Object sender, EventArgs e)
at System.Web.UI.Control.OnLoad(EventArgs e)
at System.Web.UI.Control.LoadRecursive()
at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
Request information:
Request URL: http://www.greenwichlibrary.org/pageincludes/MainGLTabContent.aspx
Request path: /pageincludes/MainGLTabContent.aspx
User host address: 172.22.1.52
User:
Is authenticated: False
Authentication Type:
Thread account name: NT AUTHORITY\NETWORK SERVICE
Thread information:
Thread ID: 18
Thread account name: NT AUTHORITY\NETWORK SERVICE
Is impersonating: False
Stack trace: at ASP.pageincludes_maingltabcontent_aspx.Page_Load(Object sender, EventArgs e)
at System.Web.Util.CalliHelper.EventArgFunctionCaller(IntPtr fp, Object o, Object t, EventArgs e)
at System.Web.Util.CalliEventHandlerDelegateProxy.Callback(Object sender, EventArgs e)
at System.Web.UI.Control.OnLoad(EventArgs e)
at System.Web.UI.Control.LoadRecursive()
at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
Custom event details:
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
--Will--
Member
72 Points
28 Posts
Re: Intermittent connection errors on ASP.NET 4 site
Mar 21, 2012 03:45 PM|LINK
We heard back from our provider folks, and it appears that we also had a number of MS patches and updates made to the server on the last day of January. The coincidence seems uncanny in regard to timing, and it's possible that the problems were already occurring and that I was merely the first to really notice it 7 days later. Anyone have any thoughts on this? Thanks...
--Will--
Member
72 Points
28 Posts
Re: Intermittent connection errors on ASP.NET 4 site
Mar 22, 2012 01:29 AM|LINK
Anyone? Please? I could really use some help on this.
The only other thing I can think of trying is to uninstall all the updates that went through on January 31 and see if that resolves the issue, then selectively add them back in to see which one is the culprit. But if it's something I could be doing better/different in my code, I'd rather know that. At this point I'm thinking that I should at least put in the try/catch so that the page will at least load (albeit with an error message in place of the content that was supposed to be scraped), but that still doesn't sound like a real solution to me.
necro_mancer
Star
7981 Points
1566 Posts
Re: Intermittent connection errors on ASP.NET 4 site
Mar 22, 2012 02:55 AM|LINK
hi will,
do you host it on a shared server or a dedicated server?
Professional SQL 2008 R2 Service
--Will--
Member
72 Points
28 Posts
Re: Intermittent connection errors on ASP.NET 4 site
Mar 22, 2012 03:05 AM|LINK
Hi necro_mancer,
It's a dedicated server, hosted by us, but it is also host for our development site which is available by local intranet (can also be accessed externally via VPN though when we need such). We also have 3rd-party support that has access to the server (and other parts of our network) that is responsible for maintenance, backups, applying updates, etc.
--Will--
Member
72 Points
28 Posts
Re: Intermittent connection errors on ASP.NET 4 site
Mar 22, 2012 03:01 PM|LINK
I tried Googling around for the various patch versions that were applied at the end of January, but I didn't have any luck pinpointing any of those in regard to causing similar problems elsewhere. As mentioned, my code was working fine up until then, and it still works, up to and until the server hangs for a given browser session.
--Will--
Member
72 Points
28 Posts
Re: Intermittent connection errors on ASP.NET 4 site
Mar 23, 2012 03:13 AM|LINK
Our network maintenance folks rolled back the 2 .NET 4 patches earlier tonight: KB2656351 and KB2572078
My testing as of a half hour ago failed to cause any errors whatesoever, no matter how many times I clicked/refreshed, many dozens of times in a row. I'll be testing some more tomorrow when server load is closer to normal usage, but it's looking like one or both of those patches were responsible for causing the errors.
I know so far this has been a stumper for folks here. Now that the issue seems to have narrowed down, anyone have any thoughts on this?
mrattray
Member
2 Points
1 Post
Re: Intermittent connection errors on ASP.NET 4 site
Mar 28, 2012 09:17 PM|LINK
Hi just wondering on the status of your site now that its been a few days since you rolled back your patches? Has the site continued to run correctly?
We updated our server with those patches(among others) on Tuesday and have been having connection problems and site slowdowns ever since. The symptoms look exactly like what you originally described.
However I haven't been able to find any other internet posts about other people experiencing this problem so we are hesitant to roll back the updates without more confirmation that they are actually the root of the problem.
How did you come up with those two patches as the cause?
Thanks, any info you can provide to help convince my coworkers that we actually need to do this is very appreciated.
Monte
--Will--
Member
72 Points
28 Posts
Re: Intermittent connection errors on ASP.NET 4 site
Mar 29, 2012 03:23 PM|LINK
Hi Monte,
Our site has been running great since we rolled back those two patches. No time-outs, no errors, and speed is as good as it ever was.
We determined those patches by looking at when the problems were first observed--around the 7th of February. Taking into account a delay in noticing the symptoms due to not expecting them, and the fact that they were intermittent as opposed to consistent, and the timing coincided with the latest server patches/updates that went in at the end of January. Basically I said to our network folks: "the site was running fine prior to then, and none of the code has changed. So what *has* changed?", and the updates were the answer; out of the dozen or so patches that were applied at the time, these 2 were specifically for ASP.NET 4.
I haven't seen anything official from Microsoft about them either, but as is the nature of many of these patches, they will often affect one segment of users and not others. Googling around will confirm that...
The easiest way to see if they're the problem is to just roll them back (and restart the server, etc). If the site works fine again, then you know you nailed it. If not, then look at any other changes made. Patches can always be re-applied in the case that they weren't at fault.
I still don't know what they broke, exactly, but if I had to guess, I would say it's probably session-related. While the site was hanging in one browser, another could be opened and the site loaded just fine (for a while).
If you decide to roll back the patches, I'd be interested to hear if that works for you!
mteichrob
Member
4 Points
2 Posts
Re: Intermittent connection errors on ASP.NET 4 site
Aug 09, 2012 09:25 PM|LINK
One of our internal sites has been experiencing this same problem since moving it to a new server.
Initially I thought the difference was the new server is running IIS 7 (old was IIS 6), but now I think the it's that the new server has these two patches installed while the old one did not.
I'm curious to know if you have since re-applied either of these two patches and/or installed any newer MS patches? I'd love to know if any newer patches supercede (and fix) these ones?
Thanks --Matt