Sage 100

Worked on an upgrade yesterday - nearly every workstation came back with some variation of wrong version of CRPE32.DLL We've covered this here before -- the issue seems to come up the most on Win7 - 32 or 64. Brett previously provided this fix -- which is good to remember: Also works for CRPE32.DLL not found or similar when trying to automatically convert reports (WES/ Upgrade from 4.3 to 4.50 - 6/13/12) On a 64 BIT system drop this file into c:\windows\sysWOW64 or you will see the error message continue Brett Zimmerman: Resolution is to simply copy the CRPE32.DLL file from C:\Program Files\Business Objects\Common\3.5\Bin\ into the C:\Windows\System32\ folder.

Screen shot courtesy Jim Woodhead

Almost 100% error rate on this. I did not physically do the wksetup (an it person did). I believe all the errors were Windows 7 both 32 and 64. First one I've had where every workstation required a manual fix. Overall I find the upgrades require between 6-8 manual tweaks to get them to run. Not a ringing endorsement of a customer being able to automatically upgrade.

Sage hasn't even bothered getting the default install paths the same between wksetup and wksupdate, so I am not too worried about them ever actually implementing auto upgrades.

They have already back pedaled on this and stated Sage Advisor would advise that an upgrade is ready..... So help me -- if there is anyone within Sage collecting ""performance bonus"" for that little feature..

Thanks for posting this again! I was finishing up an upgrade late on Friday (4.3 to 4.5) I was out of town with a long drive home ahead of me, 6 out of 6 workstations got the CRPE32.cll message - I remembered seeing this post and that probalby saved me not only time, but blowing a brain gasket. :) Gotta love 90 Minds

I've not yet figured out why I suddenly was pestered with CRPE32.DLL messages. The fix is easy enough but it's a hassle to take numerous calls or to explain the copy/paste routine (careful because on 64 bit OS you have to go into the sysWOW6 or the fix won't 'work').... The only variable I could see is that I got this on a system where a large # of the standard forms/reports (saved) were prompting for conversion. It's possible that is what triggered it and that advance use of MASCRCW masks this issue?