Sage 100

Question re: Paperless Office running through Terminal Services and problems with completely different documents merging during PDF generation...MAS90 4.50 is running on a 2008 application/terminal server. MAS90 is only accessed via RDP for two different physical locations. User A from remote location 1 updates an IM Transaction Register, but also gets a SO Invoice merged in from User B at remote location 2. See attached example if curious. All local Sage PDF Converters have been removed, and the printer port assigned as a local port, and all other printers are valid and online. I'm planning to reinstall the MAS90 client and PDF Converter in install mode on Friday when users are out, but can anyone think of anything else within the remote environment that may be causing this issue somehow?

Attachment does not seem to have attached.

Oops - thanks.

Wow, haven't seen that yet. FWIW, we often have to create a dummy port for the PDF converter to resolve some issues. Instructions were: Go to Printers and Devices Right click on the Sage PDF Converter and go to Properties Click on Advanced and then Ports or Ports Click Add Port Click New Port Enter SAGE for the port name and press OK, Close, Apply and exit.

Just a thought, there don't happen to be duplicate computer names?

I thought of that too, but do you think it matters if people are accesing via TS instead of locally?

We have a number of clients where all users are on a terminal server and it seems to work well. We had to do a little learning regarding printing but Terminal Services has been evey bit as reliable as running MAS on each workstation.

I assume users at all locations are working through the same Terminal Server? We have Paperless running for most of our hosted clients and there was some getting used to the setup from the TS client rather than from the back end server to make sure the paths mapped correctly.

Gary - you sparked an idea...I should make sure that their filepaths for all documents are consistently named using a UNC path, since yes, all users connect to the same TS. I believe some payroll documents, for example, are being sent to a mapped drive secured for certain users, whereas other non-secure documents are going to the folder near the MAS90 folder. If I force everything to go to UNC or IP, maybe that will help.

Sage has suggested using the IP instead of server name and it has helped us in several situations.

Just in case anyone was wondering, I already did set up UNC/IP pathing for all paperless documents, so that was not the issue. The next step is to set all documents to go to one server instead of split between two different ones. I don't see yet how PL through TS should function that much differently than on a local machine, especially after running through the separate tasks required for a Windows 7 machine, but if I come up with anything else for ""best practices"" I will post.

Normally the Use Lockfile option (from PL_AdvancedOptions_UI ) is not preferred but in a case like this where unrelated documents are merging from 2 users on a Terminal Server, it might be warranted, assuming it is turned off. It it turned on by default