RE: Logged WSE 2.0 error: WSE350

Hello Steven,

I too found this message thread, but the supposed cause (a network package
got corrupted) is happening regularly on our server(s) which host a
WebService on the internet. So the corruption could occur anywhere on the
network/internet and breaks my code.

I need more information on this error from MS. I want to know detailed
information on why this Exception is raised in WSE 2.0 and what the code does
that raises this exception.

This might immediately lead to a simple solution (like chopping large
DIME-attachments into smaller pieces or resending the request). Our current
attachement size is 409600 bytes.

Since I have no way of reproducing this myself I want some 'code-based'
advise on what to do.

regards,


--
rvangeldrop


"Steven Cheng[MSFT]" wrote:

Hello Robbert,

From your description, one of your ASP.NET webservice(uses WSE 2.0) will
randomly report the following exception:

=========================
Microsoft.Web.Services2.Dime.DimeFormatException: WSE350: In the record
-390353390, the number of bytes in the Data field is less than 409600,
which
is the value indicated in the ContentLength field.
========================

As for the webservice application, is it newly deployed or has been running
for long time and just occured the problem recently? Based on my research,
there is some web thread discussing on the same problem which is caused by
network issue, see the post below:

http://www.topxml.com/Webservices-Enhancements/rn-228881_WSE350-Error---Dime
-attachment-Content-Length-error.aspx

Actually, the error message indicate that the request's content is less
than the expected number in the ContentLength field. It is possible that
some underlying network packet is corrupted or get problem. If possible you
can also test the same webservice on other machine to see whether it will
raise the same error.

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead



==================================================

Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.



Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.

==================================================



This posting is provided "AS IS" with no warranties, and confers no rights
.

Relevant Pages