Hi

I am getting an error as enclosed below while trying to work with HWS.
I am running BizTalk Server 2004 on my XP box. Could you suggest
anything else that I could check. I have tried going through the four
steps below and made sure that they are all fine.  In step 2 I made
sure that I have the action registered. I got a similar error while
tring out Lab 12. I created a small HWS project seperately and am
still getting the same error.

Thanks!
Jay Gattani

0) Not registered with HWS
1) Not bound to any receive port (or incorectly bound)
2) Not started
3) Not listening (i.e. you removed the receive shape at the beginning
of the template)

--------------
Client Code
--------------

//Create a instance of the Hws Web service proxy
HwsService hwss = new HwsService();
hwss.Credentials =
System.Net.CredentialCache.DefaultCredentials;
hwss.Url = @"http://localhost/HwsService/HwsService.asmx";

XmlDocument message = new XmlDocument();
System.Guid activityFlowId = hwss.GetNewActivityFlowID();

// Get all availiable actions
Activity[] actions = hwss.GetActivityList(activityFlowId,
Guid.Empty, Guid.Empty, null, null);
System.Guid actionInstanceId = System.Guid.Empty;

//Loop though actions and select assign action
foreach(Activity action in actions)
{
if(action.Name == "MyCustomAction.Action")
{
// Prepare for the activation message
message = new XmlDocument();
message.Load(@"Assign_Task_Activation_Message_New.xml");

//Get action parameters for Assign
ActionParameters param =
hwss.GetActionParameters(action.ActionTypeID, null);
param.ParametersDoc = message.OuterXml;

//Submit activation message
actionInstanceId =
hwss. AddActionToActivityFlow(activityFlowId,S
ystem.Guid.Empty,System.Guid.Em
pty,
false, param, null);
}
}


-----------
Error
-----------

System.Web.Services.Protocols.SoapException:
Microsoft.BizTalk.Hws.SoapService.H
wsServiceSoapException: Failed to add a new step to the activity flow.
---> Micr
osoft.BizTalk.Hws.Runtime.CompositionManagerException: Failed to
submit an activ ation message for the action Action ID
1d6e335f-2750-a223-6dad-bb9bc1f096aa. ---
> System.Net.WebException: The remote server returned an error: (500)
> Internal S
erver Error.
at System.Net.HttpWebRequest.CheckFinalStatus()
at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult
asyncResult)
at System.Net.HttpWebRequest.GetResponse()
at Microsoft.BizTalk.Hws.Runtime.CompositionManager.PostMessage(String
portUR L, String strMessage)
at Microsoft.BizTalk.Hws.Runtime.CompositionManager.SubmitActivationMessage(
S
tring xmlActivationMessage)
--- End of inner exception stack trace ---
at Microsoft.BizTalk.Hws.Exceptions.ThrowException.Error(Exception
newExcepti on, String strMessageID)
at Microsoft.BizTalk.Hws.Runtime.CompositionManager.SubmitActivationMessage(
S
tring xmlActivationMessage)
at Microsoft.BizTalk.Hws.SoapService.HwsService.AddActionToActivityFlow(Guid
activityFlowID, Guid parentActionInstanceID, Guid parentTaskID,
Boolean isDepend entComposition, ActionParameters actionParameters,
String actingUser)
--- End of inner exception stack trace ---
at Microsoft.BizTalk.Hws.Exceptions.ThrowException.Warning(Exception
newExcep tion, String strMessageID)
at Microsoft.BizTalk.Hws.SoapService.HwsService.HandleError(String
code, Stri ng error, Exception e)
at Microsoft.BizTalk.Hws.SoapService.HwsService.AddActionToActivityFlow(Guid
activityFlowID, Guid parentActionInstanceID, Guid parentTaskID,
Boolean isDepend entComposition, ActionParameters actionParameters,
String actingUser)
at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapCli
e
ntMessage message, WebResponse response, Stream responseStream,
Boolean asyncCal
l)
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String
methodN ame, Object[] parameters)
at Console.HWS.HwsService.AddActionToActivityFlow(Guid
activityFlowID, Guid p arentActionInstanceID, Guid parentTaskID,
Boolean isDependentComposition, Action Parameters actionParameters,
String actingUser) in C:\Program Files\Microsoft Bi zTalk Server
2004\SDK\Samples\Hws\Clients\New Folder\Console\Console\Web Referen
ces\HWS\Reference.cs:line 227
at Console.Client.Main(String[] args) in c:\program files\microsoft
biztalk s erver 2004\sdk\samples\hws\clients\new
folder\console\console\client.cs:line 46

[ Post a follow-up to this message ]

Hello,

>I am getting an error as enclosed below while trying to work with HWS.
>I am running BizTalk Server 2004 on my XP box. Could you suggest
>anything else that I could check. I have tried going through the four
>steps below and made sure that they are all fine.  In step 2 I made
>sure that I have the action registered. I got a similar error while
>tring out Lab 12. I created a small HWS project seperately and am
>still getting the same error.

