Geeks With Blogs
Nigel Parker BizTalk 2004 Developer - Auckland, New Zealand,

I have a large number of messages that are passed into an orchestration/ split in the incoming pipeline and then passed one by one into a Rules Engine policy. I have discovered when I am processing hundreds of instances at once I ocassionally get the following exception raised in HAT.


Ruleset is too complex and translation cannot complete within the configured translation timeout interval."

This is because does not throttle the calls to the rules engine and the rules engine queues the inbound message and processes them in FIFO order.

The solution:

"Increase the time out in the registry for the rules engine from 1 minute -> something like 5 minutes"


My Computer/HKEY_LOCAL_MACHINE/SOFTWARE/Microsoft/Business Rules/3.0/

TranslationTimeout - default value "60000" (1 minute)

restart Rules Engine Service



Posted on Saturday, October 16, 2004 4:30 AM Using The Business Rules Engine | Back to top

Comments on this post: RuleSetTranslationComplexityException - Scenario...

# re: RuleSetTranslationComplexityException - Scenario...
Requesting Gravatar...
I think you have to restart the host(s) and not the rules engine service. This did the trick for me. Thanks for this post by the way.
Left by Peter Dol on Sep 15, 2006 10:29 PM

# re: RuleSetTranslationComplexityException - Scenario...
Requesting Gravatar...
Hi.. its really excellent post.
i am also using a pipeline at receive to split the msgs and process each msg via rule engine. we designed this pipeline to increase performance. i am facing this translation time out error. Yes as u said i can change this property value but again it fails my ultimate goal i.e performance and also change of this value affects all my existin biztalk projects. so is there any way to solve this translation time out error with out changing its value.. ????
Left by sandeep on Dec 05, 2011 4:05 AM

Your comment:
 (will show your gravatar)

Copyright © Nigel Parker | Powered by: