Sage 100

Just did a Sage 100 standard upgrade for a client from version 4.4 to 2013 and on one computer (Windows 7) we get an error if we try to print anything that uses crystal - standard reports, custom reports, forms. It starts with a small message box that says "":Crystal"" and the Info button yields Error 200 in SY_ReportCommon.pvc Line 621. We are able to print reports just fine from the other computers. I have done the un-install, re-install of the client (as administrator) and am signed in as administrator to make sure it's not a rights issue. This is a new one for me, anyone else run across something similar?

Not exact but perhaps something to check: 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. http://www.s-consult.com/2012/04/09/error-200-in-sy_reportcommon-pvc-line-611-in-4-5-and-line-596-in-4-4/

There was a post I saw a few weeks back about something similar but it was related to jobops, it had the :200 as the error when printing reports. Should I send fix?

@Wayne - Thanks, I will give that a try. @Claudia - I'm willing to give it a shot if you send it to me.

@ClaudiaGallegos -+ Please post it here....

I had this same error on two machines a few weeks back. Both were XP machines. We had to log out of the user and log in as Administrator, completely disable Virus Scan (from Boot) restart, relog in as administrator and then install. Worked on both PC's. Good Luck!

Here it is, took me a while to find it

Thanks for the help everyone! The problem ended up being the .Net Framework 4.0 which was already on the computer before we did the client install. When we removed the client and removed .Net 4.0 and then re-installed both it fixed the problem.