NET::ERR_CERT_DATE_INVALID Error in D365 Finance and Operations

Sometimes you receive errors related to invalid or expired certificates in cloud hosted Dynamics 365 finance and operations environments.

Solution:

Solution is quite simple for this error.

Go to LCS and open the environment page

Click on the maintain dropdown and select Rotate secrets option

Click on Rotate SSL certificates

It will take a few minutes to complete this process . Refresh the environment page and, you will no longer receive the invalid certificate error.

Package deployment timeout issues (retail retail related errors)- D365 for finance and operations

Scenario:

If you are receiving retail related errors on cloud hosted environments. here is the solution:

Note: Below solution is only applicable if you’re not using the retail functionality at all and you have RDP access of the environment.

Retail server:

If you’re receiving Retail server related error than do the below steps:

Run the DropAllRetailChannelDbObjects.sql and you can find the script in below path K:\DeployablePackages\\RetailServer\Scripts”

This will drop all retail server objects but will be recreated during the update. After running the script, resume the update again.

RetailCloudPos:

RetailStorefront:

If you’re receiving error related to above two and it is timeout error(check in the log file):

Find the step in the runbook and get the script location:

Copy the UpdateCloudPos to the desktop or any other folder as backup

Open the copy file in notepad and clear the script (empty file)

Copy the empty file back to the above folder and replace it.

Same steps you have to do for RetailStorefront.

Resume the package deployment.

D365 apply updates failed – package deployment failed – Dynamics 365 for finance and operations

Issue:

Few times we came across the issue of failing of D365 apply updates or package deployment failed at the step of DevTools.

Resolution:

To resolve the issue follow below steps:

1. Download the package if not downloaded
2. Unblock the downloaded package Zip file before extracting
3. Extract the the package zip file
4. Navigate to the DevToolsService/Scripts folder in the extracted package folder
5. Find the the file Microsoft.Dynamics.Framework.Tools.Installer

6. Double click on the file and install the extension for VS2019

7. Once extension installation complete resume the package deployment.

Please feel free to comment if you’re facing any issue. We will try our best to help you solve the issues.

Uninstall a deployable package from sandbox(UAT) environment or production- Dynamics 365 for Finance and Operations

Scenario: Sometime we need to uninstall a deployable package from the UAT or Production environment.

 

Solution:

Below are the steps that need to be performed to uninstall a package.

 

• Create a deployable package using visual studio or Build server
• Do not extract the deployable package that is in ZIP folder (If you extract the zip folder you will face issue invalid HotfixInstallationInfo.xml file)
• Just open the deployable package zip folder
• Go to Deployable package zip folder -> AOS service -> Scripts folder
• create a text file name ‘ModuleToRemove’
• Write the module name to be removed in the the ModuleToRemove file

 

•  If you have multiple models to remove then write mode name per line as below
  • Model1
  • Model2
  • Model3
• Note: In multiple models removing write the models name in sequence as per dependency sequence
• Go back to main zip folder and find the file HotfixInstallationInfo.xml ,copy the file to some other location and edit the file like below

<MetadataModuleList>
</MetadataModuleList>

 

<AllComponentList>
<ArrayOfString>
</ArrayOfString>
</AllComponentList>

• Edit the file should be same as above.
• Copy and replace the HotfixInstallationInfo.xml file in the deployable folder
• upload the file in the asset library and apply the package to the UAT environment first if applied successfully then apply to the production environment.

 

Please leave comments if you are facing any issue.

 

 

 

Application release 10.0.6 Platform update 30 – Features Management- New Features List – Microsoft Dynamics 365 for Finance and Operations – D365FnO

Below are the list of features that added in the Application release 10.0.6 and platform update 30.

 

Single deployable package creation from customization and ISV package – Microsoft Dynamics 365 for Finance and operations

Upgrade Dynamics 365 Finance and operations environment – Third-Party ISVs(No Source code) and custom model(source code)

Scenario:

2 ISV packages(no source code)

2 Custom models(source)

Sandbox Environment is on Application release 8.0 and PU 24

Target version for sandbox environment Application release 10.0.4 and PU 28

The problem in the simple upgrade:

unable to merge 4 packages(2 ISVs, 1 custom model and 1 application release 10.0.4 ,PU28 package)

Maximum only 2 packages can be merged in the asset library.

Solution:

To create one package for ISVs and custom model, need build environment and code should be under source control

Then one package of latest application release and custom package can be merged into one package and apply to a sandbox environment to upgrade

 

Steps:

1. Custom models source code add to source control
   1. After you install the custom model, follow these steps to add the new model to source control.
   2. Open Source Control Explorer by clicking View > Other Windows > Source Control Explorer.
   3. Navigate to the metadata folder that is mapped on this development VM, such as MyProject/Trunk/Main/Metadata.
   4. In the metadata folder, find the folder for the package that contains the new model. Right-click the package folder, and then click Add Items to Folder.
   5. In the Add to Source Control dialog box, select the Descriptor folder and the folder that has the name of the model. Some models may also contain referenced DLLs in the bin folder. If these exist you’ll need to also include the appropriate DLL files from the bin folder. Once all files have been selected, click Next.
   6. Review the items that will be added, and then, when you’re ready, click Finish.
   7. Open the Pending Changes window from the Team Explorer pane or by clicking View > Other Windows > Pending Changes.
   8. Review the changes, enter a check-in comment, and then click Check In.
2. Add ISVs package to source control follow below steps
   1. After you install the deployable package on a development VM, follow these steps to add the package to the source control.
   2. Open Source Control Explorer by clicking View > Other Windows > Source Control Explorer.
   3. Navigate to the metadata folder that is mapped on this development VM, such as MyProject/Trunk/Main/Metadata.
   4. Right-click the Metadata folder, and then click Add Items to Folder.
   5. In the Add to Source Control dialog, double-click the folder that has the package name that you want to add to source control.
   6. Select all the folders except XppMetadata and Descriptor, if they exist, and then click Next.
   7. On the next page, on the Excluded items tab, select all files by clicking one of the files and then pressing Ctrl+A. At the bottom of the selection window, click Include item(s). When you’re ready, click Finish.
   8. Open the Pending Changes window from the Team Explorer pane or by clicking View > Other Windows > Pending Changes.
   9. Review the changes, enter a check-in comment, and then click Check-In.
3. Deploy build environment
   1. During deployment, Build Agent Name keep the same as the build environment name
   2.  Branch Name should be a source control branch name of the project
4. Use DevOps pipeline to create one package
   1. Click on Pipeline -> pipeline and then click on run pipeline
   2. 
5. Once pipeline is completed the one deployable package will be created on the build VM.
6. Upload the build package on the Asset library, validate
7. Apply on the UAT environment and production as well if all goes well.

 

Please comment if you need any clarification or you are facing some issue on any step.

Database Maintenance – September 2019 -Microsoft Dynamics 365 for Finance and Operations

Microsoft Dynamics 365 for finance and operations performing database maintaince in Septemebr 2019 and he sent emails to project owners and Environement managers.

Below are key points of the September database maintenance

1. Database scale out and migrations
   • Result regions changed for new and existing customers
   • Connection string will be updated for existing customer
2. Restricting Database access
   • After this update only Project owners and Environment managers can access the database backup option
3. Enable customers with Expired ax2012 license to take ownership of their projects on LCS
4. Soft enforecment added for the use of single deployable package for customizations and isv packages
   • Soft enforcement for now and hard enforcement in future release

 

To check in more details, please use below link of microsoft llife services blog

Lifecycle service blog