Sage 100

Issues with paperless office/print to pdf over RDP and local - driver conflict. I know this is a documented issue but is there a work around? I have a client that runs a 4.5 client on a terminal server through RDP and we just installed 2013 locally (not live yet). When we tried to print to pdf on RDP/4.5 after installing the local 2013 workstation we get unable to process lockfile issues. I renamed the local Sage PDF printer but still had the error until I completely uninstalled the local Sage PDF printer. But long term I need a work around to be able to do both. She will run some companies on RDP and other companies on a completely different installation using her local workstation. Any ideas?

The one I always see is the local install sharing the local pdf converter. This creates two pdf converters that the t RDP session can see. Shut off printer sharing when starting the RDP session and see if that solves theissue. We have a printer control utility that we install for people who need to share the local printers. It allows you to control which are shared and stop sharing the duplicate pdf converter. I can get the name if that resolves the issue.

Yikes. I would punt and just make your flight reservations, then go have a Polygamy Ale before heading out for dinner. But please limit yourself to just ONE!!!!!!!!

thanks Kevin - I'll give that a shot and let you know. Jeff - it's actually Polygamy Porter. And they also make Provo Girl pilsner (modeled after St. Pauli girl). One thing Utah doesn't lack is great breweries. My flight to San Diego has been booked!

@EricAnderson - Ale or Porter, bottom line is that I couldn't have just one......... I also have my flight to San Diego. Have to make sure I bring my sun screen....

What error do you actually see? I'm getting ""The PDF Document was not created successfully"" - no other errors - and I'm wondering if this is the issue

@BethBowers - Check to see if there are at least 2 Sage PDF Converters showing up in the printer list when in the Terminal Server session. It will definitely error if there is the local one on the Terminal Server and one getting redirected from the workstation. You will see ""Sage PDF Converter (redirected ##)"". Uncheck the ""Printers"" selection in the ""Local Resources"" tab on the remote desktop connection to remove the redirected PDF Converter.

+1 @KevinWesley, shutting off Local Printers in your RDP settings before establishing your session has resolved this for me in the past.

Thanks, everyone. I don't know exactly what fixed it, but I passed along the info re the printers to the IT guys and I know they were cleaning up local copies (no longer needed), and may have turned off the sharing, as well. Anyway, it's working now. YAY!