I have a tool write a message to MSMQ, and a receive port (in Biztalk 2016) looks up on the queue and process the message.
But I get the following error:
The adapter "WCF-Custom" raised an error message. Details "System.ServiceModel.MsmqPoisonMessageException: The transport channel detected a poison message. This occurred because the message exceeded the maximum number of delivery attempts or because the channel detected a fundamental problem with the message. The inner exception may contain additional information.
at System.ServiceModel.Channels.MsmqReceiveHelper.TryReceive(MsmqInputMessage msmqMessage, TimeSpan timeout, MsmqTransactionMode transactionMode, MsmqMessageProperty& property)
at System.ServiceModel.Channels.MsmqInputChannelBase.TryReceive(TimeSpan timeout, Message& message)
at System.ServiceModel.Channels.SecurityChannelListener`1.SecurityInputChannel.TryReceive(TimeSpan timeout, Message& message)
at System.ServiceModel.Dispatcher.InputChannelBinder.TryReceive(TimeSpan timeout, RequestContext& requestContext)
at System.ServiceModel.Dispatcher.ErrorHandlingReceiver.TryReceive(TimeSpan timeout, RequestContext& requestContext)".
I have no idea how to solve or at least find out the root cause.
I tried to read the message in MSMQ, but it is encrypted.
Related
From the last few days we have been trying to hunt down some kusto query failures. Time and again we see the following error.
Have looked into any increase in ingestions for the past few days and don't see any.
In few scenarios we use direct ingestion, can this be the issue?
Does this error mean that the server is out of sockets? If so, what is generally the cause for that? ANd ho can that be alleviated?
Couldn't find any troubleshooting guide for this.
Happy to provide more details as needed.
Failure details: Query execution has resulted in error (0x8013153D): Partial query failure: 0x8013153D (message: 'Insufficient winsock resources available to complete socket connection initiation. ==> ExecuteRemoteSubQuery failure: ', details: 'Source: mscorlib System.InsufficientMemoryException: Insufficient winsock resources available to complete socket connection initiation. ---> System.Net.Sockets.SocketException: An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full 11.0.0.82:23107 Server stack trace: Exception rethrown at [0]: --- End of stack trace from previous location where exception was thrown --- [0]Kusto.Data.Exceptions.KustoDataStreamException: Query execution has resulted in error (0x8013153D): Partial query failure: 0x8013153D (message: 'Insufficient winsock resources available to complete socket connection initiation. ==> ExecuteRemoteSubQuery failure: ', details: 'Source: mscorlib System.InsufficientMemoryException: Insufficient winsock resources available to complete socket connection initiation. ---> System.Net.Sockets.SocketException: An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full 11.0.0.82:23107 Server stack trace: Exception rethrown at [0]: --- End of stack trace from previous location where exception was thrown --- Timestamp=2020-12-04T17:47:28.3230123Z
I would recommend that you open a support ticket for your resource, via the Azure portal (https://portal.azure.com)
A send port configured with WCF-SAP adapter is failing with Unknown error description error logged to Biztalk event log.
In the event of this error we can see that the iDOC is already sent to the SAP system before the error occurred, but due to this error Biztalk thinks that the iDOC has not been sent to SAP and hence retries to send the iDOC after retry interval of 5 minutes which is creating a duplicate of the iDOC in the SAP system as well as in biztalk by archiving 2 files. Not sure of the cause of the error as it is a very generic error.
Can someone please suggest if you had similar situation or cause for this error anyway related to wcf-sap adapter in BT 2013 R2 ? Thank you.
Here is the error:
A message sent to adapter "WCF-SAP" on send port "xx" with URI
"sap://CLIENT=xx;LANG=EN;#a/xx/xx?GWHOST=xx&GWSERV=xx&ListenerGwServ=xx&ListenerGwHost=xx&RfcSdkTrace=False&AbapDebug=False"
is suspended. Error details: Unknown Error Description MessageId:
{DC121ABC-ECD3-4635-B30D-5080322C976B} InstanceID:
{B2802A71-ECBE-4237-A48D-E5DCE284D23F}
Verify at the adapter settings that EnableBizTalkCompatibilityMode is set to True. And the checkbox Use Transactions is enabled and Isolation Level selected is Serializable.
Also are you using the NCo ConnectorType to connect to SAP? This is the recommended way.
We have a web application that occasionally makes HTTPS requests to third party web services. Most of the time these work without issue. However occasionally the application will begin throwing exceptions on each request:
System.Net.WebException: The underlying connection was closed: Could not establish
trust relationship for the SSL/TLS secure channel. --->
System.Security.Authentication.AuthenticationException: The remote certificate is
invalid according to the validation procedure.
at System.Net.Security.SslState.StartSendAuthResetSignal(ProtocolToken message, AsyncProtocolRequest asyncRequest, Exception exception)
at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest)
...etc...
Now the odd part is that when we recycle the web application, the exception stops being thrown. For a while anyway.
We determined that a library was occasionally setting System.Net.ServicePointManager.ServerCertificateValidationCallback to a method which did not correctly validate certificates. The reason it seemed random is that certificate validation worked until the library was used and that callback was set.
The solution is to fix the library. And as general rule never globally set ServerCertificateValidationCallback in production code.
using bizTalk 2010 orchestration:
when i send data port configured as webservice the following error appear
The adapter failed to transmit message going to send port >"WcfSendPort_Service_ServiceSoap12" with URL "blablabla/Service.asmx". It will >be retransmitted after the retry interval specified for this Send Port. >Details:"System.Xml.XmlException: Root element is missing.
at System.Xml.XmlTextReaderImpl.Throw(Exception e)
at System.Xml.XmlTextReaderImpl.ParseDocumentContent()
at System.Xml.XmlTextReaderImpl.Read()
at System.Xml.XmlReader.MoveToContent()
at >Microsoft.BizTalk.Adapter.Wcf.Runtime.BizTalkBodyWriter.ValidateStreamContainsXml(Stream >stream)
at >Microsoft.BizTalk.Adapter.Wcf.Runtime.WcfMarshaller.CreateWcfMessage(CreateWcfMessageSetti>ngs settings)
at Microsoft.BizTalk.Adapter.Wcf.Runtime.WcfClient2.SendRequestMessage(IBaseMessage >bizTalkMessage, IRequestChannel channel)
at Microsoft.BizTalk.Adapter.Wcf.Runtime.WcfClient2.SendMessage(IBaseMessage >bizTalkMessage)".
The crucial part of the exception is:
System.Xml.XmlException: Root element is missing.
This suggests that you are not transmitting what you think you are transmitting.
From the Suspended Message Instance, check that the message body that being sent is what you expect; or - change your Send Port Adapter to FILE and write the message out to the file system in order to check the message content.
I am uploading files to Amazon S3.
1.While uploading large files(upto 50 MB) I am getting this error:
The request was aborted: The request was canceled.
2.The problem is when I dont use the net tcp binding service and directly upload from UI to business layer without a service layer in between,I am able to upload without any exceptions.
3.Here is the exception details:
System.Net.WebException: The request was aborted: The request was canceled. ---> System.IO.IOException: Cannot close stream until all bytes are written. at System.Net.ConnectStream.CloseInternal(Boolean internalCall, Boolean aborting) --- End of inner exception stack trace --- at System.Net.ConnectStream.CloseInternal(Boolean internalCall, Boolean aborting) at System.Net.ConnectStream.System.Net.ICloseEx.CloseEx(CloseExState closeState) at System.Net.ConnectStream.Dispose(Boolean disposing) at System.IO.Stream.Close() at Amazon.S3.AmazonS3Client.getRequestStreamCallback[T](IAsyncResult result)
4.In the service's web. config I have increased the timeout of both idle and receive to more than half an hour. But still getting the exception.
5.Is this related to any configuration settings for the net tcp binding service?
Any solution?