Biztalk 2013 Eventlog.WriteEntry

On Biztalk 2006R2 (windows server 2003R2), I never had problem writing to eventlog from my Biztalk orchestration.
But on BizTalk 2013 (Windows server 2008R2), whenever My Biztalk application tries to write to eventlog, I see the following error:
Inner exception: The source was not found, but some or all event logs could not be searched. Inaccessible logs: Security.
Exception type: SecurityException
Source: System
I followed the instructions in the following link and was able to resolve the issue.
http://www.codeproject.com/Articles/271578/BizTalk-Event-Log-error-The-source-was-not-found-b
But I am not sure if it is the right way of fixing the problem. Anyone faced similar problems with Biztalk 2013? Any inputs on the cause and the resolution of the problem?? Greatly
appreciate any insgiht or suggestions on it.

If the Source does not exist, an implicit attempt to create it will be made during the Write. If the logged on use does not have the ability to create Event Sources, this will fail as you see. As stated, this is a .Net thing and is in no way
BizTalk specific.
The BizTalk Host Instance Service Account should not have Administrative rights on the machine.
You have two options:
Write a program that creates the Event Source using EventLog.CreateEventSource():
http://msdn.microsoft.com/en-us/library/2awhba7a(v=vs.110).aspx
Use the eventcreate.exe utility:
http://support.microsoft.com/kb/324145/en-us
eventcreate is probably your best option here.

Similar Messages

Test/Verify Biztalk 2013/Windows 2008 R2 installation

Hi
I have experienced problems with MSDTC on a new two server development box (virtual server)
BizTalk 2013/MSSQL 2012 on Windows 2008 R2
MSDTC failed connection when receive locations was started
Seems to be fine now DTC tester is working ok
I'd like to check how the installation is doing on a more regurlar basis
Any ideas, some scheduled action, a service or something
Thanks /Peter

Peter,
You can consider few options:
Since you dont have any trace of MSDTC failure in your new installation, instead of looking for an trace, you can look for its reaction like suspend message and configure an alert to
be send to you (or to support team)
Normally any MSDTC related failures on a running instance would result in a eventlog entry, and again you can configure for an alert for this event log entry.
Another option is you can create a batch file to run the DTCPing tool and it can output an log file. Your automation script can interrogate or send the copy of the log file to you.
Also in MSDTC, you can enable tracing options, where you have options like “Trace Aborted Transaction” (In the same tab you can also choose the log file location). So you can create an
automated process to send you the log file (may be by email) when the log file is created or periodically.
As said, Messagebox view can be scheduled to run and it can capture the MSDTC failures. And this report can be emailed to you.
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.

Migrate biztalk 2006R2/SQL server 2005 projects to Biztalk 2013/SQL server 2012

We have Biztalk application projects deployed on Biztalk 2006R2/SQL server 2005 environment on a single server
Now we have installed and configured Biztalk 2013/SQL server 2012 in a multicomputer environment where Biztalk server is on one computer while SQL server is on the other.
Now it's time to migrate the projects 2006R2 to 2013.. Is it a smooth process? I found a lot of posts about migration from 2006R2 to Biztalk 2010... Just wondering if it is similar or more complex?? Appreciate any help/suggestions.. thanks!!

Hi Annee,
Following article should answer your question:
BizTalk Application Migration Guide
Also have a look at following forum post:
http://social.msdn.microsoft.com/Forums/en-US/f9ac6b6c-3dbe-487b-85c5-448d257d62f4/migration-from-biztalk-server-2006-to-2013?forum=biztalkgeneral
Maheshkumar S. Tiwari|http://tech-findings.blogspot.in/

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

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 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.

BizTalk 2013 SFTP Adapter Dynamic SFTP send port exception: Open remote file for write error

