Sage 100

Another issue from this AM with the v2013 install from last weekend. XP workstation is used to print PR checks. Checks print successfully, but the check register is not prompted for nor does the check printing menu close. When you try to print the check register, it says checks haven't been printed. Repeat check printing, same result. Print checks from server. Everything is fine. Print an AP check from XP workstation, that is fine. Issue seems to be with the legacy PR module and the XP workstation. This workstation had the have the u25store.dll installed. Any one else seen this behavior?

Isn't there a patch for this?

I think this but maybe was another one -- https://partners.sagenorthamerica.com/irj/go/km/docs/sageKM/Sage%20MAS%2090%20and%20200/Gated%20Customers/Warr_Svc_Support%20Plan/110-9000788.xml

You mean a hot fix? PU 4 was installed prior to running the WS setup, I don't see any hot fixes out there for v2013

That is it exactly. Thanks.

Take a look at the link - looks like they're claiming Crystal DLL? I just noticed that the link is not specific to payroll thought so this may not be what I'm thinking of.

I'll try the reinstall and run as administrator first. The installs from yesterday were NOT run as administrator. Sigh....

If this is an upgrade, try recreating the PR check form from scratch using Sage 2013.

Check prints fine from the 2008 server...

If it's Sage 100 Standard, run WKSUPDATE Standard from the WKSETUP folder. Starting with (I think) PU3, this program performs the actions in that KB for you (ie puts the DLLS where they need to be).

@BarbaraGoldstein - Running the wksupdate did the trick. go figure why there are two to run....

@JeffSchwenk every time there is a Sage product update - check the read me as it will tell you that you have to run the wksupdate for Sage 100 Standard if necessary.

Oh, If I would just get in the habit of reading the readme information. I normally would just run it in tandem. But in this day and age, shouldn't installs be so much easier than they are??? Sometimes you have to run wksupdate, sometimes you don't. Why???

if something changes that needs to be installed to the workstation due to a product update, Sage handles it by the wksupdate - if it is there in the folder you should run it every time. It's basically a service pack workstation setup.