Excel Error: object reference not set to an instance of an object

[blairwhitworth320]

Hi-

In the last week I've started receiving the following message whenever I open Excel 365 (through the application, or opening a file): 

I tried using the short and long repair options for Office 365 without any success.

I have all the latest updates installed for both Windows 11 Professional and Office 365.

Once I acknowledge the error I can use the program like normal.  Once I have the program operating, opening a subsequent file doesn't generate an error.

Any advice on solving this?

[#2]

@blairwhitworth320 

Completely quit Excel.

Then hold down the left Ctrl key while you start Excel.

Excel will ask whether you want to start Excel in safe mode. Answer Yes.

Does the problem still occur?

[#3]

@Hans Vogelaar 

Thanks for the suggestion.  The problem doesn't occur when opening in safe mode.

[#4 · Accepted solution]

@blairwhitworth320 

The problem could be cause by a file that is automatically loaded when you start Excel, such as the personal macro workbook PERSONAL.XLSB or an add-in. Follow the steps described in Excel not responding, hangs, freezes or stops working to check which one of these it is.

[#5]

@Hans Vogelaar 

The tool pointed me to a COM add-in as the source of the problem.  I'm not sure the origin of these applications but I inactivated Report Designer and that seems to have worked. Thanks for your help!

[#6]

Are you using Sage Accounting 50?
I updated Excel (Microsoft Home and Business 2021) yesterday (Microsoft® Excel® 2021 MSO (Version 2310 Build 16.0.16924.20054) 32-bit and started getting the same error. Before trying the MS Assistant, inactivated Report Designer Add-in and the error message stopped appearing. The full file name of the Add-in is C:\Program Files (x86)\Common Files\BIExcelFunctions1.1\32bit\Sage.BI.ExcelFunctions1.1.xll, dated 6/14/13, so that probably means the update is not compatible with my accounting program Sage 50 Accounting (US Version). If you expand the location column, you should be able to see full file name. I was able to export a report to Excel after disabling the Add-in. I will send a report to Sage for them to research.

[#7]

Good observation. I found your comment after I ran into the same error. We use Sage 100.

[#8]

Yes; we use Sage 100. Thanks for clarifying the source of the Add-In. What's surprising is that I'm the only one in our organization experiencing this so far.

[#9]

Seeing this issue on one of our employees machines.
We use sage 100 as well.
Disableing the add on did NOT fix the issue for me.

Did this add on come from sage somehow? I'm not familiar with it.

@blairwhitworth320 

[#10]

Another commenter indicated the add-on was from Sage, and when I drilled-down to the location it has a Sage-related path. Perhaps see if there are other similar "add ins" which are active and potentially related? I might try a repair installation of Office/Excel and see if that solves the issue.

[#11]

@blairwhitworth320 It is indeed a conflict with the latest M365 Apps for Business update; below is a response from Sage directly. I rolled back to 16.0.16827.20166 and all functionality has returned.

Spoiler

We’re seeing several customers having Sage Intelligence issues on a recent Microsoft office build, specifically 2310 (Build 16924.20054). If you are running this Microsoft Office/Excel version, please roll it back to the previous build 2309 and try the reports again.

[#12]

I, too am having this issue with Sage 100 and one user.  Disabling the add-in clears the error but I can't run Intelligence Reports.  Reinstalling Sage and Office didn't help

[#13]

@Hans Vogelaar  I use Office 365 and Sage 100. I opened Excel, went to Account and updated my license. After that I went to Update Options and selected Update Now. That has resolved the Excel Error: object reference not set to an instance of an object

[#14]

I use Office 365 and Sage 100. I opened Excel, went to Account and updated my license. After that I went to Update Options and selected Update Now. That has resolved the Excel Error: object reference not set to an instance of an object

[#15]

@Carnegie5930 

Good to hear that. Thanks for the heads-up.

[#16]

@Carnegie5930 This unfortunately did not work for me. Has anyone else figured out a solution to this? I am starting to see this pop up for more users as office 365 updates I assume. 

[#17]

Rolling back to version 2308 worked for us.

Also, anyone who needs to run Financial Reporting can't just remove those add-ins as they are needed for that.

[#18]

Worked perfectly thank you @Carnegie5930!

[#19]

@Nick_Miles great to hear!

[#20]

@colorflakes I use Office 365 and Sage 100. I opened Excel, went to Account and updated my license. After that I went to Update Options and selected Update Now. That has resolved the Excel Error: object reference not set to an instance of an object