mr_davidlaing
asked on
IIS Admin service fails to start after installing System State backup to a new machine
As part of by disaster recovery plan, I want to do a test reinstall of a Windows 2003 webserver.
The webserver is a bit of a jack of all trades; it runs Windows 2003 Server (Standard), IIS6, SQL Server 2000 and Active Directory.
I back it up using NT Backup; including backups for c:\InetPub, and the System State.
During my test restore, I build a new Windows 2003 server in a virtual PC, install all the software (IIS, Active Directory, SQL Server etc), and then try to restore my backups.
Restoring the files works fine.
However, when I restore the system state, the IIS admin service breaks completely. It fails to start with the following error:
"Windows could not start the IIS Admin Service on local computer. For more information review system event log. If this is a none Microsoft service, contact the the service vendor, and refer to the service specific error code: 2146893813"
In the Event log I have the following error:
"The IIS Admin Service service terminated with service specific error 2148073483"
Now, I suspect that this has something to do with the MetaBase.xml encryption being machine specific. I've manually exported a backup of the IIS Metabase using iisback.vbs using a specified password (rather than the machine password). However, I can't figure out how to restore this because I can't get IIS Admin Service to start.
So, my questions are:
(a) Does anyone know how to get IIS Admin Service to start again?
(b) How do other people backup and restore active directory via System State backup without breaking IIS on restore?
Thanks
David
The webserver is a bit of a jack of all trades; it runs Windows 2003 Server (Standard), IIS6, SQL Server 2000 and Active Directory.
I back it up using NT Backup; including backups for c:\InetPub, and the System State.
During my test restore, I build a new Windows 2003 server in a virtual PC, install all the software (IIS, Active Directory, SQL Server etc), and then try to restore my backups.
Restoring the files works fine.
However, when I restore the system state, the IIS admin service breaks completely. It fails to start with the following error:
"Windows could not start the IIS Admin Service on local computer. For more information review system event log. If this is a none Microsoft service, contact the the service vendor, and refer to the service specific error code: 2146893813"
In the Event log I have the following error:
"The IIS Admin Service service terminated with service specific error 2148073483"
Now, I suspect that this has something to do with the MetaBase.xml encryption being machine specific. I've manually exported a backup of the IIS Metabase using iisback.vbs using a specified password (rather than the machine password). However, I can't figure out how to restore this because I can't get IIS Admin Service to start.
So, my questions are:
(a) Does anyone know how to get IIS Admin Service to start again?
(b) How do other people backup and restore active directory via System State backup without breaking IIS on restore?
Thanks
David
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Backing up a DC is always a fun experience - one which is made no easier by having things like IIS and/or Exchange installed.
For a drop and run solution you would need to perform a full backup and restore it to identical (or at least very similar) hardware. If it was just AD you were worried about we could look at System State restores and such but this is more like backing up two different systems at the same time.
Worst comes to worst you could take a copy of the metabase from a System State backup and import the sites from it using the ISM and you might not have to do any additional configuration - at most you would need to set userID and password information for anonymous access and Application Pool activation.
Dave Dietz
For a drop and run solution you would need to perform a full backup and restore it to identical (or at least very similar) hardware. If it was just AD you were worried about we could look at System State restores and such but this is more like backing up two different systems at the same time.
Worst comes to worst you could take a copy of the metabase from a System State backup and import the sites from it using the ISM and you might not have to do any additional configuration - at most you would need to set userID and password information for anonymous access and Application Pool activation.
Dave Dietz
ASKER
I've just spoken with MS technical support; and they laughed at the thought of trying to reinstall a AD system state backup on a Virtual Machine. As you mention, system state backups are pretty machine specific. I just wish this was pointed out in slightly larger letters in the documentation!
Dave, I'm unfamiliar with the ISM tool. What does that stand for, and where can I find out about it?
Dave, I'm unfamiliar with the ISM tool. What does that stand for, and where can I find out about it?
ISM = Internet Services Manager -> The IIS management console..... :-)
Dave Dietz
Dave Dietz
ASKER
Doh! My accronym expansion braincells have obviously gone on holiday. I have the pleasure of being intimately associated with the ISM :) Thanks for all your help.
Not a problem.... :-)
Dave Dietz
Dave Dietz
ASKER
Thanks for the advise.
I've tried out (a); and as you suggest, if you specify a password when backing up the metabase using iisback.vbs, then it uses your password rather than the machine encryption key. I've thus been able to successfully restore the metabase to a new machine using the supplied password.
Concerning (b):
Unfortunately I can't get around installing IIS on the DC (we're a small company, and only have one dedicated hosting machine :). Are you suggesting that there is no way to backup the DC (and IIS) other than making a full hard drive backup? Is it possible to restore this full backup to a different machine (imagining the datacentre was destroyed by fire), or will I still encounter the same machinekey/SID problems?
Thanks
D