BizTalk Server 2009
1.
Because of the problems with the first version, I followed the Installation Instruction (yeah, we sometimes do this 
. I installed all pre-requisites (Powershell is a feature
of Windows Server 2008). But during installation I get the next error message:
Error while importing "C:\Program Files\Microsoft ESB Guidance 2.0 CTP2 – January 2009\Microsoft.Practices.ESB.CORE.msi".
Change requests failed for some resources.
Unable to process create change request for BizTalk binding "BindingInfo.xml". Import bindings (overwrite) failed.
Failed to update binding information.
Cannot update send port "ALL.Exceptions".
Cannot update transport information (address "SQL://(local)/EsbExceptionDb/").
The following items could not be matched up to hosts due to name and/or trust level mismatches:
Item: ‘SQL’ Host: ‘BizTalkServerApplication’ Trust level: ‘Untrusted’
You must do one of the following:
1) Create hosts with these names and trust levels and try again
2) Re-export the MSI without the binding files and have a post import script apply a suitable binding file.
You would think that I didn’t configure my BizTalkServerApplication properly, but I did. So probably there is an error in the binding file. If you install the Msi straight away you can find the binding file in the 49th Cab file (ITEM~49.CAB). I changed the binding file so it matches my Hosts (Trusted="true" instead of Trusted="false"). After
installing the Msi ‘Microsoft.Practices.ESB.CORE_NOBINDING.msi’ in BizTalk I imported the Binding file manually. And this works.
A pity this workaround (or question during installation) is not described.
2.
Don’t forget the EntLib 4.0 Dll’s must be in the GAC. Because else you will get an error in the ESB Configuration Tool when you try to configure the Itinerary Database.
I didn’t configure the Optional Components yet or did dive into this new ESB Guidance, so stay tuned…
