ODMA Incident Report

X000100: ODMASAMP with Word on NT

Last updated 2001-03-05-16:06 -0800 (pst)
The latest version of this information is available on the AIIM DMware ODMA site.

Category: Fatal Error - Critical Incident ID: X000100
Priority: 9 - Urgent Status: Under Investigation
Component: ODMA32.dll 2.0.0 and ODMASAMP 2.0.0 with Microsoft Word 2000 on Windows NT.
Repaired in: tbd
Related information:
X001000: Microsoft Word 2000 Save Failure
X000200: MS Office Between Win98 & NT
Q000606: Troubleshooting Microsoft Word ODMA Integrations
Q000602: Where Is Support Information for Microsoft Office?
Q000001: Configuring MS Office for ODMA
Assigned To: tbd
Reported By:
Boon Long (2000-01-27)
Date Logged: 2000-08-11
Date Recorded: 2001-03-04
Date Closed: none


1. Incident Summary

2. If This Is Happening to You

3. Actions Toward Resolution

4. Investigation of Incident

5. Elimination of ODMASAMP Failure


1. Incident Summary (2001-03-05)

When testing ODMA integration using Microsoft Word 2000, ODMA 2.0, and the ODMA 2.0 Sample DMS, ODMASAMP, there are conditions under which a document is not saved properly.  

It appears that the problem is not with ODMASAMP, but with Word 2000 and that the incident is the same one covered by

Please consult those incident reports for the latest status and resolution.

This incident report is being kept open until investigation confirms that there is no ODMASAMP defect that contributes to the reported case or other incidents that people experience.

Why is this incident critical?

2. If This Is Happening to You

If you are having difficulties with ODMASAMP operating properly with Microsoft Word 2000, or you want to use ODMASAMP to isolate/confirm a possible ODMA integration problem in Microsoft Word 2000, carry out the procedure in this section:

  1. Ensure that Microsoft Office is configured properly for operation with ODMA.  See Q00001: Configuring MS Office for ODMA.
  2. Make sure that you have the latest stable version of ODMA Software installed, including the latest version of ODMASAMP.  See Q000603: Latest ODMA Software.
  3. Perform the configuration operations necessary to have ODMASAMP be the global default DMS for all ODMA-aware clients, or modify the Windows Registry to make ODMASAMP the specific default assigned for Microsoft Word.

After configuring Word 2000 to operate with ODMA, conduct integration trials with unimportant test documents.  

Figure 1.  Typical Word 2000 File | New dialog.

Create a test document in Word 2000, using File | New.  At this point, there is no indication that a document-management system will be used.  It is only when the user decides to keep the document that any ODMA-related dialogs appear.

After you have selected the template to use and entered some text, select File | Close.  You should be asked whether you want to save the document or not.  Say that you do want to save the document.  At this point, if the ODMA configuration is set properly, you will be invited to specify the format of document that you want Word 2000 to deliver to the DMS.

Typical Save File As Type invitation

Figure 2.  Typical Save File As Type dialog when a DMS is present.

After you select the document type to use, you will finally see the ODMASAMP dialog for creating a rudimentary document profile:

ODMASAMP Document Profile Dialog

Figure 3.  ODMASAMP Document Profile Dialog

If instead the document is closed without any invitation to save the document, you may be seeing the Word 2000 Save Failure incident.

Finally, you should be able to see the document that you created using the Windows 2000 File | Open dialog.  This will lead to the rudimentary ODMASAMP dialog, if the ODMA configuration is operating properly:

Word 2000 File | Open response from ODMASAMP

Figure 4.  Word 2000 File | Open response from ODMASAMP

If you do not see any DMS-specific dialogs, that signifies that Microsoft Word is not detecting the presence of ODMA or ODMA is unable to initiate operation with a DMS.  In those cases, Word 2000 reverts to file-oriented operation as if no DMS is installed.

3. Actions Toward Resolution

The following actions are being taken to resolve this incident:

4. Investigation of Incident

This incident has occurred with the following configuration:

Microsoft Word 2000 Microsoft Windows NT 4.0 with ODMA Connection Manager ODMA32.dll 2.0.0 ODMASAMP 2.0.0 Sample DMS


5. Elimination of ODMASAMP Failure

Sketch the way that we demonstrate this is not an ODMASAMP problem..


Dennis Hamilton
reviewed old ODMA Tech mail for untracked incidents, logged this incident (2000-08-11) and then recorded the incident (2001-03-04) as part of having all backlog recorded.  Identified apparent relationship to X001000 and X000200 and initiated further investigation to confirm that.
Boon Long
provided the initial notification that the correct functions in ODMASAMP were not being exercised in some ODMA configurations.

created 2001-03-04-08:17 -0800 (pst) by orcmid
$$Author: Orcmid $
$$Date: 01-03-05 16:06 $
$$Revision: 5 $