SecureDoc Crystal Reports error "bobj is undefined"
We have encountered some problems in the SecureDoc reporting tool with certain customer installations (in one case where the user had installed the IIS Inetpub directory on something other than the C: drive, which our product does not support).
Part of this issue below can be traced to the fact that our reporting tool installer will not work correctly if the IIS Inetpub directory is not located on the C: drive.
In one case, having done the installation in the expected way with some "forces" to get it to work with a non-C: drive Inetpub directory, the client was able to see the graphs on the first (default) page of the reporting tool, but attempts to drill down or look at any other reports yielded report pages devoid of any details.
The web page would finish loading but would display a small yellow icon in the bottom left of the web browser (done, with errors). Clicking on this notification would show a subordinate page that would reference a cryptic message "bobj is undefined".
In this case, probably due to the difficulties in getting the Reporting tool installed cleanly in the first place (first being installed off c:, then being reinstalled on c:), it's possible that the Crystal Reports components were damaged, missing or incomplete within the Inetpub directory.
To remedy this:
Step 1: Copy the entire folder located at: C:\Program Files\Business Objects\Common\4.0\crystalreportviewers12 to the clipboard.
Step2:
1) Go to My Computer
2) Right click and select Manage
3) Expand Internet Information Services (IIS) Manager
4) Expand Web Sites
5) Expand Default Web Site
6) Expand aspnet_client
7) Expand system_web
7) Look in the folders listed under aspnet_client .. if the folder "crystalreportviewers12 does not appear in any of the folders listed under aspnet_Client, paste the entire "crystalreportviewer12" folder in the folder that is missing the "crystalreportviewers12" folder.
The above steps came from an external support bulletin board, here --> http://bytes.com/topic/net/answers/8233 ... -undefined
The person who discovered the solution looked at the most recent log file on the Server under c:\winnt\system32\logfiles and went to the very last entries in the log file. The path described in Step 2 above was listed, so he took a chance and pasted the missing folder in this path structure.
In a correct installation of the SecureDoc reporting tool, this directory IS required exactly as indicated.
Shown below is just one of these entries from the log file (note the path shown):
2008-08-19 14:09:09 10.6.71.108 GET /aspnet_client/system_web/2_0_50727/crystalreportviewers12/allInOne.js - 80 - 10.6.60.80 Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.1;+SV1;+In foPath.1;+.NET+CLR+1.1.4322;+.NET+CLR+2.0.50727) 200Another, perhaps faster and simpler solution:
NOTE: Tearing out and replacing Crystal Reports by first uninstalling, then doing a "repair" re-installation of the reporting tool fixed the issue - no more "bobj not found" message, and the downstream reports show up as they should.
Custom Fields
Error message or code: Error "bobj is undefined"