Hello mazcredi,

How did the support case go?

After Windows updates, they often flip the Firewall on and adding an exception for the Sybase Port 2638 usually fixes it. I am assuming the Network Product since there was the product I saw in our group chat over here yesterday.

~Delray

Crashing on reports - usually means you need to select a printer prior to attempting to run a report. You, for some reason, are just getting the error: See Error: "Invalid Printer Specified" on Citrix or Terminal Server 

Hi Delray,

Thanks for your answer. I'm actually on the line with Andrew right now working on this. So that's not the issue, I can connect to the server and open a company. But whenever we try to run a report the client crashes. We've already tried uninstalling the client and crystal and reinstalling but that did not work. We are now installing it fresh on another Windows 10 machine that never had FAS on it to try to isolate further. Andrew's hunch at the moment is that there is some kind of remnant of old Crystal that got tweaked during the in place Win10 upgrade that is causing it.

Any ideas?

Yeah that was the first thing that Andrew had me try.