When trying to refresh a Business Objects error... DMA0007

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.

I suggest you right click on the short cut, and select properties, go to the compatibility tab and select run as : windows XP service pack 2 and try it again.. you should be good to go

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

mac os x 10.5.2

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?

This error message occurs if the following conditions are true:

• The option Nothing (hide objects) is selected in the Display options for this workbook section in the Excel Options dialog box.
• You create an object, such as a cell comment, in any cell in a column.
• You try to hide the column to the left of the column that contains the object, the column that contains the object, or all the columns to the right side of the column that contains the object. Or, in some cases, you try to insert a row or column in the worksheet.

There are two ways to fix this problem.
Method 1:  Temporarily toggle the option from "Nothing (hide objects)" to All In Excel 2007, temporarily toggle the option from Nothing (hide objects) to All, and then insert the rows or columns as needed. To do this, follow these steps:

1. In the upper-left corner of the Excel window, click the Microsoft Office button.
2. At the bottom of the menu, click Excel Options.
3. Click Advanced from list of options on the left.
4. Scroll down to the Display options for this workbook section, and then click All under For objects, show:, and then click OK.

Notes To use the keyboard shortcut to toggle this selection, press CTRL+6. 
If these steps do not let you hide rows or columns or insert rows or columns in Excel 2007, try the steps in method 2.
Method 2: Change the position property of the object to Move and size with cells To work around this issue, Excel 2003, Excel 2002, and Excel 2000, change the position property of the object to Move and size with cells. To do this, follow these steps:

1. If the object is a cell comment, select the cell that contains the comment, right-click the cell, and then click Show Comment or Show/Hide Comments. Note This makes the comment visible.
2. Move the pointer to the edge of the object until the pointer changes into a white arrow with four small black arrows on the pointer. Then, click the object to select it.
3. In Excel 2003 and earlier version of Excel, click <object name> on the Format menu. Note In this menu command, <object name> is the name of the object, such as "Comment" or "AutoShape."  In Excel 2007, click Format <object name>.
4. In the Format dialog box, click the Properties tab.
5. Click Move and size with cells, and then click OK.
6. If you want to hide the cell comment again, right-click the cell that contains the comment, and then click Hide Comment.
7. Follow these steps for each object in the affected column as described in the "Cause" section. When you hide the columns, you do not receive the error message.

For more information, visit the Microsoft Knowledge Base article: http://support.microsoft.com/kb/211769

Why not add a simple derived table in the universe, e.g.

select 1 as 1

Then place a self restricting join on the derived table
Then add the self restricting join to both contexts

Create an object from the derived table and add to query...
this should prompt users for a context.

JB

This from the Word Help files - search for Embed.

You can simply select an area in Excel copy it and paste it into your word document, but embedding allows the data in your Word document to be automatically updated as you change the figures in the Excel Worksheet.

From the Help pages:

You can insert objects (object: A table, chart, graphic, equation, or other form of information. Objects created in one application, for example spreadsheets, and linked or embedded in another application are OLE objects.) into a Microsoft Word document when you want to include information from files created in other Microsoft Office programs or in any program that supports linked objects (linked object: An object that is created in a source file and inserted into a destination file, while maintaining a connection between the two files. The linked object in the destination file can be updated when the source file is updated.) and embedded objects (embedded object: Information (object) contained in a source file and inserted into a destination file. Once embedded, the object becomes part of the destination file. Changes you make to the embedded object are reflected in the destination file.).
Embedded object
Linked object
Source file
For example, a monthly status report might contain information that is separately maintained in a Microsoft Excel worksheet. If you link (link: Used to insert a copy of information created in one program into a Microsoft Word document while maintaining a connection between the two files. When the information changes in the source file, the changes are reflected in the destination document.) the report to the worksheet, the data in the report can be updated whenever the source file (source file: The file that contains information that was used to create a linked or embedded object. When you update the information in the source file, you can also update the linked object in the destination file.) is updated. If you embed (embed: To insert information created in one program, such as a chart or an equation, into another program. After the object is embedded, the information becomes part of the document. Any changes you make to the object are reflected in the document.) the worksheet in the report, your report, or destination file (destination file: The file that a linked or embedded object is inserted into. The source file contains the information that is used to create the object. When you change information in a destination file, the information is not updated in the source file.), contains a static copy of the data.
The differences between linked objects and embedded objects
The main differences between linked objects and embedded objects are where the data is stored and how you update the data after you place it in the destination file.
Linked objects When an object is linked, information is updated only if the source file is modified. Linked data is stored in the source file. The destination file stores only the location of the source file, and it displays a representation of the linked data. Use linked objects if file size is a consideration.
Linking is also useful when you want to include information that is maintained independently, such as data collected by a different department, and when you need to keep that information up-to-date in a Word document.
When you link to an Excel object, you can use the text and number formatting from Excel, or you can apply the formats supplied by Word. If you use the Word formats, you can preserve formatting when the data is updated. For example, you can change table layout, font size, and font color without losing those changes once the object in the source file is updated.
Embedded objects When you embed an object, information in the destination file doesn't change if you modify the source file. Embedded objects become part of the destination file and, once inserted, are no longer part of the source file.
Because the information is totally contained in one Word document, embedding is useful when you want to distribute an online version of your document to people who don't have access to independently maintained worksheets.
Edit and update linked objects
To edit a linked object in your document, use the Links command on the Edit menu.
By default, linked objects update automatically. This means that Word updates the linked information every time you open the destination file or any time the source file changes when the destination file is open.
If you prefer, you can change a linked object's setting so that the linked object is updated only when you choose to manually update it.
To ensure that your document is always up-to-date, you can also update linked objects whenever you print the document.
To prevent updates, you can lock individual linked objects. When you lock a link, Word uses the last information available from the source file.
You can also permanently break the connection between a linked object and its source file.
Edit embedded objects
To edit an embedded object, double-click it, and then make changes to it in the source program (source program: The program used to create a linked object or embedded object. To edit the object, you must have the source program installed on your computer.). If you don't have the source program, you can convert the embedded object to the file format of a program you do have.

the scanner or main circuit board is defective. Give it back to dealer due to warranty.

It's an internal bug with the program. You should try and backup your program files and do an uninstall. Reboot the computer and reinstall. If this still does not solve your problem then most likely the software is not totally XP compatible (most pre-2003 software isn't). You may want to look at similar packages I can look around and recommend if you like?