FIX: You experience high CPU utilization and no timeout exception when using a timed scope in orchestration

When you activate an orchestration that uses a timed scope in Microsoft BizTalk Server 2004, you may notice the process where this orchestration is running uses most of the CPU on your server. By default, this process is Btsntsvc.exe. Also, the scope shape never throws a timeout exception.

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:

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. Note Because of file dependencies, the most recent hotfix or feature that contains these files may also contain additional files.

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section of this article. This problem was corrected in BizTalk Server 2004 Service Pack 1.