If you are using FRx when you run the Microsoft Dynamics AX DB Upgrade Preparation tool it will fail on the frl_entity table and stop the process of copying tables to the new Microsoft Dynamics AX database. The process fails because the frl_entity has an identity column.

To prevent his failure you need to complete one of the following options:

Option 1:

Delete the frl_entity table before running the Microsoft Dynamics AX DB Upgrade Preparation tool. When the upgrade to Microsoft Dynamics AX 2009 is finished, use Data Transformation Services (DTS) to restore a backup of the frl_entity table from your Axapta 3.0 database to your new Microsoft Dynamics AX database.

Note
The same process of using DTS can be used for any table in the Dynamics AX database that does not also exist in the AOT. Use the DBPrep_nonAOTtable_SQL.sql or DBPrep_nonAOTtable_Ora.sql scripts to identify those tables affected.

1. Before you start the Microsoft Dynamics AX DB Upgrade Preparation tool make a backup of your Axapta 3.0 database.

2. Delete the frl_entity table in your Axapta 3.0 database.

3. Run the Microsoft Dynamics AX DB Upgrade Preparation tool and complete the upgrade to Microsoft Dynamics AX 2009.

4. In SQL Server 2000 Enterprise Manager or SQL Server 2005 Management Studio restore the backup of the Axapta 3.0 from step 1. Export the frl_entity table from the Microsoft Dynamics AX 3.0 database to the Microsoft Dynamics AX 2009 database.

Option 2:

If you are using Oracle, be sure that the Oracle 32-bit client (Administrator SKU) libraries are present before you run the Microsoft Dynamics AX DB Upgrade Preparation tool.

The Microsoft Dynamics AX DB Upgrade Preparation tool creates interim files that may falsely trigger your virus scanner, causing the DB Upgrade Preparation Tool to fail.

If this problem occurs, disable your virus scanner and restart the Microsoft Dynamics AX DB Upgrade Preparation Tool. Be sure to start your virus scanner again after you are done using the Microsoft Dynamics AX DB Upgrade Preparation tool.

Issue: The Microsoft Dynamics AX DB Upgrade Preparation tool fails and a syntax error is displayed while creating objects in the target database.

Possible cause #1: You have non-AOT-based tables in the source database schema.

Solution: Follow the steps in the "Non-AOT-based tables" section of the The Microsoft Dynamics AX DB Upgrade Preparation tool topic.

Possible cause #2: In your Microsoft Dynamics AX 3.0 database, you have used database reserved keywords as object, index, and constraint names.

Solution: Rename the object, index, and constraint names that use database reserved words to something else within the Microsoft Dynamics AX 3.0 database, run the Microsoft Dynamics AX DB Preparation tool to copy your data, rename the object, index, and constraint names back to their original names. For example, if one of the table columns is named INTERNAL, rename to XINTERNAL and after you run the Microsoft Dynamics AX DB Preparation tool, rename the table column back to INTERNAL.

Issue: After the Bulk Copy Process (BCP) starts, the scripts fail on the first table AccessRightsList.

Possible Cause: The Microsoft Dynamics AX DB Upgrade Preparation tool does not have rights or cannot access the BCP temp folder.

Solution: The location of the BCP temp folder for SQL Server must be local to the destination SQL server where the new Microsoft Dynamics AX 2009 database is located.

Issue: The Microsoft Dynamics AX DB Upgrade Preparation tool does not open because of an unhandled exception on startup.

Possible cause: You might not have installed the prerequisite software during the installation of Microsoft Dynamics AX 2009.

Solution: Install the prerequisite software from the installation media.