All hosts are stopped on undeployment

Topics: Server Deployment
Feb 22, 2013 at 7:04 PM

We are having a problem we can't seem to figure out how to fix.

Upon undeployment of one spesific BizTalk application (only consisting of schemas), all hosts are stopped.

I had this problem on one other application, but the problem some how went away.

This is what i see in the command prompt:
Host list (BizTalkHosts ItemGroup) not customized.
"cscript.exe" /nologo "C:\Program Files (x86)\Hemit.BizTalk.Common.Schemas\1.
0.0.0\Deployment\Framework\DeployTools\StopBizTalkHost.vbs" ALL
Stopped : <BizTalk-host 1>
Stopped : <BizTalk-host 2>
Stopped : <BizTalk-host 3>
Stopped : <BizTalk-host 4>
and so on and so on...

The hosts are not started up again after undeployment is finished.

We have this in our deployment-file <SkipHostInstancesRestart>True</SkipHostInstancesRestart>, but it does not seem to help.

Any pointers would be appreciated!

-John Viggo
Mar 6, 2013 at 6:17 AM
Hi John,

I apologize for the long delay in responding. This may be happening due to the DeployPDBsToGac property being set to true. In this case your app has only schemas, so there is no real value to the PDB's. I'd suggest just setting that property to false everywhere that it appears in your .btdfproj.

Apr 9, 2013 at 8:44 AM
Yes, setting DeployPDBsToGac to false was the solution to our problem. Thanks! :)