I'm not sure what is going on here, however if someone could provide a second opinion or suggestions it would be much appreciated.
We're recieving the above exception message which google indicates seems to be generated from the umbracoBase/RequestModule.cs (umbraco version 4.5.2)
It seems this (or perhaps one of the related errors) causes a permanent failure of the website, every subsequent request times out.
-- more details --
Surrounding errors (at the same second) are being logged for the client dependency framework, and windows desktop search... ( I guess these errors are probably not relevant as any two errors may produce the same result??, however I've upgraded Client dependency framework and removed windows desktop search which should not have been on anyway.)
As this is an error that can occur in the requestHandler (inherits from .net's IHTTPModule), I would guess that this is related to the client dependency framework. Did you get this error before you upgraded it? Any other changes made before this error popped up?
Two errors are being handled at the same time
I'm not sure what is going on here, however if someone could provide a second opinion or suggestions it would be much appreciated.
We're recieving the above exception message which google indicates seems to be generated from the umbracoBase/RequestModule.cs (umbraco version 4.5.2)
It seems this (or perhaps one of the related errors) causes a permanent failure of the website, every subsequent request times out.
-- more details --
Surrounding errors (at the same second) are being logged for the client dependency framework, and windows desktop search... ( I guess these errors are probably not relevant as any two errors may produce the same result??, however I've upgraded Client dependency framework and removed windows desktop search which should not have been on anyway.)
As this is an error that can occur in the requestHandler (inherits from .net's IHTTPModule), I would guess that this is related to the client dependency framework. Did you get this error before you upgraded it? Any other changes made before this error popped up?
We don't seem to have had this error again since upgrading CDF, will keep you posted.
is working on a reply...