Sage 100

v2013 Migrations. Seems to be an issue with the U25store.dll not being installed consistently. Seems that this DLL is needed to print checks. Last weekend, issue was with XP workstations. Yesterday, issue was with the both an XP and a WIN 7 32 OS workstation.

When you do the autorun for the initial install - are you doing ""run as administrator""? I'm not sure if that makes a difference but I've seen @BethBowers reference it a few times so now I'll always right click any executable during the installation and ""run as administrator"". Don't know if that's the cause or not. I've not seen a widespread issue where I had to move around the U25store.dll

Another thing I keep forgetting to do......... If SAP can create an install routine for Crystal, why can't Sage do the same??? I did note that trying to run a parallel migration in v2013 DOES require admin rights to install or else it fails, so why can't the wksetup check for the same rights???

Doing the Run As Admin certainly seems to install more that a regular run. And of course the Autorun does more than wksetup (but heaven forbid they tell us that - and then again, then why even have the wksetup).

The XP workstation did have admin rights..... So danged confusing now........

Doesn't seem to matter sometimes - doing Run As works differently even IF you had Admin rights. I could be completely wrong, or the IT guys could be BS'ing me about whether I have Admin rights, or maybe it makes a diff if you have LOCAL Admin rights, or who knows.