Skip to main content

The IIS Admin Service service terminated with service-specific error 2149648394 (0x8021080A)

 The IIS Admin Service service terminated with service-specific error 2149648394 (0x8021080A)



The IIS Admin Service service terminated with service-specific error 2149648394 (0x8021080A) – You may meet this error when IIS Admin Service was thrown away after restoring a Windows Server or just after DSKCHK (disk check) OR For any reason like windows update.
I decided to write this tutorial when it happens to lose my IIS Admin server. What happened was that one Windows server was attacked by a virus and I had to restore it from a recent backup. In the backup procedure there is DSKCHK part and then the image is saved.


I saw the DSKCHK processes running, and something got wrong on the NTFS volume During the ‘repair’ process (as you probably know) a number of files may become corrupt, and the Metabase.xml – the core of the IIS Admin service â€“ was damaged.
Now, since the backup itself is damaged, the only way of resolving the IIS Admin Service service terminatederror is to use the files that Windows stores itself.
The next image is the key to the issue resolution:




On your server Under C:\\Windows\\System32\\Inetsrv ™ and you\”ll find folder called \”History\” folder. Hopefully inside you will recent backups of the Metabase.XML and MBSchema.XML files. Before continuing with the next steps make sure you have backups of the existing Metabase.xml and MBSchema.xml from C:\\Windows\\System32\\Inetsrv first!



The next step will be to rename the most recent Metabase.XML file, and then the most recent MBSchema.XML file. Copy and paste each of these to the C:\\Windows\\System32\\Inetsrv ™ folder (one folder up).
The last step is to reset the IIS service so go click on Start -> Run ->™ type there cmd ™ and then a IISRESET™ in the command prompt.


  1. C:\Documents and Settings\Administrator>iisreset

  3. Attempting stop…
  4. Internet services successfully stopped
  5. Attempting start…
  6. Internet services successfully restarted


It worked for me, and I hope it will work for you to resolve this error: The IIS Admin Service service terminated with service-specific error 2149648394 (0x8021080A).

Comments

Post a Comment

Popular posts from this blog

Integration with vCloud Director failing after NSXT upgrade to 4.1.2.0 certificate expired

  Issue Clarification: after upgrade from 3.1.3 to 4.1.2.0 observed certificate to be expired related to various internal services.   Issue Verification: after Upgrade from 3.1.3 to 4.1.2.0 observed certificate to be expired related to various internal services.   Root Cause Identification: >>we confirmed the issue to be related to the below KB NSX alarms indicating certificates have expired or are expiring (94898)   Root Cause Justification:   There are two main factors that can contribute to this behaviour: NSX Managers have many certificates for internal services. In version NSX 3.2.1, Cluster Boot Manager (CBM) service certificates were incorrectly given a validity period of 825 days instead of 100 years. This was corrected to 100 years in NSX 3.2.3. However any environment originally installed on NSX 3.2.1 will have the internal CBM Corfu certs expire after 825 regardless of upgrade to the fixed version or not. On NSX-T 3.2.x interna...
Post a Comment
Read more

Calculate how much data can be transferred in 24 hours based on link speed in data center

  In case you are planning for migration via DIA or IPVPN link and as example you have 200Mb stable speed so you could calculate using the below formula. (( 200Mb /8)x60x60x24) /1024/1024 = 2TB /per day In case you have different speed you could replace the 200Mb by any rate to calculate as example below. (( 5 00Mb /8)x60x60x24) /1024/1024 =  5.15TB  /per day So approximate each 100Mb would allow around 1TB per day.
Post a Comment
Read more

Device expanded/shrank messages are reported in the VMkernel log for VMFS-5

    Symptoms A VMFS-5 datastore is no longer visible in vSphere 5 datastores view. A VMFS-5 datastore is no longer mounted in the vSphere 5 datastores view. In the  /var/log/vmkernel.log  file, you see an entry similar to: .. cpu1:44722)WARNING: LVM: 2884: [naa.6006048c7bc7febbf4db26ae0c3263cb:1] Device shrank (actual size 18424453 blocks, stored size 18424507 blocks) A VMFS-5 datastore is mounted in the vSphere 5 datastores view, but in the  /var/log/vmkernel.log  file you see an entry similar to: .. cpu0:44828)LVM: 2891: [naa.6006048c7bc7febbf4db26ae0c3263cb:1] Device expanded (actual size 18424506 blocks, stored size 18422953 blocks)   Purpose This article provides steps to correct the VMFS-5 partition table entry using  partedUtil . For more information see  Using the partedUtil command line utility on ESX and ESXi (1036609) .   Cause The device size discrepancy is caused by an incorrect ending sector for the VMFS-5 partition on the ...
Post a Comment
Read more