Muokkaa

Jaa

Data upgrade process for AX 2012 to Dynamics 365 Finance + Operations (on-premises)

  • Artikkeli

Important

Upgrade is currently only supported from either Dynamics AX 2012 R2 or Dynamics AX 2012 R3. For each release, please update to the latest available cumulative update before upgrading to latest finance and operations application release.

This article explains the process for doing a data upgrade only. For information about how to do a code upgrade, see the upgrade guides that are available for cloud versions. The code upgrade tooling is available only through Microsoft Dynamics Lifecycle Services (LCS).

AX 2012 upgrade to Dynamics 365 Finance + Operations (on-premises)

Two upgrade methods are currently supported:

  • Upgrade from your existing Dynamics 365 Finance + Operations (on-premises) environment – This method is available only in version 10.0.31 and later. It's the recommended method when you're testing the upgrade end to end.
  • Upgrade from inside the VHD – This method involves copying your database into the virtual hard disk (VHD) and running the upgrade from inside the VHD. Overall, this method is easier.
  • Upgrade where the VHD points to your database – This method involves pointing the VHD upgrade process to your database. The upgrade process is still run from inside the VHD.

Note

The VHD doesn't require external network access to run the upgrade process.

Prerequisites

  1. Sign up for a preview subscription.
  2. Install the pre-upgrade checklist. For more information, see Installation.
  3. Go through the data upgrade preparation steps. You can skip the "Set up user mapping" step. This step is relevant only for cloud-hosted upgrades.
  4. Make a backup of your database (MicrosoftDynamicsAX). For more information, see Create a Full Database Backup.

VHD prerequisites

If you will use a VHD to perform the data upgrade, you must also be aware of the following prerequisites:

  1. In LCS, go to the Shared asset library by selecting the tile on the right side of the page. Then, under Select asset type, select Downloadable VHD, and download all parts of the VHD package that most closely matches the version that you will upgrade to in your on-premises environment. The image requires a large amount of disk space. Therefore, be sure to download and extract the package on a drive that has enough free space.

  2. The files that you downloaded are a self-extracting zip file. Extract the VHD to a location that has a good amount of free space.

  3. Use Hyper-V to start a virtual machine (VM) and attach the VHD. (Note that the VM must be Generation 1.)

  4. Connect to the VM. For information about the credentials, see Running the Virtual Machine (VM) locally.

  5. Depending on your planned on-premises target version of 10.0.x and the VHD image that you downloaded, you might have to download and apply the required application update and platform update from the Shared asset library. Under Select asset type, select Software deployable package. For more information, see Install deployable packages from the command line.

    Important

    In any case, make sure that you've applied the most recent quality update to your VHD, to ensure that it contains the most recent fixes for doing data upgrades.

  6. If you have any extensions or customizations, install them on the VHD now. Otherwise, the upgrade process will remove any data that is related to customizations. If you must prepare your environment before the upgrade, check with your independent software vendor (ISV) or value-added reseller (VAR).

Dynamics 365 Finance + Operations (on-premises) prerequisites

If you will use a Dynamics 365 environment to perform the data upgrade, the following prerequisites must be in place:

  1. A Dynamics 365 Finance + Operations (on-premises) environment with version 10.0.31 or later has been deployed using a demo data backup.
  2. The latest quality update has been applied to your environment.
  3. If you have any extensions or customizations, apply them to your environment now. Otherwise, the upgrade process will remove any data that is related to customizations. If you must prepare your environment before the upgrade, check with your independent software vendor (ISV) or value-added reseller (VAR).

Upgrade from a Dynamics 365 Finance + Operations (on-premises) environment

  1. Disable all Application Object Server (AOS) and Management Reporter (MR) nodes by using Service Fabric Explorer.

    Tip

    Disable one node at a time. When you disable the last node, Azure Service Fabric will try to ensure that the services that are assigned to that node type can be put in another node. However, because no other node is available, Service Fabric won't successfully disable the node. Therefore, you must force the operation by restarting the last node from Service Fabric Explorer. After the restart, the node will be disabled.

  2. Delete your existing demo data database.

  3. Restore the backup that you created with the same name as your existing demo database. For more information, see Restore a Database Backup Using SSMS.

  4. Open Windows PowerShell in elevated mode, go to the Infrastructure folder in your file share, and run the following commands.

    .\Initialize-Database.ps1 -ConfigurationFilePath .\ConfigTemplate.xml -ComponentName AOS
.\Configure-Database.ps1 -ConfigurationFilePath .\ConfigTemplate.xml -ComponentName AOS

  5. Run the following SQL command against your restored database.

    MERGE [dbo].[SQLSYSTEMVARIABLES] AS VARIABLES
USING (values('RUNDATAUPGRADE', '1', 20, NULL)) as NEWVALUE (PARM, VALUE, IPARM, IVALUE)
ON (VARIABLES.PARM = NEWVALUE.PARM)
WHEN NOT MATCHED THEN
    INSERT (PARM, VALUE, IPARM, IVALUE)
    VALUES (NEWVALUE.PARM, NEWVALUE.VALUE, NEWVALUE.IPARM, NEWVALUE.IVALUE);

  6. Activate one of your AOS nodes by using Service Fabric Explorer.

  7. After the AOS node is activated and the service starts, the data upgrade process is automatically triggered. You can monitor the data upgrade process by using the guidance in Monitoring the data upgrade.

  8. If the data upgrade fails, you can find the data upgrade logs in the service log folder. The path will resemble the following example:

    C:\ProgramData\SF\<nodename>\Fabric\work\Applications\AXSFType_App95\log

  9. After the data upgrade succeeds, if you have customizations from ISVs or VARs, check whether you must run some post–data upgrade scripts.

  10. Re-enable the remaining AOS nodes and the MR nodes.

Upgrade from inside the VHD

  1. Restore the backup that you created to the OneBox VM. For more information, see Restore a Database Backup Using SSMS.

  2. Optional: If the name of your restored database isn't AXDB, open Windows PowerShell as an administrator, and run the following script.

    .\Configure-On-Premises-Upgrade.ps1 -DatabaseName '<DB-name>'

    Note

    • The preceding PowerShell script is provided in the Appendix of this article.
    • Replace <DB-name> with the name of your database (for example, AXDB). If you want to edit more values, see the Appendix of this article.

    The script will run a database connection test to verify that the information that you provided is valid.

  3. In LCS, go to the Shared asset library. Under Select asset type, select Software deployable package, and then select AX2012DataUpgrade-10-0-x to download the MajorVersionDataUpgrade.zip file.

  4. Copy the file, paste it in the desired location (for example: c:\D365FFOUpgrade\), and unzip it.

  5. Open a PowerShell window as an administrator, change the directory to the folder that you just unzipped, and run the following commands.

    .\AXUpdateInstaller.exe generate -runbookid="MajorVersionDataUpgrade-runbook" -topologyfile="DefaultTopologyData.xml" -servicemodelfile="DefaultServiceModelData.xml" -runbookfile="MajorVersionDataUpgrade-runbook.xml"
