BAM. Track message payload inside dynamic send port

Somehow Biztalk 2010 BAM fails to track message payload inside dynamic send port. Messaging properties and Context properties (from our own property schema) are tracked correctly.
I'm using XMLTransmit with specified document schema property on the send port, but this does not help.
Tracking the same properties on Receive port is successful.
What could cause this kind of behavior?

I do not use ESB. There are only simple send ports. I have been trying to track message payload either from static and from dynamic sen ports. In both cases it does not track anything (only null values).
I've trying with simple solution: one send and one receive ports. No mapping or other stuff. Tracking profile had the same fields set, both with two ports mapped: one send, and one receive. Receive port line is filled with correct values from message, while
send port line stays empty (null).
What could cause such behavior?

Similar Messages

Biztalk 2010 : Dynamic send Port Block : HTTP Adapter

Hi
I have a customer who makes an intensive use of the DefaultServerApp host instance.
All of his applications use this instance for dynamic send port ( HTTP send adapter)
The problem is sometimes the messages accumulate in the message queue of the HTTP Send adapter and I have to restart the host instance to fix the problem until it appears again a month later.
note: many messages are timed out , could this to be the root cause ?

Secondary messagebox
-why !!!!
You have an issue in just one of the host instances. Where is this Secondary messagebox came into play? Is your database struggle with the load and does the message process
affect “all your processing in BizTalk”?
Or is this issue in host instance/design related. As you have many dynamic ports all of them will be using the default host instance. Some of these processes may have high
volume or high size messages so your host instance may be struggling to process the message and could cause the memory/process usage related issue. Exactly for these reasons Microsoft has given an option to tweaking the host processing and throttling setting.
Adding an additional messagebox database would be overdo for your issue.
Consider tweaking the throttling settings. If the process memory was increasing
continuously and if your investigation boils down to process memory usage for this issue, consider tweaking the
Process memory usage and Physical memory usage throttling thresholds.
Consider the suggestions from this MSDN article..
http://support.microsoft.com/kb/918643
Also consider about adding more RAM, physical memory.
As I mentioned in my earlier post, run the messagebox viewer tool and review its reports for health of the server.
Also ensure you have the latest version of Cumulative Update for your version of BizTalk installed. In some of the CUs, fix for memory leak has been included.
Another suggestion, review the design where you have so many dynamic ports. May be some of these processes have high volume or high size messages and since all use the dynamic
ports hence the same host instance you could have this issue. Consider to move away from dynamic port for some of the processes, if you find either high volume or high size message processing.
If this answers your question please mark it accordingly. If this post is helpful, please vote as helpful by clicking the upward arrow mark next to my reply.

Dynamically assign a send pipeline to a dynamic send port in orchestration

Hi
I have an orchestration that is using a dynamic send port. I need to somehow assign the send pipeline to the dynamic send port programmatically.
for example, I will have a decide shape in the orchestration. Based on the condition in the decide shape I need to assign the corresponding send pipeline for that condition. let's say in Branch A, I want to select xml assembler , in Branch B I will want
to select a flat file assembler...
how can this be achieved. I have seen some links recommending using the ESB tool kit, but I do not want to go down that route.
any help is appreciated
Regards, Mazin - MCTS BizTalk Server 2006

