C0000005 'EXCEPTION-ACCESS VIOLATION' call stack at module... error

Tahir, did you download the .pfd file from Tally's site: http://mirror.tallysolutions.com/Downloads/TallyPDFs....? This appear to have all the information you need.

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.

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

Exiting tally
internal error.contact tally
software exception c0000005
(memory access violation)

pls tell me tally error c0000005 solutions..

There are 3 step to repair c0000005 error

If you got c0000005 error then there is a 94% chance that your computer has registry problems. To repair c0000005 error you need to follow the steps below:

* Step 1 - Download a c0000005 error repair tool,install this error repair tool.
* Step 2 - Click the Repair All Button.It will scan you pc for Free.
* Step 3 - Then click the Repair All Button again and your done! It is very easy to repair c0000005 error.

Here are the url of c0000005 error repair tool:http://www.fixerroreasy.com/ttfix-c00000… Source(s): http://www.fixerroreasy.com/ttfix-c00000…

256 mb RAM

If you got c0000005 error then there is a 94% chance that your computer has registry problems. To Fix the problem you need to follow the steps below:

• Step 1 - Choose a c0000005 error repair tool,download and install c0000005 error repair tool Scan for FREE.
• Step 2 - Click the Scan Button.
• Step 3 - then click the Fix Button and your done! It is very easy to repair c0000005 error.

Download Perfect Optimizer from below url
http://www.fixerror365.com/tidpp-c0000005_error-zz0001

This error - DMA0007 is generally a connectivity issue, or you are attempting to refresh a report that uses a local dataprovider , e.g. an Excel workbook.


Which version of Business Objects are you using?
How are you refreshing the report.. manually / via infoview / scheduled in XIR2 or via BCA?

If you got c0000005 error then there is a 94% chance that your computer has registry problems. To Fix the problem you need to follow the steps below:

• Step 1 - Choose a c0000005 error repair tool,download and install c0000005 error repair tool Scan for FREE.
• Step 2 - Click the Scan Button.
• Step 3 - then click the Fix Button and your done! It is very easy to repair c0000005 error.

Q: Which C0000005 Error Repair Tool is the most effective? A: The results of our research and rigerous testing procedure found that Perfect Optimizer was the most effective c0000005 error repair tool. Its easy to use, eliminated all known errors on our computer, includes great safely features and left our PC running incredibly fast. We were extremely impressed! Second came RegCure which was very user friendly, but did not perform as well in tests. Third came RegistryEasy.
Click Here To Download Our Winner C0000005 Error Repair Tool "Perfect Optimizer":