by community-syndication | May 30, 2013 | BizTalk Community Blogs via Syndication
While configuring an web service generated using the BizTalk Web Services Publishing Wizard using WCF-BasicHttp adapter you might get the following error message
The Messaging Engine failed to register the adapter for "SOAP" for the receive location "/XXXX/XXXXXXXXRequestResponse.asmx".
Please verify that the receive location exists, and that the isolated adapter runs under an account that has access to the BizTalk databases.
BizTalk 2010 gives you two ways to expose your Orchestrations as a service one using the SOAP adapter (BizTalk Web Services Publishing Wizard) the other using the WCF adapter (BizTalk WCF Service Publishing Wizard). When you use the BizTalk Web Services Publishing Wizard you generate a web service with a .asmx extension. When you use the BizTalk WCF Service Publishing Wizard you generate a web service with a .svc extension.
Usually during an upgrade it is recommended to expose your orchestrations via WCF using the BizTalk WCF Service Publishing Wizard. But using the WCF Publishing Wizard would change the URL for the service from .asmx to .svc. Which would mean a larger impact in terms of communicating to all the clients that use the service about the change in the URL.
As you know BasicHttp binding in WCF is compatible with asmx. So one of our clients had published the orchestration using the Web Services Wizard (asmx) and while configuring the receive location used the WCF-BasicHttp binding to receive the messages. That’s when this error will show up.
When you publish an orchestration using the Web Services Wizard (asmx) it internally uses an assembly from the SOAP adapter to construct the BizTalk message. So the Host needs to have permission to load the SOAP adapter. In this case we had our Host as a receive handler for the WCF-BasicHttp Adapter alone and not the SOAP Adapter.
To get around this situation you must add your HOST as a new Receive/Send Handler for the SOAP adapter as well (even though you are using the WCF-BasicHttp Adapter to receive the messages).
To conclude
1. Do upgrade to the WCF Adapter but use the BizTalk WCF Service Publishing Wizard
2. The BizTalk Web Services Publishing Wizard is meant to be used with the SOAP Adapter
3. If you use the BizTalk Web Services Publishing Wizard and configure the Receive Location to using WCF-BasicHttp binding you will need to grant the HOST permission to load both the WCF-BasicHttp and SOAP Adapters.
Blog Post by: Shinva
by community-syndication | May 29, 2013 | BizTalk Community Blogs via Syndication
IIS manager failed to connect due to a corrupt Microsoft.Adapters.Sql_schema.xml file. This post explains how to fix this file into its default state.
by community-syndication | May 28, 2013 | BizTalk Community Blogs via Syndication
Most developers who have worked with BizTalk for a while will realize the benefits of using direct bindingon orchestration ports to improve flexibility and loose coupling. What is not often realized is that using direct rather than specify later port binding comes with a bit of a trade-off in that the increased flexibility results in […]
Blog Post by: Johann
by community-syndication | May 28, 2013 | BizTalk Community Blogs via Syndication
Here’s a nifty way to add a ‘Run in Command Prompt’ context menu item to the Visual Studio solution explorer. http://www.rickglos.com/post/How-to-run-windows-batch-files-from-Visual-Studio-2010-Solution-Explorer.aspx Very handy for executing .cmd files to generate .Net type definitions from a BizTalk schema.
Blog Post by: Brett
by community-syndication | May 27, 2013 | BizTalk Community Blogs via Syndication
By default, the “Startup type” propriety of BizTalk Windows Services, Enterprise Single Sign-On Service, Microsoft UDDI Notification Service and the new BAMAlerts service are set as “Automatic”, however some of this Windows Services may not start automatically after a system restart, to avoid this behavior you must configure the “Startup type” to “Automatic (Delayed Start)” […]
Blog Post by: Sandro Pereira
by community-syndication | May 27, 2013 | BizTalk Community Blogs via Syndication
From Saravana Blog post I came to know that the new Message Box Viewer 13 is available now at JPBlog. I thought of integrating it with BizTalk360 v6.0 but I was not able to do so, ans was getting the below mentioned error:
Could not load file or assembly ‘MYHC,
Version=2.0.0.0, Culture=neutral, PublicKeyToken=null’ or one of its
dependencies.
The located assembly’s manifest definition does
by community-syndication | May 27, 2013 | BizTalk Community Blogs via Syndication
The past time I haven’t posted a lot on this blog, especially not much blog posts on BizTalk subjects. This doesn’t mean that I haven’t done any BizTalk related blog posts, I just haven’t done it on my personal blog for a while… I’ve mostly posted on my companies blog, where I am the sole contributor and administrator.
But for all of you loyal readers of my personal blog, I thought it would be nice to give an overview of all of my latest posts. I’m thinking of doing this every once in a while to keep all of you updated on ALL of my posts.
So here goes for the period till May 2013…
- BizTalk error: ’The message found multiple request response subscriptions’: solution to sending messages to multiple request-response send ports
- BizTalk file mask difference for windows 7 and windows server 2008 r2: A difference in file mask usage between windows 7 and windows server 2008 r2
- BizTalk360 v6.0: new features explained: a quick view on some of the improvements introduced in the new BizTalk360 version 6.0
- BizTalk Server 2013 is now RTM!: the announcement of the new BizTalk version release on MSDN, with the new features listed
- BTS2013 features explained: XslCompiledTransform: I started a new series on viewing some of the new features of BizTalk 2013 in more detail, the first one was about the XslCompiledTransform
- BTS2013 features explained: Improvements in dynamic send ports: follow up post on a new BizTalk 2013 feature on the Improvements in dynamic send ports
- BTS2013 features explained: Dependency tracking: an in depth view of the new dependency tracking feature of BizTalk 2013
- First Cumulative Update for BizTalk 2013 available through Microsoft Update!: the announcement that the very first cumulative update was released for BizTalk 2013, and that it even was available through Microsoft Update
- BAM error: Failed to list permissions for BAM view – System.Data.SqlTypes.SqlNullValueException: Data is Null: a solution to a BAM issue I encountered
Hope you enjoy these blog posts!
by community-syndication | May 26, 2013 | BizTalk Community Blogs via Syndication
BizTalk Server database databases and their health are very important for a successful BizTalk Server database messaging environment. BizTalk is shipped out with a total of 13 SQL Agent jobs. By default, the following BizTalk jobs aren’t configured and enabled upon installation. Backup BizTalk Server (BizTalkMgmtDb) DTA Purge and Archive (BizTalkDTADb) MessageBox_Message_Cleanup_BizTalkMsgBoxDb The two jobs […]
Blog Post by: Sandro Pereira
by community-syndication | May 24, 2013 | BizTalk Community Blogs via Syndication
This blog post represents the first in a weekly series that will highlight things you need to know about new features in BizTalk Server 2013. This week we will look at the new mapping engine and how the underlying changes in the engine might effect the behavior you see when using the BizTalk Mapper. If […]
Blog Post by: Nick Hauenstein
by community-syndication | May 24, 2013 | BizTalk Community Blogs via Syndication
One of the interesting challenges I’ve faced in the last year was creating a flat file schema for a well established custom flat file format that was in use at one of my clients. What made this flat file format different from most that I had dealt with in the past was that this flat […]
Blog Post by: Johann
