problem with IIS / Exchange (SBS2003): cannot reinstall IIS

Hi all,

Yesterday we had to reboot our SBS2003 server and i ran MS update to get all
the latest updates for the occasion.

After the server came back up, IIS wouldn't start:

The IIS Admin Service service terminated with service-specific error
2148073483 (0x8009000B).

I Googled a bit and then attempted to reinstall IIS. During reinstall, parts
of IIS (iisadmin) will start, others will not. After install, when issadmin
is restarted, iisadmin couldn't find a file and won't start at all. I quess
it is a problem with the metabase.

Somewhere is the process i also reinstalled the IIS SMTP service, killing
Exchange. I'm in a bit of a problem now: Cannot repair the Exchange install
because it relies on IIS and IIS will not install properly/cleanly.

I have checked permissions on the MachineKeys folder, checked the Machinekey
in the registry and have a copy of the MetaBase.xml from after the updates
(couldn't find an older one on backups). What I don't understand is why IIS
doesn't generate a new working metabase.

Any pointers and or suggestions? Is there a way to get better error messages
from the IIS processes and/or is there a way to generate a new, clean
metabase?

TIA!

Vincent de Lau
vincent@dgngroep.nl

Good morning, Vincent.

I would suggest that you contact MS-PSS. I have never had this situation
before, but I do remember serveral posts in here (or, was it exchange.admin)
where having to fix IIS via the resinstallation method simply does not work.

Save yourself sometime and bite the bullett. $245.00 is not that bad
compared to the time it would take you (if it is possible).

Cary

"Vincent de Lau" <vincent@dgngroep.nl> wrote in message
news:u%23gVUYilIHA.4480@TK2MSFTNGP03.phx.gbl...
> Hi all,
>
> Yesterday we had to reboot our SBS2003 server and i ran MS update to get
> all the latest updates for the occasion.
>
> After the server came back up, IIS wouldn't start:
>
> The IIS Admin Service service terminated with service-specific error
> 2148073483 (0x8009000B).
>
> I Googled a bit and then attempted to reinstall IIS. During reinstall,
> parts of IIS (iisadmin) will start, others will not. After install, when
> issadmin is restarted, iisadmin couldn't find a file and won't start at
> all. I quess it is a problem with the metabase.
>
> Somewhere is the process i also reinstalled the IIS SMTP service, killing
> Exchange. I'm in a bit of a problem now: Cannot repair the Exchange
> install because it relies on IIS and IIS will not install
> properly/cleanly.
>
> I have checked permissions on the MachineKeys folder, checked the
> Machinekey in the registry and have a copy of the MetaBase.xml from after
> the updates (couldn't find an older one on backups). What I don't
> understand is why IIS doesn't generate a new working metabase.
>
> Any pointers and or suggestions? Is there a way to get better error
> messages from the IIS processes and/or is there a way to generate a new,
> clean metabase?
>
> TIA!
>
> Vincent de Lau
> vincent@dgngroep.nl
>

Vincent,

You were very close to the resolution but missed it. You have to rename the
MachineKey folder and not just to check the permissions on it. I am sure you
must have been getting the following errors in component installation log of
IIS

Error writing encrypted data to the Web Server's configuration database
(Metabase).
0x8009000b=Key not valid for use in specified state
Press 'Retry' to retry or 'Write UnEncrypted' to the data unencrypted.
You can change this data back to encrypted after the setup has completed.
Buttons -- Retry, Write UnEncrypted, Write UnEncrypted All

"Vincent de Lau" wrote:

> Hi all,
>
> Yesterday we had to reboot our SBS2003 server and i ran MS update to get all
> the latest updates for the occasion.
>
> After the server came back up, IIS wouldn't start:
>
> The IIS Admin Service service terminated with service-specific error
> 2148073483 (0x8009000B).
>
> I Googled a bit and then attempted to reinstall IIS. During reinstall, parts
> of IIS (iisadmin) will start, others will not. After install, when issadmin
> is restarted, iisadmin couldn't find a file and won't start at all. I quess
> it is a problem with the metabase.
>
> Somewhere is the process i also reinstalled the IIS SMTP service, killing
> Exchange. I'm in a bit of a problem now: Cannot repair the Exchange install
> because it relies on IIS and IIS will not install properly/cleanly.
>
> I have checked permissions on the MachineKeys folder, checked the Machinekey
> in the registry and have a copy of the MetaBase.xml from after the updates
> (couldn't find an older one on backups). What I don't understand is why IIS
> doesn't generate a new working metabase.
>
> Any pointers and or suggestions? Is there a way to get better error messages
> from the IIS processes and/or is there a way to generate a new, clean
> metabase?
>
> TIA!
>
> Vincent de Lau
> vincent@dgngroep.nl
>
>
>

"Milind Naphade" <MilindNaphade@discussions.microsoft.com> schreef in
bericht news:3ED2B834-37B4-46A1-841C-0896EB537644@microsoft.com...
> Vincent,
>
> You were very close to the resolution but missed it. You have to rename
> the
> MachineKey folder and not just to check the permissions on it. I am sure
> you
> must have been getting the following errors in component installation log
> of
> IIS
>
> Error writing encrypted data to the Web Server's configuration database
> (Metabase).
> 0x8009000b=Key not valid for use in specified state
> Press 'Retry' to retry or 'Write UnEncrypted' to the data unencrypted.
> You can change this data back to encrypted after the setup has completed.
> Buttons -- Retry, Write UnEncrypted, Write UnEncrypted All

According to iis6.log, this error didn't occur. I've renamed the C23... key
and it was recreated (not by IIS?).

Install seems to fail on: CreateIISPackage - Creating the WAM POOL
application. !FAIL!

I'm going to remove IIS and reinstall without the w3svc and see what
happens...

Vincent

A little update:

I removed IIS and then only installed the base component. That worked OK.
Then i installed all the other IIS components
(W3,FTP,SMTP,NNTP,ASP,ASP.net). I can now reinstall Exchange... Hopefully
i'll manage to save all my data...

Vincent

Vincent,

Sorry for the late reply, you can definitely install exchange now but before
starting installation I would suggest to restart the services once and check
what happens.
Then you can proceed to with installation of exchange.
Just to let you know, as you have completely removed and reinstalled the IIS
now the common files must have been flushed out which resulted in successful
removal of IIS. Now, as the common files are also reinstalled you may lose
some of the configurations made in IIS and exchange.
Wish you best luck and let us know how it worked for you.

"Vincent de Lau" wrote:

> A little update:
>
> I removed IIS and then only installed the base component. That worked OK.
> Then i installed all the other IIS components
> (W3,FTP,SMTP,NNTP,ASP,ASP.net). I can now reinstall Exchange... Hopefully
> i'll manage to save all my data...
>
> Vincent
>
>
>