D365FO 10.0.29 platform 53 - Updating development environment fails at step 53

Hello Everyone with a new blog and a new challenge,

Today we are going to discuss updating your old development environment to the latest update,

if you try to update your development environment to 10.0.29 without upgrading your SQL server from 2016 to 2019 you will get stuck at step 53,

downloading the log will explain you that a certain SQL command is not supported by the SQL version you have, once checked the SQL command

i found out that it is not supported by SQL 2016, thus i had to upgrade it to 2019, now in the upgrade process of SQL to 2019 you will find out that SSRS is not

included in the package, and in-order to upgrade SSRS to 2019, you will have to uninstall 2016 and install 2019, the challenge here is to configure D365FO

with SSRS 2019, follow the below steps to achieve that:

• Uninstall SSRS 2016 and download SSRS 2019, install without configuration
• On your Dev machine, locate this script:

K:\AosService\PackagesLocalDirectory\Plugins\AxReportVmRoleStartupTask\ConfigureOneboxReportingCluster.ps1

K is being the service volume in my case, change it to your service volume if it was different,

now create a copy and rename the copy of this script, right click it and edit to modify the script.

• Open IIS Manager -> Server certificates:
  

Locate "ReportingService" and copy its thumbprint to notepad, 

Locate "DataEncryption" and copy its thumbprint to notepad,

Locate "DataSigning" and copy its thumbprint to notepad,

remove spaces and locate the first character visible and hit backspace to delete any invisible special character for all thumbprints copied above.

• Now in your copied script edit the below methods to include your correct thumbprints:

in script file find -> function Get-InstallConfigString

replace the thumbprints as below mapping

ReportingClientCertificateThumbprint -> IIS-> Certificates-> ReportingService -> Thumbprint
DataEncryptionCertificateThumbprint -> IIS-> Certificates-> DataEncyption -> Thumbprint
DataSigningCertificateThumbprint -> IIS-> Certificates-> DataSiging -> Thumbprint

in the script main body find -> # Update soap service certificate thumbprint setting in AOS web.config

you will find a line updating AOS config with property "BiReporting.SOAPCertificateThumbprint", paste the "ReportingService" thumbprint from your notepad

in the script body you might try to find "Thumprint" keyword and find one that i didn't discuss, this is only for cluster, in my case i didn't have it enabled

and unfortunately i was not able to know which certificate to use for it in the case of cluster, thus if you know it, please let us all know in the comment

# Update SSRS endpoints
if ($reportingCluster)
{
    Config-SsrsEndpoint -Port 50443 -Log $log -SslCertThumbprint "466cd26a6e2f346a3a813d12e2baad0e886e7bbf" -ErrorAction Stop
}

• Update $env:AxModule in -> function Update-ReportServerIP || and in -> function Update-WebConfigSetting

update the method to be as below having K: is my Service volume, change it to your Service volume letter,

in my environment, this environment parameter was returning empty.

if (!$env:AxModule)
{
    $env:AxModule = "K:\AosService\"
    #throw "AX was not deployed. Could not find environment variable AxModule"
}

• Now close the script after saving and run power-shell with administrator privileges then run your newly created script, it will take sometime as it will install the D365FO SSRS extensions, then it will configure it and update the AOS web.config, and it will test the connection to SSRS web portal, thus you will see it failing at first time and it will wait for 10 secs and try again, however you don't have to so anything but wait for the script to finish, hopefully it will be successful.
• Run DeployAllReportsToSsrs.ps1 in the same scripts folder.

Viola, you are done re-configuring your new 2019 SSRS with D365FO, go ahead and test.

If you have any concerns or issues, let me know in the comments or mail.

Happy Daxing.