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

Similar Messages

What is the best way to handle Exception in Java?

We are designing an application that will be developed using JSP + EJB .
To deal with the exception part, we have thought about following solutions
(1)All methods in EJB will be declare with throws clause, with the respect to the potential exceptions that can be thrown by method.
We will catch only those exceptions, for which we can take alternative steps or further action when they occurred. All other exceptions will be thrown to the caller.
(2)All JSP pages will have try/catch that catches exceptions thrown by EJB or by JSP code.
(3)A common JSP file will be designated to handle Exception by setting isErrorPage property true and all JSP files are pointing to that particular file for exception handling.
(4)Whenever any exception occurred in application, it will bubbled up and end user will get a common JSP page designed to handle exception.
I am looking for the suggestions to improve this mechanism.
Regards,
Chetan

The problem with the standard expection handling in a web environment is that all the potentially useful status information goes to the user, who probably won't make head nor tail of it. It also goes to the logs which someone might, or might not get arround to reading.
What I do is to have a standard method called to deal with unanticipated exceptions and e-mail me a status report. This contains not just the extended stack trace (chasing any level of wrapped exception) but also details of the transaction being processed, including the user if known.
Set up an e-mail alias with a list of people to receive these reports. Often you can have the problem fixed, and send the user an apologetic e-mail before they even get a complaint in.
Create JSP tags to do this with any other per-page housekeeping.

Best way to handle Exceptions?

