Sage 100

I have a client running MAS 200 version 4.5. One of their workstations died so they gave the employee another employee's workstation to use until a new machine is procured. We have made her a member of the local administrators group on the workstation. Any time she tries to post a batch, she gets an error message that reads ""The PDF document was not created."" I realize that this is associated with Paperless Office. What I don't understand is why this works for the previous employee and not for this employee on the same workstation. Thoughts?

Does she have full rights to wherever the PDF files are stored? Is NUL the default port in Paperless Printer? Is a redirected printer being used?

@MarkKotyla thanks for the quick response. She's logging in as the same user as before so the first question should be yes as they are stored on a file share. The Sage PDF Converter is point to a local port I don't think the printer is redirected but I'm not positive. I will continue to check.

I've attached a copy of the error message. I don't see any printers available that aren't redirected.

What version OS is the workstation now.

More information from the client: The client is running on a terminal server. They are sharing the app, not the desktop. Local workstation is running Windows 7 Professional. Sorry, I didn't realize that this workstation was running the 200 client through the terminal server. However, I did confirm that her previous workstation was running same way.

Verify you can get to the path for the PDF. I just had this and can't remember the exact resolution though I'm leaning toward not having rights to the PDF folder.

I believe this can happen if there is more than one redirected copy of a given printer on the TS.

@WayneSchulz I confirmed that she has rights to the PDF directory as defined for the document in Paperless Office. I don't think this is it as this strikes me as something to do with the workstation and probably printer related. @JohnBroadfoot I think you have a point. My problem is since only the application is shared, I can't get in to see the printer setup on the terminal server desktop. (Of course, I don't know that it is required.)

Maybe IT will let you RDP to it. We have the best luck in offices that share (redirect) the same printer(s) when we put a printer queue on the TS for each shared printer and turn of redirection in the RDP client of all workstations in that office.

Has the local PC ever had a workstation setup done on it? If so, you have to uninstall it so that there is NOT a local Sage PDF converter. If the Sage PDF Converter gets redirected (when you have local printer redirection turned on for Remote Desktop Users) paperless office will never work as it will try to 'redirect' the Sage PDF Converter.

I've had this issue caused by UAC several times in the past month for different customers. I'm not sure if UAC is still a factor when going through the terminal environment but I'll throw it out here anyway...

@MaryMays, your 's was half the problem so thank you, thank you, thank you! The other half was the IT staff. When they deployed the remote client, they pointed to the older terminal server which was supposed to be turned off and wasn't. Once pointed to new, properly configured terminal server and the local Sage PDF Converter removed, all is well. Thanks all for your help. Love this group.