Searching for my lost shaker of salt

We had troubles installing SP1, which consists of two components; WSS 3.0 SP1 and MOSS SP1.  The WSS 3.0 SP1 failed toward the end of the set up process, for a familiar yet troubling reason.  Once upon a time several past lives below, I blogged about the loss of intellisense because I had used the ASP.NET Configuration utility.  Well, apparently that little helper app is completely evil since it caused this error as well when it changes the schema in your web.config.  Here are all the ugly details from my co-worker, Denise:

The install for Windows SharePoint Services 3.0 SP1 failed when it attempted to update an extended site that was using a host header.  If we removed the site from SharePoint, the install completed successfully.  We initially thought the issue was because we were using an extended site.  After some troubleshooting, we discovered the problem was in the web.config for the site. The second line of the web.config contained:  <configuration xmlns="http://schemas.microsoft.com/.NetConfiguration/v2.0">.  As soon as we removed the schema reference from the <configuration> tag, the install completed successfully.  The altered tag was in only one of our sites and, after further research, we discovered that it was inserted when we ran the Web Site Administration Tool in Visual Studio 2005.  It does not appear to be a valid schema and the sites work without it.