Failure! Status check of Report Server – The remote server returned an error: (500) Internal Server Error – Report design not found – Microsoft Dynamics 365 for Finance and Operations

Scenario:

Sometimes users facing below issue in generating the reports from Dynamics 365 for Finance and operations or Developers while deploying the reports 

  • Failure! Status check of Report Server –
  • The remote server returned an error: (500) Internal Server Error – Report design not found
  • Report design not found

Solution:

Restart the below services by going on the services list window of the report server or from the LCS

  • Restart the service report server
  • Check and restart the Microsoft SQL Server instance service

Note: If the server is sandbox environment managed by Microsoft then go the Power BI (report server) VM and restart the above services

 

 

 

Package deployment fails – not enough disk space – Microsoft Dynamics 365 for Finance and Operations – LCS

Scenario:  Sometime during deployment users facing low space issue and deployment got failed.

Reason: The reason is deployable packages folder having many files that increase the drive used space. Microsoft by default deployable packages will delete after 30 days. If you deploy packages many times during the last 30 days. then you need to reduce the time of delete deployable packages

Solution:

 

  • Under the HKLM:\SOFTWARE\Microsoft\Dynamics\Deployment registry key, you can create the following keys to customize when cleanup should occur. The automated cleanup task will consider these values.
    • CutoffDaysForCleanup – The number of days that old packages and logs should be retained. The default value is 30.
    • CutoffDiskSpaceLimitForPackages – The minimum free disk space (in gigabytes [GB]) on the service volume drive where the package folder is located. For example, if the disk space is 200 GB, the cleanup task will remove the packages, based on the number of days.
    • CutoffDiskSpaceLimitForLogs – The minimum free disk space (in GB) of the system drive where the log folder is located. For example, if the disk space is 100 GB, the cleanup task will remove the servicing-related logs, based on the number of days.

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 pipelineScreen Shot 2019-09-05 at 10.52.56 AM.png
    2. Screen Shot 2019-09-05 at 10.54.29 AM.png
  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

Preview Features in Dynamics 365 for Finance and Operations version 10.0.5 (October 2019)

Features names of this release details you will find in the below link.

  1. Feature management
    • Check for update button will be introduced
  2. Data management job history clean up
  3. Business events catalog security
    • Role based security can be applied to individual business events
  4. Attachment Recovery
  5. New grid Control
  6. Workflows enhancements
    • support reset now
    • Flow templates for workflow items
  7. Extensibility enhancements
    • Enable extension for workflow approvals
    • display methods on form datasource
  8. CodeLens for methods references in the X++ editor

 

Preview features in Finance and Operations version 10.0.5 (October 2019)