<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic QMC not working after windows domain setup in Management &amp; Governance</title>
    <link>https://community.qlik.com/t5/Management-Governance/QMC-not-working-after-windows-domain-setup/m-p/2521577#M31996</link>
    <description>&lt;P&gt;Hi, &lt;BR /&gt;I bought Qlik Sense Enterprise with License from AWS marketplace and created an instance. First login I setup the service user and set the passwords for repository and db. I added the license, configured the proxy and virtual proxy through QMC. &lt;BR /&gt;I added the windows qliksense instance to our company domain (managed through LDAP). The domain setup was success and I could add LDAP users as well. After that QMC stops working "This site can’t be reached". I checked System_Repository logs and it keeps logging below warnings. Please note, if I remove domain from windows instance QMC works fine. Could you please look into this issue and let me know how to resolve the issue:&lt;BR /&gt;118 20250618T120202.593+0000 INFO EC2AMAZ-29T9PQ8 System.Repository.Repository.QRSMain 6 5219bc22-9105-4abd-8462-69a2b8e3dfac EC2AMAZ-29T9PQ8\xploraadmin Entering main startup phase.. 5219bc22-9105-4abd-8462-69a2b8e3dfac&lt;BR /&gt;119 20250618T120216.630+0000 WARN EC2AMAZ-29T9PQ8 System.Repository.Repository.Core.ProxySettings.ProxyServiceSettingsInstallerFile 6 2e6ea574-34f1-4e34-b7ac-1ed35cf94dbd EC2AMAZ-29T9PQ8\xploraadmin ProxyServiceSettingsUpdate will be skipped (File: C:\ProgramData\Qlik\Sense\Installation\InitialServiceCluster.xml does not exist) 2e6ea574-34f1-4e34-b7ac-1ed35cf94dbd&lt;BR /&gt;120 20250618T120216.646+0000 INFO EC2AMAZ-29T9PQ8 System.Repository.Repository.Core.Core 6 073792f5-9292-4888-b7da-8332e46c599b EC2AMAZ-29T9PQ8\xploraadmin Entering inner core.. 073792f5-9292-4888-b7da-8332e46c599b&lt;BR /&gt;121 20250618T120216.646+0000 INFO EC2AMAZ-29T9PQ8 System.Repository.Repository.Core.Core 6 36025a78-7c6f-452f-8a3f-1691c5f9cc9f EC2AMAZ-29T9PQ8\xploraadmin Setting up core.. 36025a78-7c6f-452f-8a3f-1691c5f9cc9f&lt;BR /&gt;122 20250618T120216.897+0000 INFO EC2AMAZ-29T9PQ8 System.Repository.Repository.Core.Database.DeletedEntityLogFilter 6 6537bacb-2741-4c0d-97f3-8719c595352b EC2AMAZ-29T9PQ8\xploraadmin The following entities will be excluded from the DeletedEntityLog: TempContent, ExecutionResult, ExecutionResultDetail, ExecutionSession 6537bacb-2741-4c0d-97f3-8719c595352b&lt;BR /&gt;123 20250618T120216.897+0000 INFO EC2AMAZ-29T9PQ8 System.Repository.Repository.Core.Core 6 a4214dcb-fdde-4f19-97bf-5b5cc2e634ca EC2AMAZ-29T9PQ8\xploraadmin Deleted entity log initialized a4214dcb-fdde-4f19-97bf-5b5cc2e634ca&lt;BR /&gt;124 20250618T120216.943+0000 INFO EC2AMAZ-29T9PQ8 System.Repository.Repository.Core.Cluster.ServiceClusterSetup 6 3a64defe-6407-444f-b116-17e9cc777716 EC2AMAZ-29T9PQ8\xploraadmin ServiceCluster with name ServiceCluster initialized 3a64defe-6407-444f-b116-17e9cc777716&lt;BR /&gt;125 20250618T120217.053+0000 WARN EC2AMAZ-29T9PQ8 System.Repository.Repository.Core.Licensing.LicensesInitializer 6 f833a5ca-8b13-4270-88cb-ab8c28d82933 EC2AMAZ-29T9PQ8\xploraadmin There was an error contacting the license service. Keep retrying... (1 failed requests) GET /v1/licenses/overview StatusCode: InternalServerError Response: . Could not connect to the license service. NO-STACKTRACE f833a5ca-8b13-4270-88cb-ab8c28d82933&lt;BR /&gt;126 20250618T120244.138+0000 WARN EC2AMAZ-29T9PQ8 System.Repository.Repository.Core.Licensing.LicensesInitializer 6 b22bebdd-9224-4741-a2db-1ba79906eac1 EC2AMAZ-29T9PQ8\xploraadmin There was an error contacting the license service. Keep retrying... (10 failed requests) GET /v1/licenses/overview StatusCode: InternalServerError Response: . Could not connect to the license service. NO-STACKTRACE b22bebdd-9224-4741-a2db-1ba79906eac1 &lt;BR /&gt;Thank you,&lt;BR /&gt;AJ&lt;/P&gt;</description>
    <pubDate>Wed, 18 Jun 2025 12:38:31 GMT</pubDate>
    <dc:creator>AJ10</dc:creator>
    <dc:date>2025-06-18T12:38:31Z</dc:date>
    <item>
      <title>QMC not working after windows domain setup</title>
      <link>https://community.qlik.com/t5/Management-Governance/QMC-not-working-after-windows-domain-setup/m-p/2521577#M31996</link>
      <description>&lt;P&gt;Hi, &lt;BR /&gt;I bought Qlik Sense Enterprise with License from AWS marketplace and created an instance. First login I setup the service user and set the passwords for repository and db. I added the license, configured the proxy and virtual proxy through QMC. &lt;BR /&gt;I added the windows qliksense instance to our company domain (managed through LDAP). The domain setup was success and I could add LDAP users as well. After that QMC stops working "This site can’t be reached". I checked System_Repository logs and it keeps logging below warnings. Please note, if I remove domain from windows instance QMC works fine. Could you please look into this issue and let me know how to resolve the issue:&lt;BR /&gt;118 20250618T120202.593+0000 INFO EC2AMAZ-29T9PQ8 System.Repository.Repository.QRSMain 6 5219bc22-9105-4abd-8462-69a2b8e3dfac EC2AMAZ-29T9PQ8\xploraadmin Entering main startup phase.. 5219bc22-9105-4abd-8462-69a2b8e3dfac&lt;BR /&gt;119 20250618T120216.630+0000 WARN EC2AMAZ-29T9PQ8 System.Repository.Repository.Core.ProxySettings.ProxyServiceSettingsInstallerFile 6 2e6ea574-34f1-4e34-b7ac-1ed35cf94dbd EC2AMAZ-29T9PQ8\xploraadmin ProxyServiceSettingsUpdate will be skipped (File: C:\ProgramData\Qlik\Sense\Installation\InitialServiceCluster.xml does not exist) 2e6ea574-34f1-4e34-b7ac-1ed35cf94dbd&lt;BR /&gt;120 20250618T120216.646+0000 INFO EC2AMAZ-29T9PQ8 System.Repository.Repository.Core.Core 6 073792f5-9292-4888-b7da-8332e46c599b EC2AMAZ-29T9PQ8\xploraadmin Entering inner core.. 073792f5-9292-4888-b7da-8332e46c599b&lt;BR /&gt;121 20250618T120216.646+0000 INFO EC2AMAZ-29T9PQ8 System.Repository.Repository.Core.Core 6 36025a78-7c6f-452f-8a3f-1691c5f9cc9f EC2AMAZ-29T9PQ8\xploraadmin Setting up core.. 36025a78-7c6f-452f-8a3f-1691c5f9cc9f&lt;BR /&gt;122 20250618T120216.897+0000 INFO EC2AMAZ-29T9PQ8 System.Repository.Repository.Core.Database.DeletedEntityLogFilter 6 6537bacb-2741-4c0d-97f3-8719c595352b EC2AMAZ-29T9PQ8\xploraadmin The following entities will be excluded from the DeletedEntityLog: TempContent, ExecutionResult, ExecutionResultDetail, ExecutionSession 6537bacb-2741-4c0d-97f3-8719c595352b&lt;BR /&gt;123 20250618T120216.897+0000 INFO EC2AMAZ-29T9PQ8 System.Repository.Repository.Core.Core 6 a4214dcb-fdde-4f19-97bf-5b5cc2e634ca EC2AMAZ-29T9PQ8\xploraadmin Deleted entity log initialized a4214dcb-fdde-4f19-97bf-5b5cc2e634ca&lt;BR /&gt;124 20250618T120216.943+0000 INFO EC2AMAZ-29T9PQ8 System.Repository.Repository.Core.Cluster.ServiceClusterSetup 6 3a64defe-6407-444f-b116-17e9cc777716 EC2AMAZ-29T9PQ8\xploraadmin ServiceCluster with name ServiceCluster initialized 3a64defe-6407-444f-b116-17e9cc777716&lt;BR /&gt;125 20250618T120217.053+0000 WARN EC2AMAZ-29T9PQ8 System.Repository.Repository.Core.Licensing.LicensesInitializer 6 f833a5ca-8b13-4270-88cb-ab8c28d82933 EC2AMAZ-29T9PQ8\xploraadmin There was an error contacting the license service. Keep retrying... (1 failed requests) GET /v1/licenses/overview StatusCode: InternalServerError Response: . Could not connect to the license service. NO-STACKTRACE f833a5ca-8b13-4270-88cb-ab8c28d82933&lt;BR /&gt;126 20250618T120244.138+0000 WARN EC2AMAZ-29T9PQ8 System.Repository.Repository.Core.Licensing.LicensesInitializer 6 b22bebdd-9224-4741-a2db-1ba79906eac1 EC2AMAZ-29T9PQ8\xploraadmin There was an error contacting the license service. Keep retrying... (10 failed requests) GET /v1/licenses/overview StatusCode: InternalServerError Response: . Could not connect to the license service. NO-STACKTRACE b22bebdd-9224-4741-a2db-1ba79906eac1 &lt;BR /&gt;Thank you,&lt;BR /&gt;AJ&lt;/P&gt;</description>
      <pubDate>Wed, 18 Jun 2025 12:38:31 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Management-Governance/QMC-not-working-after-windows-domain-setup/m-p/2521577#M31996</guid>
      <dc:creator>AJ10</dc:creator>
      <dc:date>2025-06-18T12:38:31Z</dc:date>
    </item>
    <item>
      <title>Re: QMC not working after windows domain setup</title>
      <link>https://community.qlik.com/t5/Management-Governance/QMC-not-working-after-windows-domain-setup/m-p/2521617#M31997</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.qlik.com/t5/user/viewprofilepage/user-id/335996"&gt;@AJ10&lt;/a&gt;&amp;nbsp;!&lt;/P&gt;&lt;P&gt;It's not recommended to change HostName and Domain after install Qlik in Windows Environment.&lt;/P&gt;&lt;P&gt;You have two options:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;1 - Remove Qlik ( if it's possible ) and reinstall and reconfigure&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;2 - Follow the same procedure when we need to reinstall or change user in Qlik&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.qlik.com/t5/Official-Support-Articles/Qlik-Sense-Enterprise-on-Windows-Change-hostname-and/ta-p/1713945" target="_blank" rel="noopener"&gt;https://community.qlik.com/t5/Official-Support-Articles/Qlik-Sense-Enterprise-on-Windows-Change-hostname-and/ta-p/1713945&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Why:&lt;/P&gt;&lt;P&gt;- Certificates are generated in installation to crypt data.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Bye!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 18 Jun 2025 14:54:43 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Management-Governance/QMC-not-working-after-windows-domain-setup/m-p/2521617#M31997</guid>
      <dc:creator>rafaelencinas</dc:creator>
      <dc:date>2025-06-18T14:54:43Z</dc:date>
    </item>
  </channel>
</rss>