Hi there, I have to deal with some exceptions and wondered if I could get some advice on best practice.
I am writing an application that accesses Lotus Domino, and in some parts of the code I have to handle NotesException. This is a class that is part of the lotus.domino package that ships with Notes. Rather unhelpfully, getMessage() does not return anything. Instead you have to use the id and text members which is horribly non-standard. NotesException cannot be extended like most of the Notes classes.
So basically I want to use a custom exception in a method where the most likely thing to go wrong will be a NotesException. I want to mask this and return a custom exception instead. So far, I am doing something like this:
try {
//Some code here;
} catch (Exception e){
String msg = "";
if (e instanceof NotesException){
NotesException ne = (NotesException)e;
msg = ne.id + " " + ne.text;
} else {
msg = msg = e.getMessage();
throw new CollectionFailedException("Could not get collection: " + msg);
Is there a better way?
Marc

try {
//Some code here;
} catch (Exception e){
String msg = "";
if (e instanceof NotesException){
NotesException ne = (NotesException)e;
msg = ne.id + " " + ne.text;
} else {
msg = msg = e.getMessage();
throw new CollectionFailedException("Could not get
t collection: " + msg);
};Why are you catching Exception & then checking if it is NotesException? Why don't you catch NotesException itself?
try
//Some code here;
catch (NotesException ne)
   String msg = ne.id + " " + ne.text;
   throw new CollectionFailedException("Could not get t collection: " + msg);
catch(Exception e)
   throw new AnotherCustomException("Exception occurred while ...Exception = " + e);
}

How to handle exceptions in BAPI

Dear Gurus,
Is there any specific way to handle exceptions in BAPI? I mean the way one handles exception in FM...can tat be applicable to BAPI or is there something specific.
Regards,
Shiku

The export parameter Return can be implemented as follows:
As a structure, whereby it must be defined in the function module as an export parameter, as well as in the method in the BOR.
As a table, whereby it must be defined in the function module as a table parameter, as well as in the method in the BOR as an export parameter.
Before filling the Return parameter you should either initialize the structure with CLEAR or the table with REFRESH and CLEAR.
If the return parameter is not set or is set to an initial value this means that no error has occurred.
The Return parameter may be based on the following reference structures:
BAPIRET2
You must use this reference structure when developing new BAPIS.
BAPIRET1, BAPIRETURN
These reference structures are still partly used in old BAPIs.
Both structures must be filled in the logon language.
Regards,
SuryaD.
Found this info for you shiku at http://help.sap.com/saphelp_46C/helpdata/EN/a5/3ec9f74ac011d1894e0000e829fbbd/content.htm.
Hope this was helpful.

Qs on Handling Exception on BPEL Process

Hi,
Would like to know what is the best optimized way to handle exception that are caused by process because of type mismatch or variable not initialized or anything?
So how we can do it?
Thanks,

Use the new error hospital feature in rel 10.1.3.3.
http://www.oracle.com/technology/products/ias/bpel/pdf/10133technotes.pdf
Marc
http://orasoa.blogspot.com

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.

Handling the exception in BizTalk WCF-SQL Receive Adapter

As per Application, BizTalk connecting to SQL Server and executing the SP for polling the data. Occasionally we are getting Timeout SQL exception in event log.
Customer is asking why not BizTalk handling this kind of error messages.
Please let me know how to handle exceptions in WCF Receive location.already i set the properties like Suspend request
message on failur and Include exception details in faults
But the error message is returning in Eventlog and not reaching to biztalk
one of the error message is
Another one is :
DB locks happening in SQL Server

Yes definitely, you can "Enable routing for failed messages" and subscribed to the failed message.
Later you can create a send port or orchestration with below filter conditions-
"ErrorReport.ErrorType == Failed Message" .
BizTalk demotes all the properties of this message to avoid unwanted subscription and promotes only below mentioned properties under ErrorReport namespace.
Description
ErrorType
FailureCategory
FailureCode
InboundTransportLocation
MessageType
OutboundTransportLocation
ReceivePortName
RoutingFailureReportID
SendPortName
Check the below articles which provide good sample for the same.
error-message-routing-pattern-demo-in-biztalk
http://mscerts.programming4.us/application_server/biztalk%202009%20%20%20handling%20failed%20messages%20and%20errors.aspx
Using Failed Message Routing
You can also setup Backup transport feature, which will only get activated in case of failure.
You can configure it to send emails as well.
How to Configure Backup Transport Options for a Send Port
Which one to choose between the two-
Using the backup transport for SMTP would allow you to send an email, but that’s normally not a good solution because you’ll just get that message, with no context, and not really know what to do with it. Failed message routing will let you setup filters
based on the failures (types, descriptions, etc) and this way you can organize how you handle failures. If a pipeline validation fails you can send the message to one place to be repaired where as if a transport fails (or something else) it can be handled
in a different way.
https://social.msdn.microsoft.com/Forums/en-US/09256232-d92a-448b-9c8d-db6144afee84/enable-routing-for-failed-messages-versus-backup-transport?forum=biztalkgeneral
Thanks,
Prashant
Please mark this post accordingly if it answers your query or is helpful.

Is there a way to handle system exception ERROR_MESSAGE?

Hi,
I have a program executed in background, which produces a bunch of consecutive documents for a set of Bulk Shipments -> TD Loading and TD Delivery Confirmation. To create those documents I use function modules 'OIGI_LOADING_CREATE' and 'OIGI_DEL_CONF_CREATE' - both from Industry-Solution Oil-and_Gas (IS-Oil).
In some cases these FM-s produces error messages (E-type) which cancel execution of the program and broke my flow-logic.
Below are few messages recorded in a job log for my task:
18.08.2005 15:56:41 Job started
18.08.2005 15:56:41 Step 001 started (program /PTRL/TAS_POSTPONDED_SYNC, variant , user name IMUTAFCHIEV)
18.08.2005 15:56:58 Shipment 180753 saved
18.08.2005 15:57:06 The plant data of the material 177 is locked by the user BMINKOV
18.08.2005 15:57:06 The plant data of the material 177 is locked by the user BMINKOV
18.08.2005 15:57:06 The plant data of the material 177 is locked by the user BMINKOV
18.08.2005 15:57:06 Job cancelled after system exception ERROR_MESSAGE
Both function modules are not designed to handle any exceptions, and in owr environment (4.6c) there is no documented system exception 'ERROR_MESSAGE' which to be handled in CATCH-ENDCATCH block.
Is there a way to handle this exception and to track the list of error messages produced by some FM into an internal table, log, whatever, as it is done in the log of the background job. I need to find a way write these messages in my log-tables and to proceed further with my flow-logic.
FYI: my program executes an RFC call to a remote system and retrieve a list of documents which need to be synchronized with R/3. I loose information, if the R/3 broke my flow-logic.
Any help would be highly appresiated.
Many thanks in advance.
Ivaylo Mutafchiev

Sven,
I made few programs where we used business scenario:
IS-Oil Shipment => IS-Oil Loading Confirmation => IS-Oil Delivery Confirmation.
All of them are based on Function Module call:
1. OIGI_LOADING_CREATE and
2. OIGI_DEL_CONF_CREATE.
To load shipment I call 1st FM in a way:
CALL FUNCTION 'OIGI_LOADING_CREATE' DESTINATION 'NONE'
       EXPORTING
            I_SUBRC     = 9 "save and commit
            I_SHNUMBER = shNumber
            I_VEHICLE   = vehicle
            I_LDPLT     = plant
            I_LDDATE    = loadDate
            I_LDTIME    = loadTime
            I_LDCDAT    = loadDate
            I_VEH_NR    = veh_nr
       TABLES
            T_OIGISVMQ = quantity_items
            T_OIGISVMQ2 = hpm_append
            T_OIGISIQ   = doc_quan_items
       EXCEPTIONS
            COMMUNICATION_FAILURE = 1 MESSAGE p_error
            SYSTEM_FAILURE = 2 MESSAGE p_error.
To confirm shipment (status 4) I call the same FM with:
CALL FUNCTION 'OIGI_LOADING_CREATE' DESTINATION 'NONE'
       EXPORTING
            I_SUBRC    = 39 "confirm & commit 2nd step
            I_SHNUMBER = shNumber
            I_VEHICLE = vehicle
            I_LDPLT    = werks
       EXCEPTIONS
            COMMUNICATION_FAILURE = 1 MESSAGE sh_error
            SYSTEM_FAILURE = 2 MESSAGE sh_error.
And finaly to finish process (status = 6) I call 2nd FM in a way:
CALL FUNCTION 'OIGI_DEL_CONF_CREATE' DESTINATION 'NONE'
       EXPORTING
            I_SUBRC         = 19 "save, confirm and commit
            I_SHNUMBER      = shNumber
            I_RAPID_CONFIRM = 'X'
            I_DDCDAT        = loadDate
            I_DLDATE        = loadDate
            I_DLTIME        = loadTime
       EXCEPTIONS
            COMMUNICATION_FAILURE = 1 MESSAGE p_error
            SYSTEM_FAILURE = 2 MESSAGE p_error.
FYI: It tooks me some time to 'investigate' and find correct use of these function modules. And I worked VERY CLOSE with our SD consultant.
For details (what the export parameters and tables consist of) and sample code, please contact me at:
ivaylo dot mutafchiev at vbs dot bg
I would be glad to share my knowlege.
Regards,
Ivaylo

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

Best way to handle any knid of exception

Hi Experts,
What is the best way to handle any kind of Exceptions across the layer and show a user friendly error message, for eg the JBO 2900, which is an unexpected error. There is no clue as to this error happens at which layer so how an we handle these kind of exceptions ?
thnks

hey you can try.. to add the exception handler.. in the task flow.. and in the DataBidnings.cpx..
error from the controller can be got from
ControllerContext context = ControllerContext.getInstance();
ViewPortContext currentRootViewPort = context.getCurrentRootViewPort();
Exception exceptionData = currentRootViewPort.getExceptionData();
if (currentRootViewPort.isExceptionPresent()) {
exceptionData.printStackTrace();
currentRootViewPort.clearException();
//FacesContext facesContext = FacesContext.getCurrentInstance();
//facesContext.addMessage(null, new FacesMessage(FacesMessage.SEVERITY_ERROR, exceptionData.getMessage(), null));
and the ui message can be thrown by
FacesContext ctx = NavigationUtil.getFacesContext();
FacesMessage fm = new FacesMessage(FacesMessage.SEVERITY_ERROR,message,null);
ctx.addMessage(null, fm);

[svn:cairngorm3:] 17952: simpler and safer ways to handle flex3 and flex4 sdk and profiles

Revision: 17952
Revision: 17952
Author:   [email protected]
Date:     2010-09-30 08:02:19 -0700 (Thu, 30 Sep 2010)
Log Message:
simpler and safer ways to handle flex3 and flex4 sdk and profiles
Modified Paths:
    cairngorm3/trunk/build-parent/pom.xml
    cairngorm3/trunk/libraries/lib-parent/pom.xml
    cairngorm3/trunk/pom.xml

BizTalk 2013 R2 - WC-Custom Adapter SAP-Binding: Unhandeld exception on failure tests

Dear Mr./Ms.
We have set up a test environment with BizTalk 2013 R2 Developer edition.
And we have also set up the SAP adapter following this blog
https://sandroaspbiztalkblog.wordpress.com/2015/03/04/biztalk-server-20132013-r2-step-by-step-wcf-sap-adapter-installation-guide/#comments
.But instead we used a WCF-Custom adapter with SAP-Binding
Everthing works fine if BizTalk can connect to SAP. But if we do some failure test, like giving in a wrong password. We get next error in the event viewer:
Application: BTSNTSvc64.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.Runtime.CallbackException
Stack:
at Microsoft.Adapters.Internal.LayeredChannelBindingElement.LayeredAsyncResult.SignalFinished(System.Object, System.Exception)
at Microsoft.Adapters.Internal.LayeredChannelBindingElement.LayeredOutboundChannel`1[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].AsyncRequest(System.Object)
at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
at System.Threading.ThreadPoolWorkQueue.Dispatch()
We would expect that we get some kind of authentication error and a suspended message. But Instead the host instance crash and message stays in process. Thanks in advance.
Kind regards
Benny Verhamme
benny verhamme signed

We would expect that we get some kind of authentication error and a suspended message. But Instead the host instance crash and message stays in process. Thanks in advance.
Hi Benny,
Thanks for your feedback in BizTalk forum.
As you mentioned above, we will receive an unhandled exception when we did something wrong during the procedure. I'm afraid that this is "by design", if this request is urgent for you, you could consider contact support directly(http://support.microsoft.com
). Thanks for your understanding.
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.

Handle DB exception in biztalk map

How to handle exceptions in mapping

You can use Error Return functoid.
Use this functoid in conjunction with the Database Lookup and Value
Extractor functoids to capture and map error information. Some of the scenarios this might be useful include:
When your map has a Database Lookup or Value Extractor functoid that is not behaving as expected. To see the error message, temporarily map the functoid to a field in the output schema.
If your application expects different message content when database operations fail. You can use the Error Return functoid to detect an error and map the error message to an alternate structure so that downstream applications
can react in a controlled manner.
http://msdn.microsoft.com/en-us/library/aa559365.aspx

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

Simple way to handle Exception in Biztalk 2013

Similar Messages

Maybe you are looking for