<?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 Re: How to stop users accessing the system? in QlikView</title>
    <link>https://community.qlik.com/t5/QlikView/How-to-stop-users-accessing-the-system/m-p/2047915#M1244089</link>
    <description>&lt;P&gt;Hey&amp;nbsp;&lt;a href="https://community.qlik.com/t5/user/viewprofilepage/user-id/221361"&gt;@christianw&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;Based on your description it seems that handling users on the QlikView Server/AccessPoint side and handling reload tasks on the QlikView Distribution Service (QDS) side is overwhelming your system resources.&amp;nbsp; I don't believe there is a way to accomplish your goal from within QlikView itself, but you may try experimenting with using a Windows Scheduled Task to stop the QlikView Web Server service during your reload time and then start the service again once reloads have completed.&lt;/P&gt;
&lt;P&gt;For a lasting solution, suggest installing QlikView Publisher on it's own Windows Server so that QDS has enough resources in order to handle reload/distribution tasks. If you don't currently have a Publisher license, you can purchase one via your Qlik account manager.&lt;/P&gt;
&lt;P&gt;Best Regards&lt;/P&gt;</description>
    <pubDate>Fri, 10 Mar 2023 13:23:36 GMT</pubDate>
    <dc:creator>Chip_Matejowsky</dc:creator>
    <dc:date>2023-03-10T13:23:36Z</dc:date>
    <item>
      <title>How to stop users accessing the system?</title>
      <link>https://community.qlik.com/t5/QlikView/How-to-stop-users-accessing-the-system/m-p/2047710#M1244088</link>
      <description>&lt;P&gt;How can we temporarily suspend user access to QlikView?&lt;BR /&gt;We find that when we are doing a data refresh, if a user accesses the system at the same time, it causes our data refresh to fail. We are a 24x7 company, so we can't guarantee that people are not using it over night.&lt;/P&gt;
&lt;P&gt;Can we safely just stop the QlikView Web Service, and then start the service again when the data load is finished?&lt;/P&gt;</description>
      <pubDate>Mon, 26 Jan 2026 18:19:17 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/How-to-stop-users-accessing-the-system/m-p/2047710#M1244088</guid>
      <dc:creator>christianw</dc:creator>
      <dc:date>2026-01-26T18:19:17Z</dc:date>
    </item>
    <item>
      <title>Re: How to stop users accessing the system?</title>
      <link>https://community.qlik.com/t5/QlikView/How-to-stop-users-accessing-the-system/m-p/2047915#M1244089</link>
      <description>&lt;P&gt;Hey&amp;nbsp;&lt;a href="https://community.qlik.com/t5/user/viewprofilepage/user-id/221361"&gt;@christianw&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;Based on your description it seems that handling users on the QlikView Server/AccessPoint side and handling reload tasks on the QlikView Distribution Service (QDS) side is overwhelming your system resources.&amp;nbsp; I don't believe there is a way to accomplish your goal from within QlikView itself, but you may try experimenting with using a Windows Scheduled Task to stop the QlikView Web Server service during your reload time and then start the service again once reloads have completed.&lt;/P&gt;
&lt;P&gt;For a lasting solution, suggest installing QlikView Publisher on it's own Windows Server so that QDS has enough resources in order to handle reload/distribution tasks. If you don't currently have a Publisher license, you can purchase one via your Qlik account manager.&lt;/P&gt;
&lt;P&gt;Best Regards&lt;/P&gt;</description>
      <pubDate>Fri, 10 Mar 2023 13:23:36 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/How-to-stop-users-accessing-the-system/m-p/2047915#M1244089</guid>
      <dc:creator>Chip_Matejowsky</dc:creator>
      <dc:date>2023-03-10T13:23:36Z</dc:date>
    </item>
  </channel>
</rss>

