Biztalk 2009 application to Biztalk 2013 application

Hi all,
I have a Biztalk 2009 application that I moved to Biztalk 2013. It only consist of send port (wcf custom adapter), receive port, receive location (file adapter) and a party agreement.
The issue that I have is processing the file to sql server using WCF custom adapter. Does the store procedure has to be different in Biztalk 2013 in order to process files? or can it be the same as configured in Biztalk 2009?
Christiane

Hi,
Test also your Maps because in a BizTalk 2013 map a method must return something when it is invoked and can not return null.
“Extension functions cannot return null values.” Exception when running a map in BizTalk 2013
http://www.ithero.nl/post/2013/06/19/Extension-functions-cannot-return-null-values-Exception-when-running-a-map-in-BizTalk-2013.aspx
Kind regards,
Tomasso Groenendijk
Blog
| Twitter
MCTS BizTalk Server 2006, 2010
If this answers your question please mark it accordingly

Similar Messages

Developing for BizTalk 2009 and BizTalk 2013 on the same box

I currently have Visual Studio 2008 installed and setup on my local machine for doing BizTalk 2009 development. We are migrating to BTS 2013 soon.
I also have Visual Studio 2013 installed (but no BizTalk 2013 components installed). Will I be able to develop for both versions of BizTalk on the same box?
Has anyone successfully done this?
My machine is Windows 7 Professional, 64 bit. And I have also installed BTS 2009, Developer edition as well.

Hi Chris,
I don't think BTS 2009 and BTS 2013 (or for that matter any two versions of BizTalk) can be installed on the same OS. MS SQL Server and Visual Studio cannot
distinguish which instance is started. Use Microsoft Virtual Server instead.
Rachit
Please mark as answer or vote as helpful if my reply does

Simple way to handle Exception in Biztalk 2013

Hello Experts,
I am working with lots of Orchestration in my Biztalk application, i am using Biztalk 2013.
Can some one tell me what is simple way to chandle exception.
I am having requirement to handle exception in 1 day....
Thanks,
Thanks and Regards, Nilesh Thakur.

First thing One day is not enough to implement exception handling framework across your your solution. :-)
But there are so many things you need to take care, like
what you want to do with the exception messages
Do you want to re-submit a message when it has failed in exception.
how would you plan to test all these exception cases, you need to prepare all your test cases before you procced for the changes.
anyways,
ESB Exception handling framework is the main candidate however you can use built-in throw exception shape in orchestration designer.
There is an example
A developers guide to handling exceptions in BizTalk Server 2006/2009/2010 , have a look, you will get your solution,
All the best.
Greetings,HTH
Naushad Alam
When you see answers and helpful posts, please click Vote As Helpful, Propose As Answer, and/or
Mark As Answer
alamnaushad.wordpress.com

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

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/

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.

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

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 SFTP Adapter Properties

Hello All,
In Biztalk 2010, some applications use the On Receive After property in the SSHFTP adapter to remove the file after receive. How can this be done in SFTP in the Biztalk 2013.Any help is greatly appreciated.
Thanks

Sorry I don't get your point. By default files would be deleted/removed once it’s been received/downloaded. The problem what I have seen is some issue when dealing
with read-only files. In future enhancement to this adapter we may except feature like “Delete After Download” and “Enable Timestamp comparison” properties as happened in FTP adapter.
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 to pick files from webdav

Hi Guys,
Can anyone let me know whether Biztalk 2013 will work with webdav to pick files? I am thinking to use webdav and host an endpoint in IIS to store the files created by different applications. The reason would be just to avoid sharing of windows file paths
and use a consistent authentication mechanism at the IIS level.
So if any application puts a file in to the webdav, Can we configure Biztalk to pick those files? If so, do we get same message context properties as FILE adapter?
Thanks
JB

