tag:blogger.com,1999:blog-13777170.post3325526867078468308..comments2024-03-11T02:35:50.848-05:00Comments on grand stream dreams: In the trenches…Unknownnoreply@blogger.comBlogger4125tag:blogger.com,1999:blog-13777170.post-55593807193824248262010-07-17T16:11:13.361-05:002010-07-17T16:11:13.361-05:00@ Xavier -- great tip with the sfc /scannow I'...@ Xavier -- great tip with the sfc /scannow I'll have to give it a shot.<br /><br />To be honest, I got tired of working on it between services (troubleshooting time is a bit limited) so I just installed TightVNC (the <a href="http://www.tightvnc.com/download.php" rel="nofollow">latest release for Windows – TightVNC 2.0.2</a> ) on all the systems and am using that for now for the remote control work.<br /><br />In my mind it's a "patchy" solution as it still doesn't resolve or fix the root cause for the errors/behavior, but we are smoothly functional now in the meantime.<br /><br />I'll update more once I do get the time to hammer at them for an extended period of time.<br /><br />Cheers!<br /><br />--Claus V.Claushttps://www.blogger.com/profile/11692921474310162470noreply@blogger.comtag:blogger.com,1999:blog-13777170.post-83955715047307827112010-07-14T12:58:35.461-05:002010-07-14T12:58:35.461-05:00Any luck?
Just tried this and so far no issues.
...Any luck?<br /><br />Just tried this and so far no issues.<br /><br />Run command as Administrator in cmd window: sfc /scannow<br /><br />Also, under RDC window I unchecked the Printers and Clipboard under "Local Resources" Tab. Selected "More" and unchecked SmartCard as well.<br /><br />No clue which of my steps resolved the issue.<br /><br />Good luck!Unknownhttps://www.blogger.com/profile/16143913368453227281noreply@blogger.comtag:blogger.com,1999:blog-13777170.post-13331255042365982422010-05-03T20:05:15.599-05:002010-05-03T20:05:15.599-05:00@ Bozo - Thanks for the tip. I'm planning on ...@ Bozo - Thanks for the tip. I'm planning on tossing Process Monitor on it next go round to see if that provides any additional clues on missing files. I'll probably do a trace on both systems and check for failures at both ends.<br /><br />Sunday I did notice that I had not "enabled" the "Use all my monitors for the remote session" option in the RDC settings.<br /><br />I didn't feel I needed to since the remote system was only a single-monitor configuration. Right?<br /><br />However, with the desktop compositing errors I wondered if that might be causing some issues anyway as my controlling system has four monitors on it.<br /><br />So I enabled it and though the problem didn't vanish, entirely, I seemed to get a stable connection more quickly now. I only got the error once this time.<br /><br />All the themes in play are default to the OEM Dell systems. And while the hardware is just a bit different, they are both the same basic models and both are running the same x64 Win 7 OS's.<br /><br />Can't wait to figure this one out!<br /><br />Cheers.<br /><br />Claus V.Claushttps://www.blogger.com/profile/11692921474310162470noreply@blogger.comtag:blogger.com,1999:blog-13777170.post-8618772002890772062010-05-03T11:28:22.401-05:002010-05-03T11:28:22.401-05:00"Pure virtual method" sounds like you..."Pure virtual method" sounds like you're missing a DLL that contains the missing method. Maybe there's a procedural element to the desktop theme that is missing or inaccessible to the RDC user. The desktop display procs could be pointing to function that is supposed to be provided by the theme itself.Bozohttps://www.blogger.com/profile/05813653304141127470noreply@blogger.com