x Want to participate? Join the group to interact
Options
  • State Not Answered
  • Replies 4 replies
  • Subscribers 106 subscribers
  • Views 2188 views
  • Users 0 members are here
Browse Forums
Announcements
293
topics
370
replies
Business Object Interface
1k
topics
7k
replies
Core Financial Modules
2k
topics
8k
replies
Customization and Productivity
3k
topics
12k
replies
Distribution, Manufacturing, and Applications
2k
topics
7k
replies
General Discussion
1k
topics
3k
replies
Partner Cloud
45
topics
91
replies
Payroll, Time Tracking, and Job Cost
777
topics
1k
replies
Reporting and Analytics
962
topics
3k
replies
Sage CRM for Sage 100
164
topics
357
replies
Technical and Installation
2k
topics
9k
replies
Year-end Forum
89
topics
237
replies
Mark A

Paperless Office with Windows 8.1, MAS 4.40 and Windows Server 2003

Posted By

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

  • 0

    I have found some references that suggest that the pdf converter from 4.4 is not compatible with Windows 8.1.

    When you say that you did a workstation install from 2014,  I suspect that the 4.4 install may still be trying to access the prior PDF driver.   Looked at my computer and noticed that there is the Sage 100 PDF converter and the old Sage PDF converter.

    I also seem to remember that there were some upgrades to the PDF drivers partway through 4.4's lifespan that could be an issue,  but my gut reaction remains that the 4.4 converter may just not be compatible.

    Any reason why not just upgrading to current versions of Sage 100 as 4.4 is no longer a supported version anyway.

  • 0 in reply to TomTarget

    Doubtful this is the cause but, I have run in to the Printer Not Activated error before because a computer on my network was not properly authenticated to the Domain. You may want to try removing that machine from the Domain and re-adding it.

  • 0 in reply to Jon_K

    @TomTarget,

    Thanks for the reply. It isn't until PU3 or 4 that Sage 2014 installs the Sage 100 PDF Converter object. It's the same driver as 4.40 prior to that.

    Would love to upgrade them to a current version, but their server is unsupported. They'll upgrade when their budget allows it, but unfortunately for an indeterminate amount of time, I need to somehow make things work the way they are.

    We do have 4.40 working successfully with Paperless and Win8.1 on our own office workstations.

    @Jon_K,

    I have a feeling that could very much be the case.

    What I fear though is that in their current setup, there is no way to properly authenticate their modern computers to the Server 2003 domain, at least the way it's set up. It looks to me like Server 2003 needs to have some updates installed to support Win 7&8 workstations. Not sure how to explain this to their off-site IT person, and not at all 100% confident this is accurate.

  • 0 in reply to Mark A

    I ran into a similar but kind of opposite issue, we have a windows server 2012 domain and our windows XP machines had some issues joining the domain. When they were not properly authenticated they could not see any printers. Eventually my solution was to upgrade those machines to Windows 7.

    My short term work around was mapping the MAS90 network share as a network drive using the domain credentials. That way they are authenticated to the Sage server with domain credentials. Give that a shot and see if it helps, after the drive is mapped they will need to log out of Sage and log back in for the authentication to take effect.

*Community Hub is the new name for Sage City