Good to know about AxDBUpgrade.exe

-
IMPORTANT!
AxDBUpgrade.exe MUST BE RUNED! on the computer that hosts the AX 3.0 and AX 2009 database. The reason is that the program retrives information from the AX 3.0 database, stores it in the temp folder and does a bulk insert into the AX 2009 database. This also means that the user running the application will require permissions on the sql server to do bulk insertion.

Problem:
When trying run the AxDBUpgrade the following error can occure, "Cannot read the list of columns to be upgraded"

Solution:
You have to start the AX 3.0 environment, import the PrivateProject_UpgradeColumnList.xpo from the Dynamics AX 2009 dvd. When the form is imported, run it and press the generate button. This will fill the table UpgradeColumns with information about which fields that should be upgraded to 64-bit by the AxDBUpgrade tool.

Problem:
When trying to start AxDBUpgrade.exe on a operating system with 64-bit architecture you might encounter the following error "The application failed to initialize properly (0xc0150002). This is because AxDBUpgrade.exe is writen for the x86 architecture.

Solution:
This is solved by installing "Microsoft Visual C++ Redistributeable Package (x86)" which can be found on the Dynamics Ax 2009 install DVD. Start the setup procedure and the package will be installed as it is a prerequsite for installing AX. When the package have been installed just end the installation. Installing this package does not require a reboot of the computer.

Comments

Post a Comment

Popular posts from this blog

How to disable auto enabled flight key using KillSwitch

-
Image
Microsoft is introducing new functionality into Dynamics 365 for Finance and Operations with flight keys in every other new release. For this they use  Flight  classes so that the changes are automatically applied and can be reversed.  Example of a flight class that control the functionality of a new set of functionality.  When a flight key that enable functionality can be found in the flight key table  SysFlighting To disable the functionality don't delete or change the enabled flag on the flight record, instead insert a KillSwitch  record. The KillSwitch record will ensure that the flighed functionality will stay disabled as long as it exist in the flight table.  In an environment that Microsoft maintain can raise a support ticket in LCS to disable specific flight keys.  SQL statement for insert the KillSwitch record.  DECLARE @flightName NVARCHAR(100) = 'WHSWorkCancelForcedFlight_KillSwitch' IF NOT EXISTS (SELECT TOP 1 1 FROM SysFlighting WHERE flightName = @flightName
Read more

Technical intro to Feature management in D365FO

-
Image
Feature management is an alternative to configuration keys for releasing and introduce a new features into D365FO.  MS is still releasing updates around the framework but the existing state as per 10.0.9 provide all we need to get started with releasing functionality that is controlled by the feature management framework.  The key to the feature framework is the feature class, in my example below see the class  pekTestingFeature. It is used as a descriptor for the feature and the flag to indicate if the feature is enabled or not. Once the class is created and compiled, users can navigate to Feature management  under System administration  and enabled/disable the feature. It is possible to make a feature enabled by default or disable the possibility to disable the feature. If the feature doesn't automatically appear, run the Check for updates button.   The feature class can be applied to menu items and menus. If enabled the menu item or menu will be visible to the
Read more

Continuous integration and deployment Power platform FinOps tweaking

-
Image
If you are working with the new unified development environments and CICD pipelines described here .  You might find the fact that we have to update the pipeline with the platform and application version annoying.  A quick way to get around this if you are using azure hosted agent pipeline as per this repo is to pull the number from the package.config and using it in the create deployable package task as per the two example tasks below.  The first powershell task will pull the version from the nuget files and save it to variable that can be reused in later tasks within the job. 
Read more