|
Home > Archive > BizTalk Server Orchestration > October 2004 > Exposing a BizTalk 2004 Orchestration as a Web Service on Windows
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Exposing a BizTalk 2004 Orchestration as a Web Service on Windows
|
|
| Bradley J. Gibby 2004-10-15, 9:09 pm |
| Hi there,
My issue is that I'm running a BizTalk 2004 server on a Windows 2000 machine
(not server, workstation) for dev purposes. I've just created an
orchestration that I need to expose as a web service for a Client app.
After deploying the orchestration, I ran the Web Services Publishing wizard.
Set up everything including "Create Receive Locations" and "Allow Anonymous
Access" and all was well.
Opened the Web Service in IE6 and received the WSDL and all was well.
Created a stub app with a Web Reference to the WS and created my C# code to
create an object for the message and an object to instantiate the WS method
call. Ran the App and hit my dummy button and all was well.
Went to check the output in HAT, nothing. Went to the Event Log and found
the following error message:
[ Start ]
The Messaging Engine failed to register the adapter for "SOAP" for the
receive location "/Scenario1_Proxy/WDO_Receive_Incoming_OTA_IncOta.asmx".
Please verify that the receive location is valid, and that the isolated
adapter runs under an account that has access to the BizTalk databases.
[ End ]
I therefore verified the location of the ASMX file, no probs. I looked to
see if the databases had the BizTalk_User account that I created for BizTalk
and yep, it's there.
From here, I've no idea what to do.
Any help would be most appreciated!
Thanks
Bradley q
| |
| Tomas Restrepo \(MVP\) 2004-10-15, 9:09 pm |
| Bradley,
> Hi there,
>
> My issue is that I'm running a BizTalk 2004 server on a Windows 2000
machine
> (not server, workstation) for dev purposes. I've just created an
> orchestration that I need to expose as a web service for a Client app.
>
> After deploying the orchestration, I ran the Web Services Publishing
wizard.
> Set up everything including "Create Receive Locations" and "Allow
Anonymous
> Access" and all was well.
>
> Opened the Web Service in IE6 and received the WSDL and all was well.
>
> Created a stub app with a Web Reference to the WS and created my C# code
to
> create an object for the message and an object to instantiate the WS
method
> call. Ran the App and hit my dummy button and all was well.
>
> Went to check the output in HAT, nothing. Went to the Event Log and found
> the following error message:
>
> [ Start ]
> The Messaging Engine failed to register the adapter for "SOAP" for the
> receive location "/Scenario1_Proxy/WDO_Receive_Incoming_OTA_IncOta.asmx".
> Please verify that the receive location is valid, and that the isolated
> adapter runs under an account that has access to the BizTalk databases.
> [ End ]
>
> I therefore verified the location of the ASMX file, no probs. I looked to
> see if the databases had the BizTalk_User account that I created for
BizTalk
> and yep, it's there.
While that user is valid, it's likely the WebService here is running under
the context of the ASP.NET user. Either give that user access, or get your
app to run under BizTalk_User (by using <identity impersonate/> in web
config or by changing the process model in machine.config)
--
Tomas Restrepo
tomasr@mvps.org
| |
| J. Dudgeon 2004-10-17, 2:48 am |
| I recently ran into this error myself. Go into IIS and find the virtual
directory that you published the BT proxy Web service to. Right-click the
virtual directory, select "Properties", and then make sure that the
"Application name" property has a value. If it doesn't, click "Remove" and
then "Create". This should fix the problem. How this relates to the error
you are seeing in the Event Log, I'm not sure, but this solution worked for
me.
After I had published my service using the publishing wizard, I found that
my virtual directory did not have an application name. As soon as I removed
and create the application, the adapter started recognizing that location.
Good luck.
P.S. The ASP.NET account also needs to be added to the database you are
attempting to access, at least under Win2k/XP.
"Bradley J. Gibby" wrote:
> Hi there,
>
> My issue is that I'm running a BizTalk 2004 server on a Windows 2000 machine
> (not server, workstation) for dev purposes. I've just created an
> orchestration that I need to expose as a web service for a Client app.
>
> After deploying the orchestration, I ran the Web Services Publishing wizard.
> Set up everything including "Create Receive Locations" and "Allow Anonymous
> Access" and all was well.
>
> Opened the Web Service in IE6 and received the WSDL and all was well.
>
> Created a stub app with a Web Reference to the WS and created my C# code to
> create an object for the message and an object to instantiate the WS method
> call. Ran the App and hit my dummy button and all was well.
>
> Went to check the output in HAT, nothing. Went to the Event Log and found
> the following error message:
>
> [ Start ]
> The Messaging Engine failed to register the adapter for "SOAP" for the
> receive location "/Scenario1_Proxy/WDO_Receive_Incoming_OTA_IncOta.asmx".
> Please verify that the receive location is valid, and that the isolated
> adapter runs under an account that has access to the BizTalk databases.
> [ End ]
>
> I therefore verified the location of the ASMX file, no probs. I looked to
> see if the databases had the BizTalk_User account that I created for BizTalk
> and yep, it's there.
>
> From here, I've no idea what to do.
>
> Any help would be most appreciated!
>
> Thanks
> Bradley q
|
|
|
|
|