Sage 100

Slow printing to paperless, but does FINALLY come up - what should I look for to speed it up? Screens, etc, not exceptionally slow. We're talking 10 minutes to render a 2 page report.

I have the same problem today with a client. took like 10 minutes (sage 100 Advance V4.4_)

We HAD the same issue at a client - turned out they had a some very large image files on the form. I think they were .BMP files and we replaced them with smaller .jpg files and ""ZOOM"" they printed normally.

Just a plain old std ROG Register. I turned off PEP, just in case, and had the AV exclude pvxwin32.exe and the whole MAS folder, and had her reboot. At 7 minutes I logged off because I knew I was going to throw something at someone. Oh, and I noticed at first that her Sage PDF Converter was pointing to the LPT1 port, so I don't know how in the hell she ever had it working before. She originally called because on a print, Adobe was showing a box for every letter, but in preview it shows fine. After rerunning wksetup As Admin and all that good stuff, I wanted to see if it was still printing boxes to the screen, but didn't have the patience to wait for it. Maybe I should just uninstall her Adobe XI and put in Sage's Adobe 10 (they are on 4.5) and have her try again.

Look at the anti virus. Client had an update on her machine and then was very slow. Make sure exclusions are still there.

Yes that also happened. We uninstalled xi and put 10 back on - that helped another client.... These auto updates are killing me and Sage 100

http://download.cnet.com/Nitro-PDF-Reader-64-bit/3000-10743_4-75206289.html

I find that a shot and a beer help pass the time...

Some things to look at -- which may not apply here but could apply to others in similar situations: Can be caused by a form pre-2013 PU5 form code Microsoft has claimed it as a defect in RDP and the workaround is to set the Windows default printer to a LOCAL printer. o Any local printer we used 'Microsoft XPS Document Writer' for the reseller in question. * Microsoft is working on a code fix. If this customer is using terminal server or Citrix AND they are on v2013 (or 2014) setting the Windows default printer to a LOCAL printer could be tried just to see. Also versions 2013 and 2014 will be upgraded to a more recent Amyuni driver in the upcoming Product Update. Once the PU is installed Sage 100 Advanced and Premium will not require any additional work. Sage 100 Standard, each workstation will have to have wksupdate run to install the correct components.

OK, have found out this client has some new system involving N-Computing (where Win 7 machines are basically dumb terminals). Anyone worked with this?