Ashwin
Thanks again for your reply.
If I do it using role links I will loose the flexibility I have "having a dynamic file name" lots of our partners would like to receive their files with specific file naming convention based on the content of the file.
If I use a decide shape / another dynamic send port, this means that everytime I have a new custom pipeline I would need to modify the orchestration and add another decide branch with another dynamic send port.
both of the above suggestions will break the flexibility of the solution since we now can configure new partners in seconds in the configuration database without the need to modify the orchestration or add any new send ports
Regards, Mazin - MCTS BizTalk Server 2006
So in your requirement, the “dynamic” nature you want from send port are
following:
To set the send file names dynamically depends on the message received.
To send the message to different send locations depending on the message received. You want to retrieve this destination URL location from database.
And send ports may have different pipeline component like flat-file and XML ones.
As I have commented in my earlier reply, Role-Link could fit your bill perfectly and this can be achieved by using following:
1) Receive a message into an Orchestration.
2) In Orchestration set the file name dynamically based on the received file and following code shall help you to set the name of the file to dynamic.
msgToBeSend(FILE.ReceivedFileName)="YourDynamicFileNameUWantToAssign";
Use the above while constructing the outgoing message.
3) Create a “Provider” Role-Link with send port type following the wizard.
4) In Orchestration’s expression shape may be before sending the message out,
performs the party resolution using a code similar to the following:
YourRoleLinkName(Microsoft.XLANGs.BaseTypes.DestinationParty) = new Microsoft.XLANGs.BaseTypes.Party(msgToBeSend.YourDistingushedPropertyToIdentifyParty, "OrganizationName");
5) In the above sample code “YourDistingushedPropertyToIdentifyParty” refer for the code which could identify the partyname where the send port is configured.
6) Create Parties representing different type of message to be send like flat-file or XML messages.
7) Create a static send port and populate the outbound URL dynamically by using a custom pipeline component. In the custom pipeline component URL can be dynamically bound by calling the database as per your reqirement i.e based on the received message by
accessing its content in custom pipeline access the database, find the destination URL and assign the “OutboundTransportLocation” context property of the outbound message something like this
msgToBeSend.Context.Promote("OutboundTransportLocation", "http://schemas.microsoft.com/BizTalk/2003/system-properties", YourOutboundURLFromDatabase);
Refer this article on this topic:
http://www.codit.eu/blog/2013/03/06/adding-dynamic-behavior-to-static-send-ports-a-caveat/
8) In the Parties you have created assign the send ports.
9) GoTo your “Role-Links” folder within the deployed BizTalk application and enlist the parties.
These steps enable you to achieve the dynamic requirement you want to implement with the mentioned Role-Link.
Regards,
M.R.Ashwin Prabhu
If this answers your question please mark it accordingly. If this post is helpful, please vote as helpful by clicking the upward arrow mark next to my reply.

Dynamic Send Port : The FILE send adapter cannot open file C:\Temp for writing. Details: Access is denied.

Hi All,
We have requirement of using ESB toolkit and transforming incoming xml file to edi format. So, we are using ItinerarySelectReceiveXML pipeline for receiving the input from the input location and "EDISend" pipeline for transforming it into EDI and
send it to destination.
Now, the receive pipeline is picking up the file, but it is not processed and sent to destination.
And, we are getting an Access Denied error from Dynamic send port.
Error Description :
The FILE send adapter cannot open file C:\Users\Public\Temp for writing.
Details: Access is denied.
Any Immediate solutions/suggestions are appreciated...Thanks.
Anand

The difference between dynamic and static port would be send handler. For dynamic port, default send handler will be used and for static port the one configured on the port will be used, could you validate this configuration.
Also sometimes, administrative privileges are not "real" administrative privileges and company admins will have limited permissions on C Drive folders. Try writing to some other folder to isolate the issue.
Regards, Ajeet Kumar MCTS Biztalk Server

BizTalk Server 2013 and deployment MSI with dynamic send ports

