Welp my problem with the remote console started about a month after I got the MSS....it messed up my DOMAIN NAME settings...so much so that TZO had to give me an external program in order to have the domain name attached to my ip address...we think it was an add in that messd it all up...

but I tried to do a system restore...and I know when I did that, it still kept some settings from my old set up whcih means it doesnt erase or reset all files....so the possiblity of corruprted files still existed...so the only way is to do a factory restore....which I will do tonight becuase its getting worse..

First Im backing all my files to my backup enclosre ( CFI Enclosure, 4 1 TB Western Digital GPs )...taking out all 4 drives from my MSS.....
Put in a 1 TB Seagate for the system drive......and do a factory restore....
Then put in the other 3 drives into my MSS ( one at a time )....
Once thats done, Ill connect the CFI enclosure and move over all the info. Neddless to say, this will take a while nice I have about 2 TB of info...

Anyone see a flaw with my plan?

_________________
HP MediaSmart- 2GB RAM - Upgraded CPU LE-1620
APC UPS - 1300VA
10.5 TB ( 6.5 for Data 4 for backup )
CFI ESata 4 Bay Enclosure
San Digital 4 Bay Enclosure-USB ( for backup )
3 Apple TVs - Streaming from MSS
2 Xbox 360 - Streaming from MSS

It's pretty bizarre how mine came out of the blue like that. And then the system restore totally hosing it worse... although I suppose that might have been my fault for restarting it before finishing the setup assistant.

I did the factory restore last night and just finished copying back all my data from my secondary drive. It remained intact on there so all I did was remove it from the system during the restore, spot check the files using a SATA-to-USB adapter on my desktop PC (that $30 purchase has been a lifesaver SO many times), and then copy the data back before adding the drive back to the pool.

I also deleted all partitions and formatted the primary drive on my PC before doing the factory restore because I read in here about potential problems if you don't. (Sticky: README if you want to re-use WHS drives!)

Your plan sounds fine to me. Maybe a little overkill, but better to be safe than sorry.

Good luck.

_________________
Sue

Thanks for the help Sue. My problem turned out to be a bunch of files in the C:\Windows\Temp directory that appear to be zipped file sets for download. There were about 12GB of these, all named something like "wsdnld52800zip" After deleting these files all seems fine. I have no idea what "strands" these files. I haven't seen anything posted on this problem anywhere yet. If find something I'll post.

Thanks, Jay

I had EXACTLY the same issues. Fortunately the solution was easy. All i had to do was follow the instructions:

"This error usually occurs when the MetaBase.xml file is either missing or has been corrupted. MetaBase.xml is the file wherein the IIS 6 configurations are written to and read from.

The default location for MetaBase.xml is C:\WINDOWS\system32\inetsrv\ . The default location for MetaBase.xml file back up is C:\WINDOWS\system32\inetsrv\History\

To solve this problem you can either restore the copy of the MetaBase.xml file (If you have a separate backup) or grab a copy from the History folder and place it in the C:\WINDOWS\system32\inetsrv\ folder. After which rename it to MetaBase.xml. Rename it to MetaBase.xml? Yeah! That's because in the History folder you will find the backup in the form MetaBase_0000000244_0000000000.xml . Subsequently, you will also find backups of the MBSchema.xml in the same format."

Original article can be found at http://www.iisworkstation.com/2008/07/t ... t-iis.html