ASR Deployment Planner fails Generating Report in Excel

Question

Good morning, I am having problems generating Azure Sites Recovery deployment planner report even though I believe the required profiled data, files needed and software installed.

I Have Windows Server 2012 R2, excel 2013, main Microsoft Updates (included windows and office), ASR Deployment Planner (last version), all the .Net 3.5 and .NET 4.5 features (plus it updates), Microsoft Visual C++ Redistributable for Visual Studio 2012.

I created a directory C:\ASR where I work and I change to it for executing asrdeploymentplanner.exe command with its parameters. I have the PROFILEDDATA subdirectory and when I run (in POWERSHELL or CMD):

.\ASRDeploymentPlanner.exe -Operation GenerateReport -virtualization Hyper-V -VMListFile .\VMListFile.txt

I get a message like "excel failed to generate report".

Thanks in advance, greetings and have a good day, Armando

Answer 1

Hi ARMANDO LOPEZ,

Thank you for reaching out to Microsoft Q&A forum!

The Azure Site Recovery (ASR) Deployment Planner is a crucial tool for assessing and planning your disaster recovery deployment. When it comes to generating reports in Excel, there are a few common issues that might cause failures. Let’s explore some potential solutions:

Check Profiled Data Availability:

The Deployment Planner requires profiled data to generate accurate reports. Ensure that profiling has been done for at least **30 minutes** before attempting to generate a report. [If the required profiled data file is missing, the report generation process will fail](https://learn.microsoft.com/en-us/answers/questions/849653/cannot-gerenrate-report-in-run-the-deployment-plan)[1](https://learn.microsoft.com/en-us/answers/questions/849653/cannot-gerenrate-report-in-run-the-deployment-plan).

Incompatible VMs Sheet:

   The Excel report generated by the Deployment Planner includes an **“Incompatible VMs”** sheet. This sheet provides details about VMs that are incompatible with the deployment plan. [It lists VM names and the attached disks (VHDs)](https://learn.microsoft.com/en-us/answers/questions/849653/cannot-gerenrate-report-in-run-the-deployment-plan)[2](https://learn.microsoft.com/en-us/azure/site-recovery/hyper-v-deployment-planner-analyze-report).
  
  **Online Repair**:
  
      If you encounter issues, try running a **full online repair** (not a quick repair) for the Deployment Planner. [Sometimes, this can resolve underlying issues](https://learn.microsoft.com/en-us/answers/questions/849653/cannot-gerenrate-report-in-run-the-deployment-plan)[3](https://learn.microsoft.com/en-us/answers/questions/933296/asr-deployment-planner-hyper-v).
     
     **Folder Cleanup**:
     
         Occasionally, issues may arise due to specific folders. If you notice a **1.9 folder** in the key, consider deleting it. [For example:](https://learn.microsoft.com/en-us/answers/questions/849653/cannot-gerenrate-report-in-run-the-deployment-plan)
        
        ```sql
        TypeLib {000208D5-0000-0000-C000-000000000046}1.9
        
        ```
        
        After deleting the folder, reboot your system and then attempt to run the Deployment Planner again[3](https://learn.microsoft.com/en-us/answers/questions/933296/asr-deployment-planner-hyper-v).
        

Remember that the Deployment Planner relies on accurate data and proper configuration. Double-check your settings, ensure profiled data availability, and follow the troubleshooting steps to resolve any issues. If problems persist, consider reaching out to Microsoft support for further assistance.

Regards,