Hello community, wonder if any help out there for this odd problem.
Deployment of application msi fails into BizTalk 2013 prod environment, fails when deploying the project dll that contains all the orchestrations,
and reports a failure to apply early bindings. The only early bindings in this project are dynamic send ports. I cannot recreate the problem in in my QAS environment where deployments of the same msi works fine.
I can build an msi without any bindings at all except for the dynamically created ones, and this also display the same behaviour on import.
I have test deployed a 2nd unrelated app that also uses dynamic send ports, and this displays the problem.
Adding the assembly directly to BizTalk console displays the same behaviour.
Deployment of msi apps without dynamic send ports are ok.
The dynamic ports use a pipeline including a custom pipeline component which I can confirm is available in the correct directory
C:\Program Files (x86)\Microsoft BizTalk Server 2013\Pipeline Components
No specific further detail is available in the error except.
Import Wizard[09/05/2014 08:20:47]: Error in Importing Application
Import Wizard[09/05/2014 08:20:47]: Change requests failed for some resources.
BizTalkAssemblyResourceManager failed to complete end type change request.
Unable to deploy early bindings.
Failed to update binding information.
Error in the application.
Other information that may be relevant:
The main difference between QAS and PROD is that PROD is a two node cluster. Import behaviour is the same if attempted on either node. Assemblies are installed in both nodes currently.
The dynamic ports are set on handlers that are non-clustered hosts (all are for adapter type SMTP).
I have ensured that all the adapter handlers are identically setup in both environments.
The project files were migrated to BizTalk 2013 from BizTalk 2010, imported and then converted using VS 2012.
The msi has installed the assemblies as per usual and they do exist in the .net 4 gac
There is a reference to a shared resource in a different application, this application is installed and imported ok.
I’m a bit stuck at what to try now, I have option where I could recreate the dynamic ports from scratch in the orchestrations and redeploy to dev in the hope it’s something that VS2012 didn’t handle too gracefully
when converting the project. I could move the functionality into a helper class and forget about using dynamic sends, rather not go down that route. I'm still suspecting this is small difference in setup
of the group between QAS and PROD but I can't see anything jumping out.
Any comments are most welcome.

The dynamic ports use a pipeline including a custom pipeline component which I can confirm is available in the correct directory
C:\Program Files (x86)\Microsoft BizTalk Server 2013\Pipeline Components
I’m a bit stuck at what to try now, I have option where I could recreate the dynamic ports from scratch in the orchestrations and redeploy to dev in the hope it’s something
that VS2012 didn’t handle too gracefully when converting the project.
Two things.
1. That's what I would do first, recreate (really just change and reset the properties) the Orchestration Ports in Visual Studio.
2. Probably not related but, Custom Pipeline Components should not be placed in the Pipeline Components folder. All Custom Pipeline Components should be in the GAC only. The Pipeline Components folder
is a compatibility vestige from BizTalk Server 2004.

How to configure Send Handler for BizTalk 2013 Dynamic Send Port on deployment?

Hi,
I do know how to manually configure a send handler for a dynamic send port in BizTalk 2013 Administration console. Though, once you export your application's configuration to a binding file, the dynamic send port's configuration does not
contain any information regarding the send handler. When you try to use this binding file when deploying your application your dynamic port's send handler falls back to the default host instance.
So my question is, how could we automate this process to avoid manual step in a dynamic port configuration during deployment?
Thank you,
--Vlad

Hey vlad,
As discussed at work in the office.. I woudl take the powershelll approach for now as a workaround. Here's a trivial script for my local dev box (all in one biztalk & SQL) (must be run in an x86 powershell session):
param
[string] $bizTalkDbServer = ".",
[string] $bizTalkDbName = "BizTalkMgmtDb",
[string] $fileHostInstance = "SendingHost",
[string] $sendPortName = "sm_dynamic_sp_test"
[System.reflection.Assembly]::LoadWithPartialName("Microsoft.BizTalk.ExplorerOM") | Out-Null
$catalog = New-Object Microsoft.BizTalk.ExplorerOM.BtsCatalogExplorer
$catalog.ConnectionString = "SERVER=$bizTalkDbServer;DATABASE=$bizTalkDbName;Integrated Security=SSPI"
foreach($sp in $catalog.SendPorts)
if($sp.Name -eq $sendPortName)
  "Found send port $($sp.Name), analyzing send handler"
  foreach($sh in $sp.DynamicSendHandlers)
   if($sh.SendHandler.TransportType.Name -eq "FILE")
    if($sh.SendHandler.Host.Name -ne $fileHostInstance)
     "Changing $($sh.Name) send handler to '$fileHostInstance' from '$($sh.SendHandler.Host.Name)'"
     $sp.SetSendHandler("FILE", $fileHostInstance)
    else
     "Send handler for $($sp.Name) is already '$fileHostInstance' ignorning .. "
$catalog.SaveChanges()

Set Custome pipeline for dynamic send port in orchestration

I need to assign custom pipeline for dynamic send port in an orchestration .

