Sage 100

Anyone have a customer with Sage Intelligence who receives one of these Error 462 messages? As near as I can tell by Googling it seems like it could be related to the version of Excel. This customer is on Microsoft Office Professional Plus 2013

Ran into this with a client running on RDP sessions, we tried everything including lengthy calls with South Africa and Alex @ Sage. Ultimately, the IT guy got fed up waiting for them to find a fix and he installed a different version of Excel. (I can't remember if they upgraded or downgraded) but it fixed it, They have a few problems still with BI Generator errors, but the 462 went away.

SAGE was able to solve the problem today. He did the following: Set up a new Repository . Added a new folder in the repository There also, was an issue with the BHcare tree and any locations that were set up with an underscore. Additionally, some of the cost centers in the tree weren't showing up he fixed this I'm not sure how. I did notice I'm still missing one cost center which I'll have to read up on how to add it to the reporting tree. Otherwise I appear to be set.

Is the new folder just blank or?

I don't know. Customer sent this resolution to me. Reading through it I'm almost thinking that it was taking out the underscores which may have resolved it as the other stuff seems pretty simplistic.

Hmmm. I wonder if that would fix those lingering BI Errors. I will have to give it a shot. We did not follow the ""Correct procedure"" of exporting/importing reports when they upgraded over a year ago, just pointed to the same repository and everything seemed to work fine for a while, then out of the blue we got the errors.

@MichelleForsey I haven't had any issues after doing that myself but maybe I haven't had any extensive enough to matter yet........

@LouWagner most of the errors we get now are all related to distribution (File Publish); it conks out, kill the add-on and breaks the report. sometimes to the point that we have to copy the report and re-save the template. But if we don't distribute, we don't see issues. Let me know if you have complaints of the same, it would be interesting to know!

Thanks for the heads up on that, @MichelleForsey Will definitely keep my eyes peeled for it.