RE: Logged WSE 2.0 error: WSE350

{\rtf1\ansi\ansicpg936\deff0\deflang1033\deflangfe2052{\fonttbl{\f0\fnil\fprq2\fcharset0 MS Sans Serif;}}
\viewkind4\uc1\pard\lang2052\f0\fs20 Hello Robbert,
\par
\par From your description, one of your ASP.NET webservice(uses WSE 2.0) will randomly report the following exception:
\par
\par =========================
\par Microsoft.Web.Services2.Dime.DimeFormatException: WSE350: In the record
\par -390353390, the number of bytes in the Data field is less than 409600, which
\par is the value indicated in the ContentLength field.
\par ========================
\par
\par 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:
\par
\par http://www.topxml.com/Webservices-Enhancements/rn-228881_WSE350-Error---Dime-attachment-Content-Length-error.aspx
\par
\par 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.
\par
\par Sincerely,
\par
\par Steven Cheng
\par
\par Microsoft MSDN Online Support Lead
\par
\par
\par
\par ==================================================
\par
\par Get notification to my posts through email? Please refer to http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notifications.
\par
\par
\par
\par 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.
\par
\par ==================================================
\par
\par
\par
\par This posting is provided "AS IS" with no warranties, and confers no rights.
\par }

Relevant Pages

  • Re: Authentication in WSE
    ... can't control the Exception publishing mechanism, it's controlled by WSE ... >> the usual best practices for secure authentication, ... >> Though I am relatively new to WSE, my understanding is that the custom ...
    (microsoft.public.dotnet.framework.webservices.enhancements)
  • Why doesnt WSE2.0 work with the autogenerated proxy?
    ... I'm trying to get a basic web service up and running with WSE 2.0, ... An unhandled exception of type ... I downloaded and installed the WSE 2.0 ... Int32 msg, IntPtr wparam, IntPtr lparam) ...
    (microsoft.public.dotnet.framework.webservices.enhancements)
  • Problem with WSE and Win98...(MVP Replies prefered)
    ... I am using Visual Studio .NET 2003. ... I'm using WSE to send text files that must be digitally signed, ... we must alter Web.Config on the client and on the ... but now an other exception occurs: ...
    (microsoft.public.dotnet.framework.aspnet.webservices)
  • Re: Authentication in WSE
    ... Why don't you publish the exceptions using the "Exception Handling" ... > the usual best practices for secure authentication, ... > Though I am relatively new to WSE, my understanding is that the custom ... > can only supply the expected credentials to WSE for internal verification ...
    (microsoft.public.dotnet.framework.webservices.enhancements)
  • Re: Cant instantiate WSE Service class.
    ... I think you should use the Wse version of the proxy class i.e. ... MyWSEServiceWse class. ... > Can someone tell me what I need to do to get this exception to go away? ...
    (microsoft.public.dotnet.framework.webservices.enhancements)
Loading