The option is available in the Port Configuration wizard
Thanks, Murugesan M - Please Mark as the Answer, if this answers your question. Please vote as helpful, if this post is helpful.

How to configure SMTP dynamic send port?

Hi,
I am trying to configure STMP send port to send emails, enabled SMTP Server on the DEV box and configured it as described in the link below.
https://sandroaspbiztalkblog.wordpress.com/2013/05/09/biztalk-2013-installation-and-configuration-install-and-configure-smtp-server-feature-part-4/
Able to send emails using Telnet client, and these email get stored in C:\inetpub\mailroot\Queue folder.
I have a dynamic send with following values.
msgEMail(SMTP.CC) = “[email protected]”;
msgEMail(SMTP.DeliveryReceipt) = False;
msgEMail(SMTP.From) = “[email protected]”;
msgEMail(SMTP.ReadReceipt) = False;
msgEMail(SMTP.Password) = “XXX;
msgEMail(SMTP.Username) = “DDD”;
msgEMail(SMTP.SMTPAuthenticate) = System.Convert.ToUInt32(XX.SMTPAuthenticate);
msgEMail(SMTP.SMTPHost) = “smtp.domain.local”;
msgEMail(SMTP.Subject) = “sdfgdfgd;
msgEMail(SMTP.MessagePartsAttachments) = 2;
Message gets suspended with the following error message.
A message sent to adapter "SMTP" on send port "XXX_DynamicSendPort_XXXX" with URI "mailto:
[email protected]" is suspended.
Error details: There was a failure executing the send pipeline: "Microsoft.BizTalk.DefaultPipelines.XMLTransmit,
Microsoft.BizTalk.DefaultPipelines, Version=3.0.1.0, Culture=neutral, PublicKeyToken=81bf3856ad764e35" Source: "XML assembler" Send Port: "XXX_DynamicSendPort_XXXXX URI: "mailto:localhost" Reason: Data at the root level is invalid.
Line 1, position 1.
MessageId:
{3C50F418-24C4-4661-9B34-4B7F5F6FBBA4}
InstanceID: {2F6B9A0E-92EE-4953-81D2-9A124FAC99CE}
Please can some advise me what is wrong here? do you think I have configured
msgEMail(SMTP.SMTPHost) property correctly? Or should it be the name of the DEV box?
Thanks
SS
Shiva Sadayan

Hi Shiva,
You should not be using XMLTransit pipeline at the send port.
Perhaps you should go with default passthrough pipeline or
Create a send pipeline with MIME/SMIME encoder and drop it at Encode section of pipeline. Accept the default settings for MIME/SMIME encoder and use it with the dynamic port.
I found this article very useful while sending email from BizTalk. Refer:
Sending Emails in Biztalk
Rachit
Please mark as answer or vote as helpful if my reply does

Proxy settings for dynamic ftp send port

Does anyone have an idea how to configure the proxy settings when using a dynamic send port to connect to an ftp server?
When using the FTP send port there is the property 'Server' to specify the proxy settings, but how would this be done with a dynamic send port?
I can't find anything about this. And there doesn't seem to be a property
FTP.Server according to intellisence in my orchestration.
Kind regards,
Mitch Vanhelden
Blog: http://mitchvanhelden.blogspot.com

