WSE/DIME - WSE352: The size of the record uuid:{g-u-i-d} exceed its limit

WSE/DIME - WSE352: The size of the record uuid:{g-u-i-d} exceed its limit

• SimonH6804

  Hi.
  How really big are these files
  I am very interested in this because I have a problem uploading a file bigger than 64 MB through a web service.
  
  Thanks.
  Mircea
  

• Carlos Voltolini Neto

  Hi Joseph.
  
  Unfortunatelly I did not find any solution to this problem yet.
  
  Did you try MTOM from WSE 3.0
  
  Regards,
  Mircea
  

• Ronald Cuzco

  Are you using WSE/DIME or native Web Services (Base64 encoded string)
  
  I just tested a 70 meg file and it downloaded fine using DIME. (I haven't developed upload yet, but I have no reason to assume this will be a problem. I'll report back once I've got upload developed and tested.)
  
  Hope this helps,

  
  
  

• opc3

  Hi Mircea,
  
  Sorry, no solution. I won't be working on this again for a while. 100meg download and 64meg upload is adequate for our needs for the forseeable future.
  
  Hopefully, by the time we need more, WSE 3.0 will have corrected this and will be in production.
  
  Good luck with your issue! Please post back if you do find a solution.
  
  Microsoft: Please help us out here!
  
  

• losoriomx

  Oops, my bad.
  
  My mistake was with the client config file. The name of the driver is FetchFile so I mistakenly created FetchFile.config. Once I renamed this to App.config, I am able to transfer really large files.
  
  
  

• Algorith

  Hi Mircea,
  
  I am seeing results identical to yours. I can download 100MB files sucessfully, however on upload, I am facing a 64MB limitation, even though I've encoded my web.config file to support a much larger filesize:
  
  <configuration>
    <microsoft.web.services2>
      <messaging>
         <maxRequestLength>-1</maxRequestLength>
      </messaging>
    </microsoft.web.services2>
    <system.web>
       <httpRuntime useFullyQualifiedRedirectUrl="true"
           maxRequestLength="102400"
           executionTimeout="60"
       />
     </system.web>
  <configuration>
  
  P.S. Why is this maxRequestLength issue so disorganized Why must it be specified as both an attribute of httpRuntime as well as a node of messaging Also, note that the legal values for these are different. For the latter, you can specifiy -1 to indicate no limitation, whereas the former must be a positive number. I guess DIME is still on the bleeding edge. Hopefully this will coalesce into a coherent standard.
  
  

• Joseph Torre

  Thanks Per!

  We do intend to convert to WSE 3.0 / MTOM eventually. The link you posted will be very helpful!

  Thanks,

  
  
  

• John Cronin

  For anyone having stil having the problem at this point.
  
  This was what me helped out.
  
  http://groups.google.de/group/microsoft.public.dotnet.framework.webservices/browse_thread/thread/fd27360ce079e142/aa067808a8a5b0ed lnk=st&q=WSE352&rnum=1&hl=de#aa067808a8a5b0ed
  
  Regards,
  Alexander
  
  
  

• Slow

  Hi Mircea,
  
  As I mentioned earlier, I am able to download very large files (70 meg) using DIME. Unfortunately, I'm finding that I'm running into the infamous 4 meg limitation when trying to upload large files.
  
  I have the following block in my App.config and Web.config files:
  
      <messaging>
         <maxRequestLength>-1</maxRequestLength>
      </messaging>
  
  But this seems only to be effective for Download.
  
  You mention that you are uploading files up to 64MB. How do you acheive that upload size Did you need to do anything specific to break the 4MB barrier
  
  Thanks,
  
  

• Kirill Osenkov

  Just a thought, you might want to try chunking the file into several attachments. It may be that the maxRequestLength determines the total for all attachments on a single request, however there may be a fundamental 64 meg limit for a single attachment. (Although this doesn't seem to be a problem on download.)
  
  Whatever, I'm just speculating here...
  
  

• Fabio Pintos

  Hi

  This is a solution to your problem using the technique mentioned above.

  http://www.codeproject.com/soap/MTOMWebServices.asp

  
  

• Tim Sohn

  Hello,
  I am still having Problems with this. I am using WSE2 and need to receive DIME-Attachments.
  I always receive an Limit Exceedede exception when transfering more than one File. Each of these files is about 1,5 Mb big. I have 6 of them. So there shouldn't be any problem, should there
  I tried to add the
  
  <microsoft.web.services2>
  <messaging>
  <maxRequestLength>-1</maxRequestLength>
  </messaging>
  </microsoft.web.services2>
  
  block to my app.conf. But then Exception is thown while initiating the Service. Configuration not known is said.
  
  Can please anyone give me a hint. I need this to get working.
  
  Thx,
  Alexander
  
  
  

• hda

  Hi.
  
  What I have done is sending a file (using DIME attachment) from a client to server.
  In web.config (on the server) I've set this:
  

  <httpRuntime maxRequestLength="xxx"/>
  and
  

  <messaging>

  <maxRequestLength>xxx</maxRequestLength>

  </messaging>
  
  That is all that I set. With this I succeeded to send 64 MB. But I want to send more. :)
  
  Thanks.
  Mircea

  
  
• WSE/DIME - WSE352: The size of the record uuid:{g-u-i-d} exceed its limit