locked
The Messaging Engine failed while notifying an adapter of its configuration.The Receive Locations that are shutting down RRS feed

  • General discussion

  • The Messaging Engine failed while notifying an adapter of its configuration.The Receive Locations that are shutting down
    Saturday, February 11, 2012 6:37 PM

All replies

  • Hi

    Could you please provide more details about the problem, What adapter you are using on receive location? make sure that the BizTalk SSO service and Biztalk hosts are running.

    Please provide more details.

    HTH,Thanks, Naushad (MCC/MCTS) http://alamnaushad.wordpress.com |@naushadalam

    If this is helpful or answers your question - please mark accordingly.

    Saturday, February 11, 2012 6:43 PM
    Moderator
  • File,SQL,FTP adpaters using. we changed Ip address to host name.after changing this error "The Messaging Engine failed while notifying an adapter of its configuration" and The Receive Locations that are shutting down
    Saturday, February 11, 2012 7:42 PM
  • Hi

    Could you try restarting the BizTalk Hosts, which is configured on the receive location?

    Also you would need to check if the folder location has access for Biztalk Service account? You might need to check if the permissions are valid for BizTalk service accont.

    Also please see this support article and this blog post link which are for same problem. 

    HTH,Thanks, Naushad (MCC/MCTS) http://alamnaushad.wordpress.com |@naushadalam

    If this is helpful or answers your question - please mark accordingly.



    Saturday, February 11, 2012 7:46 PM
    Moderator
  • Hi Niranjan,

    1) one more suggestion have you added hostname in hosts file at C:\WINDOWS\system32\drivers\etc

    This is basically required for your hostname resolution. Make sure you add these entries in all the BizTalk servers. 

    2) Ensure that the host name can be resolved using the ping command from command prompt.

    3) If above steps dont help you. Please get in touch with network guys. This is more of a host name resolution issue which is causing the receive locations to shut down. 

    I hope this helps you.


    Thanks With Regards,
    Shailesh Kawade
    MCTS BizTalk Server
    Please Mark This As Answer If This Helps You.
    http://shaileshbiztalk.blogspot.com/


    Monday, February 13, 2012 6:16 AM
  • This is not even close to being answered. if you are running a WCF-Custom adapter.  Where have you ever read that it is recommended to put any hosts in the Host file? 
    Friday, March 16, 2012 9:26 PM
  • Hi Tom,

    Good point I have not read that either. It seems that the host either cannot find the address/location of FTP, SQL and File receive locations or does not have appropriate rights. However the issue is not clear:

    File,SQL,FTP adpaters using. we changed Ip address to host name.after changing this error "The Messaging Engine failed while notifying an adapter of its configuration" and The Receive Locations that are shutting down

    WCF-Custom adapter is not mentioned. I leave it open for discussion.

    Cheers,

    Steef-Jan Wiggers

    MVP & MCTS BizTalk Server 2010

    http://soa-thoughts.blogspot.com/ | @SteefJan

    If this answers your question please mark it accordingly


    BizTalk

    Saturday, March 17, 2012 7:18 AM
    Moderator
  • Altering the hosts file can in cases solve issues, eg. moving a dns name to another server instaed of the original one, for example if you are having issues with connecting to www.testing.com and that domina is point to a wrong IP, altering the hosts file manipulating it to point towards another IP may resolve the issue, however it is not even close to recommended in any ways. I used to do that when i was a developer developing webpages and "hosted" them internally (faster to connect to a local server using local IP then via the internet).

    Either way, as Tom and Steef-Jan says this is not even close to answered (and im sorry for my "marked as answer") :)

    Since the person asking the question havent had any feedback I'm pretty sure the whole thing is resolved and no long an issue. Having the resolution here would help a lot. But If people ever feel to search for this, and end up here, re recommended things to check is:

    • Verify SSO
    • Verify MSDT

    But without any more information is impossible to resolve it.

    Best regards

    Tord Glad Nordahl
    Bouvet ASA, Norway
    http://www.BizTalkAdmin.com |@tordeman

    Please indicate ”Mark as Answer” if this post has answered the question.

    Monday, March 19, 2012 9:37 AM