Is the machine on which you are having problems known to be particularly "locked down"?
It seems like it might be a permissions problem with your pseudo-terminal. After getting this error message, check the output of ls -l /dev/pts/0 (use the path from the error message). If it does not show you as the owner with read and write bits, then you may check it out with the machine's administrator.
I can imagine a system that would chown-away and chmod-down a pseudo-terminal after the initial login process gets going (sub-processes could inherit the already open file handles for std{in,out,err}), but that would be pretty draconian. What does mount | grep pts show? Maybe the mount options are setup incorrectly…
http://serverfault.com/questions/116775/sudo-as-different-user-and-running-screen/116830#116830 – Nakilon – 2013-12-11T15:20:50.333