Attempting to launch the Import Export tool results in the server throwing error messages.  Started about 7 pm EST last night and continues this morning.  I waited to see if fatal errors would ping the admin, but based on other posts it appears this has gone undiscovered or could be just related to the Import Export sessions on my account.

I have been using account OKFoundry to export Items table and to Import Items.  Successfully exported 3000+ records, imported a test set of 30 records, and then server started to hang after import attempts of 2350 records.  Some routine errors on import like finding Hex values in file, lookup values missing, etc.

Current message from server.  This message has appeared several times.  There is another message related to the warning message system that also appears.

Server Error in '/MethodImpex' Application.

---

Unexpected end of file has occurred. The following elements are not closed: column, row, rows, records. Line 66465, position 28.

[XmlException: Unexpected end of file has occurred. The following elements are not closed: column, row, rows, records. Line 66465, position 28.]
   System.Xml.XmlTextReaderImpl.Throw(Exception e) +95
   System.Xml.XmlTextReaderImpl.ThrowUnclosedElements() +354
   System.Xml.XmlTextReaderImpl.ParseElementContent() +5088225
   System.Xml.Linq.XContainer.ReadContentFrom(XmlReader r) +1053
   System.Xml.Linq.XContainer.ReadContentFrom(XmlReader r, LoadOptions o) +75
   System.Xml.Linq.XDocument.Load(XmlReader reader, LoadOptions options) +350
   System.Xml.Linq.XDocument.Load(String uri, LoadOptions options) +62
   _Default.Page_Load(Object sender, EventArgs e) +481
   System.Web.Util.CalliHelper.EventArgFunctionCaller(IntPtr fp, Object o, Object t, EventArgs e) +25
   System.Web.Util.CalliEventHandlerDelegateProxy.Callback(Object sender, EventArgs e) +42
   System.Web.UI.Control.OnLoad(EventArgs e) +132
   System.Web.UI.Control.LoadRecursive() +66
   System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +2428

Also, now this message.

Server Error in '/MethodImpex' Application.

---

Runtime Error

<!-- Web.Config Configuration File -->

<configuration>
    <system.web>
        <customErrors mode="Off"/>
    </system.web>
</configuration>

<!-- Web.Config Configuration File -->

<configuration>
    <system.web>
        <customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/>
    </system.web>
</configuration>

 Hey jnoneiliv1,

We are currently looking into this and will post an update when we have more details.

TX.

I'm sure you have a better way to diagnose, but my guess is that the import tool is hung on a couple of corrupt, or at least corrupt for the import tool files and the import temp file queue or import buffers just need to be reset or cleared.

I think the import files should be clean going forward.  Even forcing Excel to use all Text data time, saving to a CSV file, and inspecting the file using notepad, the import tool was reporting some Hex value data improperly in the file.

This is fixed, thanks.

This thread can be deleted as there isn't anything helpful for someone else, importing a large amount of records is just a bit tricky.

This is happening to me now:

Server Error in '/MethodImpex' Application.

---

Runtime Error

<!-- Web.Config Configuration File -->

<configuration>
    <system.web>
        <customErrors mode="Off"/>
    </system.web>
</configuration>

<!-- Web.Config Configuration File -->

<configuration>
    <system.web>
        <customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/>
    </system.web>
</configuration>

Skye,

I'm just guessing you might be importing a large number of records when you get this error.

I'm not sure I mentioned it in my other postings, but I found that if I break down large import files into several smaller files I could get good results on import.  It's a bit tedious, but files with 200 to 300 records work much better than 1,000's.

I think that 1000's of records just hangs the web server in some fashion.  Overnite, I think it clears itself, but until then the error messages won't make much sense.  Once it's hung, nothing works properly.

This import tool works much better than the Quickbooks IIF tool from 6 years ago, so I think if you just stick with it you'll be able to get everything done.

Cheers,

James

:) Well it was under 1000, but I'll go even smaller and test ~ THANKS (ok, it wasn't THAT much under 1000 :P)

Yeah, I think around 1,000 tended to bust.  I think 500 ran okay.  Curious what you find out.