locked
Cannot Create New Organization in CRM 2013 UR 1 (On-Prem) & Report Is Not Enabled message even though it is Installed RRS feed

  • Question

  • Hi there CRM Experts & Experienced Implementers,

    We have 2 CRM 2013 Servers (1 Sandbox & 1 Dev) that are both Full Server Configurations (CRM Full Server Roles + SQL Server 2012 in single server) that are working properly and we didn't have any issues with the installation.

    Main Issue: We cannot create a new Organization on both servers and we get the same error:

    "All Microsoft Dynamics CRM servers that have the AsyncService server role are disabled. This server role is required to complete the operation. To enable the server, use Microsoft Dynamics CRM Deployment Manager.

    Error Screenshot when creating additional Org:

    Error creating new Org: All MS Dynamics CRM servers that have AsyncService server role are disabled

    Another issue is when we check Deployment Manager, it says 2 issues:

    Issue 1. Reporting is not enabled

    Clicking on the link says:

    ["To enable reports, you must first install MS Dynamics CRM Reporting Extensions for SQL Server Reporting Services. For more info, see CRM Implementation Guide."]

    But NOTE that I have installed the CRM 2013 Reports Authoring Extensions on both servers and we can run & view the OOB reports properly.

    I researched this, and found the same issue was a known issue in CRM 2011 when you update to UR 12, and seems to occur in deployments where sql is installed to a named instance, but we installed using the default instance of SQL. I don't see any KBs or blog/forum entries for this issue in CRM 2013.

    See related thread here: http://social.microsoft.com/Forums/en-US/026f79fc-54a1-4927-ab83-1be207163550/crm-2011-deployment-manager-shows-reporting-is-not-enabled-even-though-reporting-extensions?forum=crm

    See CRM 2011 Support KB here: http://support.microsoft.com/kb/2825497/en-us?sd=rss

    Issue 2. One of more server roles are missing from this deployment

    Clicking on the link says:

    ["The following server roles are missing from this deployment: Full Server.

    To resolve this issue, either add a new MS Dynamics CRM Server to the deployment with the missing server roles or add the missing server roles to an existing MS Dynamics CRM Server in the deployment."]

    It's saying the Full Server role is missing, but how come, our CRM 2013 Applications (Default Orgs) are working properly, and we haven't had any issues with them.

    Please help, any input is greatly appreciated.

    Thanks a lot!

    -ProgCRM

    Thursday, March 20, 2014 1:50 AM

Answers

  • Hi TZ00KI,

    Thanks for the reply.

    1. Yes, that's what I meant - I already installed the CRM SRS Data connector prior and used the installer inside the CRM Server 2013 Installation folder. The OOB reports have been working properly, but that error message that reporting is not enabled on the Deployment Managers bothers us.

    Here's an UPDATE today everyone: Regarding my main issues on creating new CRM Orgs and missing server roles, they are now resolved and I've discovered that the issue was internal, and I'm still sharing it here because it might help others in the future.

    The problem was that somebody from our Infra team removed/deleted the Active Directory Organization Units used specifically in the CRM Server 2013 installations. Note that when CRM Server 2013 is installed, the system creates 4 security groups (PrivReportingGroup, PrivUserGroup, SQLAccessGroup, & ReportingGroup) added to the AD Organization Unit specified during installation. Having an AD OU per CRM 2013 deployment is a recommended practice.

    Solution: After recreating the appropriate Active Directory Org Units, and then reapplying all the CRM Installation & Service Account permission requirements, we repaired the CRM Server 2013 "Full Server Role" installation using the CRM Server 2013 Install/Repair wizard, and sure enough, we were able to create new Orgs and the error message on the dashboards regarding the missing server roles have disappeared. Furthermore, the error message "Reporting is not enabled." also disappeared after the repair and restarting the servers. Interestingly, I've tried restarting our other CRM 2013 servers with the same error message on dashboard "Reporting is not enabled." (even though it's already installed on these servers and the OOB reports are working just fine), but unfortunately the error message is still there. I'm not sure how the error message "Reporting is not enabled." disappeared on our Sandbox and Dev servers deployment managers, as I didn't perform anything specific to this issue, but since after performing a repair of the full server installation and then restarting the servers, I'm thinking this could be a solution.

    Thanks to those always looking & taking the time to help fellow MS CRM community members.

    ProgCRM


    Monday, March 24, 2014 8:23 AM

All replies

  • Hi

    1. You are supposed to install the CRM SRS Data connector and not the Reports Authoring Extensions as these are 2 different things. You can find the installation to SRS Data Connector in the CRM installation folder.

    2. There may be several causes to this:

    a. The Async role is disabled in the deployment manager - enter the deployment manager and under servers check that all the roles are in enabled state.

    b. The Async service may be down - check in services.msc that all CRM related services are running.

    CRM can be still functional at some level - even with the Async service down -  but workflows and some other functionality won't work.

    Good Luck



    • Proposed as answer by TZ00KI Sunday, March 23, 2014 2:53 PM
    Sunday, March 23, 2014 2:52 PM
  • Hi TZ00KI,

    Thanks for the reply.

    1. Yes, that's what I meant - I already installed the CRM SRS Data connector prior and used the installer inside the CRM Server 2013 Installation folder. The OOB reports have been working properly, but that error message that reporting is not enabled on the Deployment Managers bothers us.

    Here's an UPDATE today everyone: Regarding my main issues on creating new CRM Orgs and missing server roles, they are now resolved and I've discovered that the issue was internal, and I'm still sharing it here because it might help others in the future.

    The problem was that somebody from our Infra team removed/deleted the Active Directory Organization Units used specifically in the CRM Server 2013 installations. Note that when CRM Server 2013 is installed, the system creates 4 security groups (PrivReportingGroup, PrivUserGroup, SQLAccessGroup, & ReportingGroup) added to the AD Organization Unit specified during installation. Having an AD OU per CRM 2013 deployment is a recommended practice.

    Solution: After recreating the appropriate Active Directory Org Units, and then reapplying all the CRM Installation & Service Account permission requirements, we repaired the CRM Server 2013 "Full Server Role" installation using the CRM Server 2013 Install/Repair wizard, and sure enough, we were able to create new Orgs and the error message on the dashboards regarding the missing server roles have disappeared. Furthermore, the error message "Reporting is not enabled." also disappeared after the repair and restarting the servers. Interestingly, I've tried restarting our other CRM 2013 servers with the same error message on dashboard "Reporting is not enabled." (even though it's already installed on these servers and the OOB reports are working just fine), but unfortunately the error message is still there. I'm not sure how the error message "Reporting is not enabled." disappeared on our Sandbox and Dev servers deployment managers, as I didn't perform anything specific to this issue, but since after performing a repair of the full server installation and then restarting the servers, I'm thinking this could be a solution.

    Thanks to those always looking & taking the time to help fellow MS CRM community members.

    ProgCRM


    Monday, March 24, 2014 8:23 AM
  • Chek if server version is the same as the organization version. in my case i got this error the versions was diferents, i have upgraded to the same version and i'm able to create a new organization without errors.
    Thursday, October 16, 2014 5:41 PM
  • Hi,

    I am also have the same problem. I am new to MS Dynamics CRM, Can you explain the solution in Detail. 

    Wednesday, October 29, 2014 4:41 AM
  • There are few ad group created by CRM during installation. the issue reported above was when someone deleted these groups.

    solution is to recreate the ad group and add all permissions or reinstall crm and re-,import the organisation . Please check the following link about the ad group created.

    http://technet.microsoft.com/en-us/library/hh699704.aspx

    regards

    Jithesh

    Wednesday, October 29, 2014 10:40 AM