R Raghu

Hi,

I am working with R2 beta. After I installation and configuration, I tried to start the BizTalkServerIsolatedHost instance. When I right clicked on this host instance in BizTalk Server 2006 Administration tool (below BizTalk Server 2006 Administration/BizTalk Group [...]/Platform Settings/Host Instances node), the menu items Start/Stop/Restart are disabled.

What could be the reason for this and how can I get them to be active again (not all of them at same time ofcourse)

I was able to start BizTalkServerApplication host instance without any problem. Both of these instances are configured to be Trusted with identical user.


Thanks.




Re: BizTalk R2 General BizTalkServerIsolatedHost host instance - Start/Stop/Restart menu items disabled

Jon Flanders

You can't control an isolated host from the MMC - because BizTalk doesn't manage the lifetime of an isolated host. Its part of the reason Isolated hosts exists - so that BizTalk components can get loaded into a process that BizTalk doesn't manage explicitly.

Generally an isolated host is mapped into IIS - so you control the isolated host through the IIS manager. But any process can be an isolated host.






Re: BizTalk R2 General BizTalkServerIsolatedHost host instance - Start/Stop/Restart menu items disabled

quicki

biztalk inprocess runs under btsntsvc application

where as BizTalkServerIsolatedHost host instance runs under w3wp process or inetinfo.exe

so try restarting iis if you make any change in recieve location of http or soap webservice location

in order to refresh them





Re: BizTalk R2 General BizTalkServerIsolatedHost host instance - Start/Stop/Restart menu items disabled

Jon Flanders

You do not need to restart IIS when you make a change to the Receive Location. All ReceivePort/Location and Send Port configuration is pushed out to all hosts (isolated and non-isolated) on a cache refresh schedule. There isn't any reason to ever restart a host due to a configuration change.




Re: BizTalk R2 General BizTalkServerIsolatedHost host instance - Start/Stop/Restart menu items disabled

Tomas Restrepo

Just to addd to Jon's reply: If you find yourself waiting too long for the host settings to take effect, it might be because the default configuration cache refresh frequency is set to 60 seconds. One trick I always do in my own developer workstation is to change the frequency to 5 seconds, so that I don't have to wait as much. Here's how.