Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.7K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 115 Navision DOS
- 854 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 615 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 304 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 993 SQL General
- 384 SQL Performance
- 34 SQL Tips & Tricks
- 34 Design Patterns (General & Best Practices)
- Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.7K General
- 1.1K General Chat
- 1.6K Website
- 79 Testing
- 1.2K Download section
- 23 How Tos section
- 260 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Proxy bindings - Maximum string content length quota (8192)
Warazz
Member Posts: 15
Needed to create a proxy to interact from another platform.
(Thanks, Freddy for http://blogs.msdn.com/b/freddyk/archive/2010/01/30/web-services-infrastructure-and-how-to-create-an-internal-proxy.aspx)
I call a function in a codeunit to process an xml file.
All works fine but only with ridiculous small files.
I found numerous of posts concerning following error
The maximum string content length quota (8192) has been exceeded while reading XML data. This quota may be increased by changing the MaxStringContentLength property on the XmlDictionaryReaderQuotas object used when creating the XML reader
...and as many replies saying it still does not work.
Anyone who has experience with bindings?
Almost panicking....
(Thanks, Freddy for http://blogs.msdn.com/b/freddyk/archive/2010/01/30/web-services-infrastructure-and-how-to-create-an-internal-proxy.aspx)
I call a function in a codeunit to process an xml file.
All works fine but only with ridiculous small files.
I found numerous of posts concerning following error
The maximum string content length quota (8192) has been exceeded while reading XML data. This quota may be increased by changing the MaxStringContentLength property on the XmlDictionaryReaderQuotas object used when creating the XML reader
...and as many replies saying it still does not work.
Anyone who has experience with bindings?
Almost panicking....
0
Answers
Now getting a bad request error.
Apparantly this has nothing to do with the proxy.
A direct call of the method of the codeunit reference with a larger file does not work either.
Stupid, stupid!
Forgot the "WebServicesMaxMsgSize" in the CustomSettings.
I had been messing with that before, but as it did not help, I had reset it.
Now I got my binding right, I had to change this again.
Still got errors with a very large file.
Seemed to be timed out this time.
All I had to do was to set the timeout on the proxy service
like service.TimeOut = ms;