- This topic has 7 replies, 1 voice, and was last updated 9 years, 5 months ago by
.
-
Posts
-
-
I got WebException: The operation has timed out
when i send a large file through biztalk to a web service.xception type: XlangSoapException
Source: Microsoft.XLANGs.BizTalk.Engine
Target Site: Void VerifyTransport(Microsoft.XLANGs.Core.Envelope, Int32, Microsoft.XLANGs.Core.Context)
The following is a stack trace that identifies the location where the exception occuredat Microsoft.BizTalk.XLANGs.BTXEngine.BTXPortBase.VerifyTransport(Envelope env, Int32 operationId, Context ctx)
at Microsoft.XLANGs.Core.Subscription.Receive(Segment s, Context ctx, Envelope& env, Boolean topOnly)
at Microsoft.XLANGs.Core.PortBase.GetMessageId(Subscription subscription, Segment currentSegment, Context cxt, Envelope& env, CachedObject location)
at WSL.DatacapInvoice.orchWS_PO.segment1(StopConditions stopOn)
at Microsoft.XLANGs.Core.SegmentScheduler.RunASegment(Segment s, StopConditions stopCond, Exception& exp)How to fix it in biztalk? The only possilbe related setting is \”Maximum Batch Size, it’s default to be 102400. Any idea?
Or it’s merely a timeout problem on webservice and should change some configuration value there?
Thanks
-
Thanks a lot, i got rid of the TimeOut error. 🙂
But then ran into another error:
SoapException: There was an exception running the extensions specified in the config file. –> Maximum request length exceeded.
The file is large around 8M.
How to change the Maximum Allowed Length in biztalk?
Cheers
Merry-
client side
i’m sending a file using biztalk to an public web service, and got this error in biztalk
is there a message limit for biztalk to process?
-
The whole error description is following:
Error Description: SoapException: There was an exception running the extensions specified in the config file. –> Maximum request length exceeded.
Exception type: XlangSoapException
Source: Microsoft.XLANGs.BizTalk.Engine
Target Site: Void VerifyTransport(Microsoft.XLANGs.Core.Envelope, Int32, Microsoft.XLANGs.Core.Context)
The following is a stack trace that identifies the location where the exception occuredat Microsoft.BizTalk.XLANGs.BTXEngine.BTXPortBase.VerifyTransport(Envelope env, Int32 operationId, Context ctx)
at Microsoft.XLANGs.Core.Subscription.Receive(Segment s, Context ctx, Envelope& env, Boolean topOnly)
at Microsoft.XLANGs.Core.PortBase.GetMessageId(Subscription subscription, Segment currentSegment, Context cxt, Envelope& env, CachedObject location)
at orchWS_PO.segment1(StopConditions stopOn)
at Microsoft.XLANGs.Core.SegmentScheduler.RunASegment(Segment s, StopConditions stopCond, Exception& exp)-
Are you sending the message to a BizTalk Web Service, or are you sending a message to a diferent web service from your BizTalk orchestration?
If it’s the latter, it would be nice to see the entire error message. Meanwhile, have you tried incrementing the client-side timeout for the SOAP adapter when making the call? You can do this by setting the SOAP.ClientConnectionTimeout property on the message you’re setting. See here for some details:
[url]http://www.winterdom.com/weblog/2005/07/17/WebServiceCallTimeoutInBizTalk.aspx[/url]
-
[quote:b9877e5cf1=\”Merryhe45 \”]SoapException: There was an exception running the extensions specified in the config file. –> Maximum request length exceeded.[/quote:b9877e5cf1]
Did you get this on the client or the server side?
On the server side, for ASP.NET applications, this can be changed using the maxRequestLength attribute of the <httpRuntime/> element in the web.config file (the default is 4MB). You can see the documentation for it here:
[url]http://msdn2.microsoft.com/en-us/library/e1f13641.aspx[/url]
-
[quote:96a732a34b=\”Merryhe45 \”]client side
i’m sending a file using biztalk to an public web service, and got this error in biztalk
is there a message limit for biztalk to process?[/quote:96a732a34b]
Are you sure the server you’re calling to doesn’t have this restriction enabled? The error message you mention you’re getting is the exact same message used by ASP.NET 🙂
Can you show us the entire error + stack trace you’re getting?
-
At the risk of sounding like a broken record (too late for that, probably! :)), have you asked your webservice provider to see if they support that level of large uploads?
I’ve only seen that error on the server side of an ASP.NET application/service, so if your service provider is exposing an ASMX service, my guess is the problem is on their end. I’m not aware of having that limitation enforced from the client side of the HTTP mechanism in .NET (HttpWebRequest, which biztalk uses underneath the HTTP and SOAP adapters).
Anyone else has any other ideas?
-
-
-
-
-
-
-
- The forum ‘BizTalk 2004 – BizTalk 2010’ is closed to new topics and replies.