Biztalk 2013 configuring to receive a 999

While attempting to process a 999 file that we receive (not generating it), the message goes suspended with the following error
Message Type 999 is not allowed as part of the Agreement
Since there is no 999 in the dropdown list for supported transactions, and there's lots of hints on the web that say the support for 999 was moved into the base artifact set for Biztalk 2013, what does one need to do in the party agreements to set to receive
a 999
Thanks
Scott K Berger

Hi,
BizTalk Server 2013 introduces a new way to configure this, while allowing us to use out of the box components and update the setting at the agreement level.
For more information, you can refer here(#new way to 999)
http://blog.quicklearn.com/tag/biztalk-server-2013/
Hope it can help you.
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Similar Messages

Biztalk 2013 configuration with remote sqlserver 2008 R2

Hi
can any one help me to configure Biztalk server 2013 with remote sqlserver 2008 R2(Installed in other system) ,
what are the steps need to be follow to configure the same.

Hi All,
Thanks for the quick repose ,i am getting below error while configure the BTS 2013 .
Error Details:
TITLE: Microsoft BizTalk Server Configuration Wizard
Failed to create the SQL database 'SSODB' on SQL Server '' (with SSO Administrator account 'SSO Administrators'). (SSO)
For help, click: http://go.microsoft.com/fwlink/events.asp?ProdName=Microsoft+BizTalk+Server+2013&ProdVer=3.10.229.0&EvtSrc=SSO&EvtID
ADDITIONAL INFORMATION:
(0xC0002A21) An error occurred while attempting to access the SSO database.
(SSO)
For help, click: http://go.microsoft.com/fwlink/events.asp?ProdName=Microsoft+BizTalk+Server+2013&ProdVer=3.10.229.0&EvtSrc=SSO&EvtID
An error occurred while attempting to access the SSO database. See the event log (on computer ' ') for more details.
(SSO)
For help, click: http://go.microsoft.com/fwlink/events.asp?ProdName=Microsoft+BizTalk+Server+2013&ProdVer=3.10.229.0&EvtSrc=SSO&EvtID
BUTTONS:
OK

BizTalk 2013 SFTP Adapter : Host Instance configured for SFTP Receive cause high CPU usage

Hi,
Our BizTalk 2013 Server test env have 16 GB RAM. We have one SFTP Receive Location which is using a dedicated Host instance for SFTP receive.
As soon as we start this SFTP Host Instance it starts consuming 50-60% CPU. (Even when it is not handling any file receive)
As suggested in below thread, to fix this issue, we changed the SFTP RL default configuration. i.e. Changed polling interval from default 0 sec to
10 minutes and also changed the RL Schedule window to business hours only.
https://connectedpawns.wordpress.com/2014/04/13/biztalk-2013-sftp-adapter-biztalk-host-receiving-throttled-because-processmemory-exceeded-the-configured-throttling-limit/#comment-2602
Even after changing the RL configuration , the Host Instance continuously consumes ~60% CPU.
Any suggestions to troubleshoot more on this issue ?
Thanks in advance !!
Anoop

This is one of the issue which has already been raised to Microsoft and hopefully a public build will be available soon in next cumulative update pack .
There are variety of reason for this starting for password mismatch or password not given , SFTP adapter unable to connect and so on .
There is good post here in below link for this issue
http://thoughtsofmarcus.blogspot.co.uk/2013/06/leaving-password-blank-in-biztalk-2013.html
Another greate artcicle is by Nino which states these issues .SFTP adapter is protocol sensitive and some configuration by server side, can cause a lot of crazy situations
http://ninocrudele.me/2014/01/29/checkstat-and-sftp-adapter-issues/
Thanks
Abhishek

BizTalk 2013 choice for "999" file type missing in Party Agreement configuration

Ok guys--this makes no sense. In BizTalk 2010, we were able to select the 999 file type in the party Config/Agreement section, specifically in the "Envelopes", "Local Host Settings" & Transaction Set List" sections under
"Transaction Set Settings". I could see if this was a 997 file type as that should be deprecated under 5010, but this is 999, the new format.
Since my experience with 2013 is limited, can anyone tell me if there is a service pack or CU we missed when this was setup that might include this? A setting somewhere perhaps?
Any assistance is appreciated--thanks in advance---
Tom

Confirmed as bug / oversight in Biztalk 2013 -Ugh
Hello Scott,
We did an in-house repro and realized that this does not work.
It seems in BizTalk Server 2010, we had 999 listed under the
supported transactions list, but it is somehow not listed in BizTalk Server 2013.
We have raised a ticket to the Product Group to review this and make the required change. However, we do not have an ETA by when this change will be implemented.
Thanks,
Kshitij
Scott K Berger

SFTP Adapter Receive location does not work on BizTalk 2013

I am using SFTP 32 bit Adapter on BizTalk 2013 , I have provided proper credentials like user name and password, server name, port #......but the file is being not picked.
Iam dropping just 1 file at a time, but why doesn't it work ?
Please suggest
MBH

The Messaging Engine failed to add a receive location "corp.Integration.RP.SeTwoAxis_rcvPayad" with URL "sftp://dcla.sftp.xxxxcorp.com:22/users/mnopt_user/sereng/IN/*.txt" to the adapter "SFTP". Reason: "Microsoft.BizTalk.Adapter.SftpInvoker.SftpException:
List remote directory error.
   at Microsoft.BizTalk.Adapter.SftpInvoker.SftpInvoker.ListRemoteDirectory(String dirname)
   at Microsoft.BizTalk.Adapter.Sftp.SftpRLConfig.ValidateConfiguration(SftpReceivePropertyBag receivePropertyBag)
   at Microsoft.BizTalk.Adapter.Sftp.SftpRLConfig.CreateBinding(RHConfig rhConfig)
   at Microsoft.BizTalk.Adapter.Wcf.Runtime.BtsServiceHostBase.InitializeRuntime()
   at System.ServiceModel.ServiceHostBase.OnBeginOpen()
   at System.ServiceModel.ServiceHostBase.OnOpen(TimeSpan timeout)
   at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
   at Microsoft.BizTalk.Adapter.Wcf.Runtime.WcfReceiveEndpoint.Enable()
   at Microsoft.BizTalk.Adapter.Wcf.Runtime.WcfReceiveEndpoint..ctor(BizTalkEndpointContext endpointContext, IBTTransportProxy transportProxy, ControlledTermination control)
   at Microsoft.BizTalk.Adapter.Wcf.Runtime.WcfReceiver`2.AddReceiveEndpoint(String url, IPropertyBag adapterConfig, IPropertyBag bizTalkConfig)".
MBH

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()

BizTalk 2013 BAM Tools - BAM Alerts Configuration error in Multi Computer Env

Hi,
I am trying to install BizTalk Server in multi-computer environment.
I did install BizTalk Server on primary server smoothly.
On Sencodary Server, I am able to join existing SSO and BizTalk Group.
When I try to configure BAM Tools and BAM Alerts I get an error in BizTalk Log -
2014-02-06 11:12:39:6987 [Info] BAMTools Source:
2014-02-06 11:12:39:6987 [Info] BAMTools System.ServiceProcess
2014-02-06 11:12:39:6987 [Info] BAMTools Error messages:
2014-02-06 11:12:39:6987 [Info] BAMTools
2014-02-06 11:12:39:6987 [Info] BAMTools Service BAMAlerts was not found on computer '.'.
2014-02-06 11:12:39:6997 [Info] BAMTools The specified service does not exist as an installed service
2014-02-06 11:12:39:6997 [Info] BAMTools
2014-02-06 11:12:39:6997 [Info] BAMTools Call stack:
2014-02-06 11:12:39:6997 [Info] BAMTools
2014-02-06 11:12:39:6997 [Info] BAMTools at System.ServiceProcess.ServiceController.GenerateNames()
2014-02-06 11:12:39:6997 [Info] BAMTools at System.ServiceProcess.ServiceController.get_ServiceName()
2014-02-06 11:12:39:6997 [Info] BAMTools at System.ServiceProcess.ServiceController.GenerateStatus()
2014-02-06 11:12:39:6997 [Info] BAMTools at System.ServiceProcess.ServiceController.get_Status()
2014-02-06 11:12:39:6997 [Info] BAMTools at Microsoft.BizTalk.Bam.Management.AlertHostHelper.StopService()
2014-02-06 11:12:39:6997 [Info] BAMTools <BizTalk2009>
02/06/2014 11:12:38 1
Microsoft.BizTalk.Bam.Management.AlertModule2012
UpdateConfig Error
Exception thrown
2014-02-06 11:12:39:6997 [Info] BAMTools Source:
2014-02-06 11:12:39:6997 [Info] BAMTools System.ServiceProcess
2014-02-06 11:12:39:6997 [Info] BAMTools Error messages:
2014-02-06 11:12:39:6997 [Info] BAMTools
2014-02-06 11:12:39:6997 [Info] BAMTools Service BAMAlerts was not found on computer '.'.
2014-02-06 11:12:39:6997 [Info] BAMTools The specified service does not exist as an installed service
2014-02-06 11:12:39:6997 [Info] BAMTools
2014-02-06 11:12:39:6997 [Info] BAMTools Call stack:
2014-02-06 11:12:39:6997 [Info] BAMTools
2014-02-06 11:12:39:6997 [Info] BAMTools at System.ServiceProcess.ServiceController.GenerateNames()
2014-02-06 11:12:39:6997 [Info] BAMTools at System.ServiceProcess.ServiceController.get_ServiceName()
2014-02-06 11:12:39:6997 [Info] BAMTools at System.ServiceProcess.ServiceController.GenerateStatus()
2014-02-06 11:12:39:6997 [Info] BAMTools at System.ServiceProcess.ServiceController.get_Status()
2014-02-06 11:12:39:6997 [Info] BAMTools at Microsoft.BizTalk.Bam.Management.AlertHostHelper.StopService()
2014-02-06 11:12:39:6997 [Info] BAMTools at Microsoft.BizTalk.Bam.Management.AlertModule2012.UpdateConfig(BamConfigurationManager originalConfig, BamConfigurationManager bamConfig)
2014-02-06 11:12:39:6997 [Info] BAMTools <BizTalk2009>
02/06/2014 11:12:38 1
Microsoft.BizTalk.Bam.Management.AlertModule2012
UpdateConfig Exit
2014-02-06 11:12:39:6997 [Info] BAMTools <BizTalk2009>
02/06/2014 11:12:38 1
Microsoft.BizTalk.Bam.Management.BamManagementUtility.BamManagementUtility
Main Error
Exception thrown
2014-02-06 11:12:39:6997 [Info] BAMTools Source:
2014-02-06 11:12:39:6997 [Info] BAMTools System.ServiceProcess
2014-02-06 11:12:39:6997 [Info] BAMTools Error messages:
2014-02-06 11:12:39:6997 [Info] BAMTools
2014-02-06 11:12:39:6997 [Info] BAMTools Service BAMAlerts was not found on computer '.'.
2014-02-06 11:12:39:6997 [Info] BAMTools The specified service does not exist as an installed service
2014-02-06 11:12:39:6997 [Info] BAMTools
2014-02-06 11:12:39:6997 [Info] BAMTools Call stack:
2014-02-06 11:12:39:6997 [Info] BAMTools
2014-02-06 11:12:39:6997 [Info] BAMTools at System.ServiceProcess.ServiceController.GenerateNames()
2014-02-06 11:12:39:6997 [Info] BAMTools at System.ServiceProcess.ServiceController.get_ServiceName()
2014-02-06 11:12:39:6997 [Info] BAMTools at System.ServiceProcess.ServiceController.GenerateStatus()
2014-02-06 11:12:39:6997 [Info] BAMTools at System.ServiceProcess.ServiceController.get_Status()
2014-02-06 11:12:39:6997 [Info] BAMTools at Microsoft.BizTalk.Bam.Management.AlertHostHelper.StopService()
2014-02-06 11:12:39:6997 [Info] BAMTools at Microsoft.BizTalk.Bam.Management.AlertModule2012.UpdateConfig(BamConfigurationManager originalConfig, BamConfigurationManager bamConfig)
2014-02-06 11:12:39:6997 [Info] BAMTools at Microsoft.BizTalk.Bam.Management.AlertModule.UpdateConfig()
2014-02-06 11:12:39:6997 [Info] BAMTools at Microsoft.BizTalk.Bam.Management.BamManager.UpdateConfigurationXml()
2014-02-06 11:12:39:6997 [Info] BAMTools at Microsoft.BizTalk.Bam.Management.BamManagementUtility.BamManagementUtility.HandleUpdateConfig()
2014-02-06 11:12:39:6997 [Info] BAMTools at Microsoft.BizTalk.Bam.Management.BamManagementUtility.BamManagementUtility.DispatchCommand()
2014-02-06 11:12:39:6997 [Info] BAMTools at Microsoft.BizTalk.Bam.Management.BamManagementUtility.BamManagementUtility.Run()
2014-02-06 11:12:39:6997 [Info] BAMTools at Microsoft.BizTalk.Bam.Management.BamManagementUtility.BamManagementUtility.Main(String[] args)
2014-02-06 11:12:39:6997 [Info] BAMTools <BizTalk2009>
02/06/2014 11:12:38 1
Microsoft.BizTalk.Bam.Management.BamManagementUtility.BamManagementUtility
Main Exit
2014-02-06 11:12:39:6997 [Info] BAMTools Finished logging tracing of bm.exe execution.
2014-02-06 11:12:39:6997 [Info] BAMTools Deleting File: C:\Users\!gtqk\AppData\Local\Temp\2\6fc65525-7a2d-4c82-aa3a-e776e4e58291-BamManagerTrace.log
2014-02-06 11:12:39:7007 [Info] BAMTools Deleting File: E:\Program Files (x86)\Microsoft BizTalk Server 2013\Tracking\bm.exe.config
2014-02-06 11:12:39:7007 [Error] BAMTools Error configuring
Error executing bm.exe with tracing enabled. (Microsoft.BizTalk.Bam.CfgExtHelper.Utility)
Error executing process: E:\Program Files (x86)\Microsoft BizTalk Server 2013\Tracking\bm.exe (Microsoft.BizTalk.Bam.CfgExtHelper.Utility)
Microsoft (R) Business Activity Monitoring Utility Version 3.10.229.0
Copyright (C) Microsoft Corporation. All rights reserved.
I have made the required changes on the SQL Server - MSTDC, Named Pipes Enabled.
BizTalk Server 1 and BizTalk Server 2 both have required MSDTC settings. Along with this Firewall settings are also modified.
I have followed this link - http://social.technet.microsoft.com/wiki/contents/articles/1888.install-and-configure-bam-business-activity-monitoring-in-a-multi-computer-environment.aspx
which is for BizTalk Server 2010 (provided for BizTalk Server 2013 ?).
Kindly, let me knoe if anyone had similar issue and it has been resolved , or any other pointers
With Regards,
Gopal Talreja

I faced similar problem while installing BAMAlerts on 2nd BizTalk 2013 R2 server in a group. The reason for this error is the Wizard is unable to create the windows service (BAMAlerts) during the configuration. To fix the issue you need to create the service
manually. I had to perform following actions:
1.CREATE SERVICE:
Start command prompt as administrator on the node with problems. Execute (do not use copy paste from email, it often gives error):
sc create BAMAlerts binPath= "C:\Program Files (x86)\Microsoft BizTalk Server 2013\Tracking\BAMAlerts.exe”
2. SET USERNAME and PASSWORD on this Service:
Open services admin console, and change the user and password for the BAMAlerts Service.
- Start the service.
Start again the configuration for the BAM on the node with problems and complete the BAMTools and BAMAlerts configration (do not enter any username and password in the BAMAlerts configuration wizard).
3. RUN SQL Statement:
After starting the Service, BAMAlerts service may stop with following error in the event log:
Microsoft.BizTalk.Bam.Management.BamManagerException: Encountered error while executing command on SQL Server "A-CLS01VISQL1". --->
System.Data.SqlClient.SqlException: The EXECUTE permission was denied on the object 'bam_Metadata_GetProperty', database 'BAMPrimaryImport', schema 'dbo'.
To solve this, run following SQL statement
USE BAMPrimaryImport
GRANT
EXECUTE
ON
bam_Metadata_GetProperty
TO
BAM_ManagementNSReader;
GO
This should solve the problem.
Thanks to Microsoft support engineer for help.
Strange bug and I hope MS will solve this issue in next patch/CU/update

Unable to Connect to DB Server Error while configuring UDDI 3.0 in BizTalk 2013

Hi Team ,
While configuring BizTalk UDDI 3.0 , i am getting an error "unable to connect to DB Server. " In BizTalk 2009 , hotfix was available , but could not find any for BizTalk 2013
DB Server : SQL Server 2012 64 bit
Please help me to fix this
Abhijith

Got the solution
We need to proceed in such a way that DB component alone need to be installed in DB Server. Rest in BizTalk Application Servers
FYI
http://tjthompson5150.blogspot.in/2010/04/esb-toolkit-20-multi-server.html
Abhijith

BizTalk 2013 - Receiving XML file suspended due to Hexadecimal 0X01 (en dash/tiny black box) issue

Hello,
Our BizTalk process consist of 2 schemas, a map to transform schema1 to schema2, and an orchestration. When the BizTalk process "Receive Port" receives an xml file (with policy data information), BizTalk will suspend the xml file
and it will never get pass the Receive Port to be transformed because some of the policy data will include an "en dash" a hexadecimal 0X01 (looks like a tiny black box when opened in TextPad), how can we configure the receive port
and or schema1 in BizTalk to ignore/or replace/remove the "en dash" a hexadecimal 0X01 (looks like a tiny black box)?
Thank you for your help in advance!
Thank you for your help! M_Blanc

Yes, BizTalk has a solution for that. If you know the encoding and BOM then in the XML Receive/FFDASM or in a custom component you can specify the encoding for BizTalk to process the message.
Refer https://msdn.microsoft.com/en-us/library/aa559602.aspx to understand how the character encoding works in the pipeline and
https://msdn.microsoft.com/en-us/library/aa577393.aspx on how the XML Dissembler component can be configured in your own custom pipeline to address issues pertaining to charset encoding and
BOM.
Regards.

Connect BizTalk Server Configuration with Sql Azure - version 2013 R2

Hi,
My data resides on Sql Azure. I need to create BizTalkRuleEngineDb on Sql Azure using Microsoft BizTalk Server Configuration wizard. Subsequently manage rules from Business Rule Composer.
I am unable to connect to Sql Azure from BizTalk Server Configuration application. Without this i could not create BizTalkRuleEngineDb on Sql Azure. I gave the following details:
Database server name: <servername>.database.windows.net,1433
User name: <username>
Password: <pwd>
When i click configure button, a message pops "The database server you specified cannot be reached...."
All i need from BizTalk is to create Business Rules Engine DB on Sql Azure. Then I would like to manage rules using Business
Rule Composer connecting to Sql Azure BizTalkRuleEngineDb.<o:p></o:p>
My business logic will programmatically access BizTalkRuleEngineDb db and execute rules using Microsoft.RuleEngine.dll<o:p></o:p>
Is this a feasible solution? I would like to see your inputs.
Any help is appreciated.
Thanks,
Tushar

First I would suggest you to perform sanity check to confirm if SQL server connectivity is perfect.
1) Verify the MSDTC Settings on both the servers:- It should resemble as below.
2) UDL Test:- Create a new "Text Document"(new notepad file) rename it to ABC.udl, double click and give the SQL server details and Test connection. If this fails it means BizTalk is not at all able to connect with SQL and in this
case BizTalk Application is just a victim of Network connectivity issue.
You can also refer the below article-
Resolving the issues you may face during BizTalk Runtime Configuration
Thanks,
Prashant
Please mark this post accordingly if it answers your query or is helpful.

How To convert BizTalk 2009 Web Services(Receive Locations) to 2013 WebServices ??

Hi ,
We are actually going to migrate from BizTalk 2009 to BizTalk 2013 . As a part of this i want to convert all current BizTalk Artifacts to get compatibly with BizTalk 2013. I was able to convert schemas , maps , Orchestration etc to .net 4.5 directly
via Visual Studio 2012 Conversion Wizard. But for BizTalk Rcv Location WebServices (.asmx and .svc) , i was not able to do the same. Could anyone give some insight on how to migrate the Rcv Location during the migration from BizTalk 2009 to BizTalk 2013.
Abhijith

well i guess you need not to re expose the schema, i am not pretty sure though. Because your code relies on .net 2.0 and you are moving it to higher version 4.5, it should work.
So only changes in apppool settings and if required, changes on web.config file for runtime version property will do.
well i am not pretty sure though, just try and trouble shoot it.
Please mark the post as answer if this answers your question. If this post is helpful, please vote as helpful by clicking the upward arrow mark next to my reply.

BizTalk 2013 SFTP adapter not polling

Hi,
I am trying to poll some files from an SFTP location. I have configured my SFTP Receive Location on the BizTalk Server 2013. However I do not see any polling happening.
I have a BizTalk Server 2006 R2 environment from where I have configured the polling from the same location (this is ofcourse stopped when using the BizTalk 2013). From here, the polling is happening fine (bLogical sftp adapter).
Can you please let me know if I am missing any other steps apart from the RL configuration.
Regards,
Ujjwal
-Ujjwal

Though you have been using SFTP process with your BizTalk 2006 environment, your new BizTalk server may have new IP and new configurations. So ensure the SFTP server where
you’re trying to receive the files from allow this new server.
First try to use any SFTP client tools like
FileZilla or
WinSCP and see whether you can connect to your SFTP server. This would help you to solve some of the access issues.
Ensure your IP (external IP) is not blocked by your SFTP server. If any firewall is involved between, check this firewall is not blocking the access.
Also ensure that values you give while configuring the Security section of the Receive Location is correct. Most of the issues around the SFTP adapter trying to receive the
files are Firewall issue, Security properties configuration.
Also check
this SFTP adapter article from TechNet Wiki for more help..
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.

MQ Series adapter error in BizTalk 2013

Hi All,
I stuck in the process of migrating one application from biztalk 2006 to bizTalk 2013 .
I need to enable a MQ series receive location but while configuration I am getting below error .
retrieving the com class factory for remote computer with CLSID from machine failed due to following error -80070005
Can anyone has a solution for this .
Thanks
Abhishek

Few things I would consider when installing MQSC:
Ensure you have correct version of client installed on your server.
With MQSC adapter in the past, there is always a issue with the registry entry - HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Wow6432Node\CLSID key. I have not tried it with BizTalk 2013. But its worth check whether the registry entries has been created properly.
Check this MSDN blog in this context:
http://blogs.msdn.com/b/biztalkcpr/archive/2011/06/28/mqsc-options-may-not-be-available-in-biztalk-administration-console.aspx
Also ensure the host instance you're using for the port is 64 bit, not 32-bit (which is the default host setting when you create a host).
If these options doesn't help, check the blogpost where the author has similar error as yours:
BizTalk MQSeries Adapter COM+ Error 80004005
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.

WCF-Custom Biztalk 2013 - Access to SQL Server 2014 Database

Hi,
i don't see nowhere of capability from the Biztalk adapter to access differente version of Sql server.
I want to send ou receive information with a WCF-Custom from SQL Server 2014, i'm in Biztalk 2013 (not R2 ) it's possible ?
Do you have a link or a list of version autorized to accessed by the wcf-custom Sql binging ?
Thanks a lot

Hi, I can suppose that the main problem for Joao is not if it works in general or not.
The real problem is that he is not sure if this configuration is officially supported by Microsoft.
If you are developing an integration project for a client you need to have this guarantee. If not, you can have an unsupported scenario, and if something fails you could have a big problem with your client.
If I were you, I would talk with the client account manager about this.
Regards.

Issues connecting BizTalk 2013 WCF to Microsoft CRM 2011 using ADFS

I have a Microsoft CRM 2011 instance I'm trying to connect to from BizTalk 2013 using WCF. The CRM instance is using ADFS based security
and basic "domain/user" "password" security. The OrganizationService has the following policy in the WSDL.
<wsp:Policy wsu:Id="CustomBinding_IOrganizationService_policy">
<wsp:ExactlyOne>
<wsp:All>
<ms-xrm:AuthenticationPolicy xmlns:ms-xrm="http://schemas.microsoft.com/xrm/2011/Contracts/Services">
<ms-xrm:Authentication>Federation</ms-xrm:Authentication>
<ms-xrm:SecureTokenService>
<ms-xrm:Identifier>http://example.com/adfs/services/trust</ms-xrm:Identifier>
</ms-xrm:SecureTokenService>
</ms-xrm:AuthenticationPolicy>
<sp:TransportBinding xmlns:sp="http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702">
<wsp:Policy>
<sp:TransportToken>
<wsp:Policy>
<sp:HttpsToken/>
</wsp:Policy>
</sp:TransportToken>
<sp:AlgorithmSuite>
<wsp:Policy>
<sp:Basic256/>
</wsp:Policy>
</sp:AlgorithmSuite>
<sp:Layout>
<wsp:Policy>
<sp:Strict/>
</wsp:Policy>
</sp:Layout>
<sp:IncludeTimestamp/>
</wsp:Policy>
</sp:TransportBinding>
<sp:EndorsingSupportingTokens xmlns:sp="http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702">
<wsp:Policy>
<sp:IssuedToken sp:IncludeToken="http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702/IncludeToken/AlwaysToRecipient">
<Issuer xmlns="http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702">
<Address xmlns="http://www.w3.org/2005/08/addressing">http://www.w3.org/2005/08/addressing/anonymous</Address>
<Metadata xmlns="http://www.w3.org/2005/08/addressing">
<Metadata xmlns="http://schemas.xmlsoap.org/ws/2004/09/mex" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<wsx:MetadataSection xmlns="">
<wsx:MetadataReference>
<Address xmlns="http://www.w3.org/2005/08/addressing">
https://example.com/adfs/services/trust/mex
</Address>
</wsx:MetadataReference>
</wsx:MetadataSection>
</Metadata>
</Metadata>
</Issuer>
<sp:RequestSecurityTokenTemplate>
<trust:KeyType xmlns:trust="http://docs.oasis-open.org/ws-sx/ws-trust/200512">
http://docs.oasis-open.org/ws-sx/ws-trust/200512/SymmetricKey
</trust:KeyType>
<trust:KeySize xmlns:trust="http://docs.oasis-open.org/ws-sx/ws-trust/200512">256</trust:KeySize>
<trust:Claims xmlns:trust="http://docs.oasis-open.org/ws-sx/ws-trust/200512" Dialect="http://schemas.xmlsoap.org/ws/2005/05/identity">
<wsid:ClaimType xmlns:wsid="http://schemas.xmlsoap.org/ws/2005/05/identity" Uri="http://schemas.xmlsoap.org/ws/2005/05/identity/claims/upn"/>
</trust:Claims>
<trust:KeyWrapAlgorithm xmlns:trust="http://docs.oasis-open.org/ws-sx/ws-trust/200512">http://www.w3.org/2001/04/xmlenc#rsa-oaep-mgf1p</trust:KeyWrapAlgorithm>
<trust:EncryptWith xmlns:trust="http://docs.oasis-open.org/ws-sx/ws-trust/200512">http://www.w3.org/2001/04/xmlenc#aes256-cbc</trust:EncryptWith>
<trust:SignWith xmlns:trust="http://docs.oasis-open.org/ws-sx/ws-trust/200512">http://www.w3.org/2000/09/xmldsig#hmac-sha1</trust:SignWith>
<trust:CanonicalizationAlgorithm xmlns:trust="http://docs.oasis-open.org/ws-sx/ws-trust/200512">http://www.w3.org/2001/10/xml-exc-c14n#</trust:CanonicalizationAlgorithm>
<trust:EncryptionAlgorithm xmlns:trust="http://docs.oasis-open.org/ws-sx/ws-trust/200512">http://www.w3.org/2001/04/xmlenc#aes256-cbc</trust:EncryptionAlgorithm>
</sp:RequestSecurityTokenTemplate>
<wsp:Policy>
<sp:RequireInternalReference/>
</wsp:Policy>
</sp:IssuedToken>
</wsp:Policy>
</sp:EndorsingSupportingTokens>
</wsp:All>
</wsp:ExactlyOne>
</wsp:Policy>
I've set up the following client configuration:
<binding name="ws2007FederationHttpBinding">
<security mode="TransportWithMessageCredential">
<message>
<issuer address="https://adfs20.example.com/adfs/services/trust/2005/usernamemixed"
binding="wsHttpBinding"
bindingConfiguration="stsBinding" />
<issuerMetadata address="https://adfs20.example.com/adfs/services/trust/mex" />
</message>
</security>
</binding
And referencing this for adfs specific communication
<wsHttpBinding>
<clear />
<binding name="stsBinding">
<security mode="TransportWithMessageCredential">
<transport clientCredentialType="None"/>
<message clientCredentialType="UserName" establishSecurityContext="false"/>
</security>
</binding>
</wsHttpBinding>
As I try using it I get the receive the following error message
A message sent to adapter "WCF-Custom" on send port "SendPort6" with URI "https://crm-test.example.com/XRMServices/2011/Organization.svc" is suspended.
Error details: System.ServiceModel.FaultException: MSIS3127: The specified request failed.
Server stack trace:
at System.ServiceModel.Security.IssuanceTokenProviderBase`1.DoNegotiation(TimeSpan timeout)
at System.ServiceModel.Security.IssuanceTokenProviderBase`1.GetTokenCore(TimeSpan timeout)
at System.IdentityModel.Selectors.SecurityTokenProvider.GetToken(TimeSpan timeout)
at System.ServiceModel.Security.Tokens.IssuedSecurityTokenProvider.GetTokenCore(TimeSpan timeout)
at System.IdentityModel.Selectors.SecurityTokenProvider.GetToken(TimeSpan timeout)
at System.ServiceModel.Security.SecurityProtocol.TryGetSupportingTokens(SecurityProtocolFactory factory, EndpointAddress target, Uri via, Message message, TimeSpan timeout, Boolean isBlockingCall, IList`1& supportingTokens)
at System.ServiceModel.Security.TransportSecurityProtocol.SecureOutgoingMessageAtInitiator(Message& message, String actor, TimeSpan timeout)
at System.ServiceModel.Security.TransportSecurityProtocol.SecureOutgoingMessage(Message& message, TimeSpan timeout)
at System.ServiceModel.Security.SecurityProtocol.SecureOutgoingMessage(Message& message, TimeSpan timeout, SecurityProtocolCorrelationState correlationState)
at System.ServiceModel.Channels.SecurityChannelFactory`1.SecurityRequestChannel.Request(Message message, TimeSpan timeout)
at System.ServiceModel.Security.SecuritySessionSecurityTokenProvider.DoOperation(SecuritySessionOperation operation, EndpointAddress target, Uri via, SecurityToken currentToken, TimeSpan timeout)
at System.ServiceModel.Security.SecuritySessionSecurityTokenProvider.GetTokenCore(TimeSpan timeout)
at System.IdentityModel.Selectors.SecurityTokenProvider.GetToken(TimeSpan timeout)
at System.ServiceModel.Security.SecuritySessionClientSettings`1.ClientSecuritySessionChannel.OnOpen(TimeSpan timeout)
at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
at System.ServiceModel.Channels.ServiceChannel.OnOpen(TimeSpan timeout)
at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
at System.ServiceModel.Channels.CommunicationObject.Open()
Exception rethrown at [0]:
at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
at System.ServiceModel.ICommunicationObject.Open()
at Microsoft.BizTalk.Adapter.Wcf.Runtime.WcfClient`2.GetChannel[TChannel](IBaseMessage bizTalkMessage, ChannelFactory`1& cachedFactory)
at Microsoft.BizTalk.Adapter.Wcf.Runtime.WcfClient`2.SendMessage(IBaseMessage bizTalkMessage)
MessageId: {0A8D8BB1-0838-43AF-B3A1-D63D432C22AA}
InstanceID: {B57B4979-2187-4CF7-8115-4D65B3952982}
What am I missing ..?
http://www.richardhallgren.com

Hi Angie and Richard
Currently I am also having the similar issue and I tried the settings you mentioned. But I get his error
The adapter failed to transmit message going to send port "WcfSendPort_OrganizationService_CustomBinding_IOrganizationService" with URL "https://examplecrm.com/XRMServices/2011/Organization.svc".
It will be retransmitted after the retry interval specified for this Send Port. Details:"System.ServiceModel.FaultException: The message with Action 'http://docs.oasis-open.org/ws-sx/ws-trust/200512/RST/Issue' cannot be processed at the receiver, due
to a ContractFilter mismatch at the EndpointDispatcher. This may be because of either a contract mismatch (mismatched Actions between sender and receiver) or a binding/security mismatch between the sender and the receiver. Check that sender and receiver
have the same contract and the same binding (including security requirements, e.g. Message, Transport, None).
By any chance did you go through this error or do you have any suggestions?I am trying to connect from WCF-Custom adapter on BizTalk 2010 to CRM 2013 using ADFS.
Thanks
Narri

Biztalk 2013 configuring to receive a 999

Similar Messages

Maybe you are looking for