'Element not found' error after upgrade

  • Thread starter Thread starter gazguru
  • Start date Start date
G

gazguru

Two of my clients upgraded their client apps when prompted by the auto update reminder.
Now they cannot use 2X. The application pops up 'Element not found' when the try to run the published app.
I have tried un-installing the Client, removing any folders and registry entries and then re-installing. I have not been able to overcome the fault.
Any help would be appreciated.

As a side note, I have 20+ users that are working properly without upgrading to the latest version.
 
It seams that you need to upgrade your msrdp client to version 6.

What is the OS version you are having issues with?

Nixu
 
All clients using RDP 6

Hi nixu, thanks for reply.
All my clients are up to date with RDP 6 installed.
 
Ok then..

Go on those 2 machines where the 2x client is not working. Open the client -> help ->Control version.

What is control version it is displaying?

Nixu
 
client -> help ->Control version

Nixu, I tried what you said.
I cannot get to one as the user has turned his machine of and it is 600klms away.
The other one does the same thing as before. When I select Control Version a dialog pops up saying 'Element not found.' I can't do anymore with it today as this uaer has taken his laptop and gone home.
 
What is the OS where you are experiencing this problem??
Is there some other RDP software installed on the same machine?

Try the following...
Reinstall MSRDP 6
From a command prompt execute "regsvr32 msrdp.ocx"

Try to lunch a published app.

If you still cannot connect, try to log on the machine with a different user.

Nixu
 
So i was getting this error also on one of my computers so i decided well i'll just upgrade everything to the version 6 beta and see if that would resolve the issue.

Now when i try to launch an application or select Control Version from the Help menu it just simply does nothing. No errors or prompts.

Anyone have any ideas?
 
And fixed, reregistered the msrdp.ocx but that had no effect. Reinstalled ms rdp 6 and that seems to have fixed it.
 
You must log in or register to reply here.
Back
Top