XMLPort File Size in RTC

matttrax
Member Posts: 2,309
When exporting data using an XMLPort from the RTC I am getting the error "The size of the file you are trying to use is too large." Confirmed that when exporting the data in batches the total file size is 6 MB and I know the service configuration file has the MaxUploadSize parameter defaulted to 5. Changed it to 10 (as high as 500 actually just for grins), restarted the service, but still the same error.
Confirmed that I was modifying the correct configuration file by looking at the service properties and the path to the executable. When I restart that service it kicks me out of my current RTC session as I would expect. So I am reasonably confident that I am changing the correct configuration file.
Everything works fine with the test service running on the same machine. The only difference between the config files are the database name, instance name, and port number. There is nothing in the event log on either the client machine or service tier to indicate what is wrong (no error at all).
Anyone have a clue where I could start?
Confirmed that I was modifying the correct configuration file by looking at the service properties and the path to the executable. When I restart that service it kicks me out of my current RTC session as I would expect. So I am reasonably confident that I am changing the correct configuration file.
Everything works fine with the test service running on the same machine. The only difference between the config files are the database name, instance name, and port number. There is nothing in the event log on either the client machine or service tier to indicate what is wrong (no error at all).
Anyone have a clue where I could start?
0
Answers
-
Did you check this
http://blogs.msdn.com/b/nav/archive/2011/11/22/manage-max-no-of-xml-records-to-send-option-from-role-tailored-client-with-net-interop.aspx
Before this, Max. no. of XML records to send is 5000 only..0 -
There are almost 90,000 records in the table and it is exporting from one but not the other.0
-
Also, even though it is an XMLPort, it is exporting in flat file format. So I'm not sure that the number of XML records applies. Since they are on a build lower than that hot fix I don't think it matters.0
-
Ended up I had to kick every single other session out. That includes Classic users, application servers, web services, other service tiers, etc. Not sure which of them was the actual offender, but I got it down to only me in the database, logged out of classic, and restarted the service tier that needed the config file change.0
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
- 116 Navision DOS
- 851 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 617 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 320 Dynamics CRM
- 111 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 990 SQL General
- 383 SQL Performance
- 34 SQL Tips & Tricks
- 35 Design Patterns (General & Best Practices)
- 1 Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.6K General
- 1.1K General Chat
- 1.6K Website
- 83 Testing
- 1.2K Download section
- 23 How Tos section
- 252 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions