JavaScript error when searching for users in Location Directory
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-01-2025 07:12 AM - edited 05-01-2025 07:14 AM
Been living with this issue for a few releases now. Kicked the can on dealing with it, as we hoped updating the plugins would take care of it organically. That hasn't been the case, so now I'm invested in troubleshooting.
Failed to load resource: the server https://adtprod.service-now.com/api/sn_wsd_core/wsd_unified_search/current_location?userSysId=XXXXXXXXXXXXXXXX responded with a status of 500 (Internal Server Error)
Anyone else experienced this problem, or any known fixes before I go the route of opening a support case?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-01-2025 07:42 AM
Hi @davidb, looking at the API you have pasted it looks like WSD Location is being queried with that user's sysID and its not finding the relevant component on the page. First picture that you have pasted also points at some of the elements missing while loading.
You can launch "Script Tracer" and start the Script Tracer then launch that page again to see which application file is creating that load error at run time.
Like example below it will show you from where it is coming.
In this way you can find the source of that error and fix yourself.
Hope this helps.
Let me know if it was helpful.
Regards,
Vikas K
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-02-2025 07:55 AM
Thanks, will give Script Tracer a go! Not sure what that 'oneway' image issue is about, we don't have anything on our maps like that. I know we built our maps before Indoor Mapping got its overhaul to be an actual CAD program, so I'm thinking that we're starting to reach the point of needing to redo our maps.
I also reviewed the API in the REST API explorer - that parameter structure being passed in doesn't match the parameter definitions in the API. Also going to see if we have some WSD components that aren't up-to-date.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-02-2025 08:23 AM
Thanks for updating me!
Please update this thread when you find the solution. It will help in future if someone needs similar fix.
Cheers!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-21-2025 04:56 PM
@DavidB-ADT Im getting the same errors. Were you able to fix this?