Last week I have encountered an unusual situation in my BizTalk Server 2010 production environment… when I was trying to restart BizTalk Host Instance after publishing a small change in one of my applications, one of the host instances got stuck in “Stop pending” state.
The major problem of this stage is that we cannot perform any kind of operations on it through BizTalk Server Administration Console or Service window
Well, unfortunately, I don’t know exactly why this problem has occurred, but I came across with these posts:
- FIX: “Error saving map. Stored procedure returned non-zero result.” error message when you deploy the BizTalk Server 2010 applications in BizTalk Server 2010 Administration Console.
- Stuck in a SERVICE_STOP_PENDING state when restarting host instances while deploying an application
And I believe that this problem was due to the deploy, unfortunately, and against my suggestions, the client had not installed the latest CU (I think that the last CU installed, was the CU2)
First of all, I suggest that you install the latest CU available.
But because this was a production environment and I needed to solve the problem quickly the solution to solve this problem is to kill the process via Windows Task Manager! Is not an elegant solution, I know and please avoid doing it.
Then go to BizTalk Server Administration Console or Service window and start the process.
Another precaution that you must have if you have multiple Host Instances, is to know what is the process id of the host instance in order to terminate the correct one, you can accomplish this following the steps in this post:
- How to determine the process ID of BizTalk Host Instances with PowerShell
- or in this Debugging External assembly’s or pipeline components – Attach to Process – which BizTalk process to use?