Question

41

Crystal Reports 13 bobj is undefined JavaScript Error after installed visual Studio 2015 community edition

rated 0 times [ 47] [ 6] / answers: 1 / hits: 21891 / 9 Years ago, wed, july 29, 2015, 12:00:00

In Visual studio 2010 with Crystal Report 13 my project worked fine.

After I installed Visual studio 2015 community edition for my personal use. When i opened my project and run in Visual studio 2010 it throws JavaScript runtime error: ‘bobj’ is undefined.

I surfed some website

http://www.mahadera.com/error-0x800a1391-javascript-runtime-error-bobj-is-undefined/
http://www.aspsnippets.com/Articles/Crystal-Reports-13-Visual-Studio-2010-Issue-with-IIS---bobj-is-undefined-JavaScript-Error-and-Crystal-Report-Viewer-not-displaying.aspx

and I reinstalled and copied aspnet_client folder and paste into project. Eventhough problem not yet solved. I guess the error because i installed VS2015 community edition.

Please help me and im clueless.

Answers

Only authorized users can answer the question. Please sign in first, or register a free account.

reed

Add To Favorites

Follow

Total Points: 725

Total Questions: 85

Total Answers: 89

Location: Singapore

Member since Sat, Jul 25, 2020

4 Years ago

reed questions

1 npx react-native link command not working in latest version of react native. How can we link custom font family in my project

Tue, Jul 5, 22, 00:00, 2 Years ago

1 Alpine.js: How do I access x-data from a function in an external file?

Fri, Apr 16, 21, 00:00, 3 Years ago

1 I have an error : Cannot find module './utils'

Sun, Aug 16, 20, 00:00, 4 Years ago

1 react drag,drop, and connect arrow(or anything else) with animation between elements

Tue, Jun 16, 20, 00:00, 4 Years ago

1 Lodash.uniqueId always returns 1

Thu, May 23, 19, 00:00, 5 Years ago

View All

answered 9 Years ago dasias · Accepted Answer

We figured out the root cause of the problem. When you installed VS2015, it installed .NET framework 4.6, which is causing the dreaded bobj not defined error. Unfortunately, .NET 4.6 wiped out (or overwrote) earlier version of .NET - whatever comes with VS2010 in your case or VS2013 in my case. You can uninstall .NET 4.6 and then repair VS2013, which reinstalled .NET 4.5.1 and the problem went away. Unfortunately, repairing VS2015 puts .NET 4.6 right back and the problem reappears.

So the bottom line, you can either have VS2015 - or earlier version of Visual Studio without bobj error; but not both

Don't thank me - thank Steve :)