Home Advanced Request Offering

Long time to save ARO Request

Peter_NordqvistPeter_Nordqvist Customer Adept IT Monkey ✭✭
Hi, got an issue with ARO in the portal.
When the form is filled in and we hit save, it takes around 60 seconds to save and create a SR in Service Manager.
Does anyone else had this problem?

Answers

  • Tony_CollettTony_Collett Cireson Support Super IT Monkey ✭✭✭✭✭
    Are you getting any errors appear in the Webconsole log at the time of saving? Do users get any errors in their developer console tab?
  • Peter_NordqvistPeter_Nordqvist Customer Adept IT Monkey ✭✭
    Hi
    Thanks, just before the request getting saved in the portal this pops up in webconsole.log:
     PopulateCachedEmos failed: The query processor ran out of internal resources and could not produce a query plan. This is a rare event and only expected for extremely complex queries or queries that reference a very large number of tables or partitions. Please simplify the query. If you believe you have received this message in error, contact Customer Support Services for more information.
    And it seems this occurs even on requests that not having any query or enumeration filelds in the form (just text) No errors in dev console
    Thanks
  • Tony_CollettTony_Collett Cireson Support Super IT Monkey ✭✭✭✭✭
    Which version of the portal are you using?
  • Peter_NordqvistPeter_Nordqvist Customer Adept IT Monkey ✭✭
    Which version of the portal are you using?
     8.4.3.2012
  • Peter_NordqvistPeter_Nordqvist Customer Adept IT Monkey ✭✭
    I have opened a case for this
  • David_Morris1David_Morris1 Member Advanced IT Monkey ✭✭✭
    did you work out this issue?
  • Peter_NordqvistPeter_Nordqvist Customer Adept IT Monkey ✭✭
    did you work out this issue?
    Hi David, yes, we got it sorted with help from @john_doyle
    We altered the setting PrePopulateCiLimit to 10000 (portal settings), and then recycled the application pool.
Sign In or Register to comment.