I am using BizTalk 2013 SFTP adapter. I defined a Dynamic One-Way
send port on BizTalk server administration.
Below is the error I'm getting on BizTalk while trying to write files to a designated folder on a client's SFTP server.
When defining the same path and properties on a Static One-Way send port everything works properly and the files are being saved on the SFTP server.
A message sent to adapter "SFTP" on send port "ComverseSFTP_1.0.0.0_ComverseSFTP.SendFileToSFTP_SendFileToSFTPServer_f6b86b86a22079f8" with URI "SFTP://abc.xyz.com:22/upload/%SourceFileName%"
is suspended.
Error details: Microsoft.BizTalk.Adapter.SftpInvoker.SftpException: Open remote file for write error.
Server stack trace:
   at Microsoft.BizTalk.Adapter.SftpInvoker.SftpInvoker.OpenRemoteFileWrite(String fileName, Int32 fileOffset)
   at Microsoft.BizTalk.Adapter.SftpInvoker.SftpFileWriterStream.Write(Byte[] buffer, Int32 offset, Int32 count)
   at Microsoft.BizTalk.Adapter.Sftp.SftpOutputChannel.Send(Message message, TimeSpan timeOut)
   at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Object[]& outArgs)
   at System.Runtime.Remoting.Messaging.StackBuilderSink.AsyncProcessMessage(IMessage msg, IMessageSink replySink)
Exception rethrown at [0]:
   at System.Runtime.AsyncResult.End[TAsyncResult](IAsyncResult result)
   at System.ServiceModel.Channels.ServiceChannel.SendAsyncResult.End(SendAsyncResult result)
   at System.ServiceModel.Channels.ServiceChannel.EndCall(String action, Object[] outs, IAsyncResult result)
