Thanks for the reply. Although I am not using Wizard to create the receive port (in stead, I manually create a SOAP port and bind the orchestration), it turns out the same weird result. This problem becomes even critical when I tried to export the MSI and deploy to staging server, manually modify the binding property is not the final solution … A bug of BizTalk 2006?
Search this Site:
Recent Posts
- Logic App Consumption deployment: The secret of KeyVault parameter cannot be retrieved. Http status code: ‘Forbidden’. Error message: ‘Access denied to first party service
- BizTalk Server Visual Studio project: attempted re-targeting of the project has been canceled.
- BizTalk Oracle Adapter error: The assembly required for type mapping not found.
- PowerShell script to identify all SQL V1 actions and triggers inside Logic Apps Consumption
- Friday (funny) Fact: There is no size limit for the Logic App parameter name