Troubleshooting Import Export Tool

1. The export or import operation fails and the error log contains this message: java.sql.SQLException: Access denied for user 'root'@'localhost'

   Solution: Make sure the database is running and that the database connection properties in conf/misc/importexporttool.config are set correctly.

2. The export or import operation fails and the error log contains a message similar to the following: java.lang.ClassNotFoundException: com.mysql.jdbc.Driver

   Solution: Make sure the appropriate JDBC library is on the Import-Export tool’s class path. Copy the JDBC library used by the Elastic Path web applications to the Import-Export tool’s lib directory.

3. The export or import operation fails and the error log contains ConfigurationException and/or SAXParseException messages.

   Solution: Make sure that the export or import configuration file contains well formed XML and that it validates against the corresponding schema in the schema directory (schemaExportConfig.xsd or schemaImportConfig.xsd).

4. The export or import operation fails and the error log contains this message: java.net.ConnectException: Connection refused: connect

   Solution:

   • Ensure that the database and the Elastic Path search web application are available and the search server URL is correct.
   • When connecting to a database and a search server on a remote host, ensure that either the COMMERCE/SYSTEM/SEARCH/searchHost setting or the -Dep.search.default.url Java system property value is set to the search server URL.

5. The export operation completes successfully, but the wrong data or no data is exported.

   Solution: Make sure that the search query in the search configuration file is correct.

6. The export operation fails and the error log contains the following: EpQLParseException: Cannot parse

   Solution: There is a syntax error in the search query string. Check the syntax of your query against the syntax described in Search Query Language.

7. The export operation completes successfully, but no files are created or the files are in the wrong location.

   Solution: Verify the package name and delivery target settings in the export configuration file.

8. The import operation fails because it can’t find the data files to be imported.

   Solution: Verify the retrieval source setting in the import configuration file.

9. The export operation completes successfully, but the summary report indicates that the total number of objects is 0 and the generated files contain no data.

   Solution: Make sure that the type of the exporter in the export configuration file matches the export criteria in the search configuration file. If the types do not match, no data will be exported.

10. A product or category fails to import because the parent catalog does not exist. However, the parent catalog exists in the package.

    Solution: Make sure that the import strategy for the parent object type is set to use Insert or Insert or Update. For more information, see the section Combining Import Strategies.

11. The export operation fails and the log contains a message indicating that the currency code could not be found.

    Solution: This is may be caused by conflicts between the JVM (Java Virtual Machine) used by Import-Export and the JVM that was used by the Commerce Manager when the data was originally created in Elastic Path. Newer versions of the JVM include currency code updates for several countries and the older currency codes are no longer recognized. To prevent the problem, make sure the Commerce Manager and Import-Export tool are both using the most recent JVM supported by Elastic Path. For more information, see Oracle bug JDK-6570259

12. The import operation fails when a data point is imported with the same GUID but any other different attribute.

    Solution: Verify data in the data_policies.xml file or clean up your database.