Of course I still had issues with that. I forget what, but it wasn’t good. I think it wouldn’t run on the production server. That server doesn’t have Visual Studio installed, only the CR engine. The version 10 assemblies I were using were the Crystal Report packages that came with VS.NET 2008.

In order to successfully be able to use all the correct assemblies, I had to do more research. What I ended up doing was completely uninstalling Crystal Reports and reinstalling it, and configuring some Virtual Diretories. The steps and and explanation after the jump.

When version 12 was installed, I had a javascript error on the Report Viewer page. It complained that object “bobj” was not found. It was a javascript object. I found the page was referencing a js file in the directory http://host/aspnet_client/system_web/2_0_50727/crystalreportviewers12/. There was no crystalreportviewers12 directory there, however there was one at the root… and one in the CR install directory, C:\Program Files\Business Objects\Common\4.0\. Then it was clear that the browser needed to find that folder somehow. I copied it there to test, and it worked. Later, as per direction, we created a Virtual Directory to the install folder. I also had to add C:\Program Files\Business Objects\BusinessObjects Enterprise 12.0\win32_x86\ to the PATH environment variable, otherwise I would get a DLL error when trying to export to Excel format.

That pretty much sums it up. But I’m going to outline the steps anyways:

1. Completely uninstall Crystal Reports (all version, make sure DLLs do not exist in Common Files folder, or Bin folder of web application)
2. Reboot
3. Install Crystal Reports 2008, doing a custome install and making sure to install packages for Visual Studio and the .NET framework (I don’t believe they were selected by default, this may have had something to do with it). I opted to install all features on my development machine, just in case.
4. Add C:\Program Files\Business Objects\BusinessObjects Enterprise 12.0\win32_x86\ to the PATH variable (adjust path if needed)
5. The directory crystalreportviewers12 must be accessible by client browsers from the aspnet_client\system_web\2_0_50727 folder. Copying the folder or creating a Virtual Directory to C:\Program Files\Business Objects\Common\4.0\crystalreportviewers12 are options
6. Reboot

I hope this helps anyone having Crystal Report 2008 problems with a ASP.NET site (or helps in any other way). The reason I revisted this was because I am configuring a new developement workstation I was upgraded to at work, and have to go through this process again. It’s good to refresh myself. If I run into any more problems I’ll post them. Please add your comments or ask any questions if you’re having problems!