All geek questions in one place

BizTalk Deployment Errors

I had the following errors when I deployed a BizTalk project.

Error 1 Failed to update the binding information. The bindings for the orchestration "BizTalk_Server_test.BizTalk_Orchestration1, BizTalk Server test, version = 1.0.0.0, Culture = neutral, PublicKeyToken = 56064b11c189a7aa" could not be changed because one or more orchestration instances still exist.

Error 2 Failed to add resource (s). Failed to complete change request for some resources. BizTalkAssemblyResourceManager was unable to complete the request to change the end type. Failed to update binding information. The bindings for the orchestration "BizTalk_Server_test.BizTalk_Orchestration1, BizTalk Server test, version = 1.0.0.0, Culture = neutral, PublicKeyToken = 56064b11c189a7aa" could not be changed because one or more orchestration instances still exist.

I tried rebuilding the orchestration and restarting the server, I still have these errors. Can anyone help?

+4
source share
3 answers

Hold a full stop , and then delete the project. build a solution and deploy it again.

+1
source

There is no need to complete the application complete stop , as this can lead to the loss of information about the binding if you configured your bindings without re-exporting.

As the error message says, you need to complete all instances of the service and / or messaging related to the application.

Go to the BizTalk Group page in the BizTalk Administrator, click on the "Suspended Instances" link, then right-click and select "Teminate Instances" from the pop-up menu.

You can now redistribute your BizTalk project. Be sure to restart any associated host instances, or you will not see your changes at runtime.

+8
source

Complete the following steps:

  • Go to the BizTalk Group page in the BizTalk Administrator,
  • click on the link "Suspended instances"
  • then right-click and select “Teminate Instances” from the pop-up menu.

You can now redistribute your BizTalk project. Be sure to restart all of the node instances associated with it, or you will not see changes at runtime.

0
source

Source: https://habr.com/ru/post/1342912/

More articles:


All Articles