When running a flow in Corda via RPC (or via the Shell) an "Error during RPC invocation" is returned with no further information
The error has been returned from the node via RPC. The RPC connection hides the original error in order to stop possible privacy leaks. If you check the logs of the node there should be more information on the error.
Related
I've set-up two applications, one with FILE Receive Port and the other with a Send Port subscribing to that Receive Port with filter set as BTS.ReceivePortName == {ReceivePortNameHere}. I'm using BizTalk 2013 R2.
In the Receive Port, I'm using the pipeline 'BTAHL72XReceivePipeline'. And, in the Send Port, I'm using the pipeline 'BTAHL72XSendPipeline'.
When I drop a HL7 message into the Receive Port file location, it produces the error:
The Messaging engine failed to process a message submitted by
adapter:FILE Source URL:E:\InboundToBizTalk\*.hl7. Details:The
published message could not be routed because no subscribers were
found. This error occurs if the subscribing orchestration or send port
has not been enlisted, or if some of the message properties necessary
for subscription evaluation have not been promoted. Please use the
Biztalk Administration console to troubleshoot this failure.
However, I do have a subscription set. Why is this error occurring? Is there an issue with the pipeline component or the way I am using it?
On the Group Overview page search for "Subscriptions" and filter based on your Send port name.
Verify that you see an activation Subscription and confirm that the filter conditions on the subscription are correct.
The by far most likely causes:
A typo between the Receive Port Name and the value in the Filter.
The Send Port is not Enlisted or Started.
Do not use quotes in the filter property.
Turned out to be ACK which could not be routed therefore causing the whole flow to error. For an MLLP transport type, it is two way thus the ACK can be routed. For a FILE transport type, it is one way therefore ACK needs to be accounted for separately.
To get around this, another port was created which would subscribe to the ACK.
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.
Currently I'm working on a project on which I need to send a PDF file over AS/2 using BizTalk.
Now, everything is setup in BizTalk.
However, I have an error message in BizTalk saying the following:
The receive pipeline:"Microsoft.BizTalk.EdiInt.DefaultPipelines.AS2Receive,
Microsoft.BizTalk.Edi.EdiIntPipelines, Version=3.0.1.0, Culture=neutral,
PublicKeyToken=31bf3856ad364e35" is trying to suspend a message received on Receive
Location:"/xxx/BTSHTTPReceive.dll". The Adapter/Receive Location however is configured
to never suspend messages on failure. Please change either the receive location or
receive adapter's configuration or the pipeline's configuration.
If I configure the adapter to suspend messages on failure it does work partially. However, I want to get it working with this setup. Is there any way to figure our why my messages are being suspended?
The warning message that follows on the error is the following:
The adapter failed to transmit message going to send port "SendPDFToxxxxOverAS2" with
URL "http://localhost/xxxx/BTSHTTPReceive.dll". It will be retransmitted after the retry
interval specified for this Send Port. Details:"The remote server returned an error:
(500) Internal Server Error.".
I hope someone can make some things clear.
In order to make narrow down the search, I've also removed the checkbox to send and request MDN's in the agreement.
I've found the issue myself.
"Return correlation handle on success" should be off.
"Suspend failed requests" should be on.
Thanks for the help anyway.
Kr
We have a BizTalk 2010 solution where we receive an HL7v2 message over MLLP using a request/response receive port. An orchestration processes the message, calls a web service and returns a custom ACK to the client. Seems to work well.
In testing, I created 2 scenario:
An error would occur when generating the ACK
An error would occur when sending the ACK to the client via the send pipeline of the request/response receive port. I did this by incorrectly setting a configuration parameter on the send pipeline.
My orchestration contains scope and catch blocks so that I don't end up with suspended messages in the messagebox. Essentially if there are errors, we just want to log them, there's nothing we can do to remediate so suspended messages are unnecessary and clutter the messagebox. In my testing scenarios, if errors occur then the ACK does not get sent to the client, and althouth the orchestration completes, there is still a running service instance for the receive port. I imagine that is because the send pipeline is still subscribing to the ACK and waiting for it. Is there a way to avoid this or terminate the service instance somehow through the orchestration?
I'd suggest adding a fault message to the operation on the port and throwing a fault message out from your catch block.
I'm trying to send a message and we sometime get this error :
Service not available, closing transmission channel. The server response was: 4.4.2 Timeout while waiting for command.
Anyone know what to do with this? Because it only happens "sometime" and apperently, for no specific reason.
I saw many article saying :
442 The server started to deliver the message but then the connection was broke (Source : http://www.sorkincomputer.net/SMTP%20errors.htm)
This is typically a server side (the SMTP server you're delivering to) error or a network connectivity error. There isn't anything you can do about it via your code, you would need to get the related IT staff involved to figure out why your connection is getting closed or interrupted.