All of us know BizTalk can be tough to handle when its in no mood to help you out understanding the problem.
That's what happened with me this week.
I was performing a deployment on my local box which included a number of schemas, orchestrations etc. To accomplish my deployment I generaly make use of custom-built MSI kit. Unknowingly, somehow I initiated the deployment of the document schema first(which was expecting a property-schema to be already available) which never completed and neither did failed. Probably another add-on I need to take care for my custom installer scripts!!
Further to this, when I saw the installer not completing itself, I clicked the cancel button hoping to rollback the whole thing but that even didn't work. Thus, I had to manually terminate the "msiexec" process which forcibly killed the installer. Soon I realised, I WAS IN A MESS !! BizTalk was out-of control :(
This all lead to a partial deployment of the assembly where it successfully was able to populate some of the tables in MgmtDb and failed for some, as the Property schema was never deployed to it.
I tried hitting the MgmtDb tables and deleting the newly added assembly records in the MgmtDb tables but was not much luck ... you see, I'm not that genius !! Simplest option was, restore the databases backed-up earlier in the day prior to the deployment activity was initiated.
Moral of the story: Always keep in mind the order of deployment or else BizTalk is all gone !!
