web
You’re offline. This is a read only version of the page.
close
Skip to main content
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics GP (Archived) / Unhandled Script Excep...
Microsoft Dynamics GP (Archived)

Unhandled Script Exception - Corrupted report in "My Reports"

(0) ShareShare
ReportReport
Posted on by Jodi Wurts 80

I receive the following error when any user logs into the company.  Each user appears to have a corrupt report in their "My Reports" seciton on their homepage.  If I try to go into change details for My Reports, I recieve the same error.  If I try to delete the report inside the change details screen I also receive the error.  I suspect I need to find a way to get rid of this report from My Reports to resolve the issue, but have been unable to figure out how to remove these corrupted reports.

Ran a Maintenance - Check Links - Financial - All and a Maintenance Check Links Company - All as well as a Maintenance - Check Links - System - All.  Also ran the GP DB Maintenance utility on this particular company database.  I have multiple companies, this is the only one with an issue.

Unhandled script exception:
Object has no reference.

EXCEPTION_CLASS_SCRIPT_BAD_PARAM
SCRIPT_CMD_DEREF_TABLE


Any ideas on what to do to get rid of those corrupt reports? Any ideas on how to troubleshoot the script errors?

*This post is locked for comments

I have the same question (0)
  • Jodi Wurts Profile Picture
    Jodi Wurts 80 on at
    Re: Unhandled Script Exception - Corrupted report in "My Reports"

    Further updates - The "Add Reports" link is completely missing from the "My Reports" section for all users.  This appears to be a technical problem of some kind...might need to call support.

  • Verified answer
    Jodi Wurts Profile Picture
    Jodi Wurts 80 on at
    Re: Unhandled Script Exception - Corrupted report in "My Reports"

    I figured out how to fix this on my own.  In SQL Manager I found the offending records and deleted them.  They were in the DYNAMICS db located in [dbo].[SY70700]. I deleted the offending records using SQL and the problem is gone.  Looks like the records were just orphaned somehow.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Abhilash Warrier – Community Spotlight

We are honored to recognize Abhilash Warrier as our Community Spotlight honoree for…

Congratulations to the September Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics GP (Archived)

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans