I have recently encountered an error “The BAM Portal website Default Web Site is not valid” during the Microsoft BizTalk Server installation. I encountered the following error while attempting to configure the BAM Portal in the Microsoft BizTalk Server Configuration window. And because of this failed to configure BAM Portal.
Detailed Analysis on BAM Portal
When click on not configured BAM Portal then below window will open, Select Enable BAM Portal check box to configure and enable the BAM.
Once you check the BAM check box, configuration window will come like below with error mark. click on error icon to see the full details of error.
Configure the Web service accounts with proper account but still you will see the error icon in BAM portal Web Site. When you click on error icon of BAM Web Site, you will find the below error window with error,
Failed to validate BAM Portal Web Site (BAMPortal) ADDITIONAL INFORMATION: The BAM Portal website Default Web Site is not valid. (Microsoft.BizTalk.Bam.CfgExtHelper.PortalHelper) Unknown error (0x80005000) (System.DirectoryServices)
The main root cause for this error is the “IIS 6 Management Compatibility” windows feature missing. If the IIS6 Compatibility pack is not installed then installing that should solve the problem.
Please follow below steps to resolve the issue:
Go-to Control Panel -> Programs and Features -> Turn Windows features on or off -> Internet Information Services -> Web Management Tools -> IIS 6 Management Compatibility
Please look into below screen shot for reference,
Check all under IIS 6 Management compatility and install (I guess Metabase compatibility is the one that is required but check all just in case). Your configuration should look like above snap shot.
This will resolve your issue and error icon will no more available. Click on Apply configuration.
This time it should configure without failure.
I encountered the following error while attempting to configure the BAM in the Microsoft BizTalk Server Configuration window. And because of this failed to configure BAM. We got to know how to fix this issue.