Well, I have this web application that uses Form Authentication - the problem occurs during the Login from Login. If I click on a navigation link, I am taken to the correct page and the LoginView shows that I am logged in but without navigating away from the Login page, I am just stuck there.
Thanks sumitd for your help. That was my problem - I had a detached assembly but referenced it in my web. The WebReference.
Other symptoms that I was having as well is when I hit the login button, it would direct me to a web page and in the url it would look something like this:. Pages without need for scrips do not get the error since they do not user the webresource.
There are other issues with IIS7 that you can read about in the forums. To clear things up: this workaround does not fix this problem, it does just allow the handlers to reload if the app pool has already crashed.
So if you use this code, you will still get the error, but you do not have to reset the iis every time it happens. Martin, that is correct. My guess is that this error is triggered by some sort of race condition during startup. We have the same problem with some of our EPiServer sites. Thank you for the workaround! Steve has been running this in the stress lab for a couple days.
After several hundered machine-hours of stress while touching config every 3 minutes they have not been able to reproduce the issue. This is probably a race condition that occurs because the framwork or application we have does something special.
But I have not been able to create a simple reproducable test case. Has anyone? In my case, the framwork I use EPiServer , has code that loads all assemblies in the bin folder in the constructor of the global. It does this because it looks for classes with plug-in attibute. This in combination with the call to EnsureHandlerExistenceChecked on the start page does probably increase the risk for the problem.
It occurs very frequently on both production and development servers. We have several developers working against the same dev. All the top google results for this seems to be EPi related, so this is definetly something they should look into. What, basicly, is the difference as they seem to do the same functionality. David Williams: I don't know for sure. Keep in mind that WebResource.
NET 2. My guess is that when developing ASP. That is my guess; to get a definitive answer you'd need to talk with someone at Microsoft. Sign up or log in Sign up using Google. Sign up using Facebook. Sign up using Email and Password. Post as a guest Name. Email Required, but never shown. The Overflow Blog. NET Framework version 2. I think this is a hold-over from when people were transitioning from v1.
These days all application pools should be configured for. The question becomes: what happens with. NET 3. NET 4? Is it better to add that attribute parameter for the future, or to leave it out for the future? The help page referenced above provides this sample for IIS7 when Telerik. For anyone not familiar with the syntax, the question might arise: - Should the name attribute have underscores or periods? I don't know. Note that for GAC references the assembly version is required, since the GAC can contain multiple assemblies for the same component but different versions.
Why did I write this? I was recently chasing down errors where FireBug is reporting Unauthorized errors for WebResource. Fiddler2 reports no such errors. Confused about this I started looking closely at my web.
0コメント