No, this isn’t technical support… it’s somewhere everyone on Win2 can come for emotional support - hugs, consolation and sympathy. To share their feelings in a safe, supportive environment, knowing that we will all grow from this experience. We feel your pain.
haha 
We are pretty sure we nailed the issue already. Response times have been great since..
I’m sorry for all these slowdown issues Win2 has been facing for the last 2 or so weeks. We ran through every possible logic tree that we could think of that was responsible for causing Win2 to suddenly slow up.
What we have settled on is an issue with the metabase. Some frontpage websites had corrupt metabase entries with a zero host number. IIS seems to have been performing some sort of search that used to lock it up and make it incredibly slow. This issue was like a needle in the haystack.. There were no obvious signs of it except for some odd Frontpage error messages that Microsoft’s Support KB didn’t make them seem the cause for IIS to lock up or crash.
We think we have solved this. Everything seems fine. We are watching it closely. But morning will tell
I think Yash and I together have spent longer on this matter than anything this year, its been quite a bear to this point, and withthe help of a psoft developer, we do think we may have it IDed now as to the issue.
Come on Stephen, Yash, own up:
you changed the dotnet security permissions while you were there didn’t you ?
My sites are still down as I get a security exception - I suspect its something I’m doing… I’m [DllImport]ing from Kernel32.dll (to use the high performance timer - queryPerformanceCounter etc). But it WAS working
inoodle
All .NET 2.0 sites are working to my knowledge and no permissions were changed. Have you looked into this error in MS’s documentation? Also please submit a ticket with the URL and error. I’ve not seen anything like this.
I’d also be surprised that you could directly use a kernel function in your .NET application prior as you claim
Hi Yash.
I have to say, I’m certain you changed ASPnet 2.0 to run in a Partial Trust setting. This means that anybody using any 3rd party assemblys which are ‘strong named’ must get those assemblys updated to have the [assembly:AllowPartiallyTrustedCaller] attribute added to them. As far as I’m aware its not (easily) possible to do this without the source code.
I have worked around this by adding:
in my web.confg (inside system.web element).
I’m not entirely sure you want me to be able to do this though
It wouldn’t be the first (second, third…) time I’ve been wrong, but that looks like what has happened.
Cheers
inoodle
Hi, I am sorry. You are correct. We downgraded ASP.NET 2.0 security to medium trust. There were some sites running incorrectly in full trust.
All ASP.NET applications have always run in medium trust at JodoHost and full trust is a security risk. If you noticed, 1.1 is running in medium trust
Hi Yash,
Glad I’m not going mad then
I think the problem comes from the fact that Medium trust in aspnet 2.0 is stricter than in 1.1.
This is probably something that will cause a few issues when people migrate - could be worth a kb entry - although of course its the right way to go.
Cheers
inoodle