Solution is easy, remove the info binding file and we can redeploy our orchestration.
I was confused, because Receive Location 'Receive Location MQ por FILE' didn't exists, it was a Receive Location that I have deleted weeks ago.
Searching for Binding Info inside my computer, I discovered that Biz Talk stores info about the last deployments in C:\Documents and Settings\[user name]\Application Data\Microsoft\Biz Talk Server\Deployment\Binding Files (over Vista in C:\Users\[user name]\App Data\Roaming\Microsoft\Biz Talk Server\Deployment\Binding Files).
When you do a redeployment, Biz Talk uses this information.
If this information is erroneous, we get this error "Failed to update binding information".
As an example: The snipped below commits all bound .
with "Overwrite all" checked, when I received this error: The detail error said that "Receive Location 'Receive Location MQ por FILE' has no Transport type specified.".
control, the underlying binding source is updated a soon as the control loses focus.
This is something you might want to prevent sometimes – a common scenario is a model dialog that provides a Cancel button to abort changes.
If you choose to participate, the online survey will be presented to you when you leave the Msdn Web site.