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?
Related
So I am migrating a server and can't find out why the new machine / environment is slower than the old one. Here are the facts.
Old Machine
2008 R2 - 3.1ghz quad core Xeon w/ 12gb
SQL2k \ SQL 2008
IIS 7
New Machine
2012 R2 - 2.5ghz 8 core Opteron w/ 16gb
SQL2k \ SQL 2008 \ SQL 2016
IIS 8.5
So here is what I have done. I migrated the codebase onto the new machine. I loaded up SQL2k which I know is not supported and I plan to upgrade. The same page on both machines loads fine. Old machine loads in 10 seconds new machine takes 124 seconds.
Next step was to convert database from 2k to 2016 via 2008. Done with that same load speed 124 seconds. Next changed connections strings from OLEDB to Native 11. That dropped the load time from 124 down to 30 seconds.
Next I went into query manager and ran the SP on both machines. Old machine takes 4 seconds to complete the query. New machine takes less than 2 seconds to run the same query on sql2k but on sql2016 the same query runs in under a second. I then wrote a much more intensive query and ran it on both machines. The old machine took 120 seconds to execute the new machine took 12 seconds in 2016 and about 25 seconds in SQL2k.
So at this point I am assuming it is IIS settings. Next I went to the old machine installed SQL 2016 and loaded it up to test speeds with the new database running on the old server with IIS 7. Zero difference.
I have tried connection string changes with IP vs NAME no difference.
Is there some change in IIS 8.5 that affects classic ASP performance or a setting in 2012R2 that I am missing somewhere? All app pools and sites are exactly the same on both machines.
Any help would be great, thanks
** Added all sql settings are the same also for both sql2k and sql2016 along with IIS settings. Firewall settings also the same. .NET environments all the same too.
** Changed New Machine is 8 Core not 4
Too many cores man.
Some questions - it's this all one site? All one app pool?
Classic asp wasn't written for 8 core machines. In IIS 8.5 there are settings you can set for processor affinity and numa node (memory) affinity. But really only useful if you have separate sites or app pools to run. But before looking at any of that I'd ask you to try an experiment. Make a vm version of your site, set to use 4 cores and 8 gb ram. Deploy two copies to your machine. Test hitting the page in one of them. You may get better performance. You could also try this without vms by setting the site to run in two worker processes (web garden configuration) and bind each process to half the cores.
Just try adding a host file entry IP pointing to the machine name. I understand you are running SQL server in the same machine but still it will make a big difference from my experience.
As #Brain suggested, Web gardens will help a little on high load but I think your issue is just related to the connection speed.
I am running on window 2012 R2 OS with IIS role installed on it. I have also installed websitepanel and add the websitepanel as a site in IIS.
I have created 3 Application pools for individual website :-
(1) Websitepanel Portal :- To run websitepanel.
(2) Websitepanel Enterprise Server
(3) Websitepanel Server
I have bind the application pool with all 3 websites. The problem is whenever i am going to start the websitpanel, the application pool of websitepanel crashes.
The browser gives the following error.
Service unavailable
Also IIS admin service not going to start. Asking me to search Event log.
I have checked my server usage and it is normal. I have 3 GB RAM and 35 GB diskspace on my server.
Can anyone help me in this regard.
Asking me to search Event log
Ok this is the answer here, search your event log on the server, and there you find a line that say and have the report of the error. Base on that report you can find your problem.
Relative answers:
How do I crash the App Pool?
Deploying website: 500 - Internal server error
Note
Your server running under almost the minimum ram and below the minimum hard disk !
System Requirements for Windows Server 2012 R2
Herrick,
I assume that, you owned server and have access to remote desktop OR IIS. You can try with following options to resolve your problelm:
1) Please enable 32 bit mode for all three application pools for WebsitePanel.
2) Increase private memory for application pools.
3) If you are running with fresh server then have a try with reinstallation of this application again.
Regards,
I have a school project I need to do but can't find any tutorials on how to do it. I've installed Win Server 2008 on VMWare Fusion 7 on my Macbook Pro. I also installed Windows 7 64bit on VMWare Fusion that will be the client. Now I need to copy my Win Server 2008 & install that onto VMWare Fusion as well. The problem begins with me having to connect the 2 servers together (through DHCP or something?) then be able to connect the client to either server. The teacher will then turn off one of the servers & the client has to automatically connect to the 2nd, still turned on, server. That's the entire project.
Can someone please link a tutorial for this? I must be writing my requests into google incorrectly, because I can't find anything to help me.
There are a lot of tutorial about that out there, just use keyword "windows server 2008 failover". I had done that with a client-server apps & database running on the server and the client only has 2-3 second connection down and then it's automatically re-connecting to the other server and the apps still running smoothly.
have installed BizTalk 2009 on the following environment:
Windows 2008 server
SQL Server 2008
IIS 7
Visual Studio 2008
I have also installed ESB toolkit 2.0.
The BizTalk applications generally work, except the event log all the time shows this as "information":
"Communication with all MessageBoxes has now been re-established"
No errors appear in the log.
Also when I refresh the ports view in the management console I see they change from "stopped" to "started" and vice versa every few seconds.
Any ideas?
This is normal. The Biztalk process goes into hibernation (a less responsive mode) when there is no work to do. These information messages tell you that a new message has come in and now Biztalk is operating at normal levels.
The error was effectively a bug in Biztalk 2009.
The hotfix was rolled into CU 1, which can be obtained here.
This issue is also resolved in BizTalk 2010.
After deploying a new build (mostly changed DLL's) of an ASP.NET web app the CPU on the server is now jumping to 100% every few seconds and the culprit is lsass.exe. Do you think that the deployment of the asp.net web app to the server and this problem are related? (or a coincidence that it happened at the same time?)
More info:
This is the first time that I've done the build on a Server 2008 x64 machine. Previous the builds were done on a Server 2003 x86 machine. Target is "Any CPU" so should work on either. Deployed to server is Server 2003 x86.
I've searched the web for more info on this and have confirmed that the process is lsass.exe (first character a lower case L and not an upper case i) so ruled out the virus version. Found some docs relating to a Server 2000 bug but doesn't apply here.
I eventually isolated the problem to an ASP forum running "under" that ASP.NET web app. Using the admin page on the forum I took the forum down and then brought it back up again and the problem disappeared. I find this very frustrating because the problem has now gone but I don't know what caused it and as such it could easily return.
I also installed this Microsoft Hotfix and rebooted this server but that didn't work.
Have you checked the System and Application event logs for anything unusual?
Have you updated to use Active Directory role provider? I've seen issues where enumerating groups to do role checking pegs the CPU and really slows down the app. I actually implemented a customized provider that allowed me to specify a particular OU and set of groups that I actually care about to get around this issue.
The xperf tools distributed in the Windows Performance Toolkit will tell you exactly what is usin CPU time or disk bandwith. These tools are free and work on any retail build of WS2008 or Vista. Here is series of posts on the xperf tools from myself.