Hi Janardhan,
Before I validate this approach of using WebDav as file share for BizTalk, let me just answer your question directly.
While configuring WebDav, you would create a file share for WebDAV and map this file
share to your virtual directory. And if you want to use WebDav as file share (for files created by different applications) then you can use BizTalk file adapter to access the files, so in this case since you have used the File adapter you will have file adapter
related context properties to the message published in to BizTalk message box db. You have to ensure, BizTalk host instance’s credentials uses by the file Receive location to pick the files from file share of WebDav has access to receive the files.
Following article can help you on creating file share in WebDav
MSDN
Blog:Setting up WebDAV on IIS using Windows Authentication and a UNC, mapped drive or file share
But instead of considering this option did you consider the following options through which you can still control the access at IIS level.:
BTSHTTPReceive.dll:
You can configure virtual directory with BTSHTTPReceive.dl in IIS.
Once IIS is configured for
BTSHTTPReceive.dl
BizTalk listens to this URL and, through the use of BTSHTTPReceive.dll and the HTTP receive adapter message posted to this URL is passed to the BizTalk MessageBox
Following article shall help to know details about this and how to configure it
http://tech.movie-stars.us/windows_server/biztalk-2010-recipes---adapters---configuring-http-receives.aspx
http://soa-thoughts.blogspot.co.uk/2011/07/using-btshttpreceive-in-x64-environment.html
http://www.biztalkbill.com/Home/tabid/40/EntryId/66/Configuring-BTSHTTPReceive-dll-to-work-on-IIS-7.aspx
Publish schema as WCF Service:
You can build a single schema that has a child node of type “any.” Then, you can use the “publish schemas as WCF service” option of the publishing wizards to create a general
purpose service which can be used to receive different types of message from different applications. Here different application/customer client call this WCF service upload their data document in the <Any> section of the schema, If you’re using
WCF receive locations, you can always strip out the wrapper node before publishing to the MessageBox.
For more options, read the following article:
Four Ways to Accept Any XML Data Into BizTalk Web
Services
I would certainly consider other option before using WebDav as file share for BizTalk to process the file.
The above methods are suggested since you want to control the access level at IIS, other obvious options are FTP..
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 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.

Deployement in biztalk 2013

Hi all,
I am migrating biztalk server 2010 to 2013.
Using visual studio conversion wizard i have converted all applications into 2012.
Can any one please help me out how to deploy the application in biztalk 2013 as i am new to it.
and what would be the best approach.please suggest in steps
Thanks
biztalk007

Now you got the source code migrated to Visual Studio 2012. Deployment of the BizTalk application hasn’t changed much from BizTalk 2006 onwards. Since BizTalk Server
2006 the product formalizes the notion of a BizTalk Application that allows working with these artifacts as a single unit. A BizTalk application wraps all of the pieces required for a solution into a single logical unit, making it the fundamental abstraction
for management and deployment.
Read the following article on BizTalk application deployment and best practices:
Deploy
BizTalk Applications using MSI files – Concept and Best practices
Also read this TechNet-Wiki’s excellent article on this topic:
Recommendations
for Installing, Sizing, Deploying, and Maintaining a BizTalk Server Solution
Also when you’re considering the best practices for deploying the BizTalk applications in BizTalk 2013, consider about the automating the deployment. There are various
tools available to achieve the deployment automation, but my favourite is Deployment Framework for BizTalk (BTDF). With the latest version supporting BizTalk 2013, it’s a great tool in your arsenal.
Deployment Framework for BizTalk (BTDF)
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 R2: SB-Messaging Windows Service Bus On Premise 1.1 (Not Windows Azure)