Exception rethrown at [1]:
   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.Channels.IOutputChannel.EndSend(IAsyncResult result)
   at Microsoft.BizTalk.Adapter.Wcf.Runtime.WcfClient`2.SendCallback(IAsyncResult result)
MessageId: {926F44F2-9180-4B33-96FF-9E4CBC459382}
InstanceID: {36A50A7F-63C4-48D9-903D-A33C85DDAE36}
Can you please assist with explaining why are we getting this exception?
Thank you for your help.

Below is the error I'm getting on BizTalk while trying to write files to a designated folder on a client's SFTP server.
When defining the same path and properties on a Static One-Way send port everything works properly and the files are being saved on the SFTP server.
A message sent to adapter "SFTP" on send port "ComverseSFTP_1.0.0.0_ComverseSFTP.SendFileToSFTP_SendFileToSFTPServer_f6b86b86a22079f8" with URI "SFTP://abc.xyz.com:22/upload/%SourceFileName%"
is suspended.
Error details: Microsoft.BizTalk.Adapter.SftpInvoker.SftpException: Open remote file for write error.
Hi Yaeli1,
From the error message above, please check the permission for file writing , it seems that this issue is related to access permission.
Best regards,
Angie
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.

Error handling HTTP 400 in WCF-WebHttp adapter BizTalk 2013

Hi!
Does anyone knows how to catch HTTP errors when using WCF-WebHttp REST adapter in BizTalk 2013? I've looked into the article BizTalk
Server: REST Services Error Handling, but that is for BizTalk 2010 using the WCF-Custom adapter.
What I want is to catch the exception in an orchestration, and do some actions dependent on which HTTP error it is, i.e. HTTP 400.
Idar H.

Hi Idar,
Welcome to BizTalk forum.
From your description above, I don't have exact same scenario like yours, this scenario exposes a BizTalk Orchestration as a RESTful webservice using WCF-WebHttp, perhaps it will be good reference for you. See:
http://blog.tallan.com/2014/09/29/wcf-webhttp-and-custom-json-error-messages/
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.

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.

Biztalk 2013 WCF-WebHTTP Adapter - Outbound HTTP Headers

Hi
I have a requirement to connect to a service using the WCF-WebHTTP adapter that requires authentication to be passed in the Headers.
A usercode and password is sent in the intial header and a security token is returned in the response header.
This security token is then used in the header of each subsequent call to the service.
I could not find anything in the documentation about getting and setting the "HTTP Header" data using maps or variables or using variables in the "Outbound HTTP Headers" on the adapter transport properties.
Any help on this would be gratefully received.
Malcolm

You can set the outbound HTTP header in WCF-WebHTTP adapter by 2 ways
1) At adapter level Change adapter properties
2)Changing Message context property at Orchestration or at pipeline
Its been well documented here
http://blog.codit.eu/post/2013/04/30/Using-HttpHeaders-with-WCF-WebHttp-Adapter-on-Biztalk-2013.aspx
Thanks
Abhishek

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

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

Upgrade BizTalk 2013 Standard Edition to Enterprise edition

Hi All,
I wanted to upgrade from BizTalk 2013 Standard Edition to BizTalk 2013 Enterprise edition. Could you please let me know the steps that I need to follow or the point me to any related documentation.
Thanks and Regards,
Ujjwal
-Ujjwal

Back-up of databases
BizTalk application.
Backup the binding, parties, policies, vocabularies.
BTSNTSVC.config file.
Backup the Enterprise Single Sign-On secret
This would help you if in case of any rollback
When run the installation package for
Enterprise edition, the install will detect
the exiting version and guide you to upgrade. The install will also ensure the
installed BizTalk application is not be affected.
Use the back-ups if anything goes wrong.
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.

BizTalk 2013 - BAMAlerts service crash

Hi,
I am deploying BizTalk into a new clean Production environment. My topology is the following:
- 2 SQL Server machines (clustered)
- 2 BizTalk application servers (with BTS runtime)
- 1 BAM server
I have everything deployed and working well except for the BAMAlerts service crashing a minute after it starts on the BAM server.
The software installed on the BAM server is:
Windows 2008 R2 x64
SQL Server 2012 SP1 x64 with the following features:
Reporting Services (Native)
SQL Server Data Tools
Client Tools Connectivity
Integration Services
Management Tools – Basic
Management Tools – Complete
SQL Server 2012 SP1 Cumulative Update 9
BizTalk Server 2013 x64 with the following features:
Portal Components
Business Activity Monitoring
Administrative Tools and Monitoring
Additional Software
Enterprise Single Sign-On Administration Module
Enterprise Single Sign-On Master Secret Server
BAM Alert Provider for SQL Notification Services
BAM Client
BAM-Eventing
Office Excel 2013 (x86)
Once the BizTalk binaries are installed I installed Windows Update suggested patches including the update for BizTalk Server 2013 (KB2830546).
I then went on and configured the relevant features. Configuration worked well but the BAMAlerts service crashes 1 minute after starting with the following error:
Microsoft.BizTalk.Bam.Management.BamManagerException: Encountered error while executing command on SQL Server "". ---> System.Data.SqlClient.SqlException: A network-related or instance-specific error occurred while establishing a connection
to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
I verified the following:
A database mail profile was created on the SQL Server instance and it works (I can use it to send emails)
Using the BAMAlerts service account I am able to connect to the SQL Server instance using Named Pipes or TCP/IP, call BizTalkMgmtDb.dbo.adm_Group_GetBAMServerAndDBName or query tables
I installed SQL Server 2005 Notification Services x64 in order to see if it helps but no success.
I installed BizTalk 2013 Cumulative Update 2 but it did no help either.
The worse part is that I hit the same issue when setting up our UAT environment, tried a number of things and ended up with a setup that works but I am not able to reproduce that success in Prod...
Following is the full error message:
Microsoft.BizTalk.Bam.Management.BamManagerException: Encountered error while executing command on SQL Server "". ---> System.Data.SqlClient.SqlException:
A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider:
Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
at System.Data.SqlClient.TdsParser.Connect(ServerInfo serverInfo, SqlInternalConnectionTds connHandler, Boolean ignoreSniOpenTimeout, Int64 timerExpire, Boolean encrypt, Boolean trustServerCert, Boolean integratedSecurity, SqlConnection owningObject)
at System.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo, String newPassword, Boolean ignoreSniOpenTimeout, Int64 timerExpire, SqlConnection owningObject)
at System.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(String host, String newPassword, Boolean redirectedUserInstance, SqlConnection owningObject, SqlConnectionString connectionOptions, Int64 timerStart)
at System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance)
at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance)
at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection)
at System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnection owningConnection, DbConnectionPool pool, DbConnectionOptions options)
at System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject)
at System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject)
at System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject)
at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection)
at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory)
at System.Data.SqlClient.SqlConnection.Open()
at Microsoft.BizTalk.Bam.Management.SqlHelper.ExecuteQuery(String cmdText, CommandType cmdType, Transaction transaction)
--- End of inner exception stack trace ---
at Microsoft.BizTalk.Bam.Management.SqlHelper.ExecuteQuery(String cmdText, CommandType cmdType, Transaction transaction)
at Microsoft.BizTalk.Bam.AlertHost.AlertHost.Run()
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.ThreadHelper.ThreadStart()
Thanks
Emmanuel

Known issue, you need BizTalk Server 2013 CU1:
http://support.microsoft.com/kb/2838133/en-us
(See hotfix 2832137)
Morten la Cour

Biztalk 2013 Eventlog.WriteEntry

Similar Messages

Maybe you are looking for