Technology Blogs by Members
Explore a vibrant mix of technical expertise, industry insights, and tech buzz in member blogs covering SAP products, technology, and events. Get in the mix!
Showing results for 
Search instead for 
Did you mean: 
Active Contributor

Once I deployed a web application on the production machine, to my dismay I noticed that Crystal Reports could not turn up. I checked the runtimes installed on my machine, references in my project(s) & web.config file. I redeployed my application, however could not find the answer to “Why the reports would not turn up?”

I started cursing ‘gremlins’ for this, as everything was working on my development machine. This is one of the most common errors which users usually face while they try to access the crystal reports through the web page.

Following are the symptoms of the error:

  • The Blank Page appears in the browser when a .NET Web application is run.
  • The title of the browser becomes "Untitled Page".
  • The status bar of the browser shows "Done, but with errors on page" or "Done" with yellow (!) exclamation mark.
  • When the user clicks on the yellow (!) exclamation mark, Internet Explorer dialog box shows error: "Problem with this Web page might prevent it from being displayed properly or functioning properly. In the future, you can display this message by double-clicking the warning icon displayed in the status bar."
  • Error : 'bobj' is undefined.

There are few reasons which lead to this error:

  1. Missing "crystalreportviewers12" folder in the custom website.
  2. Application pool is running under Integrated mode when IIS 7 is used.
  3. Wrong value assigned to the key called “resourceURI” .
  4. The error ‘bobj Undefined’ occurs in development machine as the .NET  Framework could not find the files needed by Crystal Report Viewer at  the specified location in the Windows folder.

Following are the solutions to the above scenarios:

  1. Copy the folder "crystalreportviewers12" from “C:Inetpubwwwrootsystem_web2_0_50727" under “Default Website” to the “Custom Website” directory in IIS. Or, create a virtual directory pointing ‘aspnet_client’ folder in the custom web site directory.
  2. In the IIS Manger, select the Application Pool and Basic Settings. Under Managed Pipeline Mode, change Integrated Mode to Classic Mode.
  3. The value of resoureURI should be "~/crystalreportviewers12" not "/crystalreportviewers12".
  4. Copy the CrystalReportViewers12 folder from
    "C:Program FilesBusiness ObjectsCommon4.0" and paste it to "C:WindowsMicrosoft.NETFrameworkv3.5ASP.NETClientFiles".

          Note: Framework may vary as per the Visual Studio version used.

This blog targets Crystal Reports 2008 (12.x) but can be applied to other versions of Crystal Reports as well. If there are any other scenarios which lead to error, they can be brought to notice by adding a comment with the resolution (if any). Please do not forget to ask questions on the SAP Crystal Reports, version for Visual Studio. If this does not help, please consider purchasing the single case.

I would suggest checking the SAP Crystal Reports, version for Visual Studio, before posting any questions and checking KBase as a solution may exist.

Additional Resources (SAP Knowledge Base Articles):

Labels in this area