Forum Discussion
Solved
Excel Error: object reference not set to an instance of an object
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 ...
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.
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.
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.
Good observation. I found your comment after I ran into the same error. We use Sage 100.