K2 Five 5.3 Configure User Filter Add New Filter issue

  • 15 August 2019
  • 2 replies

Has anyone in the K2 Five community experience any issues when using the default Configure User Filter on a new Add Filter and the popup window just spins? [see attachment for screenshot]


2 replies

Hi  @yyang469;


This seems like performance issue, just for diagnose, kindly assist us with the following: -

---I presume at this moment you ‘have dealt with memory cache, Restarted the k2 server/services and/or performed IIsreset

---have you tested this on different browsers? Familiarize yourself with this kb, if you experience the issue with only specific browser, for alignment of designer browser interaction(https://help.k2.com/kb001893)

---when did you start experiencing the issue, has it happened after certain k2 or browser related update… fixpack perhaps? Which version of k2 specifically are you on, to check please dive in this kb(https://help.k2.com/kb001893).

---On your k2 HostServer logs, recently have you ever had errors such as “systemOutOfMemory.Exception” or any memory related issue? this kind of errors can affect it badly causing weird performance behavior issues.

--- How have you performed the operation “config user filter” (https://help.k2.com/kb001441)

---If you don’t have any custom controls implemented on your system, Repair option might be valuable workaround.

--- Also consider checking smartform logging, there might be some sort of cache blockage within the design causing performance issues(http://help.k2.com/onlinehelp/K2smartforms/DevRef/4.7/default.htm#web_config_Debugging.html%3FTocPath%3DConfiguration%2520Reference%7CSmartForms%2520WebSite%2520web.config%7C_____5),

see this demo(https://help.k2.com/displaycontent.aspx?id=6241).


Hope your issue will get resolved.


Kind regards;


Userlevel 6
Badge +16

Hi yyang469,


Perhaps this support KB might help (http://help.k2.com/support-services/kbt155393).

I would double check both [Form].[UserSetting] and [Form].UserProfile] tables. If this is the case, i would suggest logging a support case to resolve it.