Sage 100

One of our consultants did an upgrade to Mas 200 4.3 a while back and everything is working except for one users machine. When she goes in to print the Daily Sales Reports/Updates it prints everything to a PDF via a printer they have set up and then upon the update process MAS stops responding. We have attempted every fix on the Sage Knowledgebase and are pretty sure it has something to do with her 64 bit Windows 7 system and the printers but can't quite figure out what. We've uninstalled and reinstalled the Sage PDF converter, we've basically disabled paperless office for this user, and we have uninstalled and reinstalled her workstation. Has anyone else ran into this issue or have any ideas what to try next? Thanks, -Jake

This occured on one of my clients. The problem was Microsoft Essentials was the Anti-Virus being used. Sage does not support Microsoft Essentials, since it is not a corporate Anti-Virus program. Removing Microsoft Essentials resolved this issue for my client (Daily Sales Journal and Update hung during the update process).

She did Have Microsoft Security Essentials installed so I removed it, rebooted the computer and still ran into the same issue. Any other ideas? I am beginning to lean towards a windows software issue since she has mentioned failed windows updates as well as failed antivirus installs. She also informed me that this has happened on her machine since it was purchased. In other words MAS has never worked properly on this machine. I advised her to get her machine checked out by their IT department while I check in on any other suggestions.

Silly question that has to be asked. Since you indicate that it is v4.3 on a WIN 7 64 OS, have you installed all the patches required? WIN 7 with V4.3 are a frequent PITA! I have even installed the v4.5 wksetup client on this configuration running v4.3. Took care of the issue.

We have installed all the ptaches and it still isn't working. We haven't installed a 4.5 wksetup client though. Never even though tof that as an option. Anything I need to know about taking that route?

Luckily, I had a v4.5 install on the server. I just ran the install. Launch the v4.3 client after that. All was well. Sure beat knocking myself out trying to fix v4.3

Re: @JeffSchwenk's mention of 4.5: http://community.90minds.com/2012/07/20/secret-of-the-day-get-your-older-sage-100-4-3-working-with-paperless/

Did you adjust the port that was being pointed to for the paperless printer? I usually set it to a new lpt port I call sage. What you will see is a 0kb for the pdf file that is created. Paperless stops during the process of creating the PDF and the process is stuck at that point for the client.

Good point @ToddMartin - The PDF device printer for the WIN 7 is quirky and this one gets me everytime. You have to verify this port setting EVERYTIME you do a workstation install as the setting is changed back to the default which doesn't work......

Weird thing happened to me yesterday. I changed the port from NUL: to SAGE as a precaution after an upgrade, and then paperless didn't work. I changed it back to NUL, and it worked.

On a WIN 7 WS?

this sounds really familiar like it was discussed before

I had a client a while back on 4.30 with new win7 and all kinds of issues with PDF. When they received MAS not responding, we were told to remove the default printer on the particular report not printing from the sy_reportsetting file. It worked for us. Just thought I'd put that out there.

@JeffSchwenk Sorry for dropping off the radar for a few days. Yes. It was a WIN7 workstation. Strangest thing I've ever seen. Color me #confused.