Re: HWS error

From: Gilles [MSFT] (Gilles_at_online.microsoft.com)
Date: 08/25/04 

Date: Wed, 25 Aug 2004 16:34:19 GMT

Hello,

>Thanks for the response. I made sure that the logical and physical
>ports are correctly configured and bound. I can see that the Isolated
>Host is not in the running state and when I right click on it the
>Start and Stop options are disabled. It says that it is installed
>though. Could you give me directions as to whether the Isolated host
>needs to be running and if so then how do I get it to running state.
>Rigth now it is using a dedicated user accoutn which has access to SQL
>Server and is configured to run with Full Trust.

BizTalk supports two kinds of hosts: in process and isolated. In process hosts are used to run orchestrations, pipelines, maps …

They run under the control of the BizTalk service (BTSNTSVC.EXE) and the console displays their full status as well as a few actions: stop/start …
 
Some BizTalk hosts cannot be run in process. This is the case for instance for the HTTP Receive handler. It must run under the context of IIS. It is called
Isolated because it does not run under BTSNTSVC.EXE. For isolated hosts, very little is available in the MMC since BizTalk does not know the status or
can start/stop these hosts. So the fact that it shows up as unavailable and you cannot start/stop it is absolutely normal.

You can see all these information here: http://msdn.microsoft.com/library/en-us/operations/htm/ebiz_ops_hosts_fxzx.asp?frame=true

I am not totally sure if you got the HWS project working on. You sound like you are concerned by the isolated host not running, perhaps because you
could not get the activation message to start.

Assuming you are still facing the same HWS error, here are a few things to do.

First, you have not reported any error that appears in the event log. I have assumed that none appeared (which is strange since HWS logs any error to the
event log). I suggest (if you are not already doing it) to bring up the vent viewer (Application log) and refresh it after every step you take (deploy an
assembly, registering an action, creating a constraint …). If a step fails with an error in the event viewer, you will have much more information on what
happened that just the exception thrown to the client.

I have noticed that the documentation for HWS is not consistent, which is most likely the root cause of your problem. Here are the steps you would do to
register a brand new action on a clean system. You want to make sure that your system matches this. By the way, I stringly suggest you re-enter the
information even if it looks the same.

Register an action with HWS:
Deploy the orchestration assembly and dependencies as appropriate
Create physical ports and bind them to the orchestration as described here: http://msdn.microsoft.com/library/en-
us/sdk/htm/ebiz_ops_hws_admin_lmde.asp?frame=true Note that the document mentions “text/XML” for the content type, but it should really be “text/xml”.
The pipeline must be the XML receive one (not specified in documentation). Also, there is a mistake in the documentation (that I am sure you already fixed
yourself). Under “To create a physical receive port for ActionInterruptPort binding”, the name should be “HwsInterruptPort” instead of “HwsActivatePort”.
You must use these ports names (or adapt the instructions if you want to change names).
Do you need a “SendTaskMessagePort”? If so, create it as follow: add a static one way port named “SendTaskMessageStaticPort” and use the FILE
transport to any directory the user you are running the BizTalkAplication host has read/write to. Make sure you create the directory. Use the XMLTransmit
pipeline.
Bind the orchestration, enlist it and start it. You bind ActionActivationPort to HwsActivatePort and ReceiveTaskResponseMessage as well as
ActionInterruptPort to HwsInteruptPort. If you have a task send port, bind this as well to SendTaskMessageStaticPort.
Open the HWS console, right click on the “Human Workflow Services (Local)” and select properties. Make sure the URL for Activation is set to http://
<yourcomputer name>/HwsMessages/BtsHttpReceive.dll?HwsActivatePort and the interrupt and response one is http://
name>/HwsMessages/BtsHttpReceive.dll?HwsInterruptPort. Do *not* put localhost in <yourcomputer name >. Put the name of the machine onto which
BizTalk is running, even if it is the same machine.
Run iisreset.
If you look at the action in the HWS management, it should no say “Invalid”
Register the action with HWS by right clicking on the action and select “register"
Add an “Allow all” constraint for that action in HWS
Using a web browser. Navigate to http:// name>/HwsMessages/BtsHttpReceive.dll?HwsActivatePort. You will see either an error page
after a few seconds or a Sharepoint services page error after. Check out the event log. You should not see an error here.
Run your sample code.
 

Most likely the step in yellow is the one that will help you. Observe that in the end, the URL of the receive locations and the URL that you put in the HWS
config should match.

As far as not having access to NNTP,, you can always use the web only interface at:

http://www.microsoft.com/biztalk/community/newsgroups/default.mspx

Results are updated as fast as if you had an NNTP server connected. This is not specific to BizTalk: any Microsoft newsgroup can be accessed from this
interface.

Thanks,
-Gilles.

Relevant Pages

  • Re: Send Hosts per Send Port?
    ... > Location in BizTalk 2004, but can't do the same for individual Send Ports? ... > per adapter. ... > adapter to go to different BizTalk Hosts. ...
    (microsoft.public.biztalk.general)
  • Re: BizTalk Server 2004 HWS
    ... get a cup of tea or smth to drink you have got 2 -5 minutes:P when you look now in the VS - biztalk explorer you can see that send and recive ports have been added ... ... hws is a system that goest through those ports after you do all in the lab you build it, deploy it, Bind it with generated from sample ports, start it, register within HWS admin. ... but untill you will create an infopath form with the custom task bar etc. it won't be to much of use but you shouldn't get that ugly error in HWS admin. ...
    (microsoft.public.biztalk.general)
  • RE: Biztalk 2006 - load balancing question...
    ... I would take a look at the Planning and Architecture section of our ... Fault tolerance for the entire BizTalk solution means maintaining high ... availability at multiple tiers: the BizTalk processing tier (BizTalk hosts ... HA of the BTS hosts can be achieved for send and orchestration ...
    (microsoft.public.biztalk.general)
  • Re: Nmap results formatting
    ... Just one note first - to check for UDP ports, you have to be root, so the ... As you can see the command only prints the open ports on both TCP and UDP ... DROP TABLE IF EXISTS `hosts`; ... Now the perl script to populate the DB: ...
    (comp.os.linux.security)
  • Re: Nmap results formatting
    ... Just one note first - to check for UDP ports, you have to be root, so the ... As you can see the command only prints the open ports on both TCP and UDP ... DROP TABLE IF EXISTS `hosts`; ... Now the perl script to populate the DB: ...
    (comp.security.unix)