Problem with xmlport import of large flat file

jelittlejohn

Hi,

I have a client that imports a very large item list on a regular basis. This has been working through a dataport in older versions of Navision for some time. We have now upgraded to NAV 2009 R2 and I am working to convert this dataport to an xmlport so they can resume running it themselves. I am currently running the original dataport for them by remoting into their server which is their only machine with the classic client installed.

My original effort gave me a "file is too large" error. After a brief search on the forum, I found references to the "MaxUploadSize" setting in the config file. The file I'm working with is just over 40 MB,so I switched the setting from 5 to 100 and restarted the middle tier service.

Now when I run the xmlport, I get the following error:

"The source text is not valid to import for Fixed or Variable format."

However, I cut and pasted 30 or so rows into a new text file and the xmlport work perfectly. So, I have to think I am still dealing with a file size or record number issue.

Are there any other settings involving the middle tire or the xmlport itself that I am missing? Any thoughts would be greatly appreciated. Breaking this file into pieces would be a major problem for the client.

jelittlejohn

I got some advice from an associate that maybe one of my import fields was too long in a record some where in the text file.

I am using Variable Text as my format, by the way.

Also, I am importing exclusively into text nodes and then manipulating in the BeforeInsertRecord trigger.

So I looked at the width property of each node. They were set to the default, <0>, so I changed them all to larger values including 1024 for my description node because I know that they can be large.

Now I get the following error:

“The server “<servername>” was unable to process the request. The application will close.”

Then the RTC shuts down.

Rob_Hansen

I had this exact same issue a couple months ago. I developed an XMLPort first, and it worked fine with a small flat file. When I tried importing the full file (tens of thousands of rows) it crashed similar to what you're describing. Because this was for a client on NAV 2009 and was for an opening import, I had the option of creating a dataport and moving the logic over. I did that, and it worked with no problems.

I posted in the forum to ask if other people had hit these sorts of issues, as we have no option other than XMLPorts in NAV 2013...so that's scary.

I have no answer or resolution for you...just wanted to say that I've had the same problem and hopefully someone has suggestions here. It may be one that needs to be sent to Microsoft for analysis.