Sage 100

Anyone have an innovative way to cure ""The wrong version of Crystal Reports is installed on this workstation"" Customer is on 4.5 and I have installed wksetup again and normally I'd just load Crystal 11.5 full version however in this case I'm remote desktop-ing in and would like to avoid rebooting the server. I was hoping to get away without installing 11.5 to remove any possible version conflicts.

Have you checked the PATH to make sure it's pointing to the correct installation of Crystal?

I'm trying to get away without installing the updated 11.5 version of Crystal until I go live. Unfortunately I don't think I'll be successful.

I am getting this same error on a clients server using v4.4.6 since I upgraded in June. I have been putting off trying to fix this for some time, can't find a solution. I have uninstalled and reinstalled crystal and workstation setup and still get error.

Hmm, normally re-doing the workstation setup takes care of it. Is there another version of MAS that's also running on that computer/server?

I agree with @Brett. I have lots of installs where I haven't bothered to upgrade the Crystal version and it's working fine (except for being able to click on the Design button in the Forms or std Reports - but these clients are the type who aren't going to have much of that).

Now that's weird - wksetup should fix it. Lots of users don't have Crystal loaded on their workstations and they run MAS just fine.

You may need to edit the Registry: http://www.sagesoftwareonline.com/sw_attach/kdb.asp?isresolutionconceptid=459926

The customer is up on 4.3 so removing Crystal 10 isn't a great option since it would remove their ability to print some custom reports. They're accessing MAS via remote desktop so it's a little more tricky than if they were standalone workstations.

I think Brett's response is probably the closest. My guess is the CRPE32.DLL file doesn't match the one 11.5 is supposed to use.

Thanks unfortunately I don't have a lot of leeway to tinker with their TS unless I want to forever own any resulting problems for the next 15 years ----- cue the recurring message from client ""Wayne ever since you did that Crystal fix our server.... (insert worldly ills) which it never did before)

1. Reinstalled WKSETUP 2. Installed Crystal 11.5 Same error Customer is using MAS 90 v4.30 on same server as 4.50 which is also on a Windows 2003 Terminal Server setup. I finally got them off and installed the full version of 11.5 and still the same error. Since I'm in testing I would like to fix the issue on this server as opposed to testing reports on another server. I also need to be careful not to take down their production 4.3 MAS90 or I'll put myself into a potential all day emergency repair session. My guess is that there is some incorrect DLL (I checked the DLL in the common file area and both sem right). Stumped on this one mostly because I'm trying to fix the wings on the plane while it's flying....

Have you tried uninstalling the WK client, rebooting (when you can) then reinstall the client?

The uninstall and reinstall of everything will be next.... Anyone know why this : Do not install Crystal Reports 11 on the same workstation that Crystal Reports 8.5 and 10 are installed on. Is listed in the KB article for how to install multiple versions of Crystal on one workstation http://infosource.sagesoftwareonline.com/sw_attach/kdb.asp?isresolutionconceptid=444103

My experience with using CR 11.5 in lieu of v10 is that it doesn't seem to be a big deal. I have saved many reports in 11.5 and then run in an earlier version of MAS without issue.

I agree though there can be issues with users who click the ""design"" button and save their report/form in a newer version of Crystal and find there is a problem with compatibility.

Hard for me to say which worked but I resolved this by: 1. Removed (uninstalled) workstation 2. Installed to a network drive letter vs C: (I was logged into server)

I remember having an actual INSTALL issue when I didn't use the network drive letter with 4.40... so I'd say you have a 50/50 on your resolution.

Thanks @WayneSchulz that fixed my problem. I would have never thought to map a network drive at the server level.