Back in April, I installed the BizTalk 2009 CU 2 hotfix in our development environment. All local (developer machine) installations were successful and have no problems. However, our QA server installation is having some problems that we cannot seem to rectify.
To provide some background, our QA BizTalk server environment is Windows Server 2003 R2 Standard SP2 running on a six-core AMD Opteron 2435 under VMware. The BizTalk databases are housed on a SQL Server 2008 box external to the BizTalk server. There are several BizTalk hosts configured, each with a single host instance on the QA box.
The problem we're having after the installation of the hotfix is our tracking host instance spikes the server CPU usage to 100% for about 5 minutes, then the host instance shuts down. The host instance will restart itself after a minute, then spike the CPU to 100% again for 5 minutes, repeating the cycle indefinitely. As you can imagine, nothing else can run on the server while the processor is spiking.
We tried deleting and recreating the tracking host instance with a different name but the issue persists. We tried installing the hotfix a second time to no avail. The only solution that works is shutting down the host instance so it can't run.
Has anyone else experienced this issue? What can I do to fix it?
Thanks in advance!
Did you give MsgboxViewer a try? Maybe a huge amount of orphaned instances accumulated.
Most database (Msgbox, DTA, etc.) can be solved using BizTalk Terminator which works hand in hand with MsgboxViewer.
Did you modify any advanced (performance) settings on this host instance?