- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-17-2024 09:33 AM
We are getting the JAVAscript error on service portal after the Washington DC upgrade.
If anyone face the similar issue please suggest the solution.
Thanks!
Vaibhav J
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-20-2024 05:14 AM
I had the same issue and opened a ticket. Apparently this is a known issue and there is a fix in Xanadu and a possible hot fix releasing today -
Issue:
Javascript error on ESC after upgrade to Wash DC
Most Probable Cause:
This is a known issue, please refer the PRB1758577
https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1644179
Solution Proposed:
This problem is currently fixed in the Xanadu Release, and is currently tentatively targeted for a fix within the "Washington DC Patch 4" and "Washington DC Patch 3 Hot Fix 1" release. As of now, there is no functional impact of this PRB.
If you wish to suppress these errors as a workaround, the property "glide.sp.show_console_error" can allow you to achieve this. These errors are governed by the above property, and are only displayed to admin users (even when impersonation is used). When a non admin accesses the portal (through a direct login), they should not be able to see the errors. Disabling this can allow you to suppress the messages for admin users, however this will disable all javascript errors:
Alternatively, upgrading to Washington DC Patch 3 Hot Fix 1, which is currently targeted for a release on the 20th May, can also resolve the issue faced.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-17-2024 10:02 AM
Please check error in console and post.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-20-2024 03:36 AM
Hi Ravi,
Here is the error in console.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-07-2024 03:45 AM
I have exactly the same errors displayed, and the last Patch didn't solve the issue for me, did it work for you?
Kind regards.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-24-2024 08:25 AM
Hi,
We have upgraded to Washington DC Patch 4 and issue got resolve.
Thanks!
Vaibhav J