IIS Admin failed to start with error code 2146893818 after fbreseal

  • Thread starter Thread starter Godzilla
  • Start date Start date
G

Godzilla

Hello,

I have been trying to find a solution to a problem where I cannot
restart the IIS Admin service after I performed a "fbreseal.exe -
keepall". I have been trying some suggestion of restarting msdtc and
reset its log files, but to no avail... I cannot restart the IIS using
the command "iisreset /restart", it says the service is being
disabled. But it is not according to "services.msc"! I just can't
start the service up again!

For more info, I am using FBWF, but before I reseal the image, I turn
FBWF off.

Please HELP!
 
Hello,

I have been trying to find a solution to a problem where I cannot
restart the IIS Admin service after I performed a "fbreseal.exe -
keepall". I have been trying some suggestion of restarting msdtc and
reset its log files, but to no avail... I cannot restart the IIS using
the command "iisreset /restart", it says the service is being
disabled. But it is not according to "services.msc"! I just can't
start the service up again!

For more info, I am using FBWF, but before I reseal the image, I turn
FBWF off.

Please HELP!
Click to expand...

After doing more readings, I realised that most people experiencing
similar problem said that IIS is NOT stable under XPE.... Has anyone
tried to disable the IIS Admin before fbreseal?? Is there a way to
prevent the problem in the first place? E.g. Disable the IIS Admin,
WWW and FTP services before manual reseal??

Using Apache instead of IIS, as suggested by others, is not a good
enough answer for us now as most of the testing were done under IIS.

Please help.
 
Well, after a weekend of testing, I found that the "fbreseal -keepall"
was the cause of the error code 2146893818 while trying to start IIS
Admin service. Gosh, I wish MS documents the fbreseal options
better... This is another case of undocumented 'features'

Without the "-keepall" switch, IIS Admin was started after cloning,
but the FTP and WWW services were not, but at least I can restart
those services without seeing that error code.

Good luck.

Cheers
 
Back
Top