Error in import logs upon washington upgrade

[Rain Vaine]

Hello,

Did anyone of you encounter the same error in the import logs upon upgrade in the Washington version?

Do you any idea on what are those errors?

Regards,
Vaine

[Community Alums]

Hi @Rain Vaine ,

Looks like you have a wrong table name.

https://www.servicenow.com/community/now-platform-articles/a-guide-to-troubleshooting-import-set-iss...

[Rain Vaine]

Hello,
Thanks for the reference article.
I will check on that one. Regarding the wrong table name, we didn't change anything. How is it possible that it just happen upon upgrade to washington?

Regards,
Vaine

[Krushna R Birla]

Hi @Rain Vaine 

For Example, For this kind of errors "Error: GlideRecord.get() - invalid table name: <TABLE_NAME> (sys_script_include.5ce7a5cddb985b84689feda5ca961917.script; line 48)"

Cause :

• The table was removed from the instance during a clone.
• The table cannot be found in sys_db_object table.
• if a script tries to query the invalid table using Glide API the mentioned error is thrown.

Resolution:

• Fix the script by removing the invalid table.
• Add the missing table on the instance.

This will definitely helps you to resolved your issue. Let me know in case you need to understand the flow or you can DM on LinkedIn.

If this solution resolves your query, kindly mark it as the accepted solution and give it a thumbs up.

Best Regards,
Krushna Birla

[Rain Vaine]

Hello,
Regarding the removed table, we didn't change anything. How is it possible that it just happen upon upgrade to washington?

Regards,
Vaine