The type initializer for 'CrystalDecisions.CrystalReports.Engine.ReportDocument' threw an exception

I installed Crystal Reports XI R2 on my development machine in addition to Visual Studio and the bundled 10.2 version of Crystal Reports.  Now my Visual Studio 2005 project will no longer build due to a 'The type initializer for 'CrystalDecisions.CrystalReports.Engine.ReportDocument' threw an exception' error.  I have uninstalled Crystal Reports XI R2, repaired visual studio 2005, uninstalled and re-installed the VS Crystal Reports option, run the redist msi file,  and nothing has solved the problem.  Any suggestions?
khuehneAsked:
Who is Participating?
 
sarabandeCommented:
does the file exist? does the file version fit to vs2005 and is the file size identical to the size when you install crystal 2005 at another system? can you check whether the dll is dependent on other dll's (using depends.exe)? can you check whether the dll is registered (try regsvr32 "<full_path_to_crpe32.dll>")

Sara
0
 
sarabandeCommented:
can you go back to a system recovery point created before installation of crystal reports XI R2?

if not, you may look into event viewer (eventvwr.exe) whether crystal has reported additional information to the exception.

if that is not the case, you could ask crystal support or try to use a good uninstaller tool. for the latter you would install first crystal for vs2005 and second the XI R2. use the uninstaller then for both in reverse order and reinstall only crystal for vs2005 afterwards. don't use redist or other installations cause crystal is not dependent on them.

Sara
0
 
khuehneAuthor Commented:
Thanks for your suggestions, Sara!  I checked the event log and didn't find any additional information and I did try uninstalling both versions of Crystal and re-installing VS 2005 Crystal Reports and that wasn't successful.  I logged a ticket with SAP as well, but it's been slow going.
0
 
sarabandeCommented:
it is difficult to solve such errors cause it could be one single dll which has a wrong version or one single registry entry not removed by the uninstaller.

you could try to locate crystal dlls in the system32 folder (check prefixes and file properties) and move them to another folder. check your "PATH" environment variable whether it points to a wrong folder. you also could try to search for name "crystal" in the registry after uninstalling. but before doing any changes make a backup (recovery point) of your registry.

can you post the full text of the exception error? sometimes such kind of errors have a much different reason than suspected.

Sara
0
 
khuehneAuthor Commented:
I agree, it's difficult to solve these types of errors.  The full text is "Could not load C:\Program Files (x86)\Common Files\Business Objects\2.7\bin\crpe32.dll."

Kris
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.