EFT is a very old program, code has not been updated in years. So the best way is to run the program in some kind of compatibility mode... you might try windows XP or even windows 2000.

PLUS

Create a RDP just to run the EFT, there is a variety of compatibility settings as well.

If you have an IT guy he will know what to do. I have a couple of shims that an IT  guy can apply.

Thanks for your reply.

Actually, an EFT 2015 upgrade has been released and plus we have EFT 2014 currently running on our virtual server with RDP access working well. So I'm mostly curious as to what has changed to make it break in the newest version. When we spoke with Sage they stated it was a known issue and they were looking into it. I was just hoping someone on here may have a fix. Thanks.

oh OK.... as far as i know the versions are exactly the same... i installed on a desk top machine and a laptop and its working

yes, I'm sure it works locally. But by questions is regarding installing on a virtual machine with RDP access

Just ran into this with a workstation - no answer for RDP yet.

Just interesting that the user logged in remote and got the error went and logged in locally to the same session worked fine and when they went back to remote with the EFT running - they could function inside without issue.

Unfortunately the hyper-v uses a variation of rdp calls to the virtual computer for the console.

Sage needs to fix what ever happens in the startup sequence that causes the program to bomb out.  and they will have to change it by the end of the year when anyone using payroll and RDP is going to get hit when they install for Jan 2015 tax tables.  

So for now - Best case is physical box with an non RDP client - at least to start the EFT program.

Tomorrow going to try RDP with as many functions shut off basically bare bones and see if that helps.

found a work around for this issue via RDP

The issue - if it is the same on as VB6 problems is when icons loaded into the program while being compiled only have HiRes images they are missing low res/colour images.

When you start remote desktop it defaults to 16 bit colour, so when the program loads and looks for low res icons there are not so it gives up with the  Runtime error: 50003.

A solution is to set the RDP client to use 32 bit color under the display tab. this will work when accessing a windows 7 workstation right away. For a 2008 server or terminal services the server must also be set to accept 32 bit video connections otherwize it will force 16 bit connections (used to limit memory and cpu load for sessions)

here is one web site that shows the spots to set this up (it goes a little overboard as it also talks about configuring aero for RDP) there may be more settings for a true Terminal server setup but this will get you started.  

http://www.win2008r2workstation.com/enable-remote-desktop-with-aero/

edit