While testing the installation of SP1 on our new environment having four front-end servers the error "The installation of this package failed' popped up on two servers. Being the Google fanatic that I am, I found a KB article that explained the error and the error was related to having not enough space available. So I checked the space available and I had >5gb of storage available on the system drive so this was, as you may have guessed, not the problem. I opened up the eventviewer of the servers and find the following errors :
Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7024
Date: 4/17/2008
Time: 12:37:26 PM
User: N/A
Computer: webserver1
Description:
The IIS Admin Service service terminated with service-specific error 2149648394 (0x8021080A).
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Event Type: Error
Event Source: IIS Config
Event Category: Catalog
Event ID: 4275
Date: 4/17/2008
Time: 12:37:26 PM
User: N/A
Computer: webserver1
Description:
Error parsing XML file. Reason: An invalid character was found in text content.
Incorrect XML:
ErrorCode : 0xC00CE508
Interceptor : 14
OperationType : Populate
Table : MBProperty
ConfigurationSource : file:///C:/WINDOWS/system32/inetsrv/MetaBase.xml
Row : 0
Column : 0
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
So next thing to Google was the "The IIS Admin Service service terminated with service-specific error 2149648394 " error! And luckily the first hit was The IIS Admin Service service terminated with service-specific error 2149648394 (0x8021080A). by Mike Hamilton ;) Strangely enough I wasn't the only with the same symptoms and problems and it was all related to the SP1 upgrade:
Interstingly, during that reboot - which for all intents should have gone fine - I see a hoard of DSKCHK processes running. Invariably, something got out of wack on the NTFS volumn between my shutting the image down and bringing it back up. During the 'fixing' process - a number of files invaribly can become corrupt - and the Metabase.xml - the blood-life of your IIS Admin service - is no exception.
Hope this helps someone ;)