none
The BizTalk HTTP receive adapter failed to initialize itself RRS feed

  • Question

  • Hi All,

    I had an application on let us say domain X which was sending Requests to BizTalk via HTTP adapter.

    It was working all fine until we decided to upgrade the application to a new server on a different domain let us say Y.

    ServiceAccount for that application changed to x\MyServiceAccount to y\MynewServiceAccount.

    Now whenever that application is sending request to BizTalk server they are getting 500 Internal server error and I am getting below events logged in BizTalk Server:

    The Messaging Engine failed to register the adapter for "HTTP" for the receive location "/HTTPInterface/BTSHTTPReceive.dll". Please verify that the receive location exists, and that the isolated adapter runs under an account that has access to the BizTalk databases.

    and

    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.

    Do I need to add the Y\MynewServiceAccount to BizTalk Isolated Host Group or somewhere else.

    And on IIS it is set for Anonymous access and I can still receive successfully from old application from old server.

    Any insights will be appreciated,

    --vikingss

    Thursday, December 5, 2013 6:53 PM

All replies

  • 500 is a server error so I don't think it has something to do with the service account of the triggering application. Any  service account of the triggering application issue should cause authorisation related errors-400*.

    And you still able to access the Virtual directory using your old application. Strange !!!

    • Is this issue something related to 32-bit/64-bit. Can you try switching this flag in application pool used by your virtual directory?  http://technet.microsoft.com/en-us/library/aa559072(BTS.10).aspx
    • Or do you send different filters between these two servers? i.e. from one server you send request like  ""/HTTPInterface/BTSHTTPReceive.dll?PO-Test" and in another server you send request like ""/HTTPInterface/BTSHTTPReceive.dll?PO-Stage" where you don't have receive location configured to another request or the receive location for another request is disabled.

    If this answers your question please mark it accordingly. If this post is helpful, please vote as helpful.


    Thursday, December 5, 2013 7:49 PM
  • Hi,

    When I am trying to browse http://localhost:81/HTTPInterface/BTSHTTPReceive.dll?GetmyInfo  from the BizTalk Server, it is giving me same error.

    I created a new virtual directory on port 82 for secure connection with require SSL and ignore certifcate

    and trying to browse https://localhost:82/HTTPInterface/BTSHTTPReceive.dll?GetmyInfo, I am not getting the error logged in eventviewer.

    Is it something to do with Port 81 for HTTP Adapter. Definitely It is an IIS issue.

    Please note in both cases it is running under same app pool which is running under account which has access to BizTalk DB's.

    Regards,

    vikingss


    Friday, December 6, 2013 6:04 AM
  • Hi,

    Could you please check that the App Pool you assigning to the web service is running with a account which has access to BizTalkMsgBoxDb.

    Refer below links for setting the App Pool Identity:

    For IIS 7.0:

    http://technet.microsoft.com/en-us/library/cc771170(v=ws.10).aspx

    For IIS 6.0:

    http://www.microsoft.com/technet/prodtechnol/WindowsServer2003/Library/IIS/f05a7c2b-36b0-4b6e-ac7c-662700081f25.mspx?mfr=true

    Hope this will help.


    Thanks,
    Prashant
    ----------------------------------------
    Please mark this post accordingly if it answers your query or is helpful.

    Friday, December 6, 2013 11:40 AM
  • Off Course Yes, otherwise how it was running till now for years until we moved the application(Who is sending to BizTalk) to another server on another domain.

    And we are still able to receive requests from old application located on the old server.

    Saturday, December 7, 2013 12:18 PM