Lessons learnt: use your judgement. Do not take the content of the installation guide to be 100% accurate. This is true especially when BizTalk Server has a lot of optional features and installation configurations which requires different range of pre-requisites.
I was setting up a virtual single-machine installation of BizTalk Server 2010 Developer Edition into Windows Server 2008 R2, following this instruction:
And 2 things i noticed to be different between the document and actual practice:
1. Hard Disk Requirement: 10GB in doc. In practice, i need about 30GB for full installation of all the features, including SharePoint Foundation 2010. This is mainly due to WinSxS folder that keeps backup and installation files (10GB in my instance), and it can't be manually removed, and there is no tool to remove it as of today.
2. SQL Server 2005 Notification Service for BAM Portal does not work. Turns out we can't install just the 3 components listed in the doc. This will cause BAM Portal configuration to fail with error:
ERROR: Failed to set up BAM database(s). There was a failure while executing nscontrol.exe. Error:"Microsoft Notification Services Control Utility 18.104.22.168╕ Microsoft Corp. All rights reserved.An error was encountered when running this command.Could not load file or assembly 'Microsoft.SqlServer.Instapi, Version=22.214.171.124, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The system cannot find the file specified."
The correct way to do it is to intall the Notification Service using SQL Server 2005 installation media. This can be done even after you tried to configure the BizTalk Server. Follow the link here to find out the reason. And you need to apply SQL Server 2005 SP3.