Sage 100

OK, you SMI gurus; please tell me if you've run into this before. Sage 100 Advanced 2014.3. I run the Report Designer Add-in report provided. It launches Excel 2010 32-bit on the workstation, and at the bottom of the add-in task pane, it says ""Unexpected error object reference not set to an object"". Sage support had me rename the SMI_Repository folder and create a new empty folder. That didn't help. Now the tech has emailed me a KBA about the fact that I probably didn't map the accounts when the mapping tool came. This is the ADD-IN report, not one of the Report Designer reports, so no mapping is needed. I can't find anything in the knowledgebase about it.

found this - looks like the resolution was actually changing the default printer from a fax printer to a regular printer: http://www.sageintelligencecommunity.com/forum/topics/object-reference-not-set-to-an-instance-of-an-object

Thank you, Eric! I'll check this out and report back.

this link actually sounds closer to your issue - I've asked Lloyd for a follow up/status: http://www.sageintelligencecommunity.com/forum/topics/report-designer-add-in-error-cannot-run-macro-mnu-showtaskpane?commentId=3368096%3AComment%3A141034

The customer's default printer is a normal laserjet, so that's not the issue. Sage support is having to contact Alchemex about it. This seems like such a fragile program.

I thought I would let you know that Sage support believed that there was a problem with the customer's data, but couldn't pin it down. The data was sent to Alchemex, but we still haven't heard back from them. I decided to try purging GL history one year at a time. Once everything through 2009 was purged, Intelligence worked.

@KarenOLane - Thanks for the update.

@KarenOLane We just worked through an installation issue with the Intelligence Support personnel in SA over the last 10 days. The actually ""engineered"" a fix for a client who was having the same error and when they looked at all of the install folders they saw different versions of the application files. They felt it was because someone installed an update which didn't completely overwrite files because they must have been in use. No one claims having installed an update to Sage or Intelligence, but the files were inconsistent according to the South African support staff and now it works.

@LloydSmith - Interesting! Mine was a new install of 2014 on a new server, with PU 3 immediately installed. On the workstation, I installed the Sage 100 client, and then Report Designer Add-in. They did not previously have Intelligence.