So I’ve been having this new issue crop up all of a sudden.
I have developers (who have LOTS and LOTS of memory in their boxes) getting “Error Getting Clipboard Data!” messages when trying to print screen (or alt print screen) and pasting (they don’t get the error when they push PS, only when they actually try to paste it into Paint or email).
They do have dual monitors, and I have tried clearing the clipboard (via CCleaner) and disabling the additional monitor to no avail.
I did find something online about changing the paging executive being disabled (it is on my machine and I have no issues) and setting it to enable:
As my machine had loads of memory (4GB) some time in past I had disabled the paging executive to speed it up even more.
Turning it back on let me be able to paste full high resolution screens.
(HKLM\System\CurrentControlSet\Control\Session Manager\Memory Management value:DisablePagingExecutive set to '1')
I did this on one girls machine and am waiting to hear back how it worked.
I have seen this before but it is weird. It has to do with the monitors. Try lowering the resolution slightly.
I have narrowed it down to the Windows Heap in the past. Sometimes a restart will help, other times, messing with just the screen resolution would help. If the restart dosen’t help, do this. I’m assuming XP is being used.
Run Registry Editor (Regedt32.exe).
From the HKEY_LOCAL_MACHINE subtree, go to the following key: \System\CurrentControlSet\Control\Session Manager\SubSystems
Select the Windows value.
From the Edit menu, choose String.
Increase the SharedSection parameter.
For Windows NT:
SharedSection specifies the system and desktop heaps using the following format: SharedSection=xxxx,yyyy
Add “,256” or “,512” after the yyyy number.
For Windows 2000, Windows XP, and Windows Server 2003:
SharedSection uses the following format to specify the system and desktop heaps: SharedSection=xxxx,yyyy,zzz
Increase the zzz number to “256” or “512.”
Thanks for the above. I’ll try that if she reports issues again. It’s definitely weird.
I don’t know if any of you have used or heard of the PrintNow application, but what it basically does is you run it in the background and when you press Print Screen it automatically sends to the printer. We’ve been having issues with that as well lately (similar Clipboard error).
Okay…so the first thing I tried (other than basic PC cleanup thinking it was a process hogging memory, etc.) was changing the following key from 0 to 1 per some google searching I did:
So I just did what you suggested above 99FRC. We’ll see how that works out once the girl reboots. She already had 512 in for the zzz value, so I bumped it to 768 (I’m assuming these values correlate to memory values, she has 2GB in her box).
Also, this issue is happening to all of her group (like 6 developers). We have like 5 different developer groups, and this is the only one it’s happening too…so I’m thinking it’s something installed on those machines (since I had her email her team and she’s getting a bunch of stuff back about it happening for a LONG time - thanks for reporting it ID10T’s)…
If it is dept. wide, then narrow down what software they use that no other dept has. That is most likely the culprit.
I would create a Windows VM on a linux based system(basically using it as a sandbox), copy the end user system to the VM, and check to see if you get the error. Remove the suspected software and then run the VM again to see if it works. This way you aren’t bringing down any “working” systems.
That’s what we’re doing. Just not a VM. We have to rebuild a box anyway for some other stuff that another tech is working on, so while we’re building it we’re going to sandbox it.
Me and the guys just had a brain storming session and we’re going to try re-enabling their onboard video and using that.
We have to give them two external (PCI) video cards for their dual monitors because if they use the external one their machines bluescreen due to the software they have running on them. They are the only ones in the company who don’t use their onboard card (most people use onboard + 1 more). We’re going to test that right now.
I already tried just using 1 card and disabling dual monitor mode and that didn’t make a difference (saw some stuff about it in my google searches).