Boy “catastrophic”… Sounds pretty horrible, huh? It’s really just a little problem created by Win2000 SP4 if that SP is implemented before installing ASP.NET on a remote server. This was my case because I only recently (finally) put .NET 1.1 on my in-house webserver.
So anyway, I didn’t waste too much time with my little “catastrophy” before I just hit google, got to KBAlertz which had the MSDN solution listed. Here:
This is surely old news, but it was new to me so I thought I’d just stick it in here.
Sign up for my newsletter so you don't miss my conference & Pluralsight course announcements!