web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Customer experience | Sales, Customer Insights,... / Error loading control ...
Customer experience | Sales, Customer Insights,...
Answered

Error loading control error on Email Form - (CRM 9.1 - On-Premise!)

(2) ShareShare
ReportReport
Posted on by PJ-20060701-0 26
Hello everyone,
We have an issue with the CRM (on-premise) that happens randomly with users that when creating emails directly in the CRM, We have not customized the email form (we are still using the default) .
Does anyone else have this problem or know a solution? 
Categories:
Microsoft Dynamics CRM
Dynamics 365 Sales
I have the same question (0)
  • Suggested answer
    Holly Huffman Profile Picture
    Holly Huffman 6,554 Super User 2026 Season 1 on at
    Good morning, afternoon, or evening :) depending on your location!
    Hope you are well today.
     
    The "Error loading control" issue in Dynamics 365 CRM (on-premise) can occur due to various reasons, such as missing dependencies, outdated configurations, or browser compatibility issues.
    Troubleshooting Steps:
    1. Check Browser Compatibility:
      • Ensure users are accessing CRM using a supported browser (e.g., the latest version of Chrome, Edge, or Internet Explorer).
      • Clear browser cache and cookies, then reload the CRM application.
    2. Enable Tracing:
      • Enable server-level tracing in Dynamics 365 CRM to capture detailed logs of the error.
      • Review the trace files for specific error messages or missing components. You can find guidance on enabling tracing here.
    3. Verify CRM Updates:
      • Confirm that the CRM instance is updated to the latest version of Dynamics 365 9.1 On-Premise.
      • Apply any available patches or updates that address known issues.
    4. Inspect Dependencies:
      • Check if the default email form relies on any missing or corrupted components.
      • Reinstall or repair the affected components if necessary.
    5. Test with Different Users:
      • Determine if the issue is user-specific or system-wide by testing with different user accounts.
      • Verify user permissions and roles to ensure they have access to the email form.
    6. Review Customizations:
      • Although the email form is not customized, check for any global customizations or plugins that might interfere with the default functionality.
     
    Hope this helps!
  • Suggested answer
    Krishna Acharya Profile Picture
    Krishna Acharya 123 on at

    You're describing a random issue with users creating emails directly in on-premise CRM, using the default email form (no customization). That kind of intermittent behavior can be tricky, but here are a few common causes and solutions to consider:

    1. Broken or Missing PCF Control
    • Even if you're using the default form, some standard fields may reference Microsoft-supplied PCF (PowerApps Component Framework) controls.
    • If CRM can't retrieve the control's manifest file, you get this error.
    Fix:
    • Check if your CRM server can access CDN resources or the local control files.
    • If this is on-premise, confirm the latest patches and updates are applied.
    • Check the field settings for “description” – see if a custom control is applied and remove or reset it if necessary.
     2. Form Customization Cleanup
    • Even if you didn’t customize the form yourself, a managed solution or an update might’ve added a control.
    Fix:
    • Go to Customization > Email entity > Form.
    • Open the main form and check the “description” field.
    • Remove or reset any associated custom controls.
    3. Script/Browser Conflict
    • Sometimes, browser extensions or caching issues prevent the manifest from loading.
    Fix:
    • Try using Incognito Mode or a different browser.
    • Clear cache and cookies.
    • Disable extensions (especially ad blockers or script blockers).
     4. CDN or Network Block
    • If your CRM tries to fetch control metadata from the cloud and your firewall or network blocks it, you’ll see this error.
    Fix:
    • Make sure the server (or client browser) has access to required Microsoft domains/CDNs.
    • If fully offline/on-prem, ensure all necessary control files are installed locally.
    I used AI to help craft rephrases this response and share some useful tips for your Dynamics 365 challenge.
    If its helpful to you please Mark as verified!
    Thanks,
    Krishna
  • Verified answer
    Daivat Vartak (v-9davar) Profile Picture
    Daivat Vartak (v-9d... 7,841 Moderator on at
    Hello PJ-20060701-0,
     

    You're encountering the same "Error while retrieving manifest during ComponentDidMount for control: description" issue that was discussed previously. Since it's happening randomly in your on-premise Dynamics 365 CRM environment when creating emails using the default form, the troubleshooting steps remain largely the same, but with a specific focus on the on-premise context.

    Here's a recap and some additional considerations for your on-premise setup:

    Understanding the Error (Revisited):

    The error indicates a problem during the initialization of the rich text editor (likely a React component) used for the email body ("description" control). It's failing to retrieve its configuration manifest. The "Fehlercode: 0x0" suggests a generic failure rather than a specific error code. The random nature points to an intermittent issue.

    Troubleshooting Steps (On-Premise Focus):

    1. Server Health and Performance:

      • Monitor Server Resources: Check the health and performance of your Dynamics 365 server and the underlying SQL Server. High CPU usage, memory pressure, or disk I/O bottlenecks can lead to intermittent issues.
      • Event Viewer (Server): Examine the Application and System logs on your Dynamics 365 server for any related errors or warnings occurring around the time users experience this issue.
      • Dynamics 365 Tracing (Server-Side): Enable server-side tracing for Dynamics 365 to capture detailed information about the error when it occurs. This can provide valuable insights into the root cause. 

    2. IIS (Internet Information Services):

       

      • IIS Reset: As mentioned before, try performing an IIS reset on the Dynamics 365 server. This can sometimes resolve temporary issues with the web server.
      • Application Pool Health: Check the health of the Dynamics 365 application pool in IIS. Ensure it's running and doesn't have excessive errors or restarts.
      • Request Limits and Timeouts: Review the IIS settings for request limits and timeouts. If these are set too low, they could potentially cause issues during the loading of complex controls.

    3. Network Connectivity (Internal):

      • Latency: Investigate your internal network for any intermittent latency issues between the users' machines and the Dynamics 365 server.
      • DNS Resolution: Ensure proper DNS resolution within your internal network. 

    4. Dynamics 365 Application Logs:

      • While server-side tracing is more detailed, also review the application logs within Dynamics 365 itself (if available) for any related errors. 

    5. Client-Side Troubleshooting (Revisited):

      • Browser Issues: As previously discussed, continue to have users try clearing their browser cache and cookies, using different supported browsers, disabling extensions, and testing in private/incognito mode.
      • Client Performance: Check the performance of the users' local machines. Insufficient resources on the client side can sometimes manifest as UI rendering issues. 

    6. Customizations (Re-Verification):

      • Unmanaged Solutions: Even if you believe the email form is default, carefully review any unmanaged solutions you have deployed. Customizations within these solutions could potentially impact the default behavior.
      • Recently Deployed Solutions: If the issue started after deploying a new solution, investigate the components of that solution. 

    7. Dynamics 365 Updates (On-Premise):

      • Recent Updates: If you recently applied a cumulative update or service pack to your Dynamics 365 on-premise environment, check the release notes and known issues for that specific update. There might be a bug that Microsoft is aware of.

        •  

      8.  

    Steps to Take (Specific to On-Premise):

    1. Engage Your IT Team: If you haven't already, involve your internal IT team, especially those responsible for server infrastructure and network management. They can assist with checking server performance, IIS, and network connectivity.
    2. Enable Server-Side Tracing: This is crucial for on-premise environments to get detailed error information. Analyze the trace logs when the error occurs.
    3. Review Deployment Logs: Check the deployment logs from the initial Dynamics 365 installation and any subsequent updates for any errors related to web components or controls.
    4. Check SSRS (SQL Server Reporting Services): While the error message doesn't directly point to SSRS, intermittent issues with SSRS can sometimes have unexpected side effects in Dynamics 365. Ensure SSRS is running correctly.
    5. Contact Microsoft Support (On-Premise): If you've exhausted these steps and the issue persists, open a support ticket with Microsoft. Provide them with detailed information about your on-premise environment, the steps to reproduce the issue (as much as possible given its random nature), and any logs or tracing you've collected.

      6.  

    The random nature of this error suggests an underlying intermittent problem, which could be related to server resources, network hiccups, or a subtle software interaction. Thoroughly investigating your on-premise environment is key to finding the root cause.

     
    If my answer was helpful, please click Like, and if it solved your problem, please mark it as verified to help other community members find more. If you have further questions, please feel free to contact me.
     
    My response was crafted with AI assistance and tailored to provide detailed and actionable guidance for your Microsoft Dynamics 365 query.
     
    Regards,
    Daivat Vartak
  • Verified answer
    GH-07051127-0 Profile Picture
    GH-07051127-0 11 on at
    We experienced the same problem, CRM On Premises 9.1.36.12, Unified Interface, standard form.

    Error: No manifest found, 'MscrmControls.RichTextEditorV2.RichTextEditorControlV2'
     
    Adding and activating the "Rich Text Editor Control" on the "description" field on the email form solved it.
  • SM-14050327-0 Profile Picture
    SM-14050327-0 2 on at
    Also having this problem after the update. The legacy web client works fine.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Meet the Microsoft Dynamics 365 Contact Center Champions

We are thrilled to have these Champions in our Community!

Congratulations to the March Top 10 Community Leaders

These are the community rock stars!

Leaderboard > Customer experience | Sales, Customer Insights, CRM

#1
ManoVerse Profile Picture

ManoVerse 184 Super User 2026 Season 1

#2
11manish Profile Picture

11manish 125

#3
CU11031447-0 Profile Picture

CU11031447-0 100

Last 30 days Overall leaderboard

Featured topics

Hide selecting Contact for potential customer when creating quote

Product updates

Dynamics 365 release plans