Question about Computers & Internet
Posted by Anonymous on
A 6ya expert can help you resolve that issue over the phone in a minute or two.
Best thing about this new service is that you are never placed on hold and get to talk to real repairmen in the US.
The service is completely free and covers almost anything you can think of (from cars to computers, handyman, and even drones).
click here to download the app (for users in the US for now) and get all the help you need.
Posted on Jan 02, 2017
The Unhandled Exception Error (C0000000005) is caused by a number of different things. It seems to be a kind of catch all for those errors that BO doesn't have a more specific error message for. You can upgrade to higher service packs to get this message less often but it still occurs even within 5.1.5. Here are a number of causes and potential resolutions.
1. Part of the Business Objects NT profile becoming corrupt.
Remove the following registry key:
Go to registry key HKEY_CURRENT_SOFTWARE/Software/Business Objects/BusinessObjects/5.0/USERNAME User Prefs
Something under here becomes corrupt. This can happen in many circumstances, but in particular where a low spec machine (e.g. 64Mb - this should ring alarm bells) is trying to open a 'large' report - sometimes as little as a couple of Mb. When USERNAME signs on to BO again, the key is recreated with the correct values.
2. Refreshing a report.
In fact, the refreshing completes and you see the message 'Disconnecting...'. This is BO, signing out from the database which it has been getting data from - normally you wouldn't see this unless BO is going slow. The fact that you see this, then get the bug is again a PC resource problem. Try it on a faster better specified machine to prove this.
Tidy up the report, remove unused variables, formulas as well as objects from the different queries. Encourage the user to purge the report, so when they pick it up next time the PC doesn't use much resource opening it. Sound them out on scheduling the report and getting the final result sent to them.
3. Importing universes
Another reason for C0000005 is a bug specific to the version of BO we have, 5.1.2. This is the problem with importing universes. Basically, each changed version of the universe has a counter which is incremented each time you save and export. Something goes wrong with this counter so BO is not happy to get the new universe. Mostly this is solved by deleting the existing universe from the C:\ drive and then forcing and import. There is a fix (which I have never got to work) which is to import and export twice. Don't forget about Tools/Universe - you can try and force an import from here. This was supposed to be fixed in 5.1.3.
4. An old or corrupt dll
If you look at the information given when you get the unhandled exception error there is a bit of hex and references to a bunch of dlls. Occasionally, one of those dlls is a duff version - try tracking that down. Also, could have problems with duplicate version of dlls, same file, e.g. ociw32.dll in more than one directory.
5. Miscellaneous resolutions
Try a full reinstallation of BO. i.e. deinstall, make sure no trace of files, folders and registry entries before reinstalling. Reduce the graphics acceleration level via control panel - not a problem on this site, but worth knowing about
Posted on Jan 24, 2011
Tips for a great answer:
Jun 26, 2015 | Tally Office Equipment & Supplies
Mar 30, 2014 | Office Equipment & Supplies
Oct 23, 2013 | Tally T2250 Matrix Printer
May 02, 2013 | Computers & Internet
Aug 20, 2012 | Microsoft XP Computers & Internet
Jun 18, 2011 | Tally T2245 Matrix Printer
Sep 01, 2010 | Computers & Internet
Feb 25, 2010 | Sony Computers & Internet
Dec 11, 2009 | Computers & Internet
2,851 people viewed this question
Usually answered in minutes!