Today I encountered the following issue when I was trying to install an application into a new BizTalk Server environment:
“An error occurred while attempting to install the BizTalk application: World Wide Web service (W3SVC) on host “localhost” not available.
The following Windows component may not be installed: Application Server -> Internet Information Services (IIS) -> Common Files.
Unknown error (0x80005000)
Unknown error (0x80005000)”

Note: This error occurred either when I tried to install the application using the MSI or the BTSTask tool, and this error is also followed by two other errors with no particular or interesting information.
📝 One-Minute Brief
Resolve the common BizTalk installation error: “World Wide Web service (W3SVC) on host ‘localhost’ not available.” This issue typically occurs during application deployment via MSI or BTSTask because the “IIS 6 Management Compatibility” role services are missing. To fix this, you must enable the IIS Metabase, WMI Compatibility, and Scripting Tools. This guide provides a step-by-step UI solution and a PowerShell script to automate the installation of all required IIS features for BizTalk Server.
Cause
On a particular note, when I’m installing or configuring a new BizTalk environment, I really prefer to install all features that BizTalk provides, like BAM, BRE, … even though I don’t need them, at least for now, since we do not know the challenges of tomorrow and I try to follow all the guidelines provided by Microsoft or community members.
However, we sometimes find clients that don’t install all components simply because they don’t need them for now, or even worse, they don’t install all the features necessary, like IIS 6 Management Compatibility role service,s because for them it makes no sense
The problem this time was that the IIS 6 Management Compatibility role services were not installed.
The Deployment Framework for BizTalk includes support for deploying application pools and virtual directories in IIS. Virtual directory and application pool deployment is fully active for server deployments.
Due to IIS 7.0/7.5 includes a significant change in the configuration system, on Windows Server 2008 and above, we need to enable IIS 6 Management Compatibility role services: IIS Metabase and IIS 6 configuration compatibility, IIS 6 WMI Compatibility and IIS 6 Scripting Tools to allow System.DirectoryServices code work on modifying IIS configurations on IIS7.x.
This topic is clearly documented in BizTalk 2010 installation guides.
Solution 1
To solve this problem, you must enablethe IIS 6 Management Compatibility role services by following the steps below:
- Go to Administrative Tools > Server Manager.
- Select Roles and under Web Server (IIS) select Add Role Services.
- On the Select Role Services window, check the box next to IIS 6 Management Compatibility. Make sure you check all four options below it.

Note: After these steps, you need to restart the ISS.
Solution 2
Alternatively, you can install these features by using PowerShell:
Import-Module ServerManager
@("Web-Server",
"Web-Http-Errors",
"Web-App-Dev",
"Web-Asp-Net",
"Web-Net-Ext",
"Web-ASP",
"Web-CGI",
"Web-ISAPI-Ext",
"Web-ISAPI-Filter",
"Web-Includes",
"Web-Basic-Auth",
"Web-Windows-Auth",
"Web-Mgmt-Compat",
"Web-Metabase",
"Web-WMI",
"Web-Lgcy-Scripting",
"Web-Lgcy-Mgmt-Console"
)| Add-WindowsFeature
Download
You can download this PowerShell from GitHub:
THIS POWERSHELL IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND.
Hope you find this helpful! If you liked the content or found it useful and would like to support me in writing more, consider buying (or helping to buy) a Star Wars Lego set for my son.
Muchas gracias Sandro!
Con la solución 1 me funcionó perfecto!
Abrazo!