System log Error message

Christian_ · ‎10-17-2019

Have encountered this error on several occasions, but have not yet been able to establish why it occurs.
This has been observed in several instances, both on Madrid and New York.

Level : Error
Message : null: no thrown error
Source : com.glide.ui.ServletErrorListener

Any suggestions or knowledge of its root cause?

Christian_ · ‎01-09-2020

This KB Article solved the issue : Error log throwing up "null: no thrown error" when loading certain Dashboards :

Resolution

Following steps can be taken to avoid these errors in the system logs:

Ensure that all the objects used in the dashboard (such as reports, PA widgets, content blocks, and other widgets) are brought over to the target instance.
If some error still show up after bringing across all the configurations and the dashboard itself is not having any issues except for the errors appearing in the logs, deleting all the sys_grid_canvas_pane records having invalid references returned by the following URL should get rid of the errors in the logs.

https://<instance>.service-now.com/sys_grid_canvas_pane_list.do?sysparm_query=portal_widget.sys_idIS...

Note:

Take an XML backup of the records before deleting them so that you can revert in case of any issues.
Please test the solution on a recently cloned instance before applying any solution on the production instance.

View solution in original post

Chris P_ · ‎08-25-2021

Ow wow that really works!

I had mistaken portal_widget.sys_idISEMPTY with an empty column Portal widget on that page...
So I had only deleted those with that column empty.

Now I just deleted everything that was shown using the given url and no more errors (or at least, not this one 🙂 )

Thanks!

Rachel Gomez · ‎07-25-2022

In short format, also called summary format, each message in the system error log occupies a single line. The description of the fields in the short format of the system error log: In long format, a page of formatted information is displayed for each error.

Steps to fix

Create a backup of everything important on your PC such as photos. It is best to backup your important files to a disk in case something goes wrong when trying to repair the computer.

Determine the cause of the error message. Consider what you are doing on your PC when the error message appears, write down what program is causing the error, what version of the program you are running, and what is the program trying to do when the error occurs.

Scan your computer with your anti-virus application and remove any threats it detects. Viruses and Spyware can cause error messages on your PC and may be the source of your current issue.

Once you scan with your anti-virus and anti-spyware application check and see if the issue is resolved.

If the program is still causing an error use your favorite search engine and type in the exact error you are getting.

Check the search results for any possible solutions to your particular error message.

Contact technical support for the product or computer if you are unable to narrow the cause of the issue with these steps. Be sure to provide the agent with a detailed list of everything you have already done.

Regards,

Rachel Gomez

Peter Groft · ‎08-04-2022

An error log is a personalized document that lists your mistakes and how to correct them. When you receive feedback about a mistake in your writing, you create an entry in your error log that includes the error and how to correct it.

Hope You Find This Useful,
Peter