FIX: Rule sets may not be evaluated correctly when you use the NOT operator in BizTalk Server (838458)

SYMPTOMS

When you have a rule set in Microsoft BizTalk Server that uses the same condition two times, one time with a NOT operator and one time without, your rule set may not be evaluated correctly. For example, you have the following rule set configured:

OR

                        AND
                                    Field A Exists in XDoc
                                    NOT
                                                Field B exists in XDoc
                        AND
                                    Field B Exists in XDoc
                                    NOT
                                                Field A exists in XDoc

Because the condition "Field A Exists in XDoc" is used both with a NOT operator and without a NOT operator, the expression in both tests may evaluate the same way: either TRUE or FALSE.

RESOLUTION

Service pack information

To resolve this problem, obtain the latest service pack for Microsoft BizTalk Server 2004. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

888751 How to obtain the latest BizTalk Server 2004 service pack

Hotfix information

The English version of this hotfix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.

   Date        Time    Version     Size     File name
   -----------------------------------------------------------------
   10-Mar-2004  20:57  3.0.5254.0  704,512  Microsoft.ruleengine.dll

Note Because of file dependencies, the most recent hotfix that contains these files may also contain additional files.

MORE INFORMATION

For additional information, click the following article number to view the article in the Microsoft Knowledge Base: