Monday, February 26, 2018

Synchronize the database manually - Dynamics 365 for Finance & Operations On Premises Installation

Hi All

Sometime in a D365FO On Premise deployment the Sync doesn't triggered!

What to do?

You can run the Database Sync manually as per the "Copy a Finance and Operations database from SQL Server to a production Azure SQL Database environment" procedure.

In an On Premise change a little bit.

The steps are:
  1. Connect to RDP to an AOS Node
  2. Open the PowerShell ISE
  3. Copy the script below and change the Bold part as per your environment
  4. In that case my package name is "K"

cd C:\ProgramData\SF\AOS_XX\Fabric\work\Applications\AXSFType_App164\\Packages\bin

.\Microsoft.Dynamics.AX.Deployment.Setup.exe -bindir "C:\ProgramData\SF\AOS_3\Fabric\work\Applications\AXSFType_App164\\Packages" -metadatadir "C:\ProgramData\SF\AOS_3\Fabric\work\Applications\AXSFType_App164\\Packages" -sqluser "axdbadmin" -sqlserver "FQDN SQL instance" -sqldatabase "axdb" -setupmode "sync" -syncmode "fullall" -isazuresql "false" -sqlpwd "password"

Enjoy with D365FO On Premise!

Update: This behaviour is related to the sf.synclog tableThis table contain all packages installed on an Environment.
If we want to move an package with a name already used before, the Deployment process found it in that table and the Synch is skipped!
The workaround is to truncate the table or at least delete the record relative to the package.

Update 2: This issue is been fixed on Platform Update 12.


Ali Khan said...

The use of personal interaction in everyday life is a thing of the past. People these days relies or even worst are now dependable upon the use of computers via the internet. navigazione sicura

Ali Khan said...

An Access VPN is used to connect remote users to the enterprise network. miglior vpn