| Sergio Otoya 2004-08-24, 3:08 am |
| Hi all,
I found that the assembly that the orchestration was running must have been
an old copy of the previous version and therefore the debugger was getting
confused.
I ended up stopping/unenlisting the orchestration, then undeploying the
assembly and then redeploying the project.
This worked. Hopefully this is useful for someone else.
--
Sergio Otoya
Winapp
"Sergio Otoya" <sergio@winapp.com.au> wrote in message
news:41235e95$1@dnews.tpgi.com.au...
> Hi,
>
> I have an orchestration that works fine up to a point. I trace the
> orchestration with HAT (orcehstration debugging) and when i can see that
the
> last few steps have not been completed.
>
> The orchestration completes with no error messages and it is not
suspended.
>
> Any ideas? where should i look for further problems?. This has happened to
> me with an orchestration where the last two steps where a transform and
then
> a send. the current one has an expression assignment and a loop.
>
> Thanks in advance.
> --
> Sergio Otoya
> Winapp
>
>
|