@Ismail27 Take a look ob below links:   https://docs.cloudera.com/data-warehouse/cloud/managing-environments/topics/dw-azure-environment-requirements-checklist.html https://blog.cloudera.com/cloudera-data-platform-cdp-now-available-on-microsoft-azure-marketplace-providing-unified-billing-for-joint-customers/ ... View more

@GregDol What is the error you are getting on the page, have you tried to see the console out put in browser's development tool to see what's happening? ... View more

@hayhapra You need to start looking at the logs first and see what's in there then start form there to investigate this issue.  ... View more

@stefen Not familiar with issue but came through these useful links if helps.    https://docs.telerik.com/reporting/knowledge-base/refused-to-display-url-in-a-frame-because-it-set-x-frame-options-to-sameorigin https://stackoverflow.com/questions/20498831/refused-to-display-in-a-frame-because-it-set-x-frame-options-to-sameorigin https://stackoverflow.com/questions/41522652/refused-to-display-url-in-a-frame-because-it-set-x-frame-options-to-sameori?noredirect=1&lq=1 ... View more

@sahil2598 Check the below thread this might help you.  https://github.com/gradle/gradle/issues/1453 ... View more

Thanks for your response.  we are configuring 60000.  present it is ok  ... View more

@ateka_18 Here is the Cause and Solution of this issue.    Cause:  Microsoft recently rolled out an Active Directory update for CVE-2020-17049 [1]. This update indicates: 'When the registry key is set to 1, patched domain controllers will issue service tickets and Ticket-Granting Tickets (TGT)s that are not renewable and will refuse to renew existing service tickets and TGTs. Windows clients are not impacted by this since they never renew service tickets or TGTs. Third-party Kerberos clients may fail to renew service tickets or TGTs acquired from unpatched DCs. If all DCs are patched with the registry settings to 1, third-party clients will no longer receive renewable tickets. Now the Solution is:   We have found out that MSFT has also released a fix for the Kerberos authentication issue. To fix the Windows AD, you can engage with the AD team to apply one of the following patches that MSFT has provided to fix the Kerberos authentication issue. Please link on the appropriate link based on the flavor of the Windows Server. Windows Server 2012: https://www.catalog.update.microsoft.com/Search.aspx?q=KB4594438 Windows Server 2012 R2: https://www.catalog.update.microsoft.com/Search.aspx?q=KB4594439Windows Server 2016: https://www.catalog.update.microsoft.com/Search.aspx?q=KB4594441 Windows Server 2019: https://www.catalog.update.microsoft.com/Search.aspx?q=KB4594442 Windows Server 1903: https://www.catalog.update.microsoft.com/Search.aspx?q=KB4594443 Windows Server 1909: https://www.catalog.update.microsoft.com/Search.aspx?q=KB4594443 Windows Server 2004: https://www.catalog.update.microsoft.com/Search.aspx?q=KB4594440 Windows Server 20H2: https://www.catalog.update.microsoft.com/Search.aspx?q=KB4594440 Once the patch is applied, the application will be able to renew the tickets without theneed to apply any patch for Hue. [1] https://msrc.microsoft.com/update-guide/vulnerability/CVE-2020-17049  So in short you have to ask you AD team to apply the below patch on Domain Controllers to resolve this  issue since it's a Microsoft Vulnerability.  https://msrc.microsoft.com/update-guide/vulnerability/CVE-2020-17049   ... View more

@GangWar Everything went smoothly after your reply.  Thank you. ... View more

@backlashhardik  The manual process means install agent beforehand on all of the hosts which you are going to add. Make sure you have local repo or internet access.    sudo yum install cloudera-manager-agent cloudera-manager-daemons  If agent is installed then reinstall to avoid any issue once again.  sudo yum reinstall cloudera-manager-agent cloudera-manager-daemons  Then you have to modify the /etc/cloudera-scm-agent/config.ini file and post this to CM server, also if TLS is enabled make necessary changes.  [General] # Hostname of the CM server. server_host=host-xx.xxx.xxx.cloudera.com Then go to the CM and try to add hosts from there. Since agent is already installed this should not take much time and you can start agent then and see if that helps.  ... View more