Configure IIS Process Private Memory Limit

On CCure 9000 version 2.90 SP6 and 3.00.1 the IIS process creates a memory leak when the personalized login feature is used with XProtect Access.

Upgrading to CCure 9000 version 3.00.2 after upgrading the XProtect Access integration to the 1.4 version will fix this issue. To fix the issue on the 2.90 SP6 and 3.00.1 versions of CCure 9000 please continue reading below.

To fix this issue it is recommended to remove the limit of memory the process can utilize. Below is the procedure for making this change:

  1. On the CCure 9000 server, search for and open the Internet Information Services (IIS) Manager app.

  2. Expand the host server node in the Connections directory and select the Application Pools menu.

  3. Right click the victorwebservice application pool, and select Advanced Settings from the short cut menu.

  1. In the Advanced Settings dialog window, scroll down to the Recycling subsection and set the Private Memory Limit (KB) to zero.

  2. Click OK, to save the configuration. Verify the victorwebservice application pool is started, and exit the IIS Manager.