All

We are having problems with assigning data to a Variable from an in coming m
essage, when we run the Orchestration in debug we get a 'NULL Reference Exce
ption Error'

We even tried fixed data values in our expression but again get the same err
or.

please note we are using 2004

cheers

Aly !

p.s this must be simple as we only want to set a value :-(

[ Post a follow-up to this message ]

have you initialized the variable to a new instance in the expression shape?
What does your expression look like and what type of variables are you
using?


Matt


"AlyD" <Alistair.Dickinson@islington.gov.uk> wrote in message
news:2123FC8A-6034-4FDF-9795-9DCC95E02738@microsoft.com...
> All
>
> We are having problems with assigning data to a Variable from an in coming
message, when we run the Orchestration in debug we get a 'NULL Reference
Exception Error'
>
> We even tried fixed data values in our expression but again get the same
error.
>
> please note we are using 2004
>
> cheers
>
> Aly !
>
> p.s this must be simple as we only want to set a value :-(
>

[ Post a follow-up to this message ]

Hi matt

We are using strings that are defined within Biztalk (2004) they are defined
 in the orchestration view.

The expression looked somthing like the string below.

//some comments here
myString = myMessage.header.fieldId;

When running in debug the  orchestration would stop at the expression with t
he NULL Error.  Have you seen anything like this before, oh and we do appric
iate the help.

Aly !

[ Post a follow-up to this message ]

in the orchestration debugger, when you are in a breakpoint, can you see
that the promoted property you are trying to access has a value and is not
null?

Matt


"AlyD" <anonymous@discussions.microsoft.com> wrote in message
news:EE4B3B73-36E0-4D1E-BE45-02BDC388880A@microsoft.com...
> Hi matt
>
> We are using strings that are defined within Biztalk (2004) they are
defined in the orchestration view.
>
> The expression looked somthing like the string below.
>
> //some comments here
> myString = myMessage.header.fieldId;
>
> When running in debug the  orchestration would stop at the expression with
the NULL Error.  Have you seen anything like this before, oh and we do
appriciate the help.
>
> Aly !
>

[ Post a follow-up to this message ]

Hi Matt

This is the problem the value for the promoted property is Null and causes t
he null error as mentioned before.  While writing these notes we have deploy
ed the orchestration again and this time we see a value so in theory it work
ed.

The problem is why did it work and what caused it to fail in the first place
, was it down to us or a bug in the application.

Anyway after a reboot of the server and redeployment we got a result, so tha
nks for your help on this one.

Aly !

----- Matt Milner wrote: -----

in the orchestration debugger, when you are in a breakpoint, can you see
that the promoted property you are trying to access has a value and is not
null?

Matt


"AlyD" <anonymous@discussions.microsoft.com> wrote in message
news:EE4B3B73-36E0-4D1E-BE45-02BDC388880A@microsoft.com...
> Hi matt 
defined in the orchestration view.[vbcol=seagreen] 
> myString = myMessage.header.fieldId; 
the NULL Error.  Have you seen anything like this before, oh and we do
appriciate the help.[vbcol=seagreen] 
>

[ Post a follow-up to this message ]