Let me preface this by saying that I have been able to connect to the destination Service Bus Topics and Queue using traditional .NET methods (e.g. System.ServiceBus.Messaging namespace) and the applications using those components are running fine on the
same local VM. This uses the connection string that is provided from GET-SBAuthorizationRule.
Development Environment:
Windows Server 2012
SQL Server 2014
BizTalk 2013 R2
Local VM that is not on the Domain (but can connect to computers on the network)
I am trying to create a simple BizTalk 2013 R2 Messaging Solution that will use the SB-Messaging adapter features with Windows Service Bus On-Premise. My solution is using a Static One-Way Send Port to send messages to an existing topic on with Windows
Service Bus 1.1 using the SB-Messaging Adapter. After using the programmatic approach, the configurations were not as intuitive, but I believe I am close to the resolution. I have tried several combinations of key data but I am still not able to
connect. This seems like I am missing something small that is causing the problem but I am at a loss for the moment. The error I receive is below:
A message sent to adapter "SB-Messaging" on send port "SBSendPort" with URI "sb://<SERVERNAME>/NsServiceBus/collateraltopic" is suspended.
Error details: System.UnauthorizedAccessException: The token provider was unable to provide a security token while accessing 'https://<SERVERNAME>:7355/WRAPv0.9/'. Token provider returned message: '<Error><Code>400</Code><Detail>Namespace cannot be resolved 'https://<SERVERNAME>:7355/WRAPv0.9/'.TrackingId:6bcd22e8-1741-41fc-a84c-9aa3f7146ab5_GUS2522512,TimeStamp:6/30/2014 8:35:35 PM</Detail></Error>'. ---> System.IdentityModel.Tokens.SecurityTokenException: The token provider was unable to provide a security token while accessing 'https://<SERVERNAME>:7355/WRAPv0.9/'. Token provider returned message: '<Error><Code>400</Code><Detail>Namespace cannot be resolved 'https://<SERVERNAME>:7355/WRAPv0.9/'.TrackingId:6bcd22e8-1741-41fc-a84c-9aa3f7146ab5_GUS2522512,TimeStamp:6/30/2014 8:35:35 PM</Detail></Error>'. ---> System.Net.WebException: The remote server returned an error: (400) Bad Request.
at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult)
at Microsoft.ServiceBus.TokenProviderHelper.TokenRequestAsyncResult.<GetAsyncSteps>b__8(TokenRequestAsyncResult thisPtr, IAsyncResult r)
at Microsoft.ServiceBus.Messaging.IteratorAsyncResult`1.EnumerateSteps(CurrentThreadType state)
--- End of inner exception stack trace ---
Server stack trace:
Exception rethrown at [0]:
at Microsoft.ServiceBus.Common.AsyncResult.End[TAsyncResult](IAsyncResult result)
at Microsoft.ServiceBus.TokenProviderUtility.GetMessagingToken(TokenProvider tokenProvider, Uri baseAddress, String appliesTo, String action, Boolean bypassCache, TimeSpan timeout)
--- End of inner exception stack trace ---
Server stack trace:
at Microsoft.ServiceBus.TokenProviderUtility.GetMessagingToken(TokenProvider tokenProvider, Uri baseAddress, String appliesTo, String action, Boolean bypassCache, TimeSpan timeout)
at Microsoft.ServiceBus.Messaging.Sbmp.SbmpMessageCreator.GetAuthorizationToken(String appliesTo, String action)
at Microsoft.ServiceBus.Messaging.Sbmp.SbmpMessageCreator.GetAuthorizationHeader(String action)
at Microsoft.ServiceBus.Messaging.Sbmp.SbmpMessageCreator.CreateWcfMessageInternal(String action, Object body, Boolean includeToken, String parentLinkId, RetryPolicy policy, TrackingContext trackingContext)
at Microsoft.ServiceBus.Messaging.Sbmp.SbmpMessageSender.GetOverheadSize()
at Microsoft.ServiceBus.Messaging.Sbmp.SbmpMessageSender..ctor(String path, SbmpMessagingFactory messagingFactory, SbmpMessageCreator messageCreator, RetryPolicy retryPolicy)
at Microsoft.ServiceBus.Messaging.Sbmp.CreateSenderLinkSettings..ctor(SbmpMessagingFactory messagingFactory, String entityName, Nullable`1 entityType, String transferDestinationEntityName, RetryPolicy retryolicy)
at Microsoft.ServiceBus.Messaging.Sbmp.SbmpMessagingFactory.OnBeginCreateMessageSender(String transferDestinationEntityName, String viaEntityName, TimeSpan timeout, AsyncCallback callback, Object state)
at Microsoft.ServiceBus.Messaging.MessagingFactory.CreateMessageSenderAsyncResult.<GetAsyncSteps>b__52(CreateMessageSenderAsyncResult thisPtr, TimeSpan t, AsyncCallback c, Object s)
at Microsoft.ServiceBus.Messaging.IteratorAsyncResult`1.EnumerateSteps(CurrentThreadType state)
at Microsoft.ServiceBus.Messaging.IteratorAsyncResult`1.Start()
Exception rethrown at [0]:
at Microsoft.ServiceBus.Common.AsyncResult.End[TAsyncResult](IAsyncResult result)
at Microsoft.ServiceBus.Common.AsyncResult`1.End(IAsyncResult asyncResult)
at Microsoft.ServiceBus.Messaging.OpenOnceManager.<>c__DisplayClass4`1.<Begin>b__3(IAsyncResult r, T& output)
at Microsoft.ServiceBus.Messaging.OpenOnceManager.OpenOnceManagerAsyncResult`1.OperationComplete(IAsyncResult result)
at Microsoft.ServiceBus.Common.AsyncResult.SyncContinue(IAsyncResult result)
at Microsoft.ServiceBus.Messaging.OpenOnceManager.OpenOnceManagerAsyncResult`1.BeginOperation()
at Microsoft.ServiceBus.Messaging.OpenOnceManager.OpenOnceManagerAsyncResult`1.OpenComplete(IAsyncResult result)
at Microsoft.ServiceBus.Common.AsyncResult.SyncContinue(IAsyncResult result)
at Microsoft.ServiceBus.Messaging.OpenOnceManager.OpenOnceManagerAsyncResult`1..ctor(OpenOnceManager openOnceManager, TimeSpan openTimeout, AsyncCallback callback, Object state, Func`3 beginOperation, EndOperation`1 endOperation)
at Microsoft.ServiceBus.Messaging.OpenOnceManager.Begin[T](AsyncCallback callback, Object state, Func`3 beginOperation, Func`2 endOperation)
at Microsoft.ServiceBus.Messaging.MessagingFactory.BeginCreateMessageSender(String transferDestinationEntityPath, String viaEntityPath, Boolean tryPairSender, TimeSpan timeout, AsyncCallback callback, Object state)
at Microsoft.ServiceBus.Messaging.Channels.ServiceBusOutputChannel.OpenMessagingFactoryAndMessageSenderAsyncResult.CreateFactoryComplete(IAsyncResult result)
at Microsoft.ServiceBus.Common.AsyncResult.SyncContinue(IAsyncResult result)
at Microsoft.ServiceBus.Messaging.Channels.ServiceBusOutputChannel.OpenMessagingFactoryAndMessageSenderAsyncResult..ctor(ServiceBusOutputChannel outputChannel, TimeSpan timeout, AsyncCallback callback, Object state)
at Microsoft.ServiceBus.Messaging.Channels.ServiceBusOutputChannel.OnOpen(TimeSpan timeout)
at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
at System.ServiceModel.Channels.CommunicationObject.Open()
at Microsoft.BizTalk.Adapter.SBMessaging.SBMessagingOutputChannelFactory.OnCreateChannel(EndpointAddress address, Uri via)
at System.ServiceModel.Channels.ChannelFactoryBase`1.InternalCreateChannel(EndpointAddress address, Uri via)
at System.ServiceModel.Channels.ChannelFactoryBase`1.CreateChannel(EndpointAddress address, Uri via)
at System.ServiceModel.Channels.ServiceChannelFactory.ServiceChannelFactoryOverOutput.CreateInnerChannelBinder(EndpointAddress to, Uri via)
at System.ServiceModel.Channels.ServiceChannelFactory.CreateServiceChannel(EndpointAddress address, Uri via)
at System.ServiceModel.Channels.ServiceChannelFactory.CreateChannel(Type channelType, EndpointAddress address, Uri via)
at System.ServiceModel.ChannelFactory`1.CreateChannel(EndpointAddress address, Uri via)
at System.ServiceModel.ChannelFactory`1.CreateChannel()
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: {28428716-88C2-437B-953F-D471DA00C5A6}
InstanceID: {18C48B89-D9C0-47A8-ADF0-0CA62746FBB1}
Below are my Send Port Adapter Configurations:
URI is blacked out
/Namespace/Topic/ are next in the path
Can someone confirm that the Issuer Name is the Namespace and the Issuer Key is the Primary Key from the get-SBAuthorizationRule? I also tried Shared Access Signature (SAS) but that service was connecting to a default port and do not believe that is
how I need to connect.
Also, there is nothing on the Properties Tab as I do not have anything custom for the initial step.
Any and all help is appreciated.

