Can anyone point me in a direction with this problem. My orchestration worke
d
fine and works fine in development pc but on production server I am getting
this Rules Engine exception.

Uncaught exception terminated service
MyApplication(f882c664-b704-987b-fb3d-f2a94c2794f5), instance
6c568f5e-46d4-4736-a83f-97ce49967f51

The type Microsoft.RuleEngine.TypedXmlDocument in Assembly
Microsoft.RuleEngine, Version=3.0.1.0, Culture=neutral,
PublicKeyToken=31bf3856ad364e35 is not marked as serializable.

Exception type: SerializationException
Source: mscorlib
Target Site: System.Reflection.MemberInfo[]
InternalGetSerializableMembers(System.RuntimeType, Boolean)
Help Link:
Additional error information:

[ Post a follow-up to this message ]

Are you definining the TypedXmlDocument as a variable in the orchestration?
If so, make sure you declare it in the scope of the transaction.

matt


"Jeno" <Jeno@discussions.microsoft.com> wrote in message
news:EE7D4D5E-7543-4BE3-AC20-9CACF6B022E3@microsoft.com...
> Can anyone point me in a direction with this problem. My orchestration
> worked
> fine and works fine in development pc but on production server I am
> getting
> this Rules Engine exception.
>
> Uncaught exception terminated service
> MyApplication(f882c664-b704-987b-fb3d-f2a94c2794f5), instance
> 6c568f5e-46d4-4736-a83f-97ce49967f51
>
> The type Microsoft.RuleEngine.TypedXmlDocument in Assembly
> Microsoft.RuleEngine, Version=3.0.1.0, Culture=neutral,
> PublicKeyToken=31bf3856ad364e35 is not marked as serializable.
>
> Exception type: SerializationException
> Source: mscorlib
> Target Site: System.Reflection.MemberInfo[]
> InternalGetSerializableMembers(System.RuntimeType, Boolean)
> Help Link:
> Additional error information:
>
>
>
>

[ Post a follow-up to this message ]

Hi Matt,
I'm having the very same problem, weird thing is that it does not happen all
the time, I have no way of tracking what causes this error. My production
environment will run for three days without a problem, then out of the blue,
this lovely error pops up.

I do not define the typed xml document as a variable in the orchestration.

What's cooking here?

"Matt Milner" wrote:

> Are you definining the TypedXmlDocument as a variable in the orchestration
?
> If so, make sure you declare it in the scope of the transaction.
>
> matt
>
>
> "Jeno" <Jeno@discussions.microsoft.com> wrote in message
> news:EE7D4D5E-7543-4BE3-AC20-9CACF6B022E3@microsoft.com... 
>
>
>

[ Post a follow-up to this message ]

Hmm, the basic answer is that your orchestration appears to be persisting
state and/or dehydrating and is trying to serialize your TypedXmlDocument
instance.  Is it possible that there is a path in your rules that only gets
followed in less common situations such that it might only fire every three
days or so?

What are you rules doing to the message(s) and what are you passing in as
facts?

Matt


"Mangi" <Mangi@discussions.microsoft.com> wrote in message
news:FFE7AB24-E49A-4B59-9213-0F802DD28E88@microsoft.com...[vbcol=seagreen]
> Hi Matt,
> I'm having the very same problem, weird thing is that it does not happen
> all
> the time, I have no way of tracking what causes this error. My production
> environment will run for three days without a problem, then out of the
> blue,
> this lovely error pops up.
>
> I do not define the typed xml document as a variable in the orchestration.
>
> What's cooking here?
>
> "Matt Milner" wrote:
> 

[ Post a follow-up to this message ]