
	Search KbAlertz Advanced Search

Receive Microsoft Knowledge Base articles by E-Mail?

Every night we scan the Microsoft Knowledge Base. If technologies you're interested in are updated, we'll send you an e-mail. You only get one e-mail a day, and only when new articles are added.

Click here to create a
FREE account

Already have an account?
[Click here to Login]

Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks

Ads by Lake Quincy Media

Article ID: 837725 - Last Review: June 23, 2006 - Revision: 1.3

How to remove Microsoft BizTalk Server 2004 Rollup Package 1

View products that this article applies to.

Expand all | Collapse all

INTRODUCTION

This article describes how to remove Microsoft BizTalk Server 2004 Rollup Package 1 from your computer.

For additional information about BizTalk Server 2004 Rollup Package 1, click the following article number to view the article in the Microsoft Knowledge Base:

837168Â (http://kbalertz.com/Feedback.aspx?kbNumber=837168/ ) List of fixes that are included in BizTalk Server 2004 Rollup Package 1

MORE INFORMATION

To remove Microsoft BizTalk Server 2004 Rollup Package 1 from your computer, follow these steps:

Click Start, point to Settings, and then click Control Panel.
In Control Panel, double-click Add or Remove Programs.
Under Currently installed programs, click Microsoft BizTalk Server 2004 Hotfix [See KB article 837168 for detail], and then click Remove.
In the confirmation message box, click Yes.
Open a Microsoft Visual Studio .NET Command Prompt window. To do this, click Start, point to Programs, point to Microsoft Visual Studio .NET, point to Visual Studio .NET Tools, and then click Visual Studio .NET Command Prompt.
At the Visual Studio .NET command prompt, type the following commands to reinstall the specified assemblies in the global assembly cache. Press ENTER after you type each command.
gacutil /if "C:\Program Files\Microsoft BizTalk Server 2004\Tracking\Microsoft.BizTalk.Bam.EventBus.dll"

gacutil /if "C:\Program Files\Microsoft BizTalk Server 2004\Microsoft.BizTalk.Deployment.dll"

gacutil /if "C:\Program Files\Microsoft BizTalk Server 2004\Developer Tools\Microsoft.BizTalk.ExplorerOM.dll"

gacutil /if "C:\Program Files\Microsoft BizTalk Server 2004\Microsoft.BizTalk.Pipeline.dll"

gacutil /if "C:\Program Files\Microsoft BizTalk Server 2004\Microsoft.XLANGs.BizTalk.Engine.dll"

gacutil /if "C:\Program Files\Microsoft BizTalk Server 2004\Microsoft.XLANGs.Engine.dll"

If you have run the Configuration Framework Wizard (Configframework.exe) on your computer that is running BizTalk Server, follow these steps.

Note If you have not run the Configuration Framework Wizard on your computer that is running BizTalk Server, do not follow these steps.

Click Start, point to Programs, point to Microsoft SQL Server, and then click Query Analyzer.

Run each one of the following SQL queries against the corresponding database as they appear in the following table.

Note Make sure that you select the corresponding database for the SQL query as they appear in the table before you run the SQL query.

Collapse this tableExpand this table

SQL query name	SQL query location	Database to run the SQL query against
Admin_server_logic.sql	Program Files\Microsoft BizTalk Server2004\Schema	Management database (default name: BizTalkMgmtDb)
Msgbox_security_logic.sql	Program Files\Microsoft BizTalk Server2004\Schema	Message Box database (default name: BizTalkMsgBoxDb)
Msgbox_application_logic.sql	Program Files\Microsoft BizTalk Server2004\Schema	Message Box database (default name: BizTalkMsgBoxDb)

To run these SQL queries against the specified databases, follow these steps in SQL Query Analyzer:

On the File menu, click Open.
For each SQL query in the table, click the corresponding database, and then click Execute Query.

Note The following error messages may appear when you run the Msgbox_application_logic.sql SQL Query. This behavior is expected.

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.

After you have run the SQL queries in step 7b, open a new blank query window in SQL Query Analyzer. To do this, click New on the File menu.
In the blank query window, type the following query:
exec bts_ResetApplicationSprocs
By default, the Message Box database is named BizTalkMsgBoxDb. Select the Message Box database, and then click Execute Query to run the bts_ResetApplicationSprocs stored procedure.

Note The following error messages may appear when you run the bts_ResetApplicationSprocs stored procedure. This behavior is expected.
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.
'BTS_BizTalkServerApplication_USERS' added to role 'BTS_HOST_USERS'.
'BTS_ADMIN_USERS' added to role 'BTS_BizTalkServerApplication_USERS'.
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.
'BTS_BizTalkServerIsolatedHost_USERS' added to role 'BTS_HOST_USERS'.
'BTS_ADMIN_USERS' added to role 'BTS_BizTalkServerIsolatedHost_USERS'.

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

Back to the top

kbbiztalk2004-2006swept kberrmsg kbinfo KB837725

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