Fixes are available
APAR status
Closed as program error.
Error description
'This OLE object is a static metafile and cannot be activated' in DOORS client after updating an OLE object created by MS office in DWA when interop server does not have MS Office installed. Tested with DOORS9.4 and DWA 1.5 and DOORS/DWA 1.5 - valid APAR in both versions MS Office 2010 Steps to reproduce: Start DWA and ensure interop is running on a server that DOES NOT have MS Office installed. 1. Install Microsoft Office 2010 on a DOORS client machine only. 2. Open a DOORS module in DOORS client and select Insert?OLE object. 3. Select 'New' and Excel Worksheet or MS Word object. 4. Add some data and save OLE and the module. 5. Open the same module from DWA in Editing mode 6. Double-click the OLE object, then it will turn into an icon and the 'Editing object text' will appear. 7. Save it by clicking 'Tick' without or with any change. (You cannot change the OLE object but you can still change Object text.). 8. Close the module. 9. Open the same module using DOORS client on the machine with Office. 10. Double click the OLE object. You will get the message 'This OLE object is a static metafile and cannot be activated'. If you update the DOORS object with OLE in a DOORS client on a machine without Office (rather than DWA), OLE can still be activated. Workaround: Ensure MS Office is installed on server machine that runs DWA interop servers.
Local fix
Problem summary
"This OLE object is a static metafile and cannot be activated" in DOORS client after updating an OLE object created by MS office in DWA when interop server does not have MS Office installed. Tested with DOORS9.4 and DWA 1.5 and DOORS/DWA 1.5 - valid APAR in both versions MS Office 2010 Steps to reproduce: Start DWA and ensure interop is running on a server that DOES NOT have MS Office installed. 1. Install Microsoft Office 2010 on a DOORS client machine only. 2. Open a DOORS module in DOORS client and select Insert>OLE object. 3. Select "New" and Excel Worksheet or MS Word object. 4. Add some data and save OLE and the module. 5. Open the same module from DWA in Editing mode 6. Double-click the OLE object, then it will turn into an icon and the "Editing object text" will appear. 7. Save it by clicking "Tick" without or with any change. (You cannot change the OLE object but you can still change Object text.). 8. Close the module. 9. Open the same module using DOORS client on the machine with Office. 10. Double click the OLE object. You will get the message "This OLE object is a static metafile and cannot be activated". If you update the DOORS object with OLE in a DOORS client on a machine without Office (rather than DWA), OLE can still be activated. Workaround: Ensure MS Office is installed on server machine that runs DWA interop servers.
Problem conclusion
The code has been changed so that the product issue no longer occurs.
Temporary fix
Ensure MS Office is installed on server machine that runs DWA interop servers.
Comments
APAR Information
APAR number
PM83334
Reported component name
TLOGIC DOORS WE
Reported component ID
5724V97WA
Reported release
130
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2013-02-21
Closed date
2013-12-12
Last modified date
2013-12-12
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
TLOGIC DOORS WE
Fixed component ID
5724V97WA
Applicable component levels
R952 PSY
UP
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSYQBZ","label":"Rational DOORS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"1.3","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]
Document Information
Modified date:
29 October 2021