BizTalk Server Orchestration - HTTP Adapter Error in 2006

This is Interesting: Free IT Magazines  
Home > Archive > BizTalk Server Orchestration > May 2006 > HTTP Adapter Error in 2006





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 HTTP Adapter Error in 2006
Umeshnath

2006-05-16, 7:13 am

I have configured hTTP Adapter and the receive location I have enabled but I
am getting the following error.
The BizTalk HTTP receive adapter failed to initialize itself. Possible
reasons:
1) Receive location URL is not created/configured correctly.
2) Receive location is not enabled.
3) HTTP receive adapter is not running under a user that has access to
management and message databases.
4) Isolated host instance is not created for HTTP Receive adapter.
Please advise me with the details

Thanks in advance
Umeshanth
anand kumar

2006-05-16, 7:14 pm

Can you make sure the application pool configured for HTTP adapter has the
right identity. Make sure the user name is part of the BizTalk isolated host
group.
Also make sure ISAPI extensions are allowed in the web service extensions in
the IIS.

Thanks,
Anand


"Umeshnath" wrote:

> I have configured hTTP Adapter and the receive location I have enabled but I
> am getting the following error.
> The BizTalk HTTP receive adapter failed to initialize itself. Possible
> reasons:
> 1) Receive location URL is not created/configured correctly.
> 2) Receive location is not enabled.
> 3) HTTP receive adapter is not running under a user that has access to
> management and message databases.
> 4) Isolated host instance is not created for HTTP Receive adapter.
> Please advise me with the details
>
> Thanks in advance
> Umeshanth

thiago_bagua@yahoo.com

2006-05-17, 7:14 pm

We had something like that on our BT2004 staging server yesterday as
well. We didn't have time to look into what caused the problem, I
believe it was some network change from the operations team, but after
restarting the application pool and making sure the "Default Web Site"
and the virtual directory security were set to "Accept client
certificate" it started working again. Weird.

Sponsored Links






Free braindumps | Software forum | Database administration forum

Copyright 2003 - 2008 webservertalk.com