I'm getting error "CRCRD5312E: The following OLE method failed. OLE problem: There is not enough memory or disk space to display or print the picture. OLE error code -2146823163" when exporting to Word a module with a single object containing a 3-row Word table, pasted as a "Microsoft Word Document Object". This is happening with new modules. We have older modules without this problem. I've tried restarting DOORS, Word and the PC. PC has 16 GB. This has happened on multiple PCs running different versions of DOORS client and Word: - Windows 10 PC, DOORS 9.6, Microsoft Office 365 Proplus - Window 10 PC, DOORS 9.3, Word 2016 Any help would be appreciated.
JKeenan - Fri Sep 28 12:29:23 EDT 2018 |
Re: OLE errors exporting to Word Had sometimes similar errors with Word, the reason remained a mystery.
Have you tried to do the export to RTF (Rich Text Format)? |
Re: OLE errors exporting to Word PekkaMakinen - Mon Oct 01 03:23:35 EDT 2018 Had sometimes similar errors with Word, the reason remained a mystery.
Have you tried to do the export to RTF (Rich Text Format)? Yes, I've tried RTF output and got the same result. This error seems very persistent. Thanks for responding. |
Re: OLE errors exporting to Word JKeenan - Tue Oct 02 10:44:31 EDT 2018 Yes, I've tried RTF output and got the same result. This error seems very persistent. Thanks for responding. Hi JKeenan,
We've been seeing the same error and dealing with it (TS001377251)...and to date, no solution from IBM. Their claim is that Microsoft changed some things and therefore it is not a DOORS problem.
I have discuss your concern with the DOORS development team. Since this is not a DOORS issue, there is not much we can do in the DOORS side. An Administrator or user with sufficient access to the registry will be required to implement the workaround. Also the affected OLE's imported previously will need to be reinserted. We are also checking to see if there is any existing DXL script that can trigger the previously imported OLE to make them work. I will keep you post. Please do not hesitate to contact us if you have any questions or concerns. Thank you and have a good day!
We have escalated this to a Priority 1 issue. If you insert an OLE from Excel 2013 or Word 2013 (and probably higher versions as well), and insert the actual text or spreadsheet (not the icon), you get a blank box in the exported Word document. We have our own document generator scripts in DXL. IBM did provide a few things that might help...but it doesn't address the OTB functions of the application. Bottom line...DOORS 9.6+ does not support Office 2013+ Take care, Mike G |
Re: OLE errors exporting to Word DOORS 9.6 does and it doesn't support Word 2013+ Here is the result of my investigation: I have 2 machines. One ALWAYS fails on the export of an ole from 9.6.1.7 thru 10 (I also have multiple versions of the desktop client) The other machine NEVER fails on export. Here's the difference: 4833 vs. 5075 A subtle update is the culprit. What smart Office person can tell me how to revert to the one that does work? If someone already has a ticket open, provide this information. Might help get a workaround or resolution.
Attachments Word that breaks ole in export from doors.JPG Word that does not break ole export from doors.JPG |
Re: OLE errors exporting to Word We have the same issues (with Windwos 10 and Office 365) and it seems that the Microsoft RichEdit Control maybe the problem! Our ticket (TS001241093) is also from 2018-12-14. We could luckily opened a case to Microsoft but ... you can guess ... still NO solution (either from Microsoft nor IBM). Trying to use the old RichEdit control may solve but is absolutely not supported and must not used in production environment!
|
Re: OLE errors exporting to Word Please consult with your IT personnel before you do anything. The following web page lists the Word 2013 update history: https://docs.microsoft.com/en-us/officeupdates/update-history-office-2013 I found officec2rclient.exe on this web page: https://www.kamind.com/2017/06/revert-earlier-build-office-software/ I googled "officec2rclient.exe switches" and found this web site: https://blogs.technet.microsoft.com/odsupport/2014/03/03/the-new-update-now-feature-for-office-2013-click-to-run-for-office365-and-its-associated-command-line-and-switches/ So it seems to me that you can revert to any version of Word 2013. BTW you stated " Here's the difference: 4833 vs. 5075 " I think you meant 4833 vs. 5085
|
Re: OLE errors exporting to Word Cliff Sadler BTI - Sat Dec 15 09:39:27 EST 2018 DOORS 9.6 does and it doesn't support Word 2013+ Here is the result of my investigation: I have 2 machines. One ALWAYS fails on the export of an ole from 9.6.1.7 thru 10 (I also have multiple versions of the desktop client) The other machine NEVER fails on export. Here's the difference: 4833 vs. 5075 A subtle update is the culprit. What smart Office person can tell me how to revert to the one that does work? If someone already has a ticket open, provide this information. Might help get a workaround or resolution.
Opps, I should have put this here:
Please consult with your IT personnel before you do anything. The following web page lists the Word 2013 update history: https://docs.microsoft.com/en-us/officeupdates/update-history-office-2013 I found officec2rclient.exe on this web page: https://www.kamind.com/2017/06/revert-earlier-build-office-software/ I googled "officec2rclient.exe switches" and found this web site: https://blogs.technet.microsoft.com/odsupport/2014/03/03/the-new-update-now-feature-for-office-2013-click-to-run-for-office365-and-its-associated-command-line-and-switches/ So it seems to me that you can revert to any version of Word 2013. BTW you stated " Here's the difference: 4833 vs. 5075 " I think you meant 4833 vs. 5085 |
Re: OLE errors exporting to Word MikeGehringer - Thu Dec 13 20:39:48 EST 2018 Hi JKeenan,
We've been seeing the same error and dealing with it (TS001377251)...and to date, no solution from IBM. Their claim is that Microsoft changed some things and therefore it is not a DOORS problem.
I have discuss your concern with the DOORS development team. Since this is not a DOORS issue, there is not much we can do in the DOORS side. An Administrator or user with sufficient access to the registry will be required to implement the workaround. Also the affected OLE's imported previously will need to be reinserted. We are also checking to see if there is any existing DXL script that can trigger the previously imported OLE to make them work. I will keep you post. Please do not hesitate to contact us if you have any questions or concerns. Thank you and have a good day!
We have escalated this to a Priority 1 issue. If you insert an OLE from Excel 2013 or Word 2013 (and probably higher versions as well), and insert the actual text or spreadsheet (not the icon), you get a blank box in the exported Word document. We have our own document generator scripts in DXL. IBM did provide a few things that might help...but it doesn't address the OTB functions of the application. Bottom line...DOORS 9.6+ does not support Office 2013+ Take care, Mike G If you double-click on the blank box in the exported document, can you see the OLE? I have had problems with OLEs from older (different) versions of Word pasted into DOORs, and then exported to Word 2016 Word version 2010 and earlier have compatibility issues with Word versions 2013 and later. see the following web page: https://support.office.com/en-us/article/compatibility-changes-between-versions-692289af-b760-4698-8326-14b2edcd6552 It is something I always had to check for until recently as our PC have continually been upgraded over the last ten years. |
Re: OLE errors exporting to Word I am getting closer to what is actually causing this. My testing points to not just the version of Word 2013 or 16 you are using, but more importantly, which version were you at when the OLE was first inserted into your DOORS object. This is why this problem is just now creeping up on us. Mine are only failing on "recent" OLE inserts, after some random update in the middle of 2018. In fact, I can reverse the issue if I use an older version of Word on my desktop when deleting the OLE object from DOORS, and then reinserting the exact same file. Now it exports without errors, RPE doesn't barf, and all is "well-ish". A work around for RPE generated docs with this problem is to set the metadata property in the launcher for OLE as a static image back to "True". Now you get the thumbnail of the OLE, not the document itself. OK for small tables and pictures. Not ok for multi-page embbed stuff (which is why we are embedding in the first place). I am circling in on what to do. Will share as things become clearer.
|
Re: OLE errors exporting to Word
Dear colleagues, Pending an official announcement, I can confirm that Microsoft's KB4512941 for Win10 1903 FIXES THIS ISSUE for all impacted applications, such as WordPad and DOORS. I can't recommend or advise to use this patch, but have a look, run a test and decide for yourself. There is no DOORS client patch (necessary) for this.
best regards, Sven.
NB: While I work for IBM DOORS product support, I'm posting here in a private capacity and my opinion may not necessarily be the same as IBM's. For official statements / support please open a support case with IBM. |
Re: OLE errors exporting to Word Sven Schubert - Wed Sep 04 06:29:13 EDT 2019
Dear colleagues, Pending an official announcement, I can confirm that Microsoft's KB4512941 for Win10 1903 FIXES THIS ISSUE for all impacted applications, such as WordPad and DOORS. I can't recommend or advise to use this patch, but have a look, run a test and decide for yourself. There is no DOORS client patch (necessary) for this.
best regards, Sven.
NB: While I work for IBM DOORS product support, I'm posting here in a private capacity and my opinion may not necessarily be the same as IBM's. For official statements / support please open a support case with IBM. Are you aware of any KB updates for other versions of Windows 10, like 1709 or 1809 Enterprise? |
Re: OLE errors exporting to Word Cliff Sadler BTI - Mon Sep 16 12:09:19 EDT 2019 Are you aware of any KB updates for other versions of Windows 10, like 1709 or 1809 Enterprise? Hi Cliff,
I can't speak for Microsoft, so please contact them directly for first hand reliable information. My current understanding is, that 1903 is fixed, 1809 has its patch pending, currently November 2019. I am not certain, if this would also include 1803. I have been told that 17xx and older are not planned to receive patches for this issue.
But again, please check this with Microsoft directly, as things might have changed since and my knowledge is outdated. Feel free to share here to keep us updated.
Kind regards, Sven.
PS: While I work for IBM DOORS product support, my statements here are my own opinion and don't reflect IBM's or its business partners. For official IBM statements, please be sure to contact IBM DOORS product support on ibm.com/support Thanks :-) |
Re: OLE errors exporting to Word Sven Schubert - Wed Oct 16 11:29:40 EDT 2019 Hi Cliff,
I can't speak for Microsoft, so please contact them directly for first hand reliable information. My current understanding is, that 1903 is fixed, 1809 has its patch pending, currently November 2019. I am not certain, if this would also include 1803. I have been told that 17xx and older are not planned to receive patches for this issue.
But again, please check this with Microsoft directly, as things might have changed since and my knowledge is outdated. Feel free to share here to keep us updated.
Kind regards, Sven.
PS: While I work for IBM DOORS product support, my statements here are my own opinion and don't reflect IBM's or its business partners. For official IBM statements, please be sure to contact IBM DOORS product support on ibm.com/support Thanks :-) How does one determine whether their version 1809 Windows system contains this patch? It is now late in November and we are still experiencing this problem. What update number for version 1809 has this fix? Thanks, Cynthia |
Re: OLE errors exporting to Word CSCifuentes - Wed Nov 27 12:00:18 EST 2019 How does one determine whether their version 1809 Windows system contains this patch? It is now late in November and we are still experiencing this problem. What update number for version 1809 has this fix? Thanks, Cynthia What is known as KB4512941 in 1903 has no equivalent in 18xx (yet), please contact Microsoft for any details on their plans. I have tested 1909 and it appears to be fixed too. |
Re: OLE errors exporting to Word Sven Schubert - Wed Nov 27 12:31:06 EST 2019 What is known as KB4512941 in 1903 has no equivalent in 18xx (yet), please contact Microsoft for any details on their plans. I have tested 1909 and it appears to be fixed too. Thank you! Unfortunately some of us are stuck on version 1809 until the "big powers that be" decide to update. But it helps to know the status. |