It seems like most or all of the FTP properties are exposed in the Global Property Schemas assembly. The FTP properties are under the "FTP" namespace (see FTP property schema below).
One thing you might try is to get it working (simple messaging) using a static FTP send port. Once it is working, turn on send port tracking of message properties (before and after port processing). Inspect the tracked message for the FTP
related properties set during static transmission and try setting these within your orchestration.
<?xml version="1.0" encoding="utf-16"?>
<xs:schema xmlns="http://schemas.microsoft.com/BizTalk/2003/ftp-properties" xmlns:b="http://schemas.microsoft.com/BizTalk/2003" targetNamespace="http://schemas.microsoft.com/BizTalk/2003/ftp-properties" xmlns:xs="http://www.w3.org/2001/XMLSchema">
<xs:annotation>
<xs:appinfo>
<b:schemaInfo schema_type="property" xmlns:b="http://schemas.microsoft.com/BizTalk/2003"/>
</xs:appinfo>
</xs:annotation>
<xs:element name="RepresentationType" type="xs:string">
<xs:annotation>
<xs:appinfo>
<b:fieldInfo propSchFieldBase="MessageContextPropertyBase" xmlns:b="http://schemas.microsoft.com/BizTalk/2003" propertyGuid="198b2027-4cde-4677-88f1-7b66caf6473a"/>
</xs:appinfo>
</xs:annotation>
</xs:element>
<xs:element name="SSOAffiliateApplication" type="xs:string">
<xs:annotation>
<xs:appinfo>
<b:fieldInfo propSchFieldBase="MessageContextPropertyBase" xmlns:b="http://schemas.microsoft.com/BizTalk/2003" propertyGuid="8045bcbe-3285-412c-8b5a-dc3be5978c9b"/>
</xs:appinfo>
</xs:annotation>
</xs:element>
<xs:element name="UserName" type="xs:string">
<xs:annotation>
<xs:appinfo>
<b:fieldInfo propSchFieldBase="MessageContextPropertyBase" xmlns:b="http://schemas.microsoft.com/BizTalk/2003" propertyGuid="6E789556-2F81-4fa6-B8E2-5214F1662289"/>
</xs:appinfo>
</xs:annotation>
</xs:element>
<xs:element name="Password" type="xs:string">
<xs:annotation>
<xs:appinfo>
<b:fieldInfo propSchFieldBase="MessageContextPropertyBase" isSensitive="true" xmlns:b="http://schemas.microsoft.com/BizTalk/2003" propertyGuid="FEFD9283-C98A-470d-8E0A-C00214EE4047"/>
</xs:appinfo>
</xs:annotation>
</xs:element>
<xs:element name="BeforePut" type="xs:string">
<xs:annotation>
<xs:appinfo>
<b:fieldInfo propSchFieldBase="MessageContextPropertyBase" xmlns:b="http://schemas.microsoft.com/BizTalk/2003" propertyGuid="58C0F130-2D2D-4374-8418-714A31046A58"/>
</xs:appinfo>
</xs:annotation>
</xs:element>
<xs:element name="AfterPut" type="xs:string">
<xs:annotation>
<xs:appinfo>
<b:fieldInfo propSchFieldBase="MessageContextPropertyBase" xmlns:b="http://schemas.microsoft.com/BizTalk/2003" propertyGuid="CFBD9956-B0C6-48af-9257-4E27C7771998"/>
</xs:appinfo>
</xs:annotation>
</xs:element>
<xs:element name="ReceivedFileName" type="xs:string">
<xs:annotation>
<xs:appinfo>
<b:fieldInfo propSchFieldBase="MessageContextPropertyBase" xmlns:b="http://schemas.microsoft.com/BizTalk/2003" propertyGuid="441B372A-23A1-4465-8329-F56AC0BDBFD8"/>
</xs:appinfo>
</xs:annotation>
</xs:element>
<xs:element name="MaxConnections" type="xs:unsignedInt">
<xs:annotation>
<xs:appinfo>
<b:fieldInfo propSchFieldBase="MessageContextPropertyBase" xmlns:b="http://schemas.microsoft.com/BizTalk/2003" propertyGuid="0A580338-036A-411B-A28A-1BCC86E56458"/>
</xs:appinfo>
</xs:annotation>
</xs:element>
<xs:element name="CommandLogFileName" type="xs:string">
<xs:annotation>
<xs:appinfo>
<b:fieldInfo propSchFieldBase="MessageContextPropertyBase" xmlns:b="http://schemas.microsoft.com/BizTalk/2003" propertyGuid="CCE01F9B-8869-4216-BD7A-8F476FA40327"/>
</xs:appinfo>
</xs:annotation>
</xs:element>
<xs:element name="AllocateStorage" type="xs:boolean">
<xs:annotation>
<xs:appinfo>
<b:fieldInfo propSchFieldBase="MessageContextPropertyBase" xmlns:b="http://schemas.microsoft.com/BizTalk/2003" propertyGuid="4945CA1F-A812-483B-B32F-C98513EBF51E"/>
</xs:appinfo>
</xs:annotation>
</xs:element>
<xs:element name="PassiveMode" type="xs:boolean">
<xs:annotation>
<xs:appinfo>
<b:fieldInfo propSchFieldBase="MessageContextPropertyBase" xmlns:b="http://schemas.microsoft.com/BizTalk/2003" propertyGuid="74B6373E-550F-4434-B2D1-DE912ACDB3A7"/>
</xs:appinfo>
</xs:annotation>
</xs:element>
<xs:element name="SpoolingFolder" type="xs:string">
<xs:annotation>
<xs:appinfo>
<b:fieldInfo propSchFieldBase="MessageContextPropertyBase" xmlns:b="http://schemas.microsoft.com/BizTalk/2003" propertyGuid="1C703221-ADE1-4DF7-9D6E-1770903DC614"/>
</xs:appinfo>
</xs:annotation>
</xs:element>
<xs:element name="UseSsl" type="xs:boolean">
<xs:annotation>
<xs:appinfo>
<b:fieldInfo propSchFieldBase="MessageContextPropertyBase" xmlns:b="http://schemas.microsoft.com/BizTalk/2003" propertyGuid="D032AB42-E927-470C-B5E8-E59A5E32851D"/>
</xs:appinfo>
</xs:annotation>
</xs:element>
<xs:element name="UseDataProtection" type="xs:boolean">
<xs:annotation>
<xs:appinfo>
<b:fieldInfo propSchFieldBase="MessageContextPropertyBase" xmlns:b="http://schemas.microsoft.com/BizTalk/2003" propertyGuid="42E3D7F0-5FF5-4C6E-8E72-BD76D203C6DD"/>
</xs:appinfo>
</xs:annotation>
</xs:element>
<xs:element name="FtpsConnectionMode" type="xs:string">
<xs:annotation>
<xs:appinfo>
<b:fieldInfo propSchFieldBase="MessageContextPropertyBase" xmlns:b="http://schemas.microsoft.com/BizTalk/2003" propertyGuid="EDA0F134-3F42-4DD7-8428-75BA65E7C4CA"/>
</xs:appinfo>
</xs:annotation>
</xs:element>
<xs:element name="ClientCertificateHash" type="xs:string">
<xs:annotation>
<xs:appinfo>
<b:fieldInfo propSchFieldBase="MessageContextPropertyBase" xmlns:b="http://schemas.microsoft.com/BizTalk/2003" propertyGuid="423E6603-652E-4A61-B49F-B632031E3180"/>
</xs:appinfo>
</xs:annotation>
</xs:element>
</xs:schema>
David Downing... If this answers your question, please Mark as the Answer. If this post is helpful, please vote as helpful.

