Thanks.

Just another item to make sure happens.

We updated (yesterday) from 4.40.0 to 4.40.4; in large part to get the PDF converter working for the 64 bit machines we bought at the end of last year. 

I am still getting a "Printer not activated, error code -20"

Can someone help me find my way around this?

Thanks.

Ben

Where are you getting this message?  MAS tends to throw this message if you click on the test converter button.  In my experience, this message tends to be a red herring as the converter will ultimately work.

If I may ask, why didn't you just install PU 5 instead of 4?  Would have saved you another installation step.

And you did do the WKSUPDATE program at each workstation as mentioned above?

To answer the question of why not straight to PU 5?  We have a couple 3rd party modules (ScanForce and VBScan) that aren't PU5 ready.  Otherwise I would have gone with it.  instead we will do PU 5 probably alongside another updated.  I understood PU2 addressed this.

I did do the WKUpdate with the workstations.  Should I have totally removed the workstations and started each one fresh?  If one got missed, would it impact other workstations.

I get the error both  in LibMaster - test email as well as PL_AdvancedOptions_Ui - Test Converter. 

This is what I get in the install log - making me think I might have something missing in the install:

Windows 2000/XP/2003 Install
------------------------------------------------------------------------------------
Checking for existing PDF printer
------------------------------------------------------------------------------------
Removing existing PDF printer
------------------------------------------------------------------------------------
Removing PDF printer driver
------------------------------------------------------------------------------------
Installing using .inf file
------------------------------------------------------------------------------------
Copying cdintf.dll file
------------------------------------------------------------------------------------
Copying xmllite.dll file
Error Code: 2
The system cannot find the file specified.
------------------------------------------------------------------------------------
Installing Amyuni PDF printer driver
------------------------------------------------------------------------------------
Installing Amyuni PDF printer
------------------------------------------------------------------------------------
Installing Licensing Information
------------------------------------------------------------------------------------
Printer setup succeeded
------------------------------------------------------------------------------------
Launch 'Install -u' to uninstall
-------------------------------------------------------

When I go ahead and turn on the paperless office and print to PDF it hangs up at "Printing Records"

Do I need to verify database with the forms?  Just thinking outloud.

What printer port is your 64 OS machines using?  It should NOT be the nul.  The 64 machines have a nasty habit of resetting back to NUL after doing a wk update.

This Sage PDF Converter installation process for W7 machines needs to be significantly cleaned up. I just went through several hours of Hell trying to figure out why a new W7 laptop onto a working, v4.4.4 MAS 200 system could not get a Paperless Office printing to work.

According to tech support:

- "some W7 installations have problems, others don't"

- UAC can cause some dlls not to install, while not throwing any signs of it.

- sometimes they revert to copying a 32-bit version of the cdintf300.dll file onto the offending w7 machine to make it work.

- when the Sage PDF Converter gets assigned to the NUL local port, there is no indication of this, even though it seems to happen 100% of the time on W7 64-bit machines.

As a former product manager, this leaves me cold. The specs for this installation need to be tightened up.  At the very least, they could run a little script to check for the presence and registration of the the needed files and dlls.  I suspect that the NUL port issue can also be identified programmatically, but if not, them at least prompt the user to check this at the end of  the installation.

And I'll suggest again that my favorite pet peeve on MAS 90-200 installations get fixed: when prompting for the location to install or update the files to, poll the registry to find out where it is and suggest that for confirmation. Don't just suggest a default location, since on an EES install it will ALWAYS be wrong. 

I know this thread is a bit cold - but for those that haven't been able to solve the problem...

This article was the key for me... worked on all three of my 64bit W7 machines.

http://infosource.sagesoftwareonline.com/sw_attach/kdb.asp?isresolutionconceptid=524104

I found it through a link of Shulz Newsletter.