Sage 100

Rough week, too many questions! Customer is on v2016 Premium with Sage Intelligence. Received a new computer a few months ago and doesn't think she's had to access Trees in SI since receiving computer. This week she has to make changes to the Trees. She can run the report (both existing report and a new template) and can do anything (launch the built in layouts, bring over the Accounts from the Task Pane, add a formula). However, when she goes to Manage Trees, either Edit, Add, Copy (any option), she gets the Microsoft .Net error in the JPG attached and the whole error is in the PDF. IT uninstalled the .Net features, uninstalled wksetup, rebooted, installed .Net, wksetup (all as Admin), UAC is turned off and still we get the errors. Excel is Office 365 v2016 (desktop, not web), .Net is 4.7.1. We confirmed the Prerequisites today. The only thing I haven't done is have them repair Office. If I click the Continue button in the error, Excel crashes. Anyone seen this or have any ideas? She is the only user so unable to test another machine without moving licenses.

There is a Sage Intelligence patch that fixed this issue for 2 of my clients. SI5200-T.exe ; can get it from Sage KB search for SI5200

Isn't that the patch for when you can't see all the 'branches' of the tree? And it fixed this issue too?

http://kb.sageintelligence.com/index.php?title=SI5200-T_Unable_to_view_all_reporting_units_in_Sage_Intelligence

Yes - that's the only patch I found so far. Make sure you follow that Prerequisites article like gospel.

@MaryMays do you install the Excel 2016 Compatibility pack too? I've done that on my Office 365 installs to avoid issues Sage 2017 SI and earlier.

@MoiraGoggin Yes I have installed that, too. Somewhere there is a document that mentions doing that, also.

Update - IT installed the 5200-T, received the same error, ran a repair on Office, received the same error. Licensed a 2nd workstation as a Manager today, didn't install the 5200-T or do the repair on the 2nd machine, but did receive the same error. Haven't tried the Compatibility Pack but will probably have IT do that next. Anybody other ideas? I've never seen this error thrown in SI before.

@NancyHanson just wondering does this work for other workstations (currently)? if so I would try uninstalling and reinstalling the .net framework from the prerequisite files in wksetup. if not I'm wondering if you have tried pointing to a new clean report repository? this is my general catch all for Sage Intelligence problems, in no real order. 1) launch excel make sure its fully registered 2) fully uninstall Sage and reinstall (like normal) 3) uninstall .net framework and reinstall it maybe something is just off who knows. 4) try creating a new report repository and see if it has issues. 5) check C:\program files (x86)\common files\ and the Sage Intelligence ones for permissions 6) check the report repository for permissions and login to the computer as the domain admin to test. 7) i take no responsibility if you use this one, messing with the registry isn't normally a good thing, but it did solve a nightmare case of the add-on not loading. check the registry for multiple instances of excel at HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\ (in any of the numbered keys) if so this suggests old entries for excel might be present. Alchamex had me uninstall excel and then delete these excel entries before reinstalling excel.

@JeremyFox Do you ever install the Office Compatibility pack?

@MaryMays I'll say no simply because I'm honestly not sure what it is. I generally never worry about any hot fixes or patches if the client is relatively up to date on office and windows. with all my Sage Intelligence problems the list i had up there has been the fix aside from maybe a aggressive virus scanner or Microsoft disabling add-ons or something like that. granted that list is for problems running Sage the demo ABX report created by Sage because custom report related errors are another bag of cats.

@JeremyFox, thank you for your suggestions, they now have 2 workstations with SI/Report Manager and neither is working. I or IT have done all the steps you suggested except the 'new report repository and since they've recently upgraded their Excel, having them check for old versions in the Registry. They are using a 64 bit Excel version, thought I might have them downgrade and see if that helps. I am hesitant to call Sage hoping someone here will be able to help! I haven't installed the Office Compatibility Pack in over a year (no need to) so not sure I hold out hope for it solving the issue.

@NancyHanson for sure, ya calling Sage for Sage Intelligence when you get to that point is largely just to get to Alchamex which definitely takes time and escalation calls. think it took like 4 weeks in total to get to that registry solution, and the alchamex guy is just like ""well its common knowledge"" i about lost my mind because its documented NO WHERE. x64 excel shouldn't be the problem though i even use that myself.

KB 71541 is the Sage KB article recommending installing the Excel 2016 compatibility pack.

@NancyHanson did you ever get this resolved?

No, spoke with Sage, they want a complete uninstall/install of .Net4.7. I think IT originally just turned off the feature and turned it back on. Waiting on IT. I did try licensing to a new repository and had same issues. The other thing i found was in the .Net4.7 feature the ASP was checked. My local install has it unchecked.