Sage 100

We have a client we recently upgraded to Sage 100 2013 Standard who is running the Payroll module. They are in a multi-server environment and the Sage 100 resides on a server that is not part of the domain that the workstations are on. When Payroll checks are run, the users at the workstations can print the checks but the checks are not ""flagged"" as printed in the Check File. Someone must log into the server then ""reprint checks"" to a text file to finish the process. Once this is done, any authorized user can print the Check Register from any workstation and update the checks. Does anyone have any ideas? I've been on the IT guys to join the domains but they're spinning off in 50 different directions.

@ChuckPeddy Do you have the latest product updates loaded. I seem to remember this being an issue that was fixed in one of the Product Updates.

Don't believe it is a domain issue. I had the exact same thing happen to one of my clients yesterday. Just upgraded them to 2013 2 weeks ago. They went to another computer and the PR journal updated fine. Same computer, sme OS, but must be configured differently somewhere just don't know where. Is the workstation OS Win 8.1 by any chance? Wondering if it is an issue with Windows Defender.

@ChuckPeddy there is a 2013 install issue where 3 u2*.dll files are going to the wrong location. The need moved. There is a thread about it somewhere on Sage City Forum. I'll see if I can find it.

Check out this KBA: 20969 fixed with patch: LM5002-T might be your issue.

Run WKSUPDATE

Like I was trying to say - run WKSUPDATE Standard from the WKSETUP folder. That will put the DLLs where they need to be.

Nice, so wksupdate should just be run as a matter of course after the setup?

I would. An ounce of prevention is worth a pound of cure.

Thanks @BarbaraGoldstein , I did wonder what the purpose of the wksupdate was. I thought it had something to do with help files or something like that.

Yes, @BarbaraGoldstein posted this save for me a few weeks back. So let's review 1) Turn off UAC, Log on to the Workstation as Administrator (could be optional). 2) Run wksetup from the MAS folder (NOT the DVD). Be sure to right click and select ""Run as Administrator, 3) Don't forget the Azalea fonts if this is new workstation. Install special Azalea 64 OS DLL's if worsktation is 64 OS, 4) Run the wksupdate.exe EVERY time. 5) Test paperless, 6) Configure Paperless PDF printer if WS is 64 OS. 7) If WIN 8 install, Hack registry so that paperless functions properly. Did I miss anything? Rinse, Repeat.

Periodically having this issue with an XP workstation on Sage 100 ""Adv"" v2013pu4, plus the XP workstation doesn't have the C:\Program Files\Business Objects\Common\3.5\Bin\ folder - although the C:\Program Files\SAP Business Objects\Crystal Reports for .NET Framwork 4.0\Common\SAP Business Objects Enterprise XI 4.0\win32_x86\ folder does have those 3 files all with date/time stamp of 8-2-12, 6:52p. Not sure how to resolve.

Fyi, turns out the cause of my client's issue was the user was re-running the Payroll Tax Calc before going back to print the Check Register; she thought she had to.