SelectObject to CompatibleDC failed: The operation
completed successfully.
James Weatherall
jnw "at" realvnc.com
Fri Dec 2 18:51:02 2005
Benjamin,
Are the DOS applications running full-screen or windowed?
Regards,
Wez @ RealVNC Ltd.
> -----Original Message-----
> From: Benjamin Jitima [mailto:ben "at" foodfairmk.com]
> Sent: 02 December 2005 18:40
> To: 'James Weatherall'; vnc-list "at" realvnc.com
> Subject: RE: SelectObject to CompatibleDC failed: The
> operation completed successfully.
>
> We have the power saving turned off and the Console is
> automatically logged
> in at session zero when the computer boots (through TweakUI).
> I checked and
> the RDP sessions that we log into begin at session 1. As I was double
> checking that just now to make sure I was telling you right,
> I noticed that
> our app (DOS based) was showing up on the taskbar three times
> as minimized.
> As soon as I click on one of them, the VNC session freezes
> and I closed it
> and when I tried to go back in, it brought back that error.
> I seem to be
> able to bring it back by doing the following:
>
> mstsc /v:ser1106 /console
> (this takes over the console through RDP, which locks out the current
> console user; something we are trying to avoid by using VNC)
>
> Closing all of the open applications in RDP, and then logging
> off (which
> doesn't seem to work everytime) or doing the tscon 0
> /dest:console which
> seems to work more often than just logging off.
>
> When this happened just now on the server, I realized that
> when I had logged
> in to the Windows XP computer earlier I seemed to have no
> problems until I
> clicked on the DOS application at which point VNC froze there
> as well. Do
> you know of any issues in which 32-bit DOS applications cause
> some kind of
> conflict with VNC? We run the same applications (in house
> point of sale
> management written in Foxpro 2.5) on all of our servers throughout the
> company and we have never seen it causing a problem.
>
> Thanks for the help,
>
> Ben
>
> -----Original Message-----
> From: James Weatherall [mailto:jnw "at" realvnc.com]
> Sent: Friday, December 02, 2005 12:13 PM
> To: 'Benjamin Jitima'; vnc-list "at" realvnc.com
> Subject: RE: SelectObject to CompatibleDC failed: The
> operation completed
> successfully.
>
> Benjamin,
>
> The error you're describing is sometimes caused by Remote
> Desktop having
> been used on session zero of the target computer, but may
> also be caused by
> the graphics card having gone into a power-saving state. Is
> it possible
> that this might be the problem that you're seeing?
>
> Regards,
>
> Wez @ RealVNC Ltd.
>
>
> > -----Original Message-----
> > From: vnc-list-admin "at" realvnc.com
> > [mailto:vnc-list-admin "at" realvnc.com] On Behalf Of Benjamin Jitima
> > Sent: 02 December 2005 15:09
> > To: vnc-list "at" realvnc.com
> > Subject: SelectObject to CompatibleDC failed: The operation
> > completed successfully.
> >
> > Hello,
> >
> >
> >
> > I've seen this several times in the archives, but never have
> > I seen a real
> > solution. There was mention of a fix in version 4.1, but we
> > are running
> > 4.1.1 and we are getting this problem, so they must not have
> > implemented a
> > solution. We are running RDP from time to time, but I don't
> > understand why
> > this is still causing a problem because we had it running
> > fine in a test
> > environment before deploying it. It is a Windows 2003 server
> > with very
> > little installed. We also have a Windows XP computer that we
> > have at the
> > same site that I just tried to connect to and got the same
> > error message.
> > We are not running RDP on that computer at all and never
> > have. I saw a
> > couple of suggestions for a work around such as tscon 0
> > /dest:console but
> > this did not work because the RDP session was not 0 and the
> > console was
> > already logged in to session 0. I also saw something talking about
> > mstsc.exe /console and I tried working with that but it also
> > did not work.
> >
> >
> >
> > We are connecting through a point to point VPN using Cisco
> > PIX firewalls.
> > Everything from one internal network to another is explicitly
> > permitted, and
> > the PIX config is basically identical to all of the other
> > sites, so I don't
> > think that it would be causing any problems.
> >
> >
> >
> > Like I said, we have had this computer in a test environment
> > where we ran
> > both VNC and RDP for a week and a half without any problems
> > whatsoever, and
> > then when we deployed it we started having issues. We also
> > have several
> > other sites where we run RDP and VNC together where we have
> > not had any
> > problems. In fact, two of the sites have identical hardware
> > and install
> > images. Does anyone have any ideas as to what else could
> possibly be
> > causing this?
> >
> >
> >
> > I appreciate any suggestions,
> >
> >
> >
> > _____
> >
> > Benjamin Jitima
> >
> > Forth Foods
> >
> > ben "at" foodfairmk.com
> >
> > (304) 617-5806
> > _______________________________________________
> > VNC-List mailing list
> > VNC-List "at" realvnc.com
> > To remove yourself from the list visit:
> > http://www.realvnc.com/mailman/listinfo/vnc-list