0x800a01b6 - JavaScript runtime error: Object doesn't support property or method 'isObject'

[Former Member]

After a great deal of hardship, I finally got Crystal Reports installed and integrated with VS2012.  Despite multiple attempts to install and re-install this program, it took several tries and the removal of all previous versions to get the Reports to show up in VS2012.  Once I got it all done, I started getting this error regarding bobj - and how it was undefined.  This went on for days.  Finally, quite by accident, I noticed that crystalreportsviewers12 had become crystalreportsviewers13.  I changed all of the references to crystalreportsviewers (notice the absence of the number), and I stopped getting errors that 'bobj' was undefined.

Well, now it is defined....

Unfortunately, it does not work, and I have no idea what I am looking for to make it work.  In VS2010, it took forever to get Crystal Reports working, but we finally did.  Now we're two weeks into the VS2012 Upgrade, and there is NO WAY to make it work, as we have no idea what bobj wants or why it cannot handle the property or method it is producing errors about.

The line of offensive code is:

if (!bobj.isObject(json))

Apparently, it want's something other than null. I have no idea how to give it what it wants...

followed by:

bobj.crv.stateManager.setComponentState('MainContent_CrystalReportViewer1__UI',eval('('+document.getElementById('__CRYSTALSTATEctl00$MainContent$CrystalReportViewer1').value+')'));

Now something tells me that this is an easy fix if I knew what I was looking for, but I do not.  This is not an error I was expecting to encounter.  When we used VS2010, once we had the versions on both server and development matched, it worked like clockwork.  Now we just have a broken intranet. When I place it on the actual development site, I do not see errors, but I do get a blank report that looks like the picture attached.

[former_member188030 · Accepted solution]

Hi Todd,

Try this.

Run process monitor with your application till it throws the error.

Search the ProcMon log for 'crv.js', this will tell you where the app is looking for the CR viewer files.

Now manually copy the crviewers folder from CR installation directory to this location from log.

Rename the folder to crystalreportviewers13.

Thanks,

Bhushan

[Former Member · Accepted solution]

I can't tell you why, but renaming everything to crystalreportviewers13 and copying over the files DID fix the bobj being undefined issue.  No idea why that did that.  However, once the error went away, my report (in DEVELOPMENT VIEW, I have not pushed it to the PRODUCTION server) shows, instead of a report, a series of grey vertical lines.  Like it is working, but not quite all the way.  But you DID fix the BOBJ error.

Note to self and others:  DO NOT CHANGE the crystalreportviewers13 directory, as that is necessary for it to work properly. You may have to copy things into it, but do not change the directory itself.

[Former Member]

Did get a chance to push it to the production server.  No more crashes or errors, but it does say load report failed....

[former_member188030]

Hi Todd,

A new error a new post please

However, ProcMon would help here too. Search the ProcMon log for your reportname.

Check the error in front of it.

Thanks,

Bhushan

[Former Member]

I actually downloaded ProcMon, and it is a very cool app, but I couldn't find a reference to the bobj anywhere, I think I popped the log over to you.  On the upside, I got my ORIGINAL Reports to run when everything got renamed the crystalreportsviewers13, and on BOTH server and development box both had the files from the asp_client thing copied over.  Once both versions were exact and it matched.  My Old CR reports came up Golden!  The viewers directory was critical. 

Of course...none of my NEW reports work. I just get database load failed....Oh well, that's an adventure for another thread.  But thanks Bhushan, at least the CRISIS has been averted.

FOR THOSE READING WHO HAD THIS ERROR (Or any other VS2012 issue):

1. look for the references to the crystalreportviewers13 directory in the web.config. Make sure they exist.
2. Shut down VS2012 - it needs to not be running.
3. Install the latest update on both development and production servers. Click Here - the one on the far left at the top of the list will be the latest
4. Re-open VS2012
5. Make sure the URI reference (to crystalreportviewers13) is correct in Web.Config, not only in NAME, but in directory level {watch for the tilde - it should only be there if you are dropping below the root of the web site to use the scripts contained therein}
6. On BOTH servers, find the reports viewer folder where it is installed in SAP Business objects, under a directory titled Common,
7. On BOTH servers COPY THESE FILES into the Crystal Reports Viewer directory under the correct inetpup/wwwroot/Your Web Site/crystalreportsviewers13 directory
8. REBUILD your project (you have to do this...)
9. Kick back and take all the credit for saving the day.