"ERR_INSUFFICIENT_RESOURCES" with Reference fields on catalog items in Service Portal

Community Alums
Not applicable

We have some reference fields that are behaving strangely in the Service Portal. they appear to be hanging after a few seconds. When we bring up the console to see what's going on, we get the error listed below.

These fields work fine from within   ServiceNow's main interface (and on our CMS pages). What's more, the behavior is somewhat inconsistent. Sometimes the reference fields appear to work fine.

Has anyone else run into this?   nathanfirth is this common, or is it something we've done?

Error Screenshot.png

Message was edited by: Andrew Cadaret

9 REPLIES 9

Community Alums
Not applicable

nathanfirth, will.leingang Do you know if this is fixed yet? I've opened up a ticket with Hi and am awaiting a response. I seem to remember talking to them about this a long time ago, and their resolution was basically to use code that used an iframe and the internal "process user" view of servicenow (not the portal). It wasn't mobile friendly or responsive.



Any updates?


Matthew Glenn
Kilo Sage

A bit late to the party, but I wanted to add this to the thread in case anyone else stumbles across it.



This is still an issue in Istanbul as of 2017-03-20, confirmed by Hi. Supposedly, it is being worked on by the development teams.



ServiceNow KB: PRB698938: Service Portal - Poor performance for Order Guide with large number of inc...


Community Alums
Not applicable

Wow, really? This is completely unacceptable. will.leingang do you know if this is in a patch?


Just heard back from Hi, with some disheartening news


Screen Shot 2017-03-21 at 9.40.02 AM.png


Community Alums
Not applicable

This is really amazing. It never should have made it into a release with this issue, and they're waiting two versions to implement a fix? Especially after telling us all earlier that it is already fixed in subsequent versions? In general I'm a ServicePortal evangelist, but at this point I'm tempted to tell management we need to go back to CMS.