Microsoft Knowledge Base Article
This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved.
Terms
of Use |
Trademarks
Article ID: 875497 - Last Review: June 1, 2006 - Revision: 2.1
FIX: Processing seems to stop when you use ordered delivery ports, and you have an increased load of messages in Microsoft BizTalk Server 2004
When you use ordered delivery ports, you may notice that processing seems to stop when you have an increased load of messages. There are no errors that appear in the event log. This problem occurs in a Microsoft BizTalk
Server 2004 solution.
If you review the SQL Profiler trace of your message
box database, you notice high latency in the execution time of the stored
procedures that are responsible for dequeuing messages. These stored procedures are
named "bts_DeQueueMessages_
BizTalkServerApplication."
The placeholder
BizTalkServerApplication is the name of your BizTalk Host Application.
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Â
(http://kbalertz.com/Feedback.aspx?kbNumber=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 file attributes) 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 Size File name
--------------------------------------------------------------
30-Jul-2004 01:46 381,802 Msgbox_application_logic.sql
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
This problem was corrected in BizTalk Server 2004 Service Pack 1.
This hotfix modifies new message boxes that you create.
Message boxes that already exist in the message box database remain unmodified.
Install this hotfix. Then, to apply this hotfix to message boxes that already exist in the message box database, follow these steps:
- Start SQL Query Analyzer. Connect to your message
box database.
By default, your message
box database is named BizTalkMsgBoxDb. - Open the updated SQL script at the following location:
\Program files\Microsoft
BizTalk Server 2004\Schema\Msgbox_application_logic.sql - Run the updated SQL script.
- Repeat steps 1 through 3 for each message box database that
you have in your BizTalk
Server 2004 solution.
When you run the updated SQL script, you may receive any one of
the following warning messages in the Output window of SQL Query
Analyzer. These warnings are not problems and can be ignored.
- Cannot add rows to sysdepends for the current stored
procedure because it depends on the missing object 'int_AddApplicationSprocs'.
The stored procedure will still be created.
- Cannot add rows to sysdepends for the current stored
procedure because it depends on the missing object
'int_RemoveApplicationSprocs'. The stored procedure will still be
created.
- Cannot add rows to sysdepends for the current stored
procedure because it depends on the missing object
'dbo.int_GetInstanceLock_BizTalkServerApplication'. The stored procedure will
still be created.
- Cannot add rows to sysdepends for the current stored
procedure because it depends on the missing object
'dbo.int_AdminResumeInstance_BizTalkServerApplication'. The stored procedure
will still be created.
- Cannot add rows to sysdepends for the current stored
procedure because it depends on the missing object
'dbo.int_AdminSuspendInstance_BizTalkServerApplication'. The stored procedure
will still be created.
- Cannot add rows to sysdepends for the current stored
procedure because it depends on the missing object
'dbo.int_AdminTerminateInstance_BizTalkServerApplication'. The stored procedure
will still be created.
- Cannot add rows to sysdepends for the current stored
procedure because it depends on the missing object
'dbo.int_ProcessCleanup_BizTalkServerApplication'. The stored procedure will
still be created.
- Cannot add rows to sysdepends for the current stored
procedure because it depends on the missing object
'dbo.int_AdminResumeInstance_BizTalkServerApplication'. The stored procedure
will still be created.
- Cannot add rows to sysdepends for the current stored
procedure because it depends on the missing object
'dbo.int_GetInstanceLock_BizTalkServerIsolatedHost'. The stored procedure will
still be created.
- Cannot add rows to sysdepends for the current stored
procedure because it depends on the missing object
'dbo.int_AdminResumeInstance_BizTalkServerIsolatedHost'. The stored procedure
will still be created.
- Cannot add rows to sysdepends for the current stored
procedure because it depends on the missing object
'dbo.int_AdminSuspendInstance_BizTalkServerIsolatedHost'. The stored procedure
will still be created.
- Cannot add rows to sysdepends for the current stored
procedure because it depends on the missing object
'dbo.int_AdminTerminateInstance_BizTalkServerIsolatedHost'. The stored
procedure will still be created.
- Cannot add rows to sysdepends for the current stored
procedure because it depends on the missing object
'dbo.int_ProcessCleanup_BizTalkServerIsolatedHost'. The stored procedure will
still be created.
- Cannot add rows to sysdepends for the current stored
procedure because it depends on the missing object
'dbo.int_AdminResumeInstance_BizTalkServerIsolatedHost'. The stored procedure
will still be created.
For additional information about performance issues in BizTalk Server
2004, click the following article number to view the article in the Microsoft Knowledge Base:
834624Â
(http://kbalertz.com/Feedback.aspx?kbNumber=834624/
)
A list of known issues in BizTalk
Server 2004
APPLIES TO
- Microsoft BizTalk Server 2004 Developer Edition
- Microsoft BizTalk Server 2004 Enterprise Edition
- Microsoft BizTalk Server 2004 Partner Edition
- Microsoft BizTalk Server 2004 Standard Edition
| kbtshoot kbbug kbfix kbqfe kbbtsmessaging kbbiztalk2004sp1fix kbhotfixserver KB875497 |
Community Feedback System
Very often, it takes hours to solve a problem. Very often, you've looked high
and low, and have tried a lot of solutions. When you finally found it, chances
are, it was because someone else helped you. Here's your chance to give back.
Use our community feedback tool to let others know what worked for you and what
didn't.
Please also understand that the community feedback system is not warranted to be
correct, it's simply a system that we've built to let people try and help each
other. If something in a feedback response doesn't make sense to you, or you're
not comfortable making changes that the feedback talks about (like registry
edits), please consult a professional.
Thank you for using kbAlertz.com Feedback System.
-- Scott Cate