Uncaught TypeError: \$j(...).popover is not a function

[Geoffrey2]

Hi.   I just wanted to document an issue I have come across a few times recently, since I couldn't find anything about it when searching for it.

There is a Problem that mentions this error, PRB713498, but the symptoms are not the same in this case.

https://hi.service-now.com/kb_view.do?sysparm_article=KB0610282

On a few random occasions, single users will start experiencing Client Side script failure when loading a specific form. The tabs won't render, UI Policies are not applied, Client Scripts don't work, and the Context Menu is not available.

I have seen it happen for single users on single forms. For example, I had this issue when viewing only Assignment Rule records, and another user had this issue when viewing Change Requests. There are no custom UI Scripts as mentioned in the Problem.

In the console log you can see the following error: Uncaught TypeError: $j(...).popover is not a function

The instance is Helsinki Patch 7.

I tried clearing the User Preferences and logging the User out, but the issue remained. I was able to fix it with cache.do

Navigate to <instance_name>.service-now.com/cache.do

I have not determined the root cause, but I wanted to let people know the immediate fix if they get this issue. Please let me know if you know a permanent solution.

[sergiu_panaite]

Hi Geoffrey,

Have you added to the instance your own jQuery library?

[kirkr]

In case it is relevant to others, ServiceNow performed routine maintenance on our production instance last night. This morning we had the same issue and was also limited to specific users.

This also worked for us with a few minor extra steps for users.

• Clear the server cache with cache.do
• Have the users that were experiencing the issue log out
• Clear their browser cache
• Log back in

This resolved the issues for the few users that had this.

Worth noting is having the users switch from UI16 to UI15 allowed users to work tickets as we worked out how to resolve this.

[timcalvert]

Thanks kirkr. We were having a similar at our organisation.

It was only affecting 1 user.

The Incident form was prevented from fully loading by a TypeError: $j(...).popover is not a function

The cache.do solution worked.

[M Turner]

We've had the same issue on our production instance, same error. A colleague pointed us this way after googling the error. cache.do cleared it almost straight away!

Our symptoms were the same - a small group of users could not load parts of a form, which failed with the errors mentioned above. Didn't seem to affect everyone, and was across browsers/devices so definitely user-servicenow-cache related rather than browser or device cache.