HL7 Unconsumed zombie ack messages suspended on MLLP R&R receive port from MLLP R&R send port.

      I have a content message routing scenario with request/response mllp receive and send port . Below are the points which describes the situation :-
      1) mllp message received from upstream application on receive port which sends back the direct synchronous ack .
      2) Message is routed to send port which sends the message to the downstream app and receive the ack from the downstream app.
      3) The ack received from downstream app is handled using a file type send port which dumps these acks to a folder.
      Now the issue which is occurring intermittently, is that the ack message received from the downstream application get suspended on the receive port with the below error -
      "The instance completed without consuming all of its messages. The instance and its unconsumed messages have been suspended." Error code - 0xC0C01B4C.
      This issue doesn't occur for all the messages. It seems the ack messages received by the send port, is searching the receive port instance which submitted the message to message box. But interestingly, not all the ack messages
are suspended.
      If anybody have any idea about this behavior , kindly respond..

I also need this question answering!
Comment from my host:
To prevent SPAM activity we have blocked the ability to send messages from our system where the FROM address is spoofed to anything other than the original sender's ID. The work around in your situation is to change the REPLY-TO address or switch to SMTP authentication.

Dynamic SMTP Port Error -Class not Registered

Hi,BizTalk receiving the Invoice Message from Source and doing some transformation.After that Biztalk will send email dynamically via SMTP .Below is the code in message construct message assignment shape
multipartMessage1.MessagePart_1= XMLdoc;
multipartMessage1.MessagePart_2="This is message part2 as a string";
multipartMessage1(SMTP.Subject) ="Email From Dynamic Port";
multipartMessage1(SMTP.From) ="[email protected]";
multipartMessage1(SMTP.SMTPHost) ="100.110.120.99";
multipartMessage1.MessagePart_2(MIME.FileName) = "Attachment_Name";
multipartMessage1(SMTP.SMTPAuthenticate) =0;
SendInvoicePort(Microsoft.XLANGs.BaseTypes.Address)="mailto:[email protected]";
When run the application, getting below error message.
A message sent to adapter "SMTP" on send port "HelloWorld_1.0.0.0_Microsoft.Samples.BizTalk.HelloWorld.HelloSchedule_SendInvoicePort_d7ce16ba803d4f87"
with URI "mailto:[email protected]" is suspended.
Error details: Class not registered
MessageId: {0D6BBA1A-F384-4AD9-8B48-44A9C342DEFB}
InstanceID: {EAFEADE1-8D05-4A7D-A908-7BC297788D06}
After googling ,I have added
multipartMessage1 (SMTP.EmailBodyTextCharset) = "UTF-8".but no use.
I’ve spent many hours on this issue .Please advise how to resolve this issue

Hi Singam,
What is the default handler(host) configured for SMTP Adapter. Check it is 32 bit or 64 bit.
This seems to be a known issue if Host is of 64 bit.
Retrieving the COM class factory for component with CLSID {254B4003-2AA7-4C82-BB2E-18BA7F22DCD2} failed due to the following error: 80040154 Class not registered (Exception from HRESULT: 0x80040154 (REGDB_E_CLASSNOTREG)).
When you use BizTalk in 64 bit version, and the Mime/Smime encoder you’ve got this error. To resolveit, just put your pipeline on a 32 bit Host.
Mime/SMIME encoder error :
Class not registered (Exception from HRESULT: 0×80040154 (REGDB_E_CLASSNOTREG))
http://social.technet.microsoft.com/wiki/contents/articles/7204.biztalk-server-list-of-errors-and-warnings-causes-and-solutions.aspx
As you are using Dynamic Send Port it will run under the default host make it of 32 bit, restart the host and see if the issue is resolved or not.
Thanks,
Prashant
Please mark this post accordingly if it answers your query or is helpful.

WCF static send port, use of custom behavior to change the endpoint location?

The send port is outbound to various web service endpoints, all of which is the same WSDL just different location. Prefer to use the static port for features like ordered delivery. Is it possible to change the Microsoft.XLANGs.BaseTypes.Address dynamically
by a custom behavior?
https://ninithepug.wordpress.com/

Hi,
You can make static send ports partially dynamic, this can be achieved in a custom pipeline component in the send pipeline.
You should refer to the below mentioned articles:
Adding dynamic behavior to static send ports
Using a Static Send Port like a Dynamic Send Port
Rachit
Please mark as answer or vote as helpful if my reply does

Send port filter and Orchestration binding priority

Hello,
say there is some receive port RecvPort1. What will happen if some send port filter has BTS.ReceivePortName == RecvPort1 and some orchestration is binded to RecvPort1 also? When message come to receive location of RecvPort1 will it be transmitted
to send port path or into the orchestration and why?
Thanks in advance,
Tomislav

Here is the pictorial representation of your scenario for better understanding:
In BizTalk subscription, you will have two subscriptions, one subscription- when you start the orchestration (which is directly bound to Receive port) and another subscription when you enlist the send port with filter for the Receive port. Here are
the high level sequence to activities that would happed:
So after the message is received by the Receive port, it would be published to BizTalk message box db.
Subscription evaluation would take place to match subscription for the published message (into BizTalk msgbox db).
As in your case for the published message two subscriptions would be evaluated. And instance of orchestration would receive the message and also the send port with filter which match to the Receive Port which published the message
Note: Image courtesy, Microsoft which I updated for users better understanding :)
If this answers your question please mark it accordingly. If this post is helpful, please vote as helpful by clicking the upward arrow mark next to my reply.

Cannot process messages after applying BT 2010 CU6 if BAM tracking profile references BTAHL7 messaging payload schemas

We are unable to process HL7 V2 messages after applying BizTalk 2010 CU 6 in a development environment when we have a BAM tracking profile deployed that references the BTAHL7 messaging payload schemas. The messages process with no issue if we remove the
message payload schema field mappings and use only message context properties. We have replicated this issue using only the default BTAHL7 pipelines and microsoft.com HL7 V2.3 unedited schemas and a very simple BAM activity and tracking
profile. In other words, we've eliminated our customization and still see the issue. The messages fail in the pipeline with the following error:
A pipeline component in the receive pipeline:<BTAHL72XReceivePipeline>,Version=1.0.0.0, Culture=neutral, PublicKeyToken=75be5a91f43bf6c9" is using the message context
properties "BTS.MessageDestination" or "BTS.SuspendMessageOnRoutingFailure" in a unsupported fashion. The pipeline processing is being terminated.
Can anyone help us resolve this issue?
Thanks.

This seems to be a known bug please refer the below discussion-
BizTalk Server 2010 Cumulative Update 6 - Compatibility with BTAHL7?
I would suggest you to uninstall CU6 first, restart the VM, Install CU7 and restart again.
CU 7 will have all the bug fixes for BizTalk 2010 till date.
Cumulative
update package 7 for BizTalk Server 2010
Service Pack
and Cumulative Update list for BizTalk Server
Please let me know if there is anything that I can do to help.
Thanks,
Prashant
Please mark this post accordingly if it answers your query or is helpful.

BAM - using with Request Response Send Port

Hi,
I have a scenario where a message is received on a receive port, sent to a solicit-response send port, and then the response is sent out on another send port. All ports have failed message routing enabled, so that any errors are sent out to an exceptions
send port.
I am interested to hear options on how you would set up a BAM tracking profile for this in the TPE to log the time received, time sent on the two way send port, time response returned and then finally the time the last send was carried out? Would you
use a single Activity/View and continuations, Multiple Activities or Views and multiple tracking profiles etc? How would you include the time that an error was sent to the exception port.....
I have a solution, but I am not sure it is ideal and I would be interested in how others would tackle this. If you know BAM, feel free to offer an opinion :)
Thanks
Stu.
Stuart Brierley - BizTalk Integration Specialist - http://geekswithblogs.net/StuartBrierley/Default.aspx

Hi Stuart,
You can start up your activity from Orchestration .No need to have a continuation from Pipeline as you can use xml receive .
You solution is simple were you are receiving your message from location and hitting a solicit-response
port .
Just have a Expression shape to start up with your activity and on the points when you want to update
the activity.
Code is listed below
//Create a Activity ID
string activityId = Guid.NewGuid().ToString() ;
//Start the activity with your Activity Name
Microsoft.BizTalk.Bam.EventObservation.OrchestrationEventStream.BeginActivity(“SampleActivity”, activityID);
// Updates the activity record.
Microsoft.BizTalk.Bam.EventObservation.OrchestrationEventStream.UpdateActivity(“SampleActivity”, activityID, “ReceiveLocation”, Rcvmsg(BTS.Receivelocation), "TRANSACTION_CREATED", DateTime.UtcNow);
// End the activity record.
Microsoft.BizTalk.Bam.EventObservation.OrchestrationEventStream.EndActivity(“SampleActivity”, activityID);
If you want to work with same activity in continuation with Other Orchestration (Generic Exception Handler may be ),then create a continuation token with a Property schema and from parent Orchestration assign value to it.
continuationToken = "_Continuation" + msg_Internal.ContinuationID;
Hope this will clear your ideas as you dont require to start up tracking from Pipeline .
Thanks
Abhishek

BAM. Track message payload inside dynamic send port

Similar Messages

Maybe you are looking for