Tuesday, May 08, 2012 8:34 AM
I've set the max upload file size attribute to 32 mb and, even though the platform manages to upload a 32mb file, when I'm trying to create, through sdk, an annotation with the same file, I get an error saying that there was no endpoint listening.
What do I need to set/use on the webservice instance so that I can also create large attachments through code?
My app seems to work only for at most 17MB files.
- Edited by Florin Sander Tuesday, May 08, 2012 8:34 AM
Thursday, May 10, 2012 10:34 PM
Can you run fiddler and check the size of the message sent via the SDK? I have a suspicion that the message has bloated due to encoding after the message is serialized.
Thursday, May 17, 2012 9:01 AM
In the end I convinced the client to shrink their attachments, so I'm not going to pursue this for the time being.
What you're saying makes sense, though, and I'm gonna keep that in mind, but, if that is the case, what would be the solution to transmit the file? First create the annotation with a dummy then update with the actual file?
Thursday, May 17, 2012 2:04 PMModerator
I think you ultimately run into a limit of the maximum size of a web service call, which I believe is 64MB. Encoding does increase a file size, but it doesn't double it. I've had one CRM implementation where attachments could be up to 40MB in size, and that worked fine.
The sdk assemblies make a WCF call to CRM. There are several WCF parameters that might limit the size of a single call. The SDK assemblies don't use an app.config file, but you should be able to access the WCF parameters programmatically
Separating the create and the update wouldn't make any appreciable difference, as the update would still have to contain the whole body.
Microsoft CRM MVP - http://mscrmuk.blogspot.com/ http://www.excitation.co.uk
Monday, May 28, 2012 1:33 PM
Thank you for your input.
At the moment I'm not sure I know how to access those parameters, but I'll look into it next time I need something like this.