Sage 100

Client is using RDP and is on a new server, getting ""There was an error opening this document. This file is already open or in use by another application"". when printing Paperless. I have the printer setup properly (had to set it up manually), have the CDTINF300.dll manually registered in the SYSWOW folder (my first successful registration in there!). What else? I had this happen a couple of years ago at a client and I actually found the issue on Sage's KB and of course now I can't. Well, I found one, but it just said to uncheck the Keep Only the Last PDF checkbox and that didn't help.

You can try opening the Sage PDF Converter printer/device and delete any hung jobs. And then you may also want to delete the failed/bad .pdf that it created.

Have you checked permissions on the folder?

Did you look at any of the post on SC ? There are a few and most of them talk about redirect printers.

The folder is within MAS and I can add/delete in it. No hung jobs. Deleted bad PDFs. I looked for the error on SC and couldn't find it, which is apparently the story of my life when it comes to searching...

No shared printers. Only 1 person using RDP.

And this was working on the old server. Somehow. :-)

Do they have reader installed?

If the Sage 100 is running as a service, the service must also have correct permissions and not just the user.

They have reader and it's just old 90, not 200. (Excuse me, 100 Peon, not 100 SuperDuper)

Have you rebooted the server?

No rebooting - yet

What's the Sage PDF printer's local port set to? Needs to be something other than ""null"" or LPT1

port = Sage

Have you disabled locks with ""Pl_AdvancedOptions_UI"" program in File > Run?

Locks were already off, strangely enough.

Is this happening with all users who RDP in?

Only 1 user. :-(

Just for S&G's, have you tried RDP'ing in as Administrator to see if the same thing happens?

Per the KB - Paperless Office hangs on printing, creates an 0kb PDF, creates a locked/unopenable PDF or appears to print but no PDF is generated when printing to a Windows 7 or Server 2008 64bit workstation via MAS 90/200. This issue seems overwhelmingly caused by security restrictions on the machine experiencing the issue, and is almost always a workstation environmental issue. If components fail to install in any way while processing these steps on a Windows 7 or Server 2008 machine, Disable UAC (User Account Control) in Windows and attempt the installation again. UAC might also cause this issue outright, test with UAC Turned off if all else fails.

I've asked the IT to give me the same login info that the user has so I can test from here and compare to Admin login. Fingers crossed it all ends up being back in his ballcourt.

In high security environments and even low security ones I always do this additional setup (see attached) for Paperless on Server 2008 Terminal/Citrix servers as well as Windows 7 PCs. I put this doc together last year after talking with Dean Yeater of Net@Work who came up with these ideas and does it this way with his clients. Have had good success with it. Perhaps it is applicable for this case as well.

Thanks, @Alnoor. Looks like what I have setup for them except I just called the port ""Sage"".

Alnoor, what is the purpose behind creating a Sage printer port with a path designation?

@BethBowers it's not the same thing. If you just create ""Sage"" then the spool file is being accessed somewhere deep below the c:\windows folder. In high security environments (which you may not have and this doesn't apply to you) users may not have permissions to write to that location but they can always write to C:\Users\Public - it all goes back to how the installer for the Sage PDF Converter / Amyuni PDF Converter doesn't go far enough to ""report"" itself to Windows as a proper printer on Vista / Win 7 / Server 2008. Probably Amyuni solved this problem a long time ago but Sage has been using the old 3.0x version of Amyuni forever.

Great post thanks.

@Alnoor - thanks for that extra info!

Also, make sure the RDP client isn't trying to pass through local printer connections. That will mess up Paperless printing, also.

OK, coming back to this. The exact same error is happening to a Win 7 client at same installation who is NOT accessing via RDP. Tried the port thing Alnoor suggested. XP clients are not getting this. It's 4.3 and they are upgrading in a few weeks, so if no one has anything off the top of their head, I think we'll just wait and hope that 4.5 handles it correctly.

At one of my clients that was still on v4.3 and is not upgrading any time, my work around was to install the new v4.4 client. Issue was resolved. Major downside to those who can't/won't are the paperless WIN 7 issues. At this particular client, we had already installed v4.4 so it was just a simple matter of loading the client. YMMV!

Same thing happened to me just last week when server crashed duting a Paperless Office task. Go into the Registry and do a search for Sage PDF Converter. Delete all JOBS and LINKS folders. Make a backup of the Registry first.

@haroldwestover - REALLY? Who would have thunk it?

It happens all the time. On a Terminal Server it can affect one person while others work fine. The lock is a user/printer registry issue. Also, does the RDP User have MAS installed locally? (say on a laptop shared at work and home) If so MAS must be removed off the local machine or that can cause confusion about using the Local vs RDP Paperless Office Printer.

@MikeBrown - I have had to do that fix before, but just not for this particular error.