Today's Errors: "Unexpected Error 0x8ffe2740 Occurred" Error Message When You Try to Start a Web Site and "Not Running ASP.NET Version 1.1" Error Message When You Try to Open an ASP.NET Web Application Project in Visual Studio .NET 2003
Good times, good times. Twenty minutes before a demo to a bank, I get this:
"Not Running ASP.NET Version 1.1" Error Message When You Try to Open an ASP.NET Web Application Project in Visual Studio .NET 2003
Now, of course, I know darn well I'm only running .NET 1.1 on this box. Hell if I know what's going on, but I've done the whole ASPNET_REGIIS thing before, so I run aspnet_regiis -ua, then aspnet_regiis -i (I could have just done -r, probably).
Didn't work. I DO have some funky stuff in my Web.config customerrors section that has a defaultredirect. Ah! http://support.microsoft.com/?id=825792 says:
"If the defaultRedirect attribute is set to an HTML file or to an ASP file, the request for the Get_aspx_ver.aspx file does not return the ASP.NET version information."
Bingo? No...now I get:
"Unexpected Error 0x8ffe2740 Occurred" Error Message When You Try to Start a Web Site
I see the 0x8ffe2740 and a Stop Sign in IIS's MMC. Turns out another process started up while IIS wasn't running and took over Port 80. Running TCPView made it clear.
So, 13 minutes spent Googling and Troubleshooting. Demo looks good and I've got 7 minutes to blog about it.
Would this be a good interview test problem for a potential employee? Like, literally give them a laptop with this problem and say "fix it." My CTO could have solved this problem as well in similar time, but I wonder (as I read Google Groups) if there aren't people who would waste days on this kind of problem. Thoughts?
About Scott
Scott Hanselman is a former professor, former Chief Architect in finance, now speaker, consultant, father, diabetic, and Microsoft employee. He is a failed stand-up comic, a cornrower, and a book author.
About Newsletter
Just Kidding :)
-paolo
Thanks again.
Comments are closed.
A good hiring test is seeing how quickly people figure out that they're thrashing, rather than how fast they can get a solution. What external resources do they turn to? Do they give up? Do they say "I haven't found an easy solution, I'm prepared to start on the hard ones."
My catch phrase when hiring has long been "the difference between a senior and junior developer is the senior developer asks more questions."