Sage 100

v2014 upgrade from v4.4. Paperless Office Issue (who would have thought). Paperless is not launching Adobe Reader after creating the PDF. Just sits there unresponsive. Uninstalled/Reinstalled PDF converter. User Adobe Reader X & XI. Batting three for three in workstations not launching reader. Thoughts? Thanks in advance. @Sage100UrgentSupportNeeded

Have you verified that it is actually creating a valid PDF? Can you open it using adobe? if not then I would start by looking at the Sage PDF Converter. if it is valid and just not opening it, I'm not sure that I can be of much help.

Thanks. It does open with Adobe. Payroll works without issue. it seems to be stalling out creating the AP transaction register (second part of update). Same thing happens with cash receipts entry. Part 1 (cash receipts posting) is created but the AR transaction update stalls out.

Check the UAC and also the permissions for the Sage PDF converter - Navigate to the Security tab and add select the ""Everyone"" group. Select ""Manage This Printer"" and ""Manage Documents"" under the Permissions box

do they have Job cost? I've seen update issues related to role maintenance where the user doesn't have rights to the Daily Job Cost Transaction Register. Since it happens in Cash Receipts I doubt this is your issue but thought I would throw that out there.

On the other hand Cash receipts CAN update to job cost so I suppose it is not that big of a stretch after all.

No job cost involved. UAC is turned off, permissions have been granted for the everyone group. Just very odd that the first PDF does generate but not the gl transactions. About to toss the towel toward Sage....

While your on hold for twenty minutes with Sage - you might verify that it is not a role maintenance issue. if that user does not have rights to everything in role maintenance try a user that does.

It happens with my ""super"" role as well as the others. I did click the roles off/on but to no avail. In watching it occur, it isn't launching the second PVX program to generate the transaction register. Weird.

You started the thread thinking it is a paperless office issue. Have you verified that? does it happen if you turn off paperless office? Also, can you manually launch the daily transaction register with or without paperless office? I realize I'm asking more questions here than I'm answering; if that is annoying just say so :) I find it interesting that payroll works since that is a legacy module.

I believe Jeff is referring to the secondary journals, e.g. the AP Recap journal that prints with the AP Invoice Register and the AR Recap that accompanies the Cash Receipts journal.

If that's the case, I recently saw a post somewhere (was it here or on Sage City?) about this being a timing issue. I'll keep looking for it . . . Can you clarify @JeffSchwenk if Therese interpreted you correctly?

If so, the problem has existed since at least 4.4. If you think that's it Jeff, see if you can talk to Chris Powers. I've seen other posts on this here and sage city.

It appears that @ThereseLogeais is spot on. When you update AP invoice register (or other module updates that post to the GL), the process actually produces the register and the GL transaction. The paperless process combines the two reports into one PDF. In the past, the process did break and you would be left with transaction reports that displayed in the paperless folder with CAT extension. This is not happening. Late last year, I was having an issue with v2013 being a bit slow and erring out. That problem was fixed by installing the v2013 PU5 patch (font issues in Crystal). THIS just started this morning with a go live v2014 (migration from v4.4). Paperless was not tested and it worked fine in v4.4. The paperless pdf for the AP register is created and does open in Adobe. Process stalls when trying to generate the transaction PDF. It works fine if you preview so I think it is paperless related. Will let Sage sort it out......

An update from Sage Tech..... Sorry for the delay. This is somewhat of a rare issue on post-4.40 installations, but overall it is one we have been seeing since the Extended Solutions days with 4.10 and 4.20. The failure is occurring when the Amyuni driver (Installed as the ""Sage PDF Converter"") attempts to append a PDF to a separate PDF that was created moments before it. The act of appending an additional PDF onto the original PDF is what fails. The original PDF is created without an issue, but the appended PDF is left ""in limbo"". This is an issue that is acknowledged by the manufacturer (Amyuni) with the 3.03 version of their driver. I believe that the issue would be resolve with an upgrade of the PDF driver version to a current version that is fully certified with Windows 7 and Windows 8. From what we have heard in support, this will be occurring with Sage 100 ERP Version 2015. We have troubleshot this issue for many hours in the past on the last 4 versions, to no avail. Unfortunately, we think it is just a facet of the driver firing off incorrectly that we are not able to address. I have documented it under 3 different program issues, but we have never been able to duplicate it in house. I am checking for a work around. WOW, relief is on the way if ONLY I could hold out until the v2015 release. Will keep everyone posted. Client will not be happy to learn that what worked in v4.4 no longer works. Of course, they will want to know how exactly the annual business care(less) support payment actually benefits THEM....

Current Amyuni version is 5.0.11, so Sage is probably about 3 years behind (or more). But all THEIR customers have to be on the latest version...

@JeffSchwenk - am having this happen on a 2014 upgrade. What was your resolution? I'm thinking it will be PU4, but client has a DSD mod that isn't ready for PU4 yet, so are currently on PU3.

Took me a while to remember which client this was..... Maybe PU will fix it now. What we ended up doing was.............. Get this........... Bought NEW servers and workstations........ Luckily the client was shopping for them anyway. We installed v2014 on a clean server and everything ran well. However, problems came back when connecting a workstation that had Sage installed previously. We tried everything. Uninstall all workstation, shut off AV. Nothing worked. Sage worked on problem for hours. Client threw in the towel. New hardware solved all the problems... Maybe if you installed the PU, ran the workstation update, rename the Sage 100 PDF to Sage PDF Converter, then went back to the PU3 install????? Lot of work, but it might work....

OK, I'm going to pray the PU4 fixes it. Jon is coming through for me at DSD and getting me the PU4 version of my mod tomorrow. Hugs and Kisses to Jon!

It's not a Windows 8 machine, is it? I ran into the same problem and found when I uninstalled Nitro (the .pdf creator that came installed automatically), everything worked fine.

Just to let everyone know - the PU4 for 2014 fixes the issue of orphaned additional pages of Paperless (where the extension is .cat instead of .pdf).

You mean the one they fixed in v4.4??