Hi, I've been struggling with this for a week and am hoping someone may have some insight. The client has been running Windows Server 2003 with WinXP workstations for years. MAS 4.40 and Paperless Office work fine on that setup. They've started an upgrade process however and have a new 64-bit Windows 8.1 computer. I cannot get the Amyuni driver to work. I currently have it at "Printer not activated, error code -30". I believe it was originally at -41. I have attempted every step in KB article 20264, " Paperless Office stops responding when printing. 'Printer Not Activated, Error Code -41', 'Printer Not Activated, Error Code -30', or 'Printer Not Activated, Error Code -20' when printing to Paperless Office". I have had newer versions of Sage 100 and Paperless running fine on Win8.1 for other clients. I'm aware of the necessary registry permissions change unique to Win8.1. I'm aware that MAS 4.40 had a PDF service pack. It's apparently a "workstation install", but when I try to install it however, it's looking for a MAS90 folder which doesn't exist on standard workstations (it also refuses to install to any other folder). I tried copying the server MAS90 folder to the workstation and installing it that way, but got a cryptic error for my trouble. What I find more bizarre is that I've tried installing Sage 2014 workstation to the computer, hoping to get a working Sage PDF Converter, but it's the same error. I noted that the Amyuni driver version is the same in MAS 4.40 and Sage 2014: 3.03. I take it the driver didn't change at all until the 2014 product update that introduced the "Sage 100 PDF Converter". I have tried: obviously set the port and security permissions on the printer object UAC is completely off, with the EnableLUA registry key disabled and workstation rebooted uninstalling and reinstalling the converter from PL_AdvancedOptions_UI while running MAS as administrator verified the correct CDINTF300.DLL is in \Windows\System32 verified registry permissions (Everyone/Full) manually installing the converter from PDFinstall.exe giving myself Domain Admin permissions ...any ideas? I have a feeling it might still be a Windows-permissions issue, possibly that Server 2003 is incapable of properly giving them on Win7/8.1 machines? I know very little about that level of Windows rights/user-management
↧