.\AXUpdateInstaller.exe import -runbookfile="MajorVersionDataUpgrade-runbook.xml"
.\AXUpdateInstaller.exe execute -runbookid="MajorVersionDataUpgrade-runbook"

    Note

    For information about how to monitor the upgrade, see the Monitoring the data upgrade section in the Appendix of this article.

  6. After the upgrade process is successfully completed, back up the newly upgraded database. If you have customizations from ISVs or VARs, check whether you must run some post–data upgrade scripts.

  7. Restore the database into your on-premises environment's SQL Server, but give it a name that differs from the name of the AX 2012 database (for example, name it AXDBupgraded). The restored database must be configured. Follow the steps in Configure the Finance + Operations (on-premises) database.

  8. Deploy a new Dynamics 365 Finance + Operations (on-premises) environment.

    • If you have customizations, follow these steps:

      1. In LCS, go to the Shared asset library.

      2. Under Select asset type, select Model, and then download Dynamics 365 Finance + Operations on-premises, Version 10.0.x Demo Data. Select the version that is closest to the 10.0.x environment that you will deploy as the on-premises baseline.

      3. Use the restore backup option for SQL Server to create a new database from this file. (Typically, this database is named AXDB.) For more information, see Restore a Database Backup Using SSMS.

      4. The demo database must be configured. Follow the steps in Configure the Finance + Operations (on-premises) database.

      5. In LCS, set up a new environment, and deploy it with version 10.0.x. For more information, see Set up and deploy on-premises environments (Platform update 12 and later). When you deploy the environment, the name of the database that you specify should be the name of the database that you created earlier (typically AXDB).

      6. Apply your own customizations, and ISV and VAR modules, to the newly created 10.0.x environment. Otherwise, when the environment is initially synced with the database, it will delete any customization-related or extension-related data.

      7. Shut down on-premises Application Object Server (AOS), Business Intelligence (BI), and Management Reporter (MR) servers, or stop the services from the Azure Service Fabric portal by selecting Deactivate (Restart).

      8. Rename or delete the demo database (typically AXDB) that you used for deployment, and then rename your new database (typically AXDBupgraded) to the name that the demo database had (typically AXDB).

      9. The renamed database must be configured. Follow the steps in Configure the Finance + Operations (on-premises) database.

      10. Start on-premises AOS, BI, and MR servers, or start the services from the Service Fabric portal by selecting Activate.

        Note

        The Database synchronization process will be triggered when the AOS nodes start up, and your environment will be unavailable until the process is completed.

    • If you don't have customizations, follow these steps:

      1. Optional: Rename your old database (typically AXDBold), and then rename your new database (typically AXDB). In the next step, make sure that you enter the name of the upgraded database.
      2. In LCS, set up a new environment, and deploy it with version 10.0.x (Redeploy). For more information, see Set up and deploy on-premises environments.

Upgrade where the VHD points to your database

  1. Back up the database from your on-premises environment (typically AXDB). For more information, see Create a Full Database Backup (SQL Server).

  2. Restore the backup that you just created into the database server, and give it a different name (for example, AXDBtoupgrade). For more information, see Restore a Database Backup Using SSMS.

  3. Open Windows PowerShell as an administrator, and run the following script.

    .\Configure-On-Premises-Upgrade.ps1 -DatabaseName '<DB-name>' -DatabaseServer '<SqlServerName>' -DatabaseUser '<User>' -DatabasePassword '<Password>'

    Note

    • The preceding PowerShell script is provided in the Appendix of this article.
    • Replace <DB-name>, <SqlServerName>, <User>, and <Password> with the values that you require.
    • Only SQL Server authentication is officially supported for this upgrade. For more information, see Create a Database User.
    • You must add the certificate authority certificate that signed your SQL Server certificate to the trusted certificate authorities store in your Onebox VHD. For more information, see Installing the trusted root certificate.
    • Make sure that the database user that you use has the sysadmin server role, or at least All Privileges, assigned on the database that you want to upgrade. Also make sure that the user has permissions to access tempDB. Step 6 of the upgrade process will fail if these conditions aren't met.
    • When you install the certificate authority certificate in the OneBox VHD, make sure that you use the fully qualified domain name (FQDN) or IP address to connect to the database that appears there. If you can't access the database by using the domain name, because it doesn't point to that server, edit your hosts file, and add the FQDN and the IP address that the FQDN should be resolved to.

  4. In LCS, go to the Shared asset library. Under Select asset type, select Software deployable package, and then select AX2012DataUpgrade-10-0-x to download the MajorVersionDataUpgrade.zip file.

  5. Copy the file, paste it in the desired location (for example: c:\D365FFOUpgrade\), and unzip it.

  6. Open a PowerShell window as an administrator, change the directory to the folder that you just unzipped, and run the following commands.

    .\AXUpdateInstaller.exe generate -runbookid="MajorVersionDataUpgrade-runbook" -topologyfile="DefaultTopologyData.xml" -servicemodelfile="DefaultServiceModelData.xml" -runbookfile="MajorVersionDataUpgrade-runbook.xml"
.\AXUpdateInstaller.exe import -runbookfile="MajorVersionDataUpgrade-runbook.xml"
.\AXUpdateInstaller.exe execute -runbookid="MajorVersionDataUpgrade-runbook"

    Note

    For information about how to monitor the upgrade, see the Monitoring the data upgrade section in the Appendix of this article.

  7. If you have customizations from ISVs or VARs, check whether you must run some post–data upgrade scripts.

  8. Run the Configure-OnpremUpgrade.ps1 script by using the values that are stated in the Resetting the VHD database (Optional) section later in this article.

  9. Configure your upgraded database for Finance + Operations by following the steps in Configure the Finance + Operations (on-premises) database.

  10. Deploy a new Dynamics 365 Finance + Operations (on-premises) environment.

    • If you have customizations, follow these steps:

      1. In LCS, go to the Shared asset library.

      2. Under Select asset type, select Model, and then download Dynamics 365 Finance + Operations on-premises, Version 10.0.x Demo Data. Select the version that is closest to the 10.0.x environment that you will deploy as the on-premises baseline.

      3. Use the restore backup option for SQL Server to create a new database (typically AXDB) from this file. For more information, see Restore a Database Backup Using SSMS.

      4. The demo database must be configured. Follow the steps in Configure the Finance + Operations (on-premises) database.

      5. In LCS, set up a new environment, and deploy it with version 10.0.x (Redeploy). For more information, see Set up and deploy on-premises environments. When you deploy the environment, the database that you should specify should be the database that you configured earlier (typically AXDB).

      6. Apply your own customizations, and ISV and VAR modules, to the newly created 10.0.x environment. Otherwise, when the environment is initially synced with the database, it will delete any customization-related or extension-related data.

      7. Shut down on-premises AOS, BI, and MR servers, or stop the services from the Service Fabric portal.

      8. Rename or delete the demo database (typically AXDB) that you used for deployment, and then rename your new database (typically AXDBupgraded) to the name that the demo database had (typically AXDB).

      9. Start on-premises AOS, BI, and MR servers, or start the services from the Service Fabric portal.

        Note

        The Database synchronization process will be triggered when the AOS nodes start up, and your environment will be unavailable until the process is completed.

    • If you don't have customizations, follow these steps:

      1. Optional: Rename your old database (typically AXDBold), and then rename your new database (typically AXDB). In the next step, make sure that you enter the name of the upgraded database.
      2. Set up a new environment, and deploy it with version 10.0.x. For more information, see Set up and deploy on-premises environments.

Configuring existing users

If you followed either of the previous procedures, you can sign in by using the Administrator user that you specified in LCS. However, none of your other users can sign in until they have been configured for the new system. Run a Select statement against your USERINFO table, and make a note of the value in the NETWORKDOMAIN field for the Administrator user (for example, https://adfs.contoso.com/adfs or http://adfs.contoso.com/adfs/services/trust). Then, for all interactive users who should be able to sign in, set the NETWORKDOMAIN field to the same value that the Administrator user has. The NETWORKALIAS field must also be modified. In Finance + Operations, this field is set to the user's email address (for example, testuser@contoso.com).

Resetting the VHD database (Optional)

If you used the Configure-On-Premises-Upgrade.ps1 script, run the following command to reset your database to the default configuration.

.\Configure-OnPremUpgrade.ps1 -DatabaseName 'AxDB' -DatabaseServer 'localhost' -DatabaseUser 'axdbadmin' -DatabasePassword 'AOSWebSite@123'

Appendix

Using the Configure-On-Premises-Upgrade.ps1 script

Important

This script is intended to be run only from a OneBox VHD environment.

The script requires that you pass at least the DatabaseName parameter. If you don't pass this parameter, the script automatically requests it.

You can pass an additional parameter, such as DatabaseServer or DatabaseUser, if you want. However, in this case, the script will request all additional parameters. This behavior occurs because the script will assume that you want to point the database connection to a machine outside the VM. Therefore, those parameters are required to correctly establish the connection.

The following parameters can be passed to the script:

  • -DatabaseName – The name of the database to upgrade.
  • -DatabaseServer – The database server that contains the Finance + Operations database.
  • -DatabaseUser – The user name for SQL Server Authentication.
  • -DatabasePassword – The password for SQL Server Authentication.

After the configuration has been passed, the script uses the new parameters to run a database connection test. If the script can't connect to the database, we recommend that you debug the connection from SQL Server Management Studio or another tool.

Configure-On-Premises-Upgrade.ps1

<#
.Synopsis
    Configures a OneBox deployment to upgrade an OnPrem 7.x database to OnPrem 10.0.x 

.DESCRIPTION
    This must be executed before the upgrade process is carried out.

.EXAMPLE
    .\Configure-OnPremUpgrade.ps1 -DatabaseName 'AxDB'

    .\Configure-OnPremUpgrade.ps1 -DatabaseName 'AxDB' -DatabaseServer '127.0.0.1' -DatabaseUser 'axdbadmin' -DatabasePassword 'secretPass'
#>
[CmdletBinding()]
param
(
    # Database server containing Microsoft Dynamics 365 for Operations, on-premises database.
    [AllowNull()]
    [string] $DatabaseServer,

    # Database name that you want to upgrade.
    [Parameter(Mandatory = $true)]
    [string] $DatabaseName,

    # Username for SQL Authentication.
    [AllowNull()]
    [string] $DatabaseUser,

    # Password for SQL Authentication.
    [AllowNull()]
    [string] $DatabasePassword
)

$webroot = "C:\AOSService\webroot"

$commandParameter = " -decrypt `"$webroot\web.config`""

$command = Resolve-Path "$webroot\bin\Microsoft.Dynamics.AX.Framework.ConfigEncryptor.exe"

Start-Process $command $commandParameter -PassThru -Wait

if([string]::IsNullOrEmpty($DatabaseUser) -and [string]::IsNullOrEmpty($DatabasePassword) -and [string]::IsNullOrEmpty($DatabaseServer)) { 

    [xml]$web = Get-Content $webroot\web.config

    $web.SelectSingleNode("configuration/appSettings/add[@key='DataAccess.Database']").value = [string]$DatabaseName

}
else { 

    if([string]::IsNullOrEmpty($DatabaseServer)){

        $DatabaseServer = if($value = Read-Host 'What is the IP or FQDN of the Database server? [127.0.0.1]') {$value} else {'127.0.0.1'}

    }

    if([string]::IsNullOrEmpty($DatabaseUser)){

        $DatabaseUser = if($value = Read-Host 'What is the SQL Authentication username? [axdbadmin]') {$value} else {'axdbadmin'}

    }

    if([string]::IsNullOrEmpty($DatabasePassword)){

        $dbPassEn = if($value = Read-Host 'What is the SQL Authentication password?' -AsSecureString) {$value} else {''}

        $BSTR = [System.Runtime.InteropServices.Marshal]::SecureStringToBSTR($dbPassEn) 

        $DatabasePassword = [System.Runtime.InteropServices.Marshal]::PtrToStringAuto($BSTR)

    } 

    [xml]$web = Get-Content $webroot\web.config

    $web.SelectSingleNode("configuration/appSettings/add[@key='DataAccess.DbServer']").value = [string]$DatabaseServer

    $web.SelectSingleNode("configuration/appSettings/add[@key='DataAccess.Database']").value = [string]$DatabaseName

    $web.SelectSingleNode("configuration/appSettings/add[@key='DataAccess.SqlUser']").value = [string]$DatabaseUser

    $web.SelectSingleNode("configuration/appSettings/add[@key='DataAccess.SqlPwd']").value = [string]$DatabasePassword

}
#Save Configuration to webroot config
$web.Save("$webroot\web.config")

#Reloading the configuration to run test
[xml]$web = Get-Content $webroot\web.config

$TestDbServer = $web.SelectSingleNode("configuration/appSettings/add[@key='DataAccess.DbServer']").value

$TestDbName = $web.SelectSingleNode("configuration/appSettings/add[@key='DataAccess.Database']").value

$TestDbUser = $web.SelectSingleNode("configuration/appSettings/add[@key='DataAccess.SqlUser']").value

$TestDbPass = $web.SelectSingleNode("configuration/appSettings/add[@key='DataAccess.SqlPwd']").value

#Setting up connection test.

$dbConn = New-Object System.Data.SqlClient.SqlConnection

$dbConn.ConnectionString = "Data Source=$TestDbServer;User ID=$TestDbUser;Password=`"$TestDbPass`";Database=$TestDbName"

try{

    $dbConn.Open()

    $result = $true

}

catch{

    $result = $_.Exception.Message

}
Finally{

    $dbConn.Close()

}

$commandParameter = " -encrypt `"$webroot\web.config`""

Start-Process $command $commandParameter -PassThru -Wait

if($result -ne $true){

    Write-Host "`nThe connection to the Database Server failed:" -ForegroundColor Red
    Write-Host $result -ForegroundColor Red

}
else{

    Write-Host "`nThe connection to the Database Server was successful!" -ForegroundColor Green

}

Monitoring the data upgrade

The deployable package has a single runbook step that processes the whole upgrade. However, this step consists of the following sub-steps that are run in the background:

  • PreReqs – This step patches the SQL dictionary, applies SQL sequences instead of system sequences, modifies user info and system variables, does database synchronization of system tables, and does additive synchronization of new tables.
  • PreSync – This step invokes the first set of upgrade jobs via batch processing, mostly to disable unique indexes.
  • DBSync – This step does the first full synchronization. Unique indexes that were disabled during the PreSync step aren't created during this step.
  • PostSync – This step runs the main data conversion jobs via batch processing.
  • FinalDBSync – This step does the final database synchronization that synchronizes all remaining objects in the database.

To determine which step the upgrade servicing is on, you can run the following SQL query on the AXDB database.

SELECT StartTime, EndTime, Steps, SubSteps, Status
FROM [DBUPGRADE].[DATAUPGRADESTATUS]
ORDER BY EndTime DESC

The results will resemble the following example. The dates and times that are given here are for illustration purposes only. Times vary, based on data volumes and the modules that are used in AX 2012.

StartTime EndTime Steps SubSteps Status
2022-05-20 17:16:07.097 2022-05-20 17:16:07.097 FinalDbSync DisableDataUpgradeFlag Completed
2022-05-20 17:16:06.997 2022-05-20 17:16:06.997 FinalDbSync EnableDbLogTriggers Completed
2022-05-20 17:16:06.937 2022-05-20 17:16:06.937 FinalDbSync DisableSafeMode Completed
2022-05-20 16:48:49.390 2022-05-20 17:16:06.802 FinalDbSync SyncSchema Completed
2022-05-20 16:48:49.333 2022-05-20 16:48:49.333 FinalDbSync EnableSafeMode Completed
2022-05-20 16:47:30.860 2022-05-20 16:48:49.169 PostSync RestoreBatchConfiguration Completed
2022-05-20 16:46:15.207 2022-05-20 16:47:30.738 PostSync EnableBatchPriorityScheduling Completed
2022-05-20 16:44:43.403 2022-05-20 16:46:15.091 PostSync DisableSysDeletedObjects Completed
2022-05-20 16:44:40.497 2022-05-20 16:44:40.497 PostSync ImportIsvLicenses Completed
2022-05-20 16:44:09.190 2022-05-20 16:44:40.379 PostSync StopBatch Completed
2022-05-20 15:49:38.207 2022-05-20 16:44:09.070 PostSync WaitForBatch Completed
2022-05-20 15:49:37.517 2022-05-20 15:49:38.108 PostSync StartBatch Completed
2022-05-20 15:48:31.517 2022-05-20 15:49:37.421 PostSync ScheduleScripts Completed
2022-05-20 15:47:13.403 2022-05-20 15:48:31.431 PostSync StartAos Completed
2022-05-20 15:47:12.667 2022-05-20 16:44:43.286 PostSync ExecuteScripts Completed
2022-05-20 15:47:12.550 2022-05-20 15:47:12.550 DbSync DisableSafeMode Completed
2022-05-20 07:49:40.827 2022-05-20 15:47:12.466 DbSync SyncSchema Completed
2022-05-20 07:49:40.760 2022-05-20 15:31:05.716 DbSync EnableSafeMode Completed
2022-05-20 07:49:06.673 2022-05-20 07:49:37.862 PreSync StopBatch Completed
2022-05-20 07:46:59.667 2022-05-20 07:49:06.528 PreSync WaitForBatch Completed
2022-05-20 07:46:58.637 2022-05-20 07:46:59.529 PreSync StartBatch Completed
2022-05-20 07:46:31.317 2022-05-20 07:46:58.497 PreSync ScheduleScripts Completed
2022-05-20 07:45:31.900 2022-05-20 07:46:31.180 PreSync StartAos Completed
2022-05-20 07:45:31.780 2022-05-20 07:45:31.780 PreSync ConfigureBatch Completed
2022-05-20 07:45:31.220 2022-05-20 07:49:40.519 PreSync ExecuteScripts Completed
2022-05-20 07:44:18.410 2022-05-20 07:45:31.092 PreSync DisaleBatchPriorityScheduling Completed
2022-05-20 07:43:14.880 2022-05-20 07:44:18.273 PreSync SaveBatchConfiguration Completed
2022-05-20 07:42:05.350 2022-05-20 07:43:14.749 PreSync EnableSysDeletedObjects Completed
2022-05-20 07:40:44.340 2022-05-20 07:42:05.211 PreSync CleanupDataUpgradeTables Completed
2022-05-20 07:40:44.250 2022-05-20 07:40:44.250 PreReqs DisableSafeMode Completed
2022-05-20 07:38:29.060 2022-05-20 07:40:44.110 PreReqs PartialDbSync Completed
2022-05-20 06:30:01.693 2022-05-20 07:38:28.908 PreReqs AdditiveDbSync Completed
2022-05-20 06:30:01.647 2022-05-20 06:30:01.647 PreReqs EnableSafeMode Completed
2022-05-20 06:30:01.590 2022-05-20 06:30:01.590 PreReqs ClearSysLastValue Completed
2022-05-20 06:30:01.523 2022-05-20 06:30:01.523 PreReqs ResetAdminUser Completed
2022-05-20 06:30:01.477 2022-05-20 06:30:01.477 PreReqs PatchSqlSystemVariables Completed
2022-05-20 06:30:01.273 2022-05-20 06:30:01.367 PreReqs PatchUserInfo Completed
2022-05-20 06:30:00.930 2022-05-20 06:30:01.164 PreReqs PatchSqlDictionaryPass2 Completed
2022-05-20 06:30:00.150 2022-05-20 06:30:00.820 PreReqs PatchSqlDictionaryPass1 Completed
2022-05-20 06:30:00.043 2022-05-20 06:30:00.043 PreReqs UpdateKernelSchema Completed
2022-05-20 06:28:01.157 2022-05-20 06:29:59.929 PreReqs CreateSqlSequences Completed
2022-05-20 06:28:01.020 2022-05-20 06:28:01.020 PreReqs DisableDbLogTriggers Completed

Troubleshooting

Database connectivity issues

  • Exception calling "Open" with "0" argument(s): "Cannot open database "AxDB1" requested by the login. The login failed. Login failed for user 'axdbadmin'." You supplied the Wrong database name or the user doesn't have access to that database.
  • Exception calling "Open" with "0" argument(s): "A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)". The script could not establish a connection with the SQL Server specified. Check the ip/fqdn and port that you used.
  • Exception calling "Open" with "0" argument(s): "Login failed for user 'axdbadmin'." The supplied login credentials are not correct.

Rerun the runbook after a failure

If the data upgrade runbook fails, you can retry the last step by using the -rerunstep option, as shown in the following example. Edit the step number as required.

.\AXUpdateInstaller.exe execute -runbookid="MajorVersionDataUpgrade-runbook" -rerunstep=3

Review the runbook logs

Logs are located in a sub-folder under the deployable package. Drill into the logs folder to find the logs for the runbook step that you're on, and review errors.

View details about a PreSync or PostSync upgrade job

Upgrade PreSync and PostSync scripts are run in X++ by using a batch process that the data upgrade process starts. In Application Explorer in Visual Studio, some classes that you can view are prefixed with ReleaseUpdate. If an upgrade script fails during the runbook process, you can learn more about the reason for the error by opening SQL Server Management Studio and running the following code to query ReleaseUpdateScriptsErrorLog.

select * from RELEASEUPDATESCRIPTSERRORLOG

Additional resources

For more troubleshooting information, see the following articles: