Skip to content

x Want to ask a question or reply? Click here to join the group.
Options
  • State Verified Answer
  • Replies 3 replies
  • Subscribers 37 subscribers
  • Views 2229 views
  • Users 0 members are here
Browse Forums
Announcements
61
topics
77
replies
Customization and Integration
89
topics
301
replies
Financials, Projects, and Administration
92
topics
247
replies
General Discussion
221
topics
554
replies
Installation and Technical Issues
131
topics
432
replies
Manufacturing, Distribution, and Applications
38
topics
77
replies
Reporting and Analytics
54
topics
223
replies

Sage intelligence object reference not set to an instance of an object

lizf
Solved
Posted By

Need assistance with our MAS Intelligence Report Designer reports all the sudden having the error “Object reference not set to an instance of an object.”?    Has anyone else started getting these recently?

Our report templates use a lot of single account numbers in the formulas so when I make those a range “xxxxx to xxxxx” they work.  I've checked to make sure we don't have any GL accounts with currency restriction codes other than 0,  that we don't have any Natural accounts without an actual GL account and no updates or changes have been applied to Windows or Excel.

  • 0

    That type of error is typically an application problem where the code did not expect a condition it is encountering. It tends to occur when you makes changes to the operating system or install an incompatible application, especially one that uses or updates Crystal. If there are no Windows updates, then review the system for other recently installed, updated or even deleted applications. If you are logging as a specific user, try an administrative account, there could have been group policy changes you aren't seeing.

  • +1 in reply to Contefication
    Verified Answer

    It was actually a Natural Account that didn't have a segmented account associated with it.  When I checked through our Natural accounts I wasn't using the accounts tab in the MAS Intelligence reports so I missed it.

    Error: 'Object reference not set to an instance of an object' on the Report Designer Add-in report

    Created on 06 July 2021 | Last modified on 06 July 2021 Highlight Matches

    •  
    •  
    •  

    Cause

    A natural account number with no associated segmented accounts exists within the chart of accounts.

    Resolution

    1. Open the Excel sheet generated by Sage Intelligence
    2. Un-hide the Accounts sheet.
    3. Perform a search for a blank Segmented Account Number on the spreadsheet.
    4. Delete the Natural Account Number from Sage 500, General Ledger, Maintenance, Maintain GL Accounts, Maintain Natural Accounts.
    5. Repeat the process for additional blank Segmented Account Numbers.
  • +1
    Verified Answer

    Error: 'Object reference not set to an instance of an object' on the Report Designer Add-in report

    Created on 06 July 2021 | Last modified on 06 July 2021 Highlight Matches

    •  
    •  
    •  

    Cause

    A natural account number with no associated segmented accounts exists within the chart of accounts.

    Resolution

    1. Open the Excel sheet generated by Sage Intelligence
    2. Un-hide the Accounts sheet.
    3. Perform a search for a blank Segmented Account Number on the spreadsheet.
    4. Delete the Natural Account Number from Sage 500, General Ledger, Maintenance, Maintain GL Accounts, Maintain Natural Accounts.
    5. Repeat the process for additional blank Segmented Account Numbers.

*Community Hub is the new name for Sage City