As you are proceeding through the Microsoft Dynamics AX 2012 Data Upgrade checklist, if the configuration options have not been setup properly, users can receive the following error when using the Connect to source database window from the Data Upgrade Checklist:
This error is caused if the Keep update objects 6.0 configuration key found under the Administration tree node has not been marked. Setting configuration options during the Data Upgrade Checklist varies slightly depending on which version of Dynamics AX 2012 is installed.
Once the License configuration window is open, it is important to expand the Administration tree node and make sure that the Keep update objects 6.0 and Keep update objects 5.0 options are marked. The entire tree should be examined and the configuration options for the other modules should be setup the way that your previous source version of Dynamics AX was setup. Some of the key options may have changed or possibly removed, so set up your options based on how they were in the previous version and how you intend to use the functionality in the new version. Failing to mark a configuration option could lead to data from the source environment to not be copied into Dynamics AX 2012.
I am upgrading from ax 2009 sp1 to ax 2012 R2 CU7.
When i try to connect to the source system database. i get a message
Cannot copy table SQLDICTIONARY from source environment to table DEL_SQLDICTIONARY
Exception has been thrown by the target of an invocation.The locale id '1030' of the source column 'NAME' and the locale id '1033' of the destination column 'NAME' do not match.
I have the Keep update objects 6.0 and Keep update objects 5.0 options marked.
Hello Krishna - that error usually indicates that your Dynamics AX 2012 database is using a different SQL collation than your Dynamics AX 2009 database. We don't allow you to change SQL collations as part of the upgrade process, they have to match exactly. If you for some reason want to change the collation, you have to go through that process on either the AX 2009 database prior to the upgrade or wait until after the upgrade is complete. That process typically involves creating a new database and importing all the data from the previous database into the new one.