Scott Hanselman

Back to your regularly scheduled technology blog: ASP.NET ClientSide JavaScript Fix for Validation Problems in .NET Framework 1.1 SP1 and ASPNET_REGIIS -c

September 14, 2004 Comment on this post [2] Posted in ASP.NET | Bugs
Sponsored By

OK, back to programming, as this is not a political blog.  Apparently there's some trouble with the .NET Framework Service Pack 1.  I personally have not experienced this problem, and I have to admin that it's so obviously weird that I am suspicious that it is in fact a bug.  Lots of stuff should/could never have worked if it is.  It's likely an install/permissions related bug.  That said, here's the details from a recent series of posts on Channel9.


  • ASP.NET Forms stop posting back when they have validators on them
  • Errors in Event Viewer like "Failed while copying the ASP.NET client side script files to directories under D:\Whatever. Error code: 80070005"

Fix/Potential Fix

  • Copy a PRE-SP1 version of WebUiValidation.js over the one you have in aspnet_client.
    • Certainly make sure you HAVE an aspnet_client folder either in that directory or mapped in another VDIR. (This is a common and unrelated problem.)

I'll get the details/diffs on the changes in this file and post them soon.

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.

facebook twitter subscribe
About   Newsletter
Hosting By
Hosted in an Azure App Service
September 15, 2004 4:12
I hit just this problem on one of my sites yesterday. Putting in a new aspnet_client directory fixed the problem.
September 17, 2004 21:07
Framework 1.1 SP1 has hosed my whole ASP.NET engine on my Win2003 dev box (Returns 500 errors on any aspx/asmx/etc). It yields nasty exceptions in VS 2003 on that box trying to just open a web solution. I have a support ticket in the works - we'll see what they say.

Comments are closed.

Disclaimer: The opinions expressed herein are my own personal opinions and do not represent my employer's view in any way.