David
Thu Feb 02 23:54:01 CST 2006
metabase.xml and mbschema.xml should be restored together.
Usually, it ends up being ok to just restore the metabase.xml because real
configuration is stored in there. mbschema.xml is just data related to how
to interpret the real configuration in metabase.xml. Usually the schema is
never customized hence never changes; thus you can safely restore just
metabase.xml.
Not certain why your mbschema.xml is being changed -- mine stays the same
when starting W3SVC. In fact, mine stayed the same since installation across
reboots/restarts. I only see metabase.xml being changed when starting up,
which is ok because some volatile runtime data gets stored and thus the
datestamp change.
--
//David
IIS
http://blogs.msdn.com/David.Wang
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"The_Canuck" <cruisein2002@yahoo.com.DONOTSPAM> wrote in message
news:2CED4455-3E4A-4C77-9349-E5A51AC5F4A0@microsoft.com...
> We have backups in place. It's just a little hard to work with on the
> crippled server.
>
> Question -> When restoring these files is it important to restore
> METABASE.xml MBschema.xml at the same time?
>
> I tried restoring MBschema.xml and when I tried to start the w3svc
> service
> manually from services I noted that w3svc did not start and the file was
> changed. The MBschema.xml is being changed when w3svc is attempting to
> start up.
>
> I am *suspicious* that SAV10 (Symantec AntiVirus) may have something to do
> with this problem. Note that SAV10 should have the approriate exclusions
> set
> for exchange as indicated in Symantecs technical bulletin. SBS (Small
> Business server is a bit different though.
>
> Can anyone tell me if I can restore MBschema.xml and METABASE.xml
> independantly?
>
>
> Can anyone explain why the MBschema.xml is being modified when w3svc
> service attempts to start?
>
>
>
> "David Wang [Msft]" wrote:
>
>> I doubt critical updates *caused* the corruption.
>>
>> IIS6 has had maybe 2-3 critical fixes to date, none directly in IIS
>> itself,
>> and none touch configuration, so I doubt critical updates caused
>> corruption.
>> Now, updates which restart the server and cause unexpected closure of the
>> configuration file handle... that may cause data corruption.
>>
>> Since you have data corruption, your best option is to restore from a
>> valid
>> backup of those XML files.
>>
>> You could try to hand-modify the textual XML file, but without an idea of
>> what was originally "valid", this will be hard. It will also take some
>> skill
>> to reconstruct the file, and it may not be correct.
>>
>> There is no way to regenerate a valid IIS configuration without
>> reinstallation of IIS, and since SBS involves OWA, Exchange, and
>> Sharepoint
>> running on top of IIS, this pretty much means you should reinstall the
>> entire SBS all over. You should be able to backup/restore Exchange and
>> Sharepoint data independent of IIS, so you can reinstall SBS and the
>> restore
>> your Exchange/Sharepoint data over it.
>>
>> And remember the backups this time! Data corruption is generally harder
>> to
>> fix and far easier to simply restore a backup.
>>
>> --
>> //David
>> IIS
>>
http://blogs.msdn.com/David.Wang
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>> //
>>
>> "The_Canuck" <cruisein2002@yahoo.com.DONOTSPAM> wrote in message
>> news:AAC2D6FE-F2C0-4199-A372-F4C18CBD5DEA@microsoft.com...
>> > w3svc won't start on my SBS 2003 machine with all the SP1 updates and
>> > all
>> > critical updates applied (Critical updates were added about 1 week
>> > before
>> > this problem started.
>> >
>> >
>> > I have determined that the MBschema.xml file is corrupt (I am familiare
>> > with
>> > tags).
>> >
>> > All of the copies in the history folder are also crorrupt. The
>> > metadata
>> > folder contains the original file of a bit smaller size. I copy that
>> > to
>> > the
>> > right place and try to start up w3svc again and the service does not
>> > start.
>> > The file grows to the same size as the corrupted size again?
>> >
>> > Can anyone help? I can't get any response from iisadmin even though
>> > the
>> > service is running. Was this caused from an update?
>> >
>> >
>> > Details below....
>> >
>> >
>> > Thanks
>> >
>> >
>> >
>> >
>> > Check if w3svc service is running No
>> > Check if iisadmin service is running Yes
>> >
>> > C:
>> > cd \windows\system32\inetsrv
>> > dir METABASE.xml MBschema.xml history metaback
>> >
>> > notepad METABASE.xml
>> > notepad MBschema.xml
>> >
>> > line 211 of MBschema.xml is corrupt for sure
>> >
>> > cd history (look at automatic iis backups)
>> > All automatic backups are also corrupt
>> > check whether the nodes "W3SVC" and "W3SVC/1" exist in your current
>> > metabase.xml. I don�t think the nodes exist
>> > 2. Also, on the commandline, run:
>> > CSCRIPT %SYSTEMDRIVE%\inetpub\adminscripts\adsutil.vbs enum
>> > w3svc/1/root
>> > Does not respond
>> > C:\WINDOWS\system32\inetsrv>
>> > C:\WINDOWS\system32\inetsrv>
>> > C:\WINDOWS\system32\inetsrv>
>> > C:\WINDOWS\system32\inetsrv>
>> > C:\WINDOWS\system32\inetsrv>CSCRIPT
>> > %SYSTEMDRIVE%\inetpub\adminscripts\adsutil.vbs enum w3svc/1/root
>> > Microsoft (R) Windows Script Host Version 5.6
>> > Copyright (C) Microsoft Corporation 1996-2001. All rights reserved.
>> >
>> >
>> >
>>
>>
>>