Can anyone tell me what I'm doing wrong or how to do it correct.
I have an BizTalk 2013 R2 project with an orchestration. The orchestration has an receive port (AnyType schema) and dynamic send port (AnyType schema).
When a receive a soap message I do this in the "ConstructMessage" with an MessageAssigment shape:
Message_1 = opeTestPerson;
Message_1(*) = opeTestPerson(*);
Message_1(SOAP.AuthenticationScheme)="Anonymous";
Message_1(SOAP.MethodName)="opeTestPerson";
Message_1(BTS.SOAPAction)="http://XXXX.dk/TestPerson/opeTestPersonIn";
Message_1(BTS.OutboundTransportType)="SOAP";
CallOpeHentPersionPort(Microsoft.XLANGs.BaseTypes.Address) = #"http://XXXX.dk/serTestPerson.asmx";
But when BizTalk try to call the webservice URL I get this error:
The server was unable to process the request due to an internal error. For more information about the error, either turn on IncludeExceptionDetailInFaults (either from ServiceBehaviorAttribute or from the configuration behavior) on the server in order to send the exception information back to the client, or turn on tracing as per the Microsoft .NET Framework SDK documentation and inspect the server trace logs.
The strange ting is that the Web-server does not log any errors.
So can anyone tell how to call a web-service using dynamic port and send the SOAP header?
PS. I don't use a proxy call for calling, just direct call, because I need to call different URL depending on the incoming message.
Related
I get the following error message when I try to send message to Microsoft Message Queue to server on the local network from BizTalk 2016 using the MSMQ adapter:
Could not load file or assembly
Microsoft.BizTalk.Adapter.MSMQ.MsmqLargeMessageWrapper.dll or one of
its dependencies. The specified module could not be found.
BizTalk, BizTalk Adapter Packs and BizTalk Enterprise Adapters are installed, and I am able to configure send and receive handlers and the send port itself.
Are there any pre-requisities I need to install?
Not very often you google and find four irrelevant answers...so what am I not getting?
Ok, got it. I was unlucky while I was thinking... ;|
MSMQ Adapter is built to call Windows Message Queuing queue on a Windows Server. If you call a remote queue, you need to activate Microsoft Messaging feature on the local server too - otherwise you end up with a simlar error message like above. It will forward the queue processing to the remote server.
I am calling a third party service. Binding information contains TransportType as Name="WCF-BasicHttp". I have consumed this service in my orchestration. I need to create send port with WCF-WSHTTP in BizTalk admin console. But I am getting below error. I have set security as NONE.
Error information:
System.Net.WebException: Content Type application/soap+xml; charset=utf-8 was not supported by service The client and service bindings may be mismatched
How do I fix this?
If the binding specifies basic-http binding, if there any specific reason to create send port with WCF-WSHttp binding ?
Have you tried creating the send port with WCF-Basichttp binding ?
the security is a server side point. you have to use the same binding as the service from the server side.
I have created a BizTalk application to connect to VSO Rest API to fetch or create work items.
I have configured a wcf-webhttp adapter for calling the rest API.
Before configuring the adapter, I have tested the API with console application and getting the results with same URL.
While running the application I am getting following error:
The adapter failed to transmit message going to send port "SendPort" with URL "the URL". It will be retransmitted after the retry interval specified for this Send Port. Details:"System.ServiceModel.EndpointNotFoundException: There was no endpoint listening at https://xxx.visualstudio.com/defaultcollection/_apis/wit/workitems/2
connected host has failed to respond 23.98.150.230:443
But when I paste the URL in the browser I am able to see the result returned by API in the browser.
What could the issue be?
We are having Tridion 2011 SP1 environment up and running with one CMS server and one CDS server. Today we installated new CMS server and pointed it to existing SQL Server database. We used same MTSUser, same database credentials. Installation went smooth, but when we try to access CMS server we are getting 9 error as below.
1) The remote server returned an error: (404) Not Found.
at System.Net.HttpWebRequest.GetResponse() at System.ServiceModel.Channels.HttpChannelFactory.HttpRequestChannel.HttpChannelRequest.WaitForReply(TimeSpan timeout)
2) Loading list of languages failed.
at System.Net.HttpWebRequest.GetResponse() at System.ServiceModel.Channels.HttpChannelFactory.HttpRequestChannel.HttpChannelRequest.WaitForReply(TimeSpan timeout)
3) Loading list of locales failed.
at System.Net.HttpWebRequest.GetResponse() at System.ServiceModel.Channels.HttpChannelFactory.HttpRequestChannel.HttpChannelRequest.WaitForReply(TimeSpan timeout)
How to troubleshoot ?
We are able to access SQL Server database using ODBC.
Use a tool like Fiddler to watch HTTP traffic when you load the Tridion GUI, and find the requests that are failing.
From here you could use WCFTestClient to get more specific details on the errors and the available bindings.
My guess is IIS Configuration.
I would like to suggest you to think a bit out of box. As errors are more specific to WCF service. so configure tracing and see what things are going wrong with the webservice.
This could be due to the service endpoint binding not using the HTTP protocol. This could also be due to an HTTP request context being aborted by the server (possibly due to the service shutting down). After all I will again recommend you to see server logs for more details. I or someone else can better help you , if you can share logs here.
Is the Tcm Service Host (windows service) running?
In Microsoft BizTalk Application when exception occurred then Services or port will goes to in suspended mode and need to manually start application or port.
What i want is when any exceptions occurred during message processing should send one email alert to system administrator and details of exception should be stored in separate database for further process.
Anyone have any better suggestion how we can do it.
Regards,
Rakesh
To handle the message failure secnario see using Failed Message Routing. As far as monitoring ports when they shut down you can either use MOM (expensive) or write a script to do what you want. There are many posts here in stackoverflow that address this... here is one such post.
To get an email alert sent for any messaging failures (i.e., a failure in a send or receive port)
For each send or receive port for which you want to track failures, edit the port properties and check the box for "Enable routing for failed messages"
For send ports, you'll find this option under "Transport Advanced Options".
The option for receive ports is under the General section of the port properties.
Create a new Send Port (perhaps in a separate "Exception Handling" BizTalk application) that uses the SMTP adapter to send the emails.
To send out all failed messages using this new port, create a filter on the send port with the Property ErrorReport.ErrorType == FailedMessage. That will evaluate as true for all messages that error on a send or receive port for which you enabled Failed Message Routing.
If you need to route messages differently, at a more granular level, then have a look at the properties on the Failed Message Routing page referenced by ChrisLoris.
To track exceptions for failed messages in a separate database, I would start with the Microsoft BizTalk ESB Toolkit Exception Management Framework, as it includes a database for this purpose and the mechanism to push exception/failed message data into that database (build atop Failed Message Routing). It even includes a web site to enable users to interact with the failed messages, which you can customize as you see fit or throw away altogether.
The instructions to install the just the Exception Management part of the ESB Toolkit are available at http://msdn.microsoft.com/en-us/library/ee250099.aspx. Microsoft's guide to using the ESB Exception Management is worth a review too and is here.