Found a bug today whilst deploying a BizTalk Server solution. Its easily reproducable.
Using the admin console deploy a solution that has two orchestrations, then apply a binding with one orchestration bound to a 32bit host and another that’s bound to a 64bit host. Now go and start the application. You’ll get a out of range exception thrown by the admin console. You have to start the orchestrations one by one. After starting all orchestrations individually if you restart the application it works fine.
Its only on the first start of an application that has orchestrations running under both 64bit and 32 bit hosts. Restarting the admin console does nothing. Only a minor bug in what has proved to be a very solid product.