Sage 100

Unable to preview MM_ReportName.rpt. Exception occurred."" when using the Export tool from any report in Sage 100 Standard 2014 (5.10.3). Allegedly just started happening yesterday. All users are connecting into a 2012 R2 Datacenter Terminal Server connected to another 2012 R2 Datacenter Application Server (I know, not supported - believe me I'd be happy to tell them that's the reason and move on with my life). I can preview any report but as soon as I click the little export icon it blows up with this error. Same if they select Export or Data Only Export from the pull down printer list - which is they way they have been doing this to export to Excel. Excel works fine. I can export directly from Crystal, reran WKsetup, UAC is NOT turned off (they say they can't), Crystal DLLs are a couple years older than mine but I need to work with their IT Admin to swap those out. Anyone have a silver bullet for this one, kemosabe?

Any automatic update listed in the logs? (To server, not Sage) I've had VI jobs stop working re NULL fields after MS updates, so strange things do happen with those Softies...

Hmm, good thought, and yesterday was Tuesday so that's quite possible. Thanks @BethBowers I'll check that out tomorrow with their IT guy (they are in FLA). So far nothing on Sage City or SAP KnowledgeBase (or of course Sage KB) that I can find.

I ran into something similar with a recent upgrade to 2014. Not exactly the same. I could click on Export but when selecting any Excel version, I would get an exception error. Ran perefctly fine when I was in Crystal but not when run by a user. The problem was the Runtime version and the fix was to download a Crystal Report Service Pack.

Well, I can just pop over and check for you, since they're in FL. *NOT* (Unless they are at Disney. Then - your wish is my command!)

make sure to give all the MAS90 users full control to the c:\sage folder on the terminal server - this has helped me in the past with strange issues. Their IT is partly right about UAC on 2012 server - it can never be turned completely off BUT you can make sure the setting is down at the lowest level for all the users. this is my preference for 2012 RD servers.

Thanks to all for your ideas, all good ones at that. How about this for a kick in the head? As this issue sprang up suddenly on Tuesday it went away just as suddenly today. The user reports that he can preview and export to his heart's content today! So whether Microsoft sent out a patch for a patch or some network tech made some adjustment I may never know. This was interesting to say the least.

My vote is on network adjustment to user rights or AV or some combination.

@MaryMays GOOD CALL! I just had this crop up at a client. in my case: I changed the security settings on the folder ""C:\SAGE"" (on the terminal server not the server where Sage is installed) so that ""users"" have full control. As soon as I did that the reports started working for me again.