FIX: Processing seems to stop when you use ordered delivery ports, and you have an increased load of messages in Microsoft BizTalk Server 2004 (875497)

   Date         Time                      Size    File name
   --------------------------------------------------------------
   30-Jul-2004  01:46                    381,802  Msgbox_application_logic.sql

MORE INFORMATION

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:

1. Start SQL Query Analyzer. Connect to your message box database.
   
   By default, your message box database is named BizTalkMsgBoxDb.
2. Open the updated SQL script at the following location:
   
   \Program files\Microsoft BizTalk Server 2004\Schema\Msgbox_application_logic.sql
3. Run the updated SQL script.
4. 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: