Sage 100

This is on my personal system - my 4.40 and 4.50 versions both stopped printing anything from a Business Framework module (forms, reports) and giving me an error 200 in SY_ReportCommon.pvc line 611 in 4.5 and line 596 in 4.4. Sage says to uninstall and reinstall WKSETUP. Did that. Reinstalled EVERYTHING in 4.4. Including up to PU8. Still no go. And no, I don't think I've installed anything since the last time it worked.

Just a guess, but is the default printer working from other apps?

I've tried the different printers, tried Deferred, tried Export/Email. Does it on preview or print.

I had something similar to this - I had to rename CRPE32.DLL from Windows\System32 and make sure there was a CRPE32.DLL in Program Files\Common Files\Crystal Decisions\2.5\bin\ After I did that it worked again.

Keep 'em coming - I renamed the CRPE32.dll and I did have it in the other directory. Still same error.

What is the WS OS? Anything come to mind on what you installed immediately prior to it crapping out on you? New MSFT patches?

I found this, expect you probably did, too. Subject: Error 200 SY_ReportCommon.pvc 560 occurs when printing graphical reports. Possible Resolution: In the report setup window, select the Collated check box. Note: The printer driver may require this setting to print properly. Print the report to a different printer.

It's trying to create the Crystal runtime object and for BF the main file behind that is CRAXDRT.DLL (the CRPE32.DLL is for legacy). Try to manually register that DLL which is typically in C:\Program Files (x86)\Business Objects\Common\3.5\Bin and the version for it laid down by MAS (as see in properties) is 11.5.something. If you get errors registering the DLL, look for multiple versions of it.

@AlnoorCassim - I LOVE YOU, MAN! Wherever I see you next - drinks are on me!

Care to blog this?

Sure - tell me where.

Just ran into this issue last week at MAS 200 client running a RDP session in v4.4 Their local instals work without incident. Haven't tried the suggested Sage remedy. Will try @AlnoorCassim suggestion. Beth, any luck?

Jeff - See that ""I LOVE YOU MAN"" entry - yes it worked.

Sorry, I didn't grasp the significance of the LOVE!

Men.

Can't live with them, can't live without them........................ Unfortunately, the resolution for me requires that I get the IT staff involved in order to register it. I hope they are successful....

Well, I just had the IT staff try Alnoor's suggestion. Did not work. Not sure if IT ""really"" followed the steps exactly or what. He says he only has two terminal servers running and he registered both of them. I'll wait for a reboot tonight then try again in the morning. Not sure what effect the reboot will have, but it is worth a shot.

@JeffSchwenk - But are you getting the same exact Error 200 SY_ReportCommon.pvc 596 Beth was getting in 4.4 or something similar to that?

It looks the same.

@JeffSchwenk don't you mean, ""Can't live with them, can't live with their hypotheses""?

Checked old emails and apparently troubleshot this exact error last year with someone. Besides craxdrt.dll not registered, another reason is an XI R1 version of that DLL was found in the 3.5\Bin folder (in my case it was laid down by Remedy software by BMC) instead of the expected XI R2 version. Another reason is registry permissions on HKCR \ CrystalRuntime.Application. You can contact me directly if you need to ..

This is so weird - did a MAS 200 upgrade (4.4-4.5) last night and one person is getting my original error. THANK GOODNESS I had it first! But WTH?

Lucky that you don't have a remote workstation couple with a reluctant IT staff to jump around...............

Well, damn it, but I do have the fix that worked for me NOT fixing their problem. I'm contacting Alnoor.

My issue was cured by reinstalled the workstation client. The cause was the WS had another program running a slightly different Crystal version. After the reinstall, MAS was able to locate the proper version. This client has had this issue in the past. In prior instances, user would get the ""incorrect version of Crystal was found, please rerun WK setup"" A big shout out to @AlnoorCassim for his assist.