When working with Dynamics 365 Finance and Operations (on-premises), there are times when you need to manually synchronize the application database (AXDB) with your metadata. This is especially common after deploying new models, applying hotfixes, or troubleshooting schema mismatches.
In this guide, we’ll walk through the manual sync process, how to test SQL connectivity, and a quick troubleshooting checklist to ensure smooth execution.
π Running the Manual Sync Command
The sync is triggered using the Microsoft.Dynamics.AX.Deployment.Setup.exe tool. Below is an example command for a full tables and views sync:
C:\ProgramData\SF\SBAOS02\Fabric\work\Applications\AXSFType_App83\AXSF.Code.1.0.20251009185555\bin\Microsoft.Dynamics.AX.Deployment.Setup.exe ^
--setupmode sync ^
--syncmode FullTablesAndViews ^
--metadatadir C:\ProgramData\SF\SBAOS02\Fabric\work\Applications\AXSFType_App83\AXSF.Code.1.0.20251009185555\Packages ^
--bindir C:\ProgramData\SF\SBAOS02\Fabric\work\Applications\AXSFType_App83\AXSF.Code.1.0.20251009185555\Packages ^
--sqlserver SBSQL01.domain.local ^
--sqldatabase AXDB ^
--sqluser axdbadmin ^
--sqlpwd "password"
π Alternative Approach: Test Connection from PowerShell
You can also verify if the connection works from PowerShell to ensure no issues with the credentials:
$server = "SBSQL01.alkan.ae"
$database = "AXDB"
$username = "axdbadmin"
$password = "7744&&$$"
# Create SQL connection string
$connectionString = "Server=$server;Database=$database;User Id=$username;Password=$password;"
# Test connection
try {
$connection = New-Object System.Data.SqlClient.SqlConnection
$connection.ConnectionString = $connectionString
$connection.Open()
Write-Host "Connection successful!"
$connection.Close()
}
catch {
Write-Host "Connection failed: $_"
}
Comments
Post a Comment