Вернуться   AXForum > Microsoft Dynamics AX > DAX Blogs
Забыли пароль?
Зарегистрироваться Правила Справка Пользователи Сообщения за день Поиск Все разделы прочитаны

Опции темы Поиск в этой теме Опции просмотра
Старый 02.11.2012, 23:13   #1  
Blog bot is offline
Blog bot
21,047 / 719 (66) +++++++
Регистрация: 28.10.2006
emeadaxsupport: Cannot copy table SQLDictionary error when Connecting to Source Database during upgrade

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:
  • Error Message: Cannot copy table SQLDICTIONARY from source environment to table
  • Error Message: Exception has been thrown by the target of an invocation.Specified argument was out of the range of valid values.
  • Parameter name: DestinationTableName
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.
  • If using Dynamics AX 2012 CU-3 or higher, or with the Dynamics AX 2012 Feature Pack installed, the License configuration window can be opened from the Upgrade preparation part of the Data Upgrade Checklist under the option Configure application functionality.
  • If using a version of Dynamics AX 2012 RTM prior to CU-3, then the user will have to do the following steps:
    • Press Ctrl-D while looking at the checklist to go into a developer workspace
    • Open the AOT and navigate to to Menus – SystemAdministration – Setup – Licensing
    • Right click on the Licensing menu option and choose Open
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.

Расскажите о новых и интересных блогах по Microsoft Dynamics, напишите личное сообщение администратору.

Похожие темы
Тема Автор Раздел Ответов Посл. сообщение
emeadaxsupport: Writing Data Upgrade Scripts Part 1: Understanding the components of the process Blog bot DAX Blogs 0 10.02.2012 05:16
emeadaxsupport: Microsoft Dynamics AX 2012 Upgrade - Using the State Transfer Tool Blog bot DAX Blogs 0 28.01.2012 02:16
emeadaxsupport: Multiple database data files, table partitioning using multiple file groups… and Microsoft Dynamics AX 2009 Blog bot DAX Blogs 3 04.10.2011 16:30
emeadaxsupport: Identifying damaged Table objects in the AOT MetaData Blog bot DAX Blogs 0 16.03.2010 21:05
emeadaxsupport: Checking Database entries after restoring a Microsoft Dynamics 2009 SQL Database to another Domain or Environment Blog bot DAX Blogs 0 18.02.2010 23:05
Опции темы Поиск в этой теме
Поиск в этой теме:

Расширенный поиск
Опции просмотра

Ваши права в разделе
Вы не можете создавать новые темы
Вы не можете отвечать в темах
Вы не можете прикреплять вложения
Вы не можете редактировать свои сообщения

BB коды Вкл.
Смайлы Вкл.
[IMG] код Вкл.
HTML код Выкл.
Быстрый переход

Часовой пояс GMT +3, время: 03:23.
Powered by vBulletin® v3.8.5. Перевод: zCarot
Контактная информация, Реклама.