Import Order Utility issues

What's the error you're getting?  I just got it to work for us and I'm pretty sure I hit all of them at one point or another!  ;-)

Common problems are the location of the file being inaccessable to the database, incorrect formatting of the data, or a problem with your performance set-up so that's where I'd start looking.  The error message should point you to which of these things is causing the issue.

Here's what our IT department passed along:

The error message was:  50000 The file The system cannot find the file specified. does not have a valid
extention() and will be skipped.

Entered on 08/31/2010 at 12:05:06 by Chris Hipschen:
I am currently testing the Ticket Order Import Report to discern if it could be used to seat our "opening night" performances. I've
placed the test import file in multiple locations but the same error is returned for all of them.

Attempted locations:

\\file-server\imports\order (files residing on a file server)
\\file-server\imports\order\ <file:///\\file-server\imports\order\> (files residing on a file server)
T:\imports\orders (files residing on a file server)
T:\imports\orders\ (files residing on a file server)

C:\imports\orders (files residing on the SQL server)
C:\imports\orders\ (files residing on the SQL server)
C:\imports\ (files residing on the SQL server)
C:\imports (files residing on the SQL server)

The test file is simply an Ticket Order Export file, saved to excel, edited, and saved as txt.

From the SQL server the file could be manually opened from all of the above locations.

Responses from our IT team:

A few quick things I can think of to check.  First, in the import set, do not specify the file name, just the path to the folder where the file is located. 

No file name is specified (as indicated in the issue details)

 Second, the file must have a .txt extension. 

File is cmhImport.txt

And lastly, there was a bug discovered where if there were spaces in the file path or the file name it would not recognize the file.  The bug is fixed in v10, but in the meantime just rename things to replace the spaces.  One last thing I had happen once was that I had accidentally inserted a space at the very beginning of my file path that I didn’t see.  Once I found it and removed it, after an hour of trying other things, everything worked.

Path = T:\Imports\Orders

File = cmhImport.txt

Hi Jeffrey,

good day.

a few things need to be awared.

1, full file name has no space, also not too long.

There is limitation of full file name too, we had run into these two troubles before. In the import script, the full command line length is 250? charaters. 

2, You cannot import the file when the file is openning.

3, two tables should check if you want to.

T_ORDER_IMPORT_SESSION

T_ORDER_IMPORT_LOG

if you want to run an imported file again, you can delete the file in T_ORDER_IMPORT_SESSION, then you can import it again.

have fun

Ben