Hello I am using Windows 10 DOORS 9.6. When I try to copy and paste an image (png, jpeg- any image) into an Object ( specifically in the Object Text) - the object appears- and then once i click away form the object the image disappears and its gone forever.
This issue does not happen on my Windows 7 machine.
I found that this was a known defect for Windows 8.1 http://www-01.ibm.com/support/docview.wss?uid=swg21903758 I was not able to follow the steps because i can not copy anything inside the doors Bin folder Please help
Thank you Alex_4_IBM - Wed May 11 09:43:56 EDT 2016 |
Re: Copy paste Image in to DOORS object Failed It seems that this problem has not been fixed yet (well, it has been opened only 1.5 years ago, so why should it?....) From https://www-304.ibm.com/support/entdocview.wss?uid=swg1PI29326 Local fixPaste the screenshot into Microsoft Paint first, and then copy it from there, and paste it into the DOORS module. In this case, the screenshot can be saved. Apart from that and the work around you already know I fear you have no chance. You could contact your Admins and ask them to distribute the DLL to the DOORS client directories of all users. |
Re: Copy paste Image in to DOORS object Failed Mike.Scharnow - Wed May 11 11:46:30 EDT 2016 It seems that this problem has not been fixed yet (well, it has been opened only 1.5 years ago, so why should it?....) From https://www-304.ibm.com/support/entdocview.wss?uid=swg1PI29326 Local fixPaste the screenshot into Microsoft Paint first, and then copy it from there, and paste it into the DOORS module. In this case, the screenshot can be saved. Apart from that and the work around you already know I fear you have no chance. You could contact your Admins and ask them to distribute the DLL to the DOORS client directories of all users. Hi Mike, I cant open the link you sent me could you send it again or provide pdf of what it said I will try the approach you mentioned. I included a link that this was a known issue for Windows 8.1,... and its not fixed by the time Windows 10 is released?
Thank you so much |
Re: Copy paste Image in to DOORS object Failed Mike.Scharnow - Wed May 11 11:46:30 EDT 2016 It seems that this problem has not been fixed yet (well, it has been opened only 1.5 years ago, so why should it?....) From https://www-304.ibm.com/support/entdocview.wss?uid=swg1PI29326 Local fixPaste the screenshot into Microsoft Paint first, and then copy it from there, and paste it into the DOORS module. In this case, the screenshot can be saved. Apart from that and the work around you already know I fear you have no chance. You could contact your Admins and ask them to distribute the DLL to the DOORS client directories of all users. I understand IBM is not doing any more development on Classic DOORS -- IBM is just putting minimum effort and money -- and going to stop all support in 2024 for DOORS classic. |
Re: Copy paste Image in to DOORS object Failed DOORSHAM - Wed May 11 12:03:44 EDT 2016 I understand IBM is not doing any more development on Classic DOORS -- IBM is just putting minimum effort and money -- and going to stop all support in 2024 for DOORS classic. 2014? Which year do you mean? Have you seen an official statement that IBM is really going to stop the support? I have never seen this up to now, besides the problem that IBM will probably never bring out version 9.7 as this would extend the support time for some more years. |
Re: Copy paste Image in to DOORS object Failed Alex_4_IBM - Wed May 11 11:55:05 EDT 2016 Hi Mike, I cant open the link you sent me could you send it again or provide pdf of what it said I will try the approach you mentioned. I included a link that this was a known issue for Windows 8.1,... and its not fixed by the time Windows 10 is released?
Thank you so much acheytan, the pdf is attached, but it does not say much more than what I quoted. Attachments IBM PI29326_ CANNOT INSERT SCREENSHOTS DIRECTLY INTO TEXT AT.pdf |
Re: Copy paste Image in to DOORS object Failed |
Re: Copy paste Image in to DOORS object Failed Mike.Scharnow - Wed May 11 11:46:30 EDT 2016 It seems that this problem has not been fixed yet (well, it has been opened only 1.5 years ago, so why should it?....) From https://www-304.ibm.com/support/entdocview.wss?uid=swg1PI29326 Local fixPaste the screenshot into Microsoft Paint first, and then copy it from there, and paste it into the DOORS module. In this case, the screenshot can be saved. Apart from that and the work around you already know I fear you have no chance. You could contact your Admins and ask them to distribute the DLL to the DOORS client directories of all users. I know this is a really old thread, but the bug still exists with Windows Server 2012 and DOORS 9.6.1.x. You say you can distribute the DLL to the DOORS client directory. Specifically, what DLL can be distributed to fix this? We have a Terminal Server implementation and it would be easy to do this for those users. Any information would be greatly appreciated. Thank you! |
Re: Copy paste Image in to DOORS object Failed Brad Jenks - Mon Jul 02 14:24:36 EDT 2018 I know this is a really old thread, but the bug still exists with Windows Server 2012 and DOORS 9.6.1.x. You say you can distribute the DLL to the DOORS client directory. Specifically, what DLL can be distributed to fix this? We have a Terminal Server implementation and it would be easy to do this for those users. Any information would be greatly appreciated. Thank you! Sorry, Brad, but I only quoted the content of the linked information. It seems that IBM has removed this document, I don't remember the content. Perhaps you can contact DOORS support and ask them about it. |
Re: Copy paste Image in to DOORS object Failed Hi there, we have the same issue here with Win10 and the picture-problem as described.
I checked the Door's bin-folder from Win10 against the Win7-bin-folder and there was no difference, so sadly no "missing" *.dll i could install.
Has anyone find out, which dll we have to copy into the Doors's bin-folder? I appreciate any help! Cheeers, Ben
|
Re: Copy paste Image in to DOORS object Failed Hi all,
I work for IBM DOORS Support, anything I post here, is my personal opinion and may not reflect IBM's official position. For an official reply from IBM, please create a support case with IBM DOORS product support.
The issue is connected to a change in how Windows handles clipboard data, specifically meta data describing the clipboard content, which the old interface didn't include in that form. The part of Windows, DOORS client is making heavy use of, is MSFTEDIT.DLL which is part of the operating system and NOT shipped with DOORS. Due to changes to that library, the above behaviour is now seen across all DOORS client versions running on Windows 10 (and 8.1, 2012 and 2016 for that matter). The previous technote was removed, because it provided advice, which while technically sound, left some "logistical" questions unanswered.
A make-shift workaround is to paste the image into MS Paint first and then copy it back to the clipboard from there, as this will strip off the meta data causing the issue. This was true at the time of writing, if Microsoft updates Paint to start using the new clipboard data format, the work around will stop working.
On a (slightly) different note, DOORS client will first look for any DLLs in it's own \bin folder and following that in the OS folders (ie. <WIN>\system32).
Feel free to draw your own conclusions on how these two bits of information may relate to the OP's problem. An official solution is being investigated. The IBM defekt number is PI29326 .
best regards, Sven.
PS: the next major release of DOORS 9 is in the works and due before the end of this decade! :-) PPS: please open a support case if you would like to discuss any details of this issue further with a member of IBM DOORS product support. |
Re: Copy paste Image in to DOORS object Failed Sven Schubert - Mon Jan 21 12:12:52 EST 2019 Hi all,
I work for IBM DOORS Support, anything I post here, is my personal opinion and may not reflect IBM's official position. For an official reply from IBM, please create a support case with IBM DOORS product support.
The issue is connected to a change in how Windows handles clipboard data, specifically meta data describing the clipboard content, which the old interface didn't include in that form. The part of Windows, DOORS client is making heavy use of, is MSFTEDIT.DLL which is part of the operating system and NOT shipped with DOORS. Due to changes to that library, the above behaviour is now seen across all DOORS client versions running on Windows 10 (and 8.1, 2012 and 2016 for that matter). The previous technote was removed, because it provided advice, which while technically sound, left some "logistical" questions unanswered.
A make-shift workaround is to paste the image into MS Paint first and then copy it back to the clipboard from there, as this will strip off the meta data causing the issue. This was true at the time of writing, if Microsoft updates Paint to start using the new clipboard data format, the work around will stop working.
On a (slightly) different note, DOORS client will first look for any DLLs in it's own \bin folder and following that in the OS folders (ie. <WIN>\system32).
Feel free to draw your own conclusions on how these two bits of information may relate to the OP's problem. An official solution is being investigated. The IBM defekt number is PI29326 .
best regards, Sven.
PS: the next major release of DOORS 9 is in the works and due before the end of this decade! :-) PPS: please open a support case if you would like to discuss any details of this issue further with a member of IBM DOORS product support. my opinion: We checked the second topic and for me it is working but this can not be really proposed as no-one knows the side-effects, or? We tried this out but only with a small number of key-users, but unfortunately I cannot provide this for thoussands of users! I understand that this topic is not a DOORS problem and Microsoft must solve this but my feeling is (according some very nice articles in the German computer magazine c't) that MS has some quality problems and a solution seems to be not quickly available. BTW: I'll hope that the next major release will be earlier than in this decade 😊 I talked to many (internal) users (about DNG) and it seems that there (DNG) are many features missing which denies a quick and smooth migration. Ok, I understand that DOORS classic has (very!) old architecture and (DOORS) Development is limited, but are really (much) more customers using DNG instead of DOORS classic? Best regards, Dirk. |
Re: Copy paste Image in to DOORS object Failed Dirk0 - Mon Feb 04 08:42:47 EST 2019 my opinion: We checked the second topic and for me it is working but this can not be really proposed as no-one knows the side-effects, or? We tried this out but only with a small number of key-users, but unfortunately I cannot provide this for thoussands of users! I understand that this topic is not a DOORS problem and Microsoft must solve this but my feeling is (according some very nice articles in the German computer magazine c't) that MS has some quality problems and a solution seems to be not quickly available. BTW: I'll hope that the next major release will be earlier than in this decade 😊 I talked to many (internal) users (about DNG) and it seems that there (DNG) are many features missing which denies a quick and smooth migration. Ok, I understand that DOORS classic has (very!) old architecture and (DOORS) Development is limited, but are really (much) more customers using DNG instead of DOORS classic? Best regards, Dirk. Hi Dirk, in short and simple terms: this defect has currently no solution and the only official work around is to strip the clipboard contents of its problematic meta data via MS Paint.
Therefore, if I was in your position, I would not contemplate rolling out topic 2 to thousands of users. Please be sure to open a support case with IBM DOORS Support so we can track this and communicate on an official level. We can address your specific concerns there. We can also discuss the time frame for the next DOORS 9 iteration. And your perceptions about DNG and DOORS.
I'd like to encourage anyone to engage with IBM DOORS product support and IBM DNG product support actively in regards to any concerns and suggestions for improvements they might have.
This: IBM Support Portal is a good starting point to contact us.
Because I'm limited to personal opinions here, I'd rather not go further into all of the above topics here. As soon as an official solution is available, I'll update you all here. Before the end of the decade ;-) Thank you for your understanding.
Kind regards, Sven. |
Re: Copy paste Image in to DOORS object Failed Shall we assume this is also the issue with being able to export OLE objects that have been imported into DOORS using Windows 10 and newer versions of Word? All "workarounds" proposed by support have been ineffective, including the Registry settings tech note. I have found an unsupported solution, which is to export using an older version of DOORS (like early 9.6 and 9.5) At least for the OLEs, it appears to me that changes to both DOORS and Office and Windows have contributed to the failure of exporting from DOORS to Word. Case TS001715675 - Closed |
Re: Copy paste Image in to DOORS object Failed Sven Schubert - Mon Jan 21 12:12:52 EST 2019 Hi all,
I work for IBM DOORS Support, anything I post here, is my personal opinion and may not reflect IBM's official position. For an official reply from IBM, please create a support case with IBM DOORS product support.
The issue is connected to a change in how Windows handles clipboard data, specifically meta data describing the clipboard content, which the old interface didn't include in that form. The part of Windows, DOORS client is making heavy use of, is MSFTEDIT.DLL which is part of the operating system and NOT shipped with DOORS. Due to changes to that library, the above behaviour is now seen across all DOORS client versions running on Windows 10 (and 8.1, 2012 and 2016 for that matter). The previous technote was removed, because it provided advice, which while technically sound, left some "logistical" questions unanswered.
A make-shift workaround is to paste the image into MS Paint first and then copy it back to the clipboard from there, as this will strip off the meta data causing the issue. This was true at the time of writing, if Microsoft updates Paint to start using the new clipboard data format, the work around will stop working.
On a (slightly) different note, DOORS client will first look for any DLLs in it's own \bin folder and following that in the OS folders (ie. <WIN>\system32).
Feel free to draw your own conclusions on how these two bits of information may relate to the OP's problem. An official solution is being investigated. The IBM defekt number is PI29326 .
best regards, Sven.
PS: the next major release of DOORS 9 is in the works and due before the end of this decade! :-) PPS: please open a support case if you would like to discuss any details of this issue further with a member of IBM DOORS product support. Hi all, After I read all posts and especially the post of Sven Schubert I try following action and it worked: Because : "DOORS client will first look for any DLLs in it's own \bin folder and following that in the OS folders (ie. <WIN>\system32)" I search on an old server where the copy/paste of OLE worked with DOORS 9.6.1.3 and look after MSFTEDIT.DLL from <WIN>\system32 Copy this MSFTEDIT.DLL in DOORS client own \bin folder to not change Windows and now the issue was solved. It's working. Please find the MSFTEDIT.dll from 21.11.2010 Size 781KB in attachement
Best regards Adriana Papp |
Re: Copy paste Image in to DOORS object Failed adisu - Wed Jul 31 09:08:34 EDT 2019 Hi all, After I read all posts and especially the post of Sven Schubert I try following action and it worked: Because : "DOORS client will first look for any DLLs in it's own \bin folder and following that in the OS folders (ie. <WIN>\system32)" I search on an old server where the copy/paste of OLE worked with DOORS 9.6.1.3 and look after MSFTEDIT.DLL from <WIN>\system32 Copy this MSFTEDIT.DLL in DOORS client own \bin folder to not change Windows and now the issue was solved. It's working. Please find the MSFTEDIT.dll from 21.11.2010 Size 781KB in attachement
Best regards Adriana Papp Disclaimer: I work for IBM DOORS Support. In this forum I am posting in a personal capacity and all views are my own and not necessarily congruent to those of IBM. If you require official support / statements, please open a support case with IBM.
Dear Adriana,
the DLL is the intellectual property of its vendor and MUST NOT be copied between separate versions of their product or shared. Please remove the file.
Everyone else, this is (at the very best) a temporary test and a proof that you're facing the RichEdit Control issues in Windows >8.1/2008 which Microsoft is currently working on. Do not use this in production! Do not use this. Please contact Microsoft to obtain any details. IBM advises against using non-native DLLs in production, you need to comply with your local and international laws applicable and if you open support cases where you have replaced this DLL, you will be asked to return your environment / OS to its proper state before you will receive any support.
You can reproduce most if not all of the RichEdit Control issues in Win10 with WordPad instead of DOORS. Microsoft is aware of this and if you describe the issue in sufficient detail, their support will be able to make the connection to their on-going investigation into a patch. Microsoft should be able to give you a time frame for when this issue is going to be fixed in Windows.
Regarding the point that this works in previous versions of DOORS (9.5/9.6) -- please note that Windows 10 support was introduced in 9.6.1.6 -- using an older DOORS on Win10 is not a supported configuration.
Kind regards, Sven.
|
Re: Copy paste Image in to DOORS object Failed Sven Schubert - Wed Jul 31 09:35:22 EDT 2019 Disclaimer: I work for IBM DOORS Support. In this forum I am posting in a personal capacity and all views are my own and not necessarily congruent to those of IBM. If you require official support / statements, please open a support case with IBM.
Dear Adriana,
the DLL is the intellectual property of its vendor and MUST NOT be copied between separate versions of their product or shared. Please remove the file.
Everyone else, this is (at the very best) a temporary test and a proof that you're facing the RichEdit Control issues in Windows >8.1/2008 which Microsoft is currently working on. Do not use this in production! Do not use this. Please contact Microsoft to obtain any details. IBM advises against using non-native DLLs in production, you need to comply with your local and international laws applicable and if you open support cases where you have replaced this DLL, you will be asked to return your environment / OS to its proper state before you will receive any support.
You can reproduce most if not all of the RichEdit Control issues in Win10 with WordPad instead of DOORS. Microsoft is aware of this and if you describe the issue in sufficient detail, their support will be able to make the connection to their on-going investigation into a patch. Microsoft should be able to give you a time frame for when this issue is going to be fixed in Windows.
Regarding the point that this works in previous versions of DOORS (9.5/9.6) -- please note that Windows 10 support was introduced in 9.6.1.6 -- using an older DOORS on Win10 is not a supported configuration.
Kind regards, Sven.
Hello all Remove the library. We will contact Microsoft in order to fix this issue. Best regards Adriana |