OK, I made some more tests and here is a small update.
The exception I mentioned earlier occurs when I change the port binding
in VS, e.g. from “Specify Later” to “Direct Binding”. It won’t be fired
when I only change the Filter Expression.
In the latter case, I can enlist the orchestration but its subscriptions
won’t be updated, that means the orchestration will continue to
subscribe to messages that comply to the preceding filter ; as mentioned
I am 100% sure that the host instance and the GAC are up to date, and
there is no suspended message.
I mentioned that I looked to the subscriptions with a specific query, I
found out that when unenlisting the orchestration, subscriptions stay to
“stopped”, it won’t be “disabled” nor be deleted. These subscriptions
problems come up only with orchestrations, the same tests on send ports
are sucessfull.
I also tried to deploy my orchestration from dev environment and then
manage artefacts from staging (distant). Un- and enlisting still didn’t
update orchestration subscriptions at all.
Latest thing I tryed was to rename the orchestration (e.g. from “test”
to “newTest”) ; in that case, subscriptions were updated as expected,
but only at 1st deployment ; if I change them a second time, the problem
comes back. And to this : if I re-change it from “newTest” to “test”,
the “old” orchestration comes back with its old subscription conditions !
All these tests were made with Admin Console opened and simply refreshed
(F5) ; when I close and reopen it, everything works all right, except
that orchestration subsciptions keep their “stopped” state despite
unenlisting them. This is also true when I manage the artefacts from a
distant console.
I have to make clear that I installed the SP1 and the cumulative
correction packs 1 and 2 in the last weeks, and that is the first time
that I am “playing” with orchestrations and subscriptions. I didn’t see
anywhere that VS or the admin console needed to be updated separately,
maybe I’m missing a fix or another KB article ?
Next steps will be :
– reinstall admin console
– reinstall VS Biztalk add-ins
– try to deploy my orchestration on my staging environment.
Any suggestion will be fully appreciated, thanks a lot!
Thomas