Sage 100

I have a client who gets the ""Sage 100 has stopped working..."" when trying to preview or print, virtually any register/document on their terminal server. I was going to manually clear out the printer name in the PrinterName$ field number (9), but there are 351 keys in the SY_ReportSetting.m4t file, so that would be very inefficient. Any issue with just re-initializing this file? @Sage100Routine

Hi, Brandon. I'm not technical to answer this question, but did you check that all the printers are all valid, and there is only one Sage PDF converter on the TS (and none are being sent over via a local Sage install)? I've found that if I change the default printer, then change it back, that sometimes helps, too.

See if this helps...

Thanks Karen and Roberta - that's exactly the path I was taking with this. Seems simple and straightforward enough, right? I ended up focusing on one report, just to verify that the SY_ReportSetting file is my culprit, and I manually deleted the PrinterName$ field, but the issue persists, even after clearing up this field as the KB article suggests. So the plot thickens, on to other causes... Thoughts?

Hello Brandon, is it for only one user or everyone that remotes into that terminal server?

Hello there Diane! So far I have been able to replicate for all users on the terminal server, including myself, with full admin rights.

I've never had to do this for all reports, but I have gone into Crystal and chosen ""no printer"" in the Crystal Reports Printer Setup Screen when I have issues with certain reports. I cannot imagine doing it for all reports, but you can at least test it on one report.

I know this document is similar to Karens but make sure about the invalid printers.