Dropframe Posted October 16, 2012 Report Share Posted October 16, 2012 I have been getting an error message on a new DELL laptop that I use for production CPU. As soon as I do CTRL+C I get the following message. FAiled to get data from the clipboard (error -2147221940) openClipboard Failed)... I have been looking in the forum but now topics on this yet... Any ideas ! Seb 0 Quote Link to comment Share on other sites More sharing options...
Mike Fahl Posted October 17, 2012 Report Share Posted October 17, 2012 This sometimes happen if you have multiple instances of the production software open simultaneously. You can copy/paste without opening multiple instances by loading another show between Copy and Paste. Mike 0 Quote Link to comment Share on other sites More sharing options...
Dropframe Posted October 17, 2012 Author Report Share Posted October 17, 2012 Ok so if I'm running a single show, would it be a RAM memory issue ? I just ran some tests after restarting to make sure that only one show was open end and it still is doing it. Maybe it as to do with another program messing with WO. I will keep checking ! Is there a list of the error codes that would help me narrow it down ? 0 Quote Link to comment Share on other sites More sharing options...
Dropframe Posted October 17, 2012 Author Report Share Posted October 17, 2012 Note that this as also happens when copying two ctrl cues. So it was not while copying and pasting from two different shows. 0 Quote Link to comment Share on other sites More sharing options...
Mike Fahl Posted October 18, 2012 Report Share Posted October 18, 2012 Yes, I would then suspect something else in your computer. Have you tyried WATCHOUT production software on anothe computer, to see if it solves this problem? I have not seen or heard of it except occasionally in the case I mention above. Mike 0 Quote Link to comment Share on other sites More sharing options...
Member keitht Posted November 29, 2012 Member Report Share Posted November 29, 2012 Not that it ever bothered me much, but I have seen this behavior many times. So, now you know it is not just you. 0 Quote Link to comment Share on other sites More sharing options...
Dropframe Posted December 13, 2012 Author Report Share Posted December 13, 2012 So to get back on this problem. We finally re-installed Windows and everything else to get it to point 0. Now the problem is fixed ! Seb 0 Quote Link to comment Share on other sites More sharing options...
Mike Fahl Posted December 20, 2012 Report Share Posted December 20, 2012 Now the problem is fixed! So it sounds like the problem was caused by some other software/configuration on your machine, which was resolved by re-installing the OS. ANy idea what that might have been, for the benefit of other users, should they run into this problem? Mike 0 Quote Link to comment Share on other sites More sharing options...
Neil Stratton Posted December 23, 2012 Report Share Posted December 23, 2012 I read this post and the very next day I started getting the same messages. I am still on 5.2. and have only seen it in 64 bit environments. I have seen it in a number of my show set ups so it is not restricted to a particular show file. It hasn't caused me any problems but I am left wondering what it is actually trying to tell me. I haven't changed my system set up for over 6 months so quite sure I haven't caused this through a driver/update etc. I will report back if I find a reason/solution. 0 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.