[...]

>0) Not registered with HWS
>1) Not bound to any receive port (or incorectly bound)
>2) Not started
>3) Not listening (i.e. you removed the receive shape at the beginning
>of the template)

By looking at the stack trace, progress has been made. You used to get this 
error when HWS verified that the action could be called.
Now the call itself is failing, probably because the actions's logical port 
are not properly bound to the physical HTTP ports.

I suggest you un-biond and re-bind the orchestration according to the instru
ctions found at:

http://msdn.microsoft.com/library/d..._admin_lmde.asp

Make sure you select the HTTP transport and pay extra attention when enterin
g the URL
Use the IIS management console to make sure that there is an HwsMessages vir
tual root on your server.

Thanks,
-Gilles.

[ Post a follow-up to this message ]

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.

Thanks!
Jay

[ Post a follow-up to this message ]

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 hos
ts are used to run orchestrations, pipelines, maps …

They run under the control of the BizTalk service (BTSNTSVC.EXE) and the con
sole 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 f
or the HTTP Receive handler. It must run under the context of IIS. It is cal
led
Isolated because it does not run under BTSNTSVC.EXE. For isolated hosts, ver
y 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/e....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 d
o.

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 th
e
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 a
n
assembly, registering an action, creating a constraint …). If a step fails w
ith an error in the event viewer, you will have much more information on wha
t
happened that just the exception thrown to the client.

I have noticed that the documentation for HWS is not consistent, which is mo
st 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 yo
ur 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 men
tions “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). A
lso, there is a mistake in the documentation (that I am sure you already fix
ed
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 cha
nge names).
Do you need a “SendTaskMessagePort”? If so, create it as follow: add a stati
c one way port named “SendTaskMessageStaticPort” and use the FILE
transport to any directory the user you are running the BizTalkAplication ho
st has read/write to. Make sure you create the directory. Use the XMLTransmi
t
pipeline.
Bind the orchestration, enlist it and start it. You bind ActionActivationPor
t to HwsActivatePort and ReceiveTaskResponseMessage as well as
ActionInterruptPort to HwsInteruptPort. If you have a task send port, bind t
his as well to SendTaskMessageStaticPort.
Open the HWS console, right click on the “Human Workflow Services (Local)” and select p
roperties. Make sure the URL for Activation is set to http://
<yourcomputer name>/HwsMessages/BtsHttpReceive.dll?HwsActivatePort and the interrupt an
d response one is http://<yourcomputer
name>/HwsMessages/BtsHttpReceive.dll?HwsInterruptPort. Do *not* put localhos
t 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 “reg
ister"
Add an “Allow all” constraint for that action in HWS
Using a web browser. Navigate to http://<yourcomputer name>/HwsMessages/BtsH
ttpReceive.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 i
n 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 interf
ace at:

http://www.microsoft.com/biztalk/co...ps/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.

[ Post a follow-up to this message ]

Hi

I think I found out the reason why this issue was popping up.

The web.config file at C:\Program Files\Microsoft BizTalk Server
2004\Hws\Web Service has the following entry:

<identity impersonate="true"
userName=" registry:HKLM\SOFTWARE\Microsoft\BizTalk

Server\3. 0\Hws\WebService\Identity\ASPNET_SETREG,
userName"

password=" registry:HKLM\SOFTWARE\Microsoft\BizTalk

Server\3. 0\Hws\WebService\Identity\ASPNET_SETREG,
password"

/>

I had the HWSMessage and HWSServices Virutal Hosts configured for Windows
Integrated Authentication. Hence while using the client I was able to get
myself authenticated but when the aspnet_wp.exe tried to impersonate the
account found at the above registry key locations it failed since it runs
under the ASPNET local account which did not have read permissions on the
registry entries. Giving this permission solved the problem and I was able t
o
submit new Activity flows and track the same through the Health and Activity
Tracking tool.

I ran Regmon.exe and found that aspnet_wp was denied access to the registry.

Also, I had the following messages on the System Event Logs, as Gilles had
suggested that I should check, which were good clues:

----------------------

Error Message

---------------------

DCOM got error "Overlapped I/O operation is in progress. " and was unable to
logon \LocalServices in order to run the server:

{07F95711-F36E-4771-8B6D-7E478B31D864}

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.



--------------------------

Warning Message

--------------------------

The server failed to load application '/LM/W3SVC/1/ROOT/HwsMessages'. The
error was 'The server process could not be started because the configured
identity is incorrect. Check the username and password.

'.

For additional information specific to this message please visit the
Microsoft Online Support site located at:
http://www.microsoft.com/contentredirect.asp.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

Thanks to Vipul Goyal from the Microsoft BizTalk Support Team for his
invaluable assistance in nailing down this issue.

[ Post a follow-up to this message ]