Glenn,
Thank you very much for the response, I will go down this route in further detail. A couple of quick questions for you to help further my understanding.
Where is the SAS limitation documented? I am sure I glossed over it and it did not register, but your help in where to look next time will be helpful.
Also, can I change the default Port for which it is listening on the BizTalk Server or the Service Bus Location? The connection string I get from get-SBAuthorization Rule is as follows:
Endpoint=sb://{ServiceBusLocation}/NsServiceBus;StsEndpoint=https://{ServiceBusLocation}:7355/NsServiceBus;RuntimePort=7354;ManagementPort=7355;SharedAccessKeyName=RootManageSharedAccessKey;SharedAccessKey={KeyValue}
The exception I get is:
A message sent to adapter "SB-Messaging" on send port "SBSendPort" with URI "sb://<ServiceBusLocation>/NsServiceBus/collateraltopic" is suspended.
Error details: System.ServiceModel.EndpointNotFoundException: Could not connect to net.tcp://<ServiceBusLocation>:9354/. The connection attempt lasted for a time span of 00:00:04.0250873. TCP error code 10061: No connection could be made because the target machine actively refused it <IPAddress>:9354. ---> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it
at System.Net.Sockets.Socket.EndConnect(IAsyncResult asyncResult)
at System.ServiceModel.Channels.SocketConnectionInitiator.ConnectAsyncResult.OnConnect(IAsyncResult result)
--- End of inner exception stack trace ---
It looks like it is going to 9354 for the authentication when the Service Bus is configured for
7355. I believe I have opened the ports on both ends but do not think it will matter since it looks like it is sending the
request to a different location.
Thank you

BizTalk 2013 Synchronous scenario

Hi
Is there a sample of how to do a synchronous web service call using biztalk 2013 anywhere i can look at?
Basically i need to call biztalk from a .Net web application, biztalk passes this onto SAP and the response message needs to go back to the web application.
Thanks
Riaz

expose your schema as a service (this is what your .Net client will call) and create the associated receive port [the service endpoint]. Create a wcf SAP request-response port which will pass this request to SAP.
Bind this send port (through filter) to the receive location and apply the MAP to transform from your request schema to the SAP service schema.
If however you want to do additional processing which might not be possible through maps then convert this into an orchestration and expose the orchestration as a service.
Regards.

Biztalk 2009 application to Biztalk 2013 application

Similar Messages

Maybe you are looking for