Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[phiba]

The error I get in MC19 is "Error - A runtime error has occurred. Do you wish to debug? Line 0 - Error: 'document.body' is null or not an object'". I click "No" and the same message appears a 2nd time. I click "No" again, and the error disappears, and the program runs normally. I get the error every time I start MC19 or make a setup change and then save it.

This same problem was reported in the MC18 forum, and the resolution given there was to "change the browser engine in MC Options > Tools > Startup from IE to Google Chrome.

But when I go in MC19 to Tools > Options > Startup, I don't see any place to select or change the browser engine. I looked in all the other Options categories as well, and searched the Wiki, all without results. Any suggestions?

I am running Windows XP SP3 and IE7. Google Chrome is set as my default Windows browser. I am in the process of upgrading to IE8 in case that might help.

It would be nice to have this solved before stepping up to buy the software, as it is somewhat annoying.

Thanks!

[glynor]

The option you're looking for is set via:

Options > Tree & View > Web Browser > Engine

Remember that the Options box has a search feature.  I found that one easily by searching the options dialog for "browser".

(By the way, I have no idea what would cause your particular error or if this will solve it.  I'm not sure how people's browser engine is getting set to Chromium, as it defaults to IE, and it is NOT connected to your default browser on the system in any way.  But, it is probably worth trying.  Unless you have a good reason to reset this engine to Chromium, it is best to leave it alone.)

[phiba]

Excellent, glynor, thank you!

I don't know why, but changing the browser engine from IE to Chromium solved the problem. No more errors!

I suspect it has something to do with my running Windows XP SP3 and IE7. I think that is the same configuration as the poster in the MC18 forum who reported the same problem and the same solution.

Also, it seems like it might be associated with the Facebook, Twitter, Google, and/or Share links, as the error was coming just as those buttons appears on the screen.