Sage 100

I'm definitely seeing a problem with CRPE32.DLL not being copied to Windows\System32 (or sysWOW64 for 64 bit os) on my last three or four upgrades. About 70% of the time the problem is that it does not seem to have copied. The other 30 % it's a DLL version error (old CRPE32.DLL in the SYSTEM32). And just when I though Sage had fixed this issue...

Are these MAS90, MAS200, or both? I wonder if it's because of PU3, because I never had this issue on my older upgrades, but I did see it on the latest I did last week. Just one workstation, though.

These have all been 4.50.3 https://www.evernote.com/shard/s1/sh/a6d7a93a-d742-4953-94f7-ca9b63242ef8/00367cd8fd8be42e78bc7b490b26a785

Encountered it this morning. New comptuers and MAS installed by IT vendor, then the Crystal error started. End user on 4.50 SU2.

I've seen two cases: 1. CRPE32.DLL not copied at all (not present in system32) 2. Old incompatible version in System32 Unsure if this is a sudden issue (think so) introduced at some later version of MAS -- cannot recall this being so widespread.

I was on a Win XP machine and all the clients legacy reports worked fine excepted for the 2012 941. It gave the Error 140 SYCOCX error. I copied the CRPE32.DLL file from C:\Program Files\Business Objects\Common\3.5\Bin\ into the C:\Windows\System32\ folder and everything was good. 4.50 PU3

Similar experience to Jim's

I just ran into the 941-related issue the other day for a client that is able to print every other Sage report. Go figure.

Since PR is a legacy module and the 941 is a legacy module, this is not quite so surprising. Irritating as all get out, but not surprising............