Sage 100

I loaded SP 4 on a Sage 100 Standard system and the PDF converter no longer works. I know there was a post on this but I can't find it. TIA

Did you run workstation setup? If so, the port defaults back to a Null port so you need to go in and change to your new local port if you created one.

Thanks Nancy. Ran workstation setup. Will look at the post issue.

Changed port to c:\users\public\sage but still not working.

Usually we just add a local port to the workstation in printer properties/ports and call it SagePDF. Can you detail 'it's not working' a bit more?

Get 'Printer not activated, error coded -60

Check the permissions in Regedit, I think that is the fix for error code -40 and -31... so maybe it is related? Here is what I have: UPDATED READ NOT FROM SAGE ON WHY THERE ARE TWO PDF DRIVERS: Heads up on dealing with this. When PU4 is installed, it creates another version of the PDF Converter, but the old version doesn't get deleted. So when you right click to go to Printer Properties on the Sage PDF Converter, 2 show up on the list. To delete the old one, you need to make sure they have separate ports. After changing the port, refresh and you should see each one individually. Delete the one called Sage PDF Converter and keep and change the one called Sage 100 PDF Converter. We still need to modify port and security settings as we have in the past. UPDATE FROM SAGE ON WHY THERE ARE TWO PDF DRIVERS: The new Sage 100 PDF Converter was created for use going forward. It will not function with previous versions so to maintain backward compatibility the Sage PDF converter is not removed. In Windows printers utilizing the same port appear together as one. As you noted you can right mouse click and modify check properties. If you remove The ""Sage PDF converter"", paperless office will no longer function for any version prior to 2013 PU4. This message occurs when running the Sage 100 ERP Launcher on a Server OS, and printing to PDF via Paperless Office. This Configuration can be utilized for testing, but using a server operating system as a Sage 100 ERP workstation is not supported. Please refer to the Sage 100 ERP Supported Platform Compatibility Matrices. Users running in a supported configuration should not encounter this error. If you are encountering this issue, please contact support for assistance. We are working with Amyuni to restore the ability for users to run the Launcher on a Server OS for testing. There is a current workaround, users can RDP to the Server, and from the Launcher, print to PDF via Paperless Office without error. This issue occurs on Server 2012 only with the following versions: 5.0.0.8 5.10.0.4

Thanks Michelle and Nancy. So far I've deleted the printer 'Sage PDF Converter', I changed the security tab per instructions, I changed the port to c:\users\public\sage, and I used regedit to give full control to the software key. This is a Windows Server 2008 R2 machine running Citrix. Paperless was running prior to SP4.

Could it be related to the Chilkat files: https://90minds-com.socialcast.com/messages/22162309

Are these chilkat files compatible with the 2014 SP4 version of the pdfconverter?

@WayneSchulz or @MichaelMcDonald may know for sure...

I changed the printer port to Sage and renamed a Cdintf500.dll file in the syswow64 folder and now the error I get is 'Unable to initialize PDF Converter'

Is the latest Sage PDF Converter actually installed (i.e., Sage ""100"" PDF converter)? Go File>Run: pl_advancedoptions_ui I just had one of these this morning and for some reason the Lockfile checkbox was enabled, and the Auto-install checkbox was disabled. I swapped them, and then clicked the Install Converter button - and that resolved it. You may still need to check the Port being used by the PDF Converter printer/device.

I have the Sage 100 PDF converter and the port is correct. However there is another citrix server which I just found out has the old converter. I'm going to have everyone get out later this afternoon and fix that server and see if that fixes the issue. Thank you all for the help. I'll let you know how it's resolved.

In the syswow64 folder there is a cdintf300.dll and cdintf500.dll and in the system32 folder there is a cdintf500_64.dll. Does anyone which files should be in these folders on a 64bit Windows Server 2008 R2 machine?

cdintf300.dll. I believe other cdintfX00's should be renamed.

Thanks Barbara. Apparently with 2014 SP4 there is a second file cdintf500.dll in the syswow64 folder. The resolution to my problem was twofold. One, I hadn't run the wksupdate standard.exe file. Second, as outlined in Knowledgebase article 51054 you cannot run paperless directly from a Citrix server. I would get a Printer Not Activated -60 error, but as described in the article if you do a RDP logon to the server it works. Indeed paperless works on the client's system though it wouldn't work for me logged directly on the Citrix server. The article says it only happens in Server 2012 but this happened to me in Server 2008 R2. Thanks all for all the help.

Yes if you run paperless directly from/on the Server console, you will get the printer not activated -60 error. The solution is to either run from a workstation or Remote desktop into the server

I certainly learned that the hard way.