Frequently Asked Questions

How can I use Intex Autodnld?

You can open a command window by typing cmd.exe in windows run menu. In the command window, change directory to your autodnld /scripts/ directory and use either: or and follow the directions inside. Autodnld will test your connectivity. Make sure that your autodnld.ini file connection uses ship.intex.com. Your firewall should allow https traffic to pass through to ship.intex.com. We suggest that you open your firewall firewall to *.intex.com:443.
For clients whose https connection requires uses a proxy server, you can add this line to autodnld.ini file: If you use a proxy that doesn't need any username/password credential, then you can use: On Windows and Unix/Linux, you can instead use the native CURL command to connect to Intex. CURL has many more options for configuring simple and complicated internet connections. On Windows, you can instead use the proxy settings used by your browser (WinInet Layer) and thus avoid entering your proxy server configuration manually as follows:
The autodnld log, stored in /autodnld/log/autodnld.log, is usually shortened to save space and computer resources. If you are debugging autodnld, please add to your autondld.ini file.

EC:2014 other kinds of timeout during http download?

This error happens during the following scenarios:

In the DownloadFileViaHTTP decoding process, usually when decoding tempBuf.bin from autodnld temp download folder,

The autodnld temp download folder and/or the destination folder are on network mapped drives.

While decoding a large .Z file

Solution: either change autodnld temp folder location to a directly attached drive or add this parameter into your autodnld.ini file: and gradually increase this parameter until the timeout issue goes away. Note that timeout is only supported by verion 5.03/u or later.

Is the download stopped?

If you think that autodnld may not be downloading any data, check to make sure that the size of /autodnld/temp/tempBuf.bin is changing. Autodnld temporarily stores data in tempBuf.bin before unpacking

How to use sendEmail utility?

Autodnld default uses blat.exe to send email for window users. In a command line window change the directory to the /autodnld/scripts/ directory and type: to find all the options that can be customized by blat.exe.
Starting with autodnld version 5.04/5.04u, Autodnld included sendEmail utility to help clients whose SMTP requires TLS or other options that blat.exe doesn't support. Inside autodnld scripts folder, Windows users can type
For Linux/Unix user, type to see all the options that can be used. To use sendEmail instead of blat.exe, Windows users have to add the following line into their autodnld.ini file: This is not needed for Autondnld Linux/Unix version because sendEmail is the default email utility for autodnld Linux/Unix version.

The following are recommended steps to configure sending emails:
First, use a command line window to customize any options needed to make sure you can send a test email to your mail server using either blat.exe or sendEmail.
Second, add the following options into autodnld.ini file using a text editor, or running "autodnld -config" Additional options can be passed in using the paramter mail_exe_option:
For example, if your mailserver requires TLS and authentication username/password, autodnld.ini should have these lines (order can be different): Additional information can be found: mail_exe_option

Download inf file failed in "autodnld -t" test (applies to https download)

At the end of "autodnld -t" test, you got message:

• Re-enter your password by running "autodnld -config" to get the prompt to change your password.
• Make sure that "connection=ship.intex.com" is included in your autodnld.ini file. The connection is case sensitive.
• If above two methods won't resolve your issue, please send tempbuf.bin file in your temp folder to autodnld_help@intex.com.

Download cmo shipment failed but other file downloading seems OK (applies to https download)

In some cases "autodnld -t" works, autodnld could access shipment directory and download shipinfo.zip file and other perfdata,histdata, etc. However, autodnld could not download the cmo shipment and got "EC1010 connection error".
This is usually caused by Intex redirecting your shipment to a different server for load-balancing. Please confirm that your firewall allow list contains *.intex.com.

How can I fix a "unpacking" or "uncompressing" file error?

If you are running Windows, make sure you are running version 4.02 or higher. If you are running UNIX, make sure you have symbolic links for gzip, tar and unzip in the autodnld/scripts subdirectory.
Regardless of operating system, make sure the compressed file was fully downloaded. It should be inside the temp directory used by autodnld. Try uncompressing it manually to make sure it is not damaged. For example, the following command would unzip a .Z file:

"Cannot see subdir" error?

You get an email similiar to the following:
This error is caused by directory write privilege issues or the directory running out of space. Try:

• Logging in to the server running autodnld. Make sure you log in on the same account that autodnld uses.
• Open a command window, and run a directory list using "dir MISSING_SUBDIR"
• If you encounter an error saying "the directory is not found", try to create the directory using the command "mkdir MISSING_SUBDIR", then resolve any issues that mkdir discovers.

How do I upgrade my version of autodnld?

Please use the sidebar link for Upgrade Instructions.

How do I find out what version of autodnld I am running?

You can run to find out the version. The emails and log files for autodnld also include the version number.

We missed some shipments due to technical problems; what should we do?

There are no additional steps required if you were only off-line for a few days. Just run autodnld, and it will download any missed shipments.

Autodnld creates a DBStatus report at the end of each download. This report contains a list of any files that are missing or out of date on your system. If autodnld creates a dbstatus report, please email it to autodnld_help@intex.com, and Intex will include any missing files in your next shipment.

Autodnld checks for new versions of remit data files on each run, and will will automatically update any missing or damaged files.

How can I detect when file(s) have been downloaded without using email?

You can find the contents of email messages (even if the weren't actually sent) in /autodnld/log/email.log.
For CMO data, you can check the age and the contents the DBStatus report, which is in /autodnld/log/dbstatus.rpt.

How can I troubleshoot sending emails on Windows?

If autodnld is having trouble sending emails, and if you are running under Windows, we suggest a multi-step debugging process:

• Run autodnld in test mode mode, and try to send a test email.
• Verify the spelling of the email directives in the .ini file: these are the correct labels that can be used:
  • email_to
  • mail_from
  • mail_sender
  • mail_server
• Verify that you can see the mail server on your network
• Run the program "blat.exe" manually  run blat.exe manually

Run autodnld in "test" mode, and try to send a test email

1. Go to the autodnld scripts subdir in a Command Window
2. Run
   autodnld.exe -t
3. Run the email test
4. Skip the connectivity test
5. Verify that you have received an email.

Run Blat Manually
Autodnld uses an open source program called "blat.exe" to send emails. The program resides in autodnld scripts directory. If you are having problems sending email, you can try running blat in a command window to test the sending of email. Open a command line window. cd to Autodnld scripts directory. Type: It will give a lot of options that you can use with blat program,i.e., how to specify a port, file with the message body, etc. Here is one quick test you can run: Be sure to use a hyphen (-) as your first argument, followed by -body "your message" if you don't want to send a file.
You will see something like this if the mail is sent successfully.
If you see any error, you have to work with your mail server administrator to figure out why.

We are downloading pooldata for the first time; what do we do?

Autodnld will automatically download and create the necessary directories for pooldata. You will also need to allocate more disk room for Intex data. Please contact Intex at autodnld_help@intex.com for information on how much data to expect.

You may want to purge pooldata by adding a line to the ini file: pool_data_purge

We are downloading mbspooldata, does dbstatus check mbs pools? Is there a separate check for pools?

There is a separate report for MBS pool data files. It is stored in /autodnld/log/mbsstat.qa. If you receive emails from autodnld, you will receive an email listing missing mbspool files.

Does Autodnld support replicating Intex ship data to another location?

Autodnld no longer supports the replication feature. Intex recommends that clients look to their own IT support for a suitable backup/replicate solution.

How do I set up autodnld so that I can run it from a pair of redundant machines?

To do this, you need to install autodnld on a network drive that all the machines can see. Then run autodnld normally from the network drive on each of the redundant machines.

By running autodnld off a network drive, autodnld will log and download files, so the the same shipment twice is not processed twice.

How can I control which CMO shipments autodnld will pull?

Change to the autodnld\scripts subdir. Then run on Windows. Unix clients should use This will mark all available shipments as processed. Then change to the autodnld\log subdir and edit the file "CMOTrack.log". Remove the lines containing the shipments you would like to download. Finally, run autodnld normally and download the selected shipments.

Where do I find the list of files being downloaded in each shipment?

If you have save_serialized_zip_files=1 inside your autodnld.ini file, autodnld saves shipinfo.timestamp.zip inside the log directory. The timestamp is a ten digit UTC number so it will change from shipment to shipment.
You have to make sure to delete zip file by themselves afterwards to make sure they don't run out of disk space later.

Inside this .zip file is a file shiplist.txt. This file contains a list of the files downloaded in this shipment.
Shiplist.txt is a "|" delimited file with 3 columns:
1) The location of the file on the Intex server for Autodnld purposes
2) The name of the file stored in your Intex data directory
3) the size of the file in KB

What directory permissions do I need to set for autodnld to run

Under Windows, autodnld runs with a user and password as set by the job scheduler. Under UNIX, autodnld runs with a user and password as set by crontab.

In either case, autodnld unpacks a zip file, and tries to either overwrite or to create new files in cmo_cdi and cmo_cdu directories within your Intex data directory.

To find out the location of your cmo_cdi and cmo_cdu subdirectories, you can look at the /autodnld/scripts/autodnld.ini file.

You should set the rights on the cmo_cdi and cmo_cdu subdirectories to allow file and/or subdirectory creation by the user that autodnld is running as. Keep access read-only for your end users.

If I am an intraday client, and all the intraday shipments are downloadeded successfully, why do I need to redownload those files at the end of the day?

The Intraday download directory on the Intex server will be purged every day at 4:00 PM EST. To guarantee clients have the complete data set, all intraday shipments will be included again in the nightly shipment.

Where do I find the list of files being downloaded in intraday shipment?

The autodnld\log\intraday\shiplistDone.txt file keeps track of the intraday files being downloaded each day. This file is erased if a new regular shipment is found on intex server.

Alternatively, if you have save_serialized_zip_files=1 inside your autodnld.ini file, autodnld saves shipinfo.timestamp.zip inside log/intraday directory. shiplist.txt is inside this zip file. The timestamp is a ten digits UTC number. So it will change during the day. You have to make sure to delete zip file by themselves afterwards to make sure they don't run out of disk space later.

ERROR: we could not erase the lock file; another process is holding it open

We use a lock file to prevent multiple instances of autodnld from running at the same time on Windows. As autodnld starts it must be able to erase this file if it exists. Autodnld then opens a file with this name for write, and holds it open until the autodnld cycle is complete. It then closes the file and erases it. The lock file is stored at /autodnld/log/autodnld.is.running.txt.

If you receive a lock file error, you probably have a instance of autodnld.exe that is already running that you have to kill. To do so, press ctrl-alt-delete, and click on the "Task Manager" button. Press the "Processes" tab, and look for

• autodnld.exe
• autodnld_run.exe
• blat.exe

Click on the line(s), and then click on the "End Process" button. This should clear up the error. Note: blat.exe could be from some other non-autodnld process you have running so be careful before you kill it.

If there are no autodnld related process running and autodnld still cannot delete the file, rebooting your computer usually resolves the issue.

What causes an error like: PKZIP: (W1) Warning! can't create: cmocusip.inf?

Please see the FAQ regarding upacking or uncomparessing files available here

What causes the error "Unknown host" in my autodnld.log file or my screen

Check your /autodnld/scripts/autodnld.ini file to make sure that your connection paramter is set to ship.intex.com. If this is set up correctly, try running autodnld in test mode: This will provide any additional details on issues that autodnld encounters.

The unknown host error may also be an indication that your Domain Name Service (DNS) is not configured correctly.

Autodnld seems to run OK, but the dbstatus program doesn't run properly

At the end of a successful download of CMO data, the dbstatus program is run by the autodnld script. DBStatus compares your copy of Intex data against the master files at Intex, and produces a report, stored in /autodnld/log/dbstatus.rpt, of any missing or damaged files. DBStatus uses cmo_cdu/mbsstat.qa for the comparison.

To troubleshoot DBStatus issues, try:

• Open /autodnld/scripts/autodnld.ini using a text editor, and make sure that "dbstatus_check=none" is not included in the file. Remove this line if you find it.
• Change to the autodnld/scripts subdirectory, and run the dbstatus program without any arguments. This will tell you how to use the program. Then run the program, specifying the cmo_cdi, cmo_cdu and report path.

When you get an error like this: you should try unzipping the file by hand in a command window, so you can see any errors happening.

You can find the command that autodnld executed by searching for the "cmd=" line in the autodnld.log file.It may be easier to create a batch file, since the paths are so long.

For the case above, you would put yourself in the autodnld\scripts directory and run this command: Any errors that happen should appear in the window as the command runs ... you might have to press control-s to freeze the output so you can read the error. You may need to adjust your command windows settings to show enough history to view the entire process.

uncompressing or unpacking a data file

See FAQ: How can I fix a "unpacking" or "uncompressing" file error

error 10060 from WinSock

The name of your mail server is incorrect. Please consult the windows email debugging FAQ.

Did autodnld Run Without Errors?

Autodnld will send you an email if it encounters an error during a run, and is configured to send email. See the manual for more information emails and autodnld.

You can also check three of the autodnld log files in the /autodnld/log directory:

• autodnld.log
• autodnld.sum.log
• email.log

More information on autodnld.sum and email.log is available in the manual. autodnld.log contains a full record of the most recent autodnld sessions.

Intex also provides optional Shipment Emails to alert you when a shipment is available, and when you have a shipment pending for a few days. To enable this feature, please contact Intex at autodnld_help@intex.com and ask to turn on shipment emails.

"file in use" errors

On Windows, autodnld cannot replace a file that is in use. Autodnld will keep files that it could not copy within the /autodnld/temp/ directory, and will try to copy the files again during its next run. If the file is continuously in use, you will begin to receive DBStatus